Re: RAC backups

[Alexander Verkooijen]

I spent the last two months installing TSM
on a two node RAC cluster (Linux, not AIX).
It was a very unpleasant experience.
There is very little documentation (at least
that I could find). I can back up now and a few
weeks ago I had to restore a corrupt datafile.
For some reason it took RMAN hours and I had to
copy archived logs manually from one node to
another node but in the end the datafile was
restored.
There is one advise I can give you: Make sure
your archived logs (if you're running your
database in archive log mode) are on some
kind of shared storage like ASM so all the
nodes can access them.

Regards,

Alexander

On Monday 23 April 2007 16:18, Thomas, Matthew wrote:
> Guys,
>
>
>
> Does anyone have any guidance on using TSM scheduled TDP backups with
> Oracle RAC multi-node grids?
>
> We're due to implement a 4-way RAC cluster (on AIX) and ultimately we'll
> need the database(s) to be backed up and restored via any of the 4 nodes in
> the grid.
>
> Any advice would be appreciated.
>
>
>
> TIA
>
> Matt Thomas
>
>
>
> This e-mail is only for the above addressees.  It may contain confidential
> or privileged information. If you are not an addressee you must not copy,
> distribute, disclose or use any of the information in it or any
> attachments.  If you have received it in error please notify the sender and
> delete it immediately.
>
>
> Lloyds TSB Bank plc.  Registered office: 25 Gresham Street, London EC2V
> 7HN.  Registered in England and Wales, number 2065.  Telephone: 020 7626
> 1500.
> Lloyds TSB Scotland plc.  Registered office: Henry Duncan House, 120 George
> Street, Edinburgh EH2 4LH.  Registered in Scotland, number 95237.
> Telephone: 0131 225 4555. Cheltenham & Gloucester plc.  Registered office:
> Barnett Way, Gloucester GL4 3RL.  Registered in England and Wales, number
> 2299428.  Telephone: 01452 372372.
>
>
> Lloyds TSB Bank plc, Lloyds TSB Scotland plc and Cheltenham & Gloucester
> plc are authorised and regulated by the Financial Services Authority and
> are signatories to the Banking Codes.
>
>
> Lloyds TSB Bank plc and Lloyds TSB Scotland plc represent only the Scottish
> Widows and Lloyds TSB Marketing Group for life assurance, pensions and
> investment business. Cheltenham & Gloucester plc acts as an introducer only
> for life assurance, pensions and investment business.
>
>
> Lloyds TSB Group plc.  Registered office: Henry Duncan House, 120 George
> Street, Edinburgh EH2 4LH.  Registered in Scotland, number 95000.
> Telephone: 0131 225 4555.

Re: partitioning 3583

[Prather, Wanda]

Been there done that, all though it was quite a while ago.
 
You are correct that 
 
- There is nothing in TSM code that will prevent TSM from trying to mount an 
LTO3 cartridge in an LTO1 drive, if they are defined to the same TSM library.  
If you dig around in the books and web site you can find that documented, but I 
agree it isn't intuitively obvious.  
 
- The partitioning of the 3583 is limited to the  FIXED configurations 
described in the 3583 Setup & Operator Guide topic "multipath library 
configurations".  One place in the book sorta implies some flexibility, but I 
checked with our regional tape specialist, and the configurations shown in the 
book are the only ones available.  (There are also restrictions on how the 
slots are divided up per logical library - if you have the 12-slot I/O door, 
the 6 slots below the door ALWAYS go with lib A, for example.)  
 
-Looks to me like you are correct that you will have 2 LTO3 drives in lib A and 
the other 4 LTO1 drives in lib B, which means you will have to move things 
around.  
 
-In addition to creating the partitions, you must assign a CONTROL PATH to the 
new logical library.  (Every logical library must have at least 1 drive 
assigned as the control path.)  See in the book "add control paths".  Then when 
you run cfgmgr, you should see a new /dev/smcx device.
 
-Everything else you have looks right.  Partition the library, reboot it, run 
config mgr.  Make sure the devices show up in AIX like you expect.  
 
Then for TSM you just create a new library, drives,  & paths in TSM on the new 
/dev/smcx device, check the tapes in to that library.  Update the paths/drives 
in the old library defined on /dev/smc0.  TSM thinks it's 2 real, physically 
separate libraries.
 
Things to check on: 
 
--Early releases of the 3583 didn't have the "multipath" feature, which means 
you can't partition.  If you don't find the right virtual buttons on your front 
panel, you probably need to upgrade the microcode, although I'm pretty sure you 
have to be reasonably current since you are running LTO3's.  (I'd recommend 
getting up to date on the microcode, anyway.)
 
-Make sure you are using a reasonably up-to-date version of the Setup & 
Operator guide.
 
Once you get past the frustration of having to use the fixed partitions you 
get, it works like a champ.
 
W
 
 
 
 
 



From: ADSM: Dist Stor Manager on behalf of Ray
Sent: Mon 4/23/2007 3:18 PM
To: ADSM-L@VM.MARIST.EDU
Subject: partitioning 3583



All,

Through a little confusion and lack of research, we have a 3583 library
where we have mixed LTO1 and LTO3 media.  Apparently we read that TSM and
the 3583 supports "mixed-media with LTO" and didn't read the fine print,
thinking it would just work.  The drives and cartridges are in a single
device class (format=drive) all in the same storage pool.  Surprisingly this
has been working fine for a few months.  I have 4 LTO-1 drives in slots 1-4,
and 2 LTO-3 drives in slots 5-6.

After a backup failure, i noticed TSM trying to mount an LTO3 cartridge in
an LTO1 drive.  Further research showed that our setup should not work at
all haha.  I've determined the best course of action now is to partition
into 2 logical libraries.  One library for LTO-1 media, one for LTO-3
media.  Having never done this before, i have a few questions.

1.  Are the 3583 partitioning configurations "fixed"?  I don't see a way to
assign a particular drive to a particular partition.  If it is a fixed
config, then according to the operator guide, when you define 2 logical
libaries, drive slots 1 and 2 are in library A, and slots 3-6 are in library
B.  If this is true, i'll have to physically move the LTO-3 drives to slots
1 and 2.   Am i following this correctly?

2.  Library is connected to a p5-570 running AIX 5.3.  Right now the library
is /dev/smc0.  After partitioning, will i get a smc0 and an smc1?  Should i
run cfgmgr after partitioning?

3.  What is the best procedure to do the partition?  I'm thinking i need to
checkout all the cartridges, then turn off the library.  Move the tape
drives, then partition the library.  Then deal with the AIX devices changing
(rmdev/cfgmgr).  Then redefine drives/paths, define new device classes and
checkin the cartridges to the right logical library.  Am i missing anything?

We're running TSM 5.3.4.0.  Thanks for any info.  I appreciate it.

ray
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ray DeJean   http://www.r-a-y.org 
 
Systems EngineerSoutheastern Louisiana University
IBM Certified Specialist  AIX Administration, AIX Support
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: Select Statement

[Thomas Denier]

-Brenda Collins wrote: -

>Does anyone know of a way to determine what files existed under a
>specific directory path for a node as of a certain date and time?

Your subject line suggests that you are looking for a select command,
but I think it will be easier to get the information using one of the
client interfaces. If need be you can use the '-virtualnodename'
option to run the interface on a system other than the one the files
came from.

If you use the command line client, you can execute a 'query backup'
command with '-subdir=y' and appropriate values for the '-pitdate'
and '-pittime' options.

If you use the GUI client, request a restore, click the 'Point In
Time' buton, and specify the appropriate date and time. You can then
drill down into the file system and directory structure to see what
files are listed. When you are done you can exit without going through
with the restore.

It should be noted that any method of using the TSM database to
determine past file populations has inherent limitations. TSM only
examines file populations when backups are run. It cannot tell you
exactly what happened between backups. For example, a file that came
and went between consectutive backups would be completely invisible
to TSM. Depending on how far back in time you want to look, TSM
expiration processing may have erased information about some of thefiles
present at the time of interest.

Select Statement

[Collins, Brenda]

Hi!

Does anyone know of a way to determine what files existed under a
specific directory path for a node as of a certain date and time?

Thank you in advance for any help you can provide on this!

Brenda




___
CONFIDENTIALITY AND PRIVACY NOTICE
Information transmitted by this email is proprietary to Medtronic and is 
intended for use only by the individual or entity to which it is addressed, and 
may contain information that is private, privileged, confidential or exempt 
from disclosure under applicable law. If you are not the intended recipient or 
it appears that this mail has been forwarded to you without proper authority, 
you are notified that any use or dissemination of this information in any 
manner is strictly prohibited. In such cases, please delete this mail from your 
records.
http://emaildisclaimer.medtronic.com

Re: Backup procedures for PICK/UNIDATA

[Kelly Lipp]

The environment under scrutiny here is Unidata on Solaris.  We, too,
want to do the snapshot thing to minimize the downtime.

Seems like this is pretty darn straightforward? 


Kelly J. Lipp
VP Manufacturing & CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Rick Saylor
Sent: Monday, April 23, 2007 12:39 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Backup procedures for PICK/UNIDATA

Kelly,

Our Unidata database is backed up with TSM and as you've suggested the
dbpause and dbresume are used to ensure a good backup. A TSM prebackup
script pauses the database, takes a snapshot of the database and then
resumes the database access. TSM then backs up the now static copy of
the database. This way the database is only paused for a few seconds.
Once the backup is complete a postbackup scripts removes the snapshot.
You didn't say what your environment is but ours is AIX 5.2 with the
database on a mirrored JFS2 filesystem.

This has worked well for us. Each day the backup is restored to a remote
site as well as our test system. We've never had any problems.
Let me know if you have any other questions.

Thanks,
Rick Saylor

Austin Community College

At 11:21 AM 4/23/2007, you wrote:
>Folks,
>
>Any of you esteemed folks using TSM to backup/restore UNIDATA or other 
>implementations of a PICK database?  Specifically, are you using the 
>dbpause and dbresume commands?
>
>Easy, hard, impossible?
>
>Thoughts as always much appreciated.
>
>Thanks,
>
>Kelly J. Lipp
>VP Manufacturing & CTO
>STORServer, Inc.
>485-B Elkton Drive
>Colorado Springs, CO 80907
>719-266-8777
>[EMAIL PROTECTED]
>




Rick Saylor  Austin Community College   Voice:
(512)223-1182
Director of System Services  9101 Tuscany Way   Fax:
(512)223-1211
Information Technology   Austin, Texas  78754

partitioning 3583

[Ray]

All,

Through a little confusion and lack of research, we have a 3583 library
where we have mixed LTO1 and LTO3 media.  Apparently we read that TSM and
the 3583 supports "mixed-media with LTO" and didn't read the fine print,
thinking it would just work.  The drives and cartridges are in a single
device class (format=drive) all in the same storage pool.  Surprisingly this
has been working fine for a few months.  I have 4 LTO-1 drives in slots 1-4,
and 2 LTO-3 drives in slots 5-6.

After a backup failure, i noticed TSM trying to mount an LTO3 cartridge in
an LTO1 drive.  Further research showed that our setup should not work at
all haha.  I've determined the best course of action now is to partition
into 2 logical libraries.  One library for LTO-1 media, one for LTO-3
media.  Having never done this before, i have a few questions.

1.  Are the 3583 partitioning configurations "fixed"?  I don't see a way to
assign a particular drive to a particular partition.  If it is a fixed
config, then according to the operator guide, when you define 2 logical
libaries, drive slots 1 and 2 are in library A, and slots 3-6 are in library
B.  If this is true, i'll have to physically move the LTO-3 drives to slots
1 and 2.   Am i following this correctly?

2.  Library is connected to a p5-570 running AIX 5.3.  Right now the library
is /dev/smc0.  After partitioning, will i get a smc0 and an smc1?  Should i
run cfgmgr after partitioning?

3.  What is the best procedure to do the partition?  I'm thinking i need to
checkout all the cartridges, then turn off the library.  Move the tape
drives, then partition the library.  Then deal with the AIX devices changing
(rmdev/cfgmgr).  Then redefine drives/paths, define new device classes and
checkin the cartridges to the right logical library.  Am i missing anything?

We're running TSM 5.3.4.0.  Thanks for any info.  I appreciate it.

ray
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ray DeJean   http://www.r-a-y.org
Systems EngineerSoutheastern Louisiana University
IBM Certified Specialist  AIX Administration, AIX Support
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: Backup procedures for PICK/UNIDATA

[Rick Saylor]

Kelly,

Our Unidata database is backed up with TSM and as you've suggested
the dbpause and dbresume are used to ensure a good backup. A TSM
prebackup script pauses the database, takes a snapshot of the
database and then resumes the database access. TSM then backs up the
now static copy of the database. This way the database is only paused
for a few seconds. Once the backup is complete a postbackup scripts
removes the snapshot. You didn't say what your environment is but
ours is AIX 5.2 with the database on a mirrored JFS2 filesystem.

This has worked well for us. Each day the backup is restored to a
remote site as well as our test system. We've never had any problems.
Let me know if you have any other questions.

Thanks,
Rick Saylor

Austin Community College

At 11:21 AM 4/23/2007, you wrote:

Folks,

Any of you esteemed folks using TSM to backup/restore UNIDATA or other
implementations of a PICK database?  Specifically, are you using the
dbpause and dbresume commands?

Easy, hard, impossible?

Thoughts as always much appreciated.

Thanks,

Kelly J. Lipp
VP Manufacturing & CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
[EMAIL PROTECTED]





Rick Saylor  Austin Community College   Voice: (512)223-1182
Director of System Services  9101 Tuscany Way   Fax:   (512)223-1211
Information Technology   Austin, Texas  78754

Re: Backup procedures for PICK/UNIDATA

[Wilkinson, Brent]

Yes, we backup multiple UNIDATA DB's here by pausing the DB during the
backup process. It works well as we restore the DB's to the development
systems without issue on a regular basis. 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kelly Lipp
Sent: Monday, April 23, 2007 10:22 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Backup procedures for PICK/UNIDATA

Folks,
 
Any of you esteemed folks using TSM to backup/restore UNIDATA or other
implementations of a PICK database?  Specifically, are you using the
dbpause and dbresume commands?
 
Easy, hard, impossible?
 
Thoughts as always much appreciated.
 
Thanks,
 
Kelly J. Lipp
VP Manufacturing & CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
[EMAIL PROTECTED]
 

Backup procedures for PICK/UNIDATA

[Kelly Lipp]

Folks,
 
Any of you esteemed folks using TSM to backup/restore UNIDATA or other
implementations of a PICK database?  Specifically, are you using the
dbpause and dbresume commands?
 
Easy, hard, impossible?
 
Thoughts as always much appreciated.
 
Thanks,
 
Kelly J. Lipp
VP Manufacturing & CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
[EMAIL PROTECTED]
 

Re: RAC backups

[Pablo Arzuaga]

You will have a hard time? If you are using Oracle 10g with RAC you will
be having a lot a problems. We have a 2 node cluster with AIX 5.3 &
oracle 10G & one in a wile the ocssd.bin will reboot the node . It is a
known issue in Oracle. The TDP works great but after all the problems we
had I just made a cron job to handel the backups & used regular Tivoli
schedule to due the backup 


 

Pablo Arzuaga

Ticket Pop Networks

Network Analyst

Cel. 787-458-9063 

[EMAIL PROTECTED]

www.ticketpop.com

 

 

 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Thomas, Matthew
Sent: Monday, April 23, 2007 10:18 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] RAC backups

Guys,



Does anyone have any guidance on using TSM scheduled TDP backups with
Oracle RAC multi-node grids?

We're due to implement a 4-way RAC cluster (on AIX) and ultimately we'll
need the database(s) to be backed up and restored via any of the 4 nodes
in the grid.

Any advice would be appreciated.



TIA

Matt Thomas



This e-mail is only for the above addressees.  It may contain
confidential or privileged information.
If you are not an addressee you must not copy, distribute, disclose or
use any of the information in it or any attachments.  If you have
received it in error please notify the sender and delete it immediately.


Lloyds TSB Bank plc.  Registered office: 25 Gresham Street, London EC2V
7HN.  Registered in England and Wales, number 2065.  Telephone: 020 7626
1500.
Lloyds TSB Scotland plc.  Registered office: Henry Duncan House, 120
George Street, Edinburgh
EH2 4LH.  Registered in Scotland, number 95237.  Telephone: 0131 225
4555.
Cheltenham & Gloucester plc.  Registered office: Barnett Way, Gloucester
GL4 3RL.  Registered in England and Wales, number 2299428.  Telephone:
01452 372372.


Lloyds TSB Bank plc, Lloyds TSB Scotland plc and Cheltenham & Gloucester
plc are authorised and regulated by the Financial Services Authority and
are signatories to the Banking Codes.


Lloyds TSB Bank plc and Lloyds TSB Scotland plc represent only the
Scottish Widows and Lloyds TSB Marketing Group for life assurance,
pensions and investment business.
Cheltenham & Gloucester plc acts as an introducer only for life
assurance, pensions and investment business.


Lloyds TSB Group plc.  Registered office: Henry Duncan House, 120 George
Street, Edinburgh
EH2 4LH.  Registered in Scotland, number 95000.  Telephone: 0131 225
4555.

RAC backups

[Thomas, Matthew]

Guys,



Does anyone have any guidance on using TSM scheduled TDP backups with Oracle
RAC multi-node grids?

We're due to implement a 4-way RAC cluster (on AIX) and ultimately we'll
need the database(s) to be backed up and restored via any of the 4 nodes in
the grid.

Any advice would be appreciated.



TIA

Matt Thomas



This e-mail is only for the above addressees.  It may contain confidential or 
privileged information.
If you are not an addressee you must not copy, distribute, disclose or use any 
of the information in
it or any attachments.  If you have received it in error please notify the 
sender and delete it
immediately.


Lloyds TSB Bank plc.  Registered office: 25 Gresham Street, London EC2V 7HN.  
Registered in
England and Wales, number 2065.  Telephone: 020 7626 1500.
Lloyds TSB Scotland plc.  Registered office: Henry Duncan House, 120 George 
Street, Edinburgh
EH2 4LH.  Registered in Scotland, number 95237.  Telephone: 0131 225 4555.
Cheltenham & Gloucester plc.  Registered office: Barnett Way, Gloucester GL4 
3RL.  Registered in
England and Wales, number 2299428.  Telephone: 01452 372372.


Lloyds TSB Bank plc, Lloyds TSB Scotland plc and Cheltenham & Gloucester plc 
are authorised
and regulated by the Financial Services Authority and are signatories to the 
Banking Codes.


Lloyds TSB Bank plc and Lloyds TSB Scotland plc represent only the Scottish 
Widows and Lloyds
TSB Marketing Group for life assurance, pensions and investment business.
Cheltenham & Gloucester plc acts as an introducer only for life assurance, 
pensions and
investment business.


Lloyds TSB Group plc.  Registered office: Henry Duncan House, 120 George 
Street, Edinburgh
EH2 4LH.  Registered in Scotland, number 95000.  Telephone: 0131 225 4555.

Ich bin nicht im Buero und kann deshalb Ihr Mail nicht beantworten.

[Oliver Martin]

I will be out of the office starting 23.04.2007 and will not return until
24.04.2007.

In dringenden Fällen wenden Sie sich bitte an meine Kollegen Klaus
Hämmerle, DW 1122, oder Michael Prantner, DW 1156.

Danke.

Oliver Martin
-

Der Austausch von Nachrichten via e-mail dient ausschließlich
Informationszwecken und ist nur für den Gebrauch des Empfängers bestimmt.
Rechtsgeschäftliche Erklärungen dürfen über dieses Medium nicht
ausgetauscht werden. Sollten Sie nicht der Adressat sein, verständigen Sie
uns bitte unverzüglich per e-mail oder Telefon und vernichten Sie diese
Nachricht.

The exchange of e-mail messages is for purposes of information only and
only intended for the recipient.
This medium may not be used to exchange legal declarations. If you are not
the intended recipient, please contact us immediately by e-mail or phone
and delete this message from your system.

Re: New personal best.

[Ibán Bernaldo de Quirós Márquez]

Hi still Running...


 Sess Comm.  Sess Wait   Bytes   Bytes 
Sess  Platform Client Name

Number Method StateTimeSent   Recvd Type
-- -- -- -- --- --- 
-  
12,225 Tcp/Ip RecvW0 S  309.1 K  10.2 T 
Node  LinuxPPC MN_PROJECTS_PROXY
12,525 Tcp/Ip RecvW0 S  138.4 K   9.9 T 
Node  LinuxPPC MN_PROJECTS_PROXY


Regards,
Ibán.


Roger Deschner wrote:

I tried this for a while, forcing large client files directly to tape,
but those big files are so awful to back up directly to tape that we
bought more disks. When a client session gets a tape drive for backup,
the network and the client (more often than not, some underpowered Mac
that some dork has filled with video files) can almost never pump enough
data down the wire to keep the tape drive streaming. So it stops and
starts - shoeshining. This really wears out your tapes. They say that
DLT and LTO tapes are good for some huge number of passes in the
millions, but once you start shoeshining you can reach those numbers
real quick.

To add insult to injury, when a slow client is backing up a huge file to
a tape drive, your TSM Server Log is pinned. We had a log-full server
crash this way.

The only way to positively prevent shoeshining and resulting full log
crashes is to buy more disks, and insure that all tape writing is done
via TSM Migration from local server disk. Set the file size limits the
same in the primary (disk) and secondary (tape) Storage Pools so that
client backup sessions never mount a tape. The cost of a little more
disk space is really worth it here, in terms of both overall
performance, and tape wear.

Another way to reduce shoeshining is to use a reclamation storage pool.
During reclamation, the output tape has to stop while the input tape is
skipping past the already-expired files.

In your situation, set RESOURCEUTULIZATION to 10 in the client options
file so that it uses 5 sessions to back up at once. This can really help
with a lot of small files like you have. That old rule of thumb that you
should have enough Storage Pool disk for one normal day of backups still
applies, especially when backing up a monster like this. Then you should
migrate to tape using as many migration processes as you have tape
drives.

Roger Deschner  University of Illinois at Chicago [EMAIL PROTECTED]
= "Things are more like they are now than they have ever been before." =
 --Dwight D. Eisenhower 


On Thu, 12 Apr 2007, Skylar Thompson wrote:

  

I have tried virtualmountpoint without chance (or without
experience)... I meant that I have one TSM for one FS (8.000.000->
today, 16.000.000 of files-> future // 10 versions) This FS is
represented by one node... the first stage is disk... so when I
migrate to tape, I only have one process...  :'( :'(

And creating more than one node with virtual mount points seems to me
so tedious to restore...

do you disk at first stage ¿? Or are you backing up to tape directly ¿?
  

My solution has been to force big files (>1GB at our site) to tape, but
spool small files on disk. You can do this with the MAXSIZE parameter on
your disk storage pool.

--
-- Skylar Thompson ([EMAIL PROTECTED])
-- Genome Sciences Department, System Administrator
-- Foege Building S048, (206)-685-7354
-- University of Washington School of Medicine