Re: TDP/SQL and Striping
Jeff, You should edit the file C:\Program Files\Tivoli\TSM\TDPSql\tdpsql.cfg and add (or change) the stripes parameter to 2. STRIPes 2 I'm concerned about your performance. Of course that depends on the LAN infrastructure you have. We use a Gbit network and a 190GB dbase is backed up in about 3 hours. We do have STRIPES 2 and max mount points 2. Yiannakis -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Jeff White Sent: 19 April 2004 13:32 To: [EMAIL PROTECTED] Subject: TDP/SQL and Striping Hi, TSM server v5.1.5.2 running on IBM mainframe. OS is Z/OS 1.4 TSM Client v4.1.5.0 TDP version 2.2.1 SQL Server 7.0 I have a 20gb SQL database that takes slightly more than an hour to backup using TDP and a 200gb SQL database taking 15 hours to backup using TDP. I am considering using striping. I have read the redbook and the TSM/SQL installation and Users guide and have evrything setup, or so i thought. Collocation on FILESPACES Node MAXNUMMP set to 8 mount points Device Class set to Mount Limit 8 TXNGROUPMAX set to 256 The 20gb database is on one physical disk The 200gb database is spread across 3 physical volumes When i backup, it only uses a single thread, i.e. one mount point. Do i need to ask our Database Admin guys to put striping on the SQL database? The manuals were'nt clear about this Jeff White Senior Systems Programmer ICT Operations and Services CIS 1st Floor Miller Street 0161 837 5020 [EMAIL PROTECTED] * This e-mail may contain confidential information or be privileged. It is intended to be read and used only by the named recipient(s). If you are not the intended recipient(s) please notify us immediately so that we can make arrangements for its return: you should not disclose the contents of this e-mail to any other person, or take any copies. Unless stated otherwise by an authorised individual, nothing contained in this e-mail is intended to create binding legal obligations between us and opinions expressed are those of the individual author. The CIS marketing group, which is regulated for Investment Business by the Financial Services Authority, includes: Co-operative Insurance Society Limited Registered in England number 3615R - for life assurance and pensions CIS Unit Managers Limited Registered in England and Wales number 2369965 - for unit trusts and PEPs CIS Policyholder Services Limited Registered in England and Wales number 3390839 - for ISAs and investment products bearing the CIS name Registered offices: Miller Street, Manchester M60 0AL Telephone 0161-832-8686 Internet http://www.cis.co.uk E-mail [EMAIL PROTECTED] CIS Deposit and Instant Access Savings Accounts are held with The Co-operative Bank p.l.c., registered in England and Wales number 990937, P.O. Box 101, 1 Balloon Street, Manchester M60 4EP, and administered by CIS Policyholder Services Limited as agent of the Bank. CIS is a member of the General Insurance Standards Council CIS & the CIS logo (R) Co-operative Insurance Society Limited
Change the default database name on TSM server
Hi all, I use TDP and RMAN to backup database for Oracle. By default, TSM server storages database that was backuped with name : \adsmorc. I want to change this default name on TSM server. Does anyone know how to change it ? Thanks in advanced ! Nghiatd,
AW: Change the default database name on TSM server
Hi, you should use TDPO_FS in tdpo.opt. If you change the filespacename on the TSM server be sure to set TDPO_FS correctly. The filespacename on the TSM server and TDPO_FS have to be in sync. See "Tivoli Data Protection for Oracle - Installation and User's Guide" TDPO_FS This option specifies a file space name on the Tivoli Storage Manager server which TDP for Oracle uses for backup, delete, and restore operations. The file-space name is a string of 1 to 1024 characters. When setting up this option, do not use a directory delimiter in front of the filespace name. If this option is set during TDP for Oracle backup operations, this option must also be set during restore and delete operations. If you have more than one Oracle database, back up each Oracle target database to its own file space on the Tivoli Storage Manager server. The default file space name is adsmorc. HTH Thomas Rupp -Ursprüngliche Nachricht- Von: nghiatd [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 20. April 2004 09:24 An: [EMAIL PROTECTED] Betreff: Change the default database name on TSM server Hi all, I use TDP and RMAN to backup database for Oracle. By default, TSM server storages database that was backuped with name : \adsmorc. I want to change this default name on TSM server. Does anyone know how to change it ? Thanks in advanced ! Nghiatd,
Re: TSM AIX server spewing error messages
>My AIX TSM server (5.2.2.3) just spewed the following error messages. > >Talk about schizophrenic/indecisive !! > >What gives ? All I was doing is a DB backup. Just inserted and >initialized this tape. The init went fine. > >This is an IBM 3583-L72 with 2-LTO2 drives. > >* > >04/19/04 15:34:18 ANR8950W Device /dev/rmt3, volume 09 has issued >the following Warning TapeAlert: The operation has stopped be cause an >error has occurred while reading or writing data which the drive cannot >correct. (SESSION: 5496, PROCESS: 17) ... You will find TapeAlert summarized in the IBM 358x Setup and Operator Guide manuals, with flag values. TapeAlert is a patented technology and standard of the American National Standards Institute (ANSI) that defines conditions and problems that are experienced by tape drives. The technology enables a server to read TapeAlert flags from a tape drive through the SCSI interface. The LTO Ultrium tape drives incorporate such alerts. TSM is merely responding to the spew coming from the tape drive. Looks like we've gone from the obscurant extreme of sense bytes to a profusion of textual possibilities regarding tape errors. Perhaps some day we'll get succinct messages saying "Here's what's wrong...". Better yet, perhaps IBM's Autonomic Computing initiative (www.ibm.com/autonomic) will some day come to its tape technology and fix problems itself. Richard Sims http://people.bu.edu/rbs
Simultaneous primary/copy of data
Hello everyone! I am in the process of creating a new storage hierarchy to create two simultaneous backups of a client's data. In the book it states that you can write to a primary disk or tape storage pool and a copy pool at the same time and that the data must be coming from the client at the time that the simultaneous backup is occurring. What I am wondering is do you just invoke this by creating a separate management class that directs certain information to these storage pools and also what is everyone using this for? Oracle, lotus notes, or other large files and databases? Does anyone send smaller files or does this mainly operate efficiently for large database and other large files? Thanks in advance for any suggestions/ideas you might have! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Exclude on AIX
Hi *SM-ers! One of our AIX guys wants to exclude all filespaces and then include specific others. We have tried the following: include.fs /home include.fs /usr exclude.fs * But that doesn't work. I don't know how to accomplish this. Because they want to use our standard way for excluding files (include-exclude file) using the domains statement is not an option. Can someone please help us here? Thank you very much in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Change the default database name on TSM server
there should be a parameter in the /opt or /usr/tivoli/tsm/client/oracle/bin/tdpo.opt file called: "tdpo_fs_name" or something to that affect. That value will determine what filespace name your backupsets are all stored as on the tsm server if backedup via that Oracle tdp. thanks!. --Justin Richard Bleistein |-+> | | nghiatd | | | <[EMAIL PROTECTED]| | | .VN> | | | Sent by: "ADSM: | | | Dist Stor| | | Manager" | | | <[EMAIL PROTECTED]| | | .EDU>| | || | || | | 04/20/2004 03:24 | | | AM | | | Please respond to| | | "ADSM: Dist Stor | | | Manager" | | || |-+> >--| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Change the default database name on TSM server | >--| Hi all, I use TDP and RMAN to backup database for Oracle. By default, TSM server storages database that was backuped with name : \adsmorc. I want to change this default name on TSM server. Does anyone know how to change it ? Thanks in advanced ! Nghiatd,
Re: Exclude on AIX
I could be mistaken, but you should just be able to move the "exclude.fs *" to the top. That should do it since it reads from the bottom up, and uses the first match it comes to. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Loon, E.J. van - SPLXM Sent: Tuesday, April 20, 2004 8:26 AM To: [EMAIL PROTECTED] Subject: Exclude on AIX Hi *SM-ers! One of our AIX guys wants to exclude all filespaces and then include specific others. We have tried the following: include.fs /home include.fs /usr exclude.fs * But that doesn't work. I don't know how to accomplish this. Because they want to use our standard way for excluding files (include-exclude file) using the domains statement is not an option. Can someone please help us here? Thank you very much in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Exclude on AIX
Hi Kevin! I know that it reads bottom up, so your solution will not work. If you code: exclude.fs * include.fs /home include.fs /usr It will first encounter the includes and then the exclude all, so It will not backup anything. TSM processes all include/excludes, it wil not exit as soon as a match has been found. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Thach, Kevin G [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 14:43 To: [EMAIL PROTECTED] Subject: Re: Exclude on AIX I could be mistaken, but you should just be able to move the "exclude.fs *" to the top. That should do it since it reads from the bottom up, and uses the first match it comes to. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Loon, E.J. van - SPLXM Sent: Tuesday, April 20, 2004 8:26 AM To: [EMAIL PROTECTED] Subject: Exclude on AIX Hi *SM-ers! One of our AIX guys wants to exclude all filespaces and then include specific others. We have tried the following: include.fs /home include.fs /usr exclude.fs * But that doesn't work. I don't know how to accomplish this. Because they want to use our standard way for excluding files (include-exclude file) using the domains statement is not an option. Can someone please help us here? Thank you very much in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Exclude on AIX
Hi Eric, > ... it wil not exit as soon as a match has been found. Actually, TSM include/exclude processing does indeed exit as soon as a match is found. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/20/2004 06:04 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Exclude on AIX Hi Kevin! I know that it reads bottom up, so your solution will not work. If you code: exclude.fs * include.fs /home include.fs /usr It will first encounter the includes and then the exclude all, so It will not backup anything. TSM processes all include/excludes, it wil not exit as soon as a match has been found. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Thach, Kevin G [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 14:43 To: [EMAIL PROTECTED] Subject: Re: Exclude on AIX I could be mistaken, but you should just be able to move the "exclude.fs *" to the top. That should do it since it reads from the bottom up, and uses the first match it comes to. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Loon, E.J. van - SPLXM Sent: Tuesday, April 20, 2004 8:26 AM To: [EMAIL PROTECTED] Subject: Exclude on AIX Hi *SM-ers! One of our AIX guys wants to exclude all filespaces and then include specific others. We have tried the following: include.fs /home include.fs /usr exclude.fs * But that doesn't work. I don't know how to accomplish this. Because they want to use our standard way for excluding files (include-exclude file) using the domains statement is not an option. Can someone please help us here? Thank you very much in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Exclude on AIX
Eric, That is not correct. It starts from the bottom and works its way up. If it finds a "match" it stops processing. Del "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 04/20/2004 09:04:06 AM: > Hi Kevin! > I know that it reads bottom up, so your solution will not work. If you code: > > exclude.fs * > include.fs /home > include.fs /usr > > It will first encounter the includes and then the exclude all, so It will > not backup anything. TSM processes all include/excludes, it wil not exit as > soon as a match has been found. > Kindest regards, > Eric van Loon > KLM Royal Dutch Airlines
Re: Exclude on AIX
It does? I didn't knew that! I'll give it a try, thanks Andy and Del! Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Andrew Raibeck [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 15:11 To: [EMAIL PROTECTED] Subject: Re: Exclude on AIX Hi Eric, > ... it wil not exit as soon as a match has been found. Actually, TSM include/exclude processing does indeed exit as soon as a match is found. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/20/2004 06:04 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Exclude on AIX Hi Kevin! I know that it reads bottom up, so your solution will not work. If you code: exclude.fs * include.fs /home include.fs /usr It will first encounter the includes and then the exclude all, so It will not backup anything. TSM processes all include/excludes, it wil not exit as soon as a match has been found. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Thach, Kevin G [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 14:43 To: [EMAIL PROTECTED] Subject: Re: Exclude on AIX I could be mistaken, but you should just be able to move the "exclude.fs *" to the top. That should do it since it reads from the bottom up, and uses the first match it comes to. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Loon, E.J. van - SPLXM Sent: Tuesday, April 20, 2004 8:26 AM To: [EMAIL PROTECTED] Subject: Exclude on AIX Hi *SM-ers! One of our AIX guys wants to exclude all filespaces and then include specific others. We have tried the following: include.fs /home include.fs /usr exclude.fs * But that doesn't work. I don't know how to accomplish this. Because they want to use our standard way for excluding files (include-exclude file) using the domains statement is not an option. Can someone please help us here? Thank you very much in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Exclude on AIX
Eric - The postings didn't indicate whether a Query Inclexcl was done to verify the full list. Remember that any server-side client options set takes precedence, so that command can be invaluable when working on the client. Customers often overlook the unseen client options set, and wonder what the heck is going on with their client-side choice changes. And if a client schedule is involved, make sure that gets restarted to pick up changes. Richard Sims
Re: Delete obsolete directories only?
Thanks Steve. We have used the expire command, but this only seems to mark them inactive. Because the management class they are assigned to holds the only version forever, or until it knows the file has been deleted, they are marked inactive, but never go away. Any suggestions for completing the process and having them expire completely? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steve Harris Sent: Monday, April 19, 2004 7:12 PM To: [EMAIL PROTECTED] Subject: Re: Delete obsolete directories only? Debbie, I'm not familiar with sql backtrack but... I've used the normal BA client to delete orphan DB2 backups in the past. These are archives and I used the delete archive command. If sql backtrack uses backups rather than archives, then take a look at the ba client expire command Because these are API backups, to address them from the BA client you need to use a special syntax with braces around the "filespace" part of the file name. See the BA client doc for details. Regards Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia >>> [EMAIL PROTECTED] 20/04/2004 0:04:23 >>> I have not seen a response to this question, and I have a similar situation. We had noticed that our filespaces for our Oracle DB backups keep growing in leaps and bounds, and it finally became clear that they were growing faster than would be expected in consideration of the number of databases we have added. Upon investigation I have found that there is an enormous amount of space being used by backups that should have expired, however I cannot delete the entire filespace because that would also eliminate the valid backups. I have found that there seems to be two separate issues at play. One is that upon installing a new version of SQL Backtrack the Oracle admin that handles those profiles used the wrong management class, leaving the backups in limbo on TSM. They have expired from the SQL Backtrack catalog and marked inactive, however, they will never be removed from TSM in their current state. I cannot bind them to the appropriate management class via the usual methods. The other issue is that we seem to have some stragglers from 2001 and 2002, that should have expired, but are still hanging around for some reason. The only way I have found in the documentation to remove these items is by deleting the object by object number from the database. Can anyone tell me if this is the only way to clean up these items, and if that will in fact work to remove them from the tapepool storage? TSM for AIX 5.2.0 TSM for SUN/Solaris 4.2.1 SQL Backtrack 3.0, 4.0.10 Thanks, Debbie -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tab Trepagnier Sent: Friday, April 16, 2004 1:47 PM To: [EMAIL PROTECTED] Subject: Delete obsolete directories only? TSM Server 5.1.8.0 on AIX; TSM Client 5.1.6.0 on Windows 2000 I have a situation where over time, the location of data on our network has moved from server to server. In many cases we moved the identity of the first server to the second server, but the data paths were not duplicated exactly. For example, \\server_name\d$\current_root_path\... \\*\*\old_root_path\... where "current_root_path" and "old_root_path" are peers under the same "d$" parent. Because the "old_root_path" became invalid on the first backup of the new server, all the data under it was marked inactive by TSM. No problem there. Once the RetOnly duration elapsed, all the FILES were purged from that path. Again, no problem there. But the directories were retained, probably because they were bound to "no limit" permanent management classes prior to our implementing DIRMC controls. Meaning those directories will live for the duration of the server's identity or our TSM system, whichever ends first. Those duplicate paths confuse our Help Desk. I would like to delete just the contents under "old_root_path" since there are no files under that path. But because both root paths are under the same filespace, I can't delete the filespace. I turned on the permission "node can delete backups" but that still didn't let me kill that directory tree. So, is there a way to kill the directory tree under "old_root_path" other than killing the entire filespace? TIA Tab Trepagnier TSM Administrator Laitram, L.L.C. *** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if yo
Re: Simultaneous primary/copy of data
From: ADSM: Dist Stor Manager on behalf of Joni Moyer I am in the process of creating a new storage hierarchy to create two simultaneous backups of a client's data. In the book it states that you can write to a primary disk or tape storage pool and a copy pool at the same time and that the data must be coming from the client at the time that the simultaneous backup is occurring. What I am wondering is do you just invoke this by creating a separate management class that directs certain information to these storage pools and also what is everyone using this for? Run help update stgpool and look at the COPYSTGPOOL flag. -- Mark Stapleton
Re: Exclude on AIX
Hi Richard! Thank you very much for your reply! We don't use server defined include-excludes, so that's not the problem. We currently tried the following: exclude.fs * include.fs /home include.fs /usr Backup now finishes in 1 second. I've had them issue a q inclexcl which shows the correct statements and when they start the GUI, you can see that no filespaces are listed through the backup window. That explains why backup finishes so quickly, but it's still not what we want to accomplish... Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 15:26 To: [EMAIL PROTECTED] Subject: Re: Exclude on AIX Eric - The postings didn't indicate whether a Query Inclexcl was done to verify the full list. Remember that any server-side client options set takes precedence, so that command can be invaluable when working on the client. Customers often overlook the unseen client options set, and wonder what the heck is going on with their client-side choice changes. And if a client schedule is involved, make sure that gets restarted to pick up changes. Richard Sims ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Exclude on AIX
>Hi Richard! >Thank you very much for your reply! >We don't use server defined include-excludes, so that's not the problem. >We currently tried the following: > >exclude.fs * >include.fs /home >include.fs /usr > >Backup now finishes in 1 second. I've had them issue a q inclexcl which >shows the correct statements and when they start the GUI, you can see that >no filespaces are listed through the backup window. That explains why backup >finishes so quickly, but it's still not what we want to accomplish... But your backups now run so much faster! :-) Checking the Unix client manual, I find no such "Include.FS" option, so what you probably want to do is "Include /home/.../*". Would that Query Inclexcl flagged such things. Richard
Re: Exclude on AIX
On Tue, 20 Apr 2004 15:04:06 +0200 "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> wrote: > Hi Kevin! > I know that it reads bottom up, so your solution will not work. If you > code: > > exclude.fs * > include.fs /home > include.fs /usr > I don't think there is such a thing as an include.fs, just an exclude.fs, I guess you should look into the domain statement in your dsm.opt to do this. > It will first encounter the includes and then the exclude all, so It > will not backup anything. TSM processes all include/excludes, it wil > not exit as soon as a match has been found. > Kindest regards, > Eric van Loon > KLM Royal Dutch Airlines > > > -Original Message- > From: Thach, Kevin G [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 20, 2004 14:43 > To: [EMAIL PROTECTED] > Subject: Re: Exclude on AIX > > > I could be mistaken, but you should just be able to move the > "exclude.fs*" to the top. That should do it since it reads from the > bottom up, and uses the first match it comes to. > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Loon, E.J. van - SPLXM > Sent: Tuesday, April 20, 2004 8:26 AM > To: [EMAIL PROTECTED] > Subject: Exclude on AIX > > > Hi *SM-ers! > One of our AIX guys wants to exclude all filespaces and then include > specific others. We have tried the following: > > include.fs /home > include.fs /usr > exclude.fs * > > But that doesn't work. I don't know how to accomplish this. Because > they want to use our standard way for excluding files (include-exclude > file) using the domains statement is not an option. Can someone please > help us here? Thank you very much in advance! Kindest regards, Eric > van Loon KLM Royal Dutch Airlines > > > ** > For information, services and offers, please visit our web site: > http://www.klm.com. This e-mail and any attachment may contain > confidential and privileged material intended for the addressee only. > If you are not the addressee, you are notified that no part of the > e-mail or any attachment may be disclosed, copied or distributed, and > that any other action related to this e-mail or attachment is strictly > prohibited, and may be unlawful. If you have received this e-mail by > error, please notify the sender immediately by return e-mail, and > delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its > subsidiaries and/or its employees shall not be liable for the > incorrect or incomplete transmission of this e-mail or any > attachments, nor responsible for any delay in receipt. > ** -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 3000Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
Re: Exclude on AIX
>From the client manual: "The exclude.fs and exclude.dir statements override all include statements that match the pattern." Orville L. Lantto Datatrend Technologies, Inc. (http://www.datatrend.com) IBM Premier Business Partner 121 Cheshire Lane, Suite 700 Minnetonka, MN 55305 Email: [EMAIL PROTECTED] CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/20/2004 08:55 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Exclude on AIX Hi Richard! Thank you very much for your reply! We don't use server defined include-excludes, so that's not the problem. We currently tried the following: exclude.fs * include.fs /home include.fs /usr Backup now finishes in 1 second. I've had them issue a q inclexcl which shows the correct statements and when they start the GUI, you can see that no filespaces are listed through the backup window. That explains why backup finishes so quickly, but it's still not what we want to accomplish... Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 15:26 To: [EMAIL PROTECTED] Subject: Re: Exclude on AIX Eric - The postings didn't indicate whether a Query Inclexcl was done to verify the full list. Remember that any server-side client options set takes precedence, so that command can be invaluable when working on the client. Customers often overlook the unseen client options set, and wonder what the heck is going on with their client-side choice changes. And if a client schedule is involved, make sure that gets restarted to pick up changes. Richard Sims ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Please help me NOT migrate
TSMers, Please help me NOT migrate the server to a different platform from AIX. server: 4way P660, 3G memory running AIX 5.1 3494 with 6 FC 3590E tape drives connected to 2 SAN switches 90G database at 60% utilized on a Shark 24T of backup data 2600 3590E tapes 460 clients: Windows, Linux, Solaris, AIX There has been a change in management, and to put it mildly, certain people do not like IXX and want to see it out of the machine room. I have to put in a strong argument on why TSM has to run on AIX. The two platforms I am offered are Linux and Solaris. Management wants to keep the 3494 and all its tapes because of the sunk cost. I have been running ADSM/TSM/ITSM v2/v3/v4/v5 for the past 8 years on a J30 and then the P660 and am perfectly happy with TSM on AIX. The two IBM CEs who work on our hardware are wonderful. Migrating to a different platform is going to be a nightmare. How long will backup be down to export/import 460 clients with 24T of data? Realistically, I know I can only stall it for 2 more years. After we outgrow the P660, the new hardware we buy will run either Solaris or Linux. What is your experience with TSM server running on either one? Thanks in advance, Eliza Lau Virginia Tech Computing Center Blacksburg, VA
Re: to know volumes of a node
Hello, isnt there a way to simulate an restore and look at the actlog ? But i think it is possible that there Data on all volumes but you dont need all to do a restore. And tomorrow it is on other volumes. The information then isnt very useful. May be your theme is collocation=yes. Is this select-command a way to bring your server down ? cu Michael Kindermann Am Montag, 19. April 2004 08:57 schrieb Geetha Thanu: > Hi all, > > How to find out the volumes(cartridges) containing the data of > a particular node. > > Is there anyway to do it. > > Please help.waiting for your replies > > > > Thank you > > Geetha Thanu > > > > > > > > > -
Re: Netware 6.5 and TSM 5.2.2
You need to look at Appendix C. http://publib.boulder.ibm.com/tividd/td/TSMC/GC32-0786-04/en_US/HTML/ans3tfrm.htm Julian Armendariz System Analyst - UNIX H.B. Fuller (651) 236-4043 >>> [EMAIL PROTECTED] 4/19/2004 8:58:17 AM >>> Every question seems to relate to Novell when I am on here...We just upgraded our NetWare Cluster servers (4) to 6.5. Upgraded TSM to 5.2.2 and all seemed well. Until I started to look at the log reports and found out TSM was not backing up the San volumes on the Cluster. It will back up the SYS: volume on all Clusters , but will not back up any SAN volumes associated to the Cluster. I have not changed anything on TSM and have upgraded all my other Novell clients without problems. Granted all the other Novell Servers are not Cluster Servers, but has anyone seen or had this problem? Thank You!
Question on LTO-2 dual-path fiber attach drives (AIX platform)
It is time to upgrade our tape drives - the current lease is coming up for renewal. I will be replacing LTO-1 SCSI drives with LTO-2 fiber drives. Do I need to get the AIX 'Control Path Fallover' option for TSM to properly recognize that there are two paths to a drive and only use one? My current understanding is that Control Path Fallover will allow TSM to continue a process running against a particular tape and tape drive on the second path if the first fails, as opposed to cancelling the process (and possibly flagging the tape as unavailable). Realisticly, how often does a path fail in the real world? We currently have two 2019-F16 switches and will be adding two more with the tape drives. We also have just the one TSM server and are not currently planning on running anything LAN-free. TIA Tom Kauffman NIBCO, Inc
Re: to know volumes of a node
How about: Select * from volumeusage where node_name='nomenodo' and stgpool_name='nomestgp' and filespace_id= fs# ? Cordiali saluti Gianluca Mariani Tivoli TSM Global Response Team, Roma Via Sciangai 53, Roma phones : +39(0)659664598 +393351270554 (mobile) [EMAIL PROTECTED] The Hitch Hiker's Guide to the Galaxy says of the Sirius Cybernetics Corporation product that "it is very easy to be blinded to the essential uselessness of them by the sense of achievement you get from getting them to work at all. In other words â and this is the rock solid principle on which the whole of the Corporation's Galaxy-wide success is founded -their fundamental design flaws are completely hidden by their superficial design flaws"... Geetha Thanu <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 19/04/2004 08.57 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject to know volumes of a node Hi all, How to find out the volumes(cartridges) containing the data of a particular node. Is there anyway to do it. Please help.waiting for your replies Thank you Geetha Thanu -
Re: Please help me NOT migrate
Ahh, the politics, we all get it. I'm in a very similar boat as you are I too am getting "encouragement" to move our 8 TSM servers from AIX to anything else. My first choice would be to keep with the IBM PSeries hardware and run Linux on it, but management also seems to want the IBM hardware gone. Some folks keep suggesting a Windows platform, but I resist. My personal opinion is that the typical Wintel platforms just can't do the I/O necessary to run multiple GB interfaces and 14 fibrechannel drives. I'm sure others in this group will rebuff my opinion, flame away :-) I'm a Unix admin, so I lean towards some other flavor of *nix. Once again, since we run most of our Linux hosts on Intel platforms & I'm not confident about the I/O ability, therefore I lean towards Solaris. We have some experience with Solaris TSM servers as I set up 2 remote sites. They seem to work OK, but they are not very large installations. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Eliza Lau Sent: Tuesday, April 20, 2004 8:53 AM To: [EMAIL PROTECTED] Subject: Please help me NOT migrate TSMers, Please help me NOT migrate the server to a different platform from AIX. server: 4way P660, 3G memory running AIX 5.1 3494 with 6 FC 3590E tape drives connected to 2 SAN switches 90G database at 60% utilized on a Shark 24T of backup data 2600 3590E tapes 460 clients: Windows, Linux, Solaris, AIX There has been a change in management, and to put it mildly, certain people do not like IXX and want to see it out of the machine room. I have to put in a strong argument on why TSM has to run on AIX. The two platforms I am offered are Linux and Solaris. Management wants to keep the 3494 and all its tapes because of the sunk cost. I have been running ADSM/TSM/ITSM v2/v3/v4/v5 for the past 8 years on a J30 and then the P660 and am perfectly happy with TSM on AIX. The two IBM CEs who work on our hardware are wonderful. Migrating to a different platform is going to be a nightmare. How long will backup be down to export/import 460 clients with 24T of data? Realistically, I know I can only stall it for 2 more years. After we outgrow the P660, the new hardware we buy will run either Solaris or Linux. What is your experience with TSM server running on either one? Thanks in advance, Eliza Lau Virginia Tech Computing Center Blacksburg, VA
Re: 64-bit support on 390?
Thanks. Hopefully this won't be too much of an adventure. "Slag, Jerry B." <[EMAIL PROTECTED]> wrote:No issues. We did make changes to WLM to place TSM into a separate service class that has the 'storcrit' setting active. TSM runs well and the storcrit setting keeps the cpu usage way down. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Joe Howell Sent: Friday, April 16, 2004 10:28 AM To: [EMAIL PROTECTED] Subject: 64-bit support on 390? We're going to a disaster-recovery exercise in a couple of months and one of the things that we want to try is running our mainframe environment on "z" hardware in 64-bit mode, Just To See What Happens. Is anyone running TSM 5.2.2 in 64-bit mode on a mainframe? Any excitement waiting for me? Joe Howell Shelter Insurance Companies Columbia, MO - Do you Yahoo!? Yahoo! Tax Center - File online by April 15th Joe Howell Shelter Insurance Companies Columbia, MO - Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25"
Re: Please help me NOT migrate
... >I'm a Unix admin, so I lean towards some other flavor of *nix. ... IBM would do well to consider producing a TSM server for the Macintosh platform. Apple has seriously been into server systems for years now, and sells some of the fastest servers made, along with RAID (and an upcoming Xsan offering). After all, it is IBM which manufactures the G5 chip. Richard Sims
Re: Please help me NOT migrate
Hi Eliza, My condolences; I don't envy the position that you're in. I'm not sure what arguments have been laid out against staying with AIX, but perhaps you could put some weight on the other pan of the scale by doing some testing and extrapolating the results to approximate the real costs of migrating to a new platform. It's probably a pretty safe bet that your users at Tech are not willing to abandon their historical backup data, so you are probably faced with doing an export/import of data to get that across to whatever new platform you will go to. Depending o how great a hurry management is to get AIX and/or IBM server hardware out the door, side-by-side co-existence might be an option. Not a very attractive one in my mind, but a possibility.) Is there a medium-size representative client node that you could perform a test of the export/import process with? It should be one that has been active for a while, so that the data is spread across volumes, rather than being on one or a couple of tapes. This is assuming that you are not using collocation. If you are, "data spread" should be much less of an issue. If you don't have a test TSM server that can access the 3590 drives, it would be a good idea to temporarily rename the node for the duration of the export so that you can import it to the same server. Some factors that you might want to keep in mind as you approach this with an eye toward presenting the cost(s) of migration: Export will not automatically free tapes on the source server; you'll need enough tapes (and slots) available to create the export and to import to the new server. How much "slack" time do you have on your six drives? Will you be able to perform these migrations and still perform the work required to keep the other backups running on the "old" AIX system? Even doing these migrations one at a time, will the downtime for any particular system be prohibitive? Can your users/applications tolerate that kind of downtime without good backups? I don't have any hands-on with TSM on either Linux or Solaris, so I can't speak to the pros or cons of either, but perhaps the costs of the migration scenario will be persuasive enough to at least slow, if not entirely stop the pressures to migrate. Let us know how you make out with this "adventure". Ted Ted Byrne Blacksburg, VA At 10:53 AM 4/20/2004, you wrote: TSMers, Please help me NOT migrate the server to a different platform from AIX. server: 4way P660, 3G memory running AIX 5.1 3494 with 6 FC 3590E tape drives connected to 2 SAN switches 90G database at 60% utilized on a Shark 24T of backup data 2600 3590E tapes 460 clients: Windows, Linux, Solaris, AIX There has been a change in management, and to put it mildly, certain people do not like IXX and want to see it out of the machine room. I have to put in a strong argument on why TSM has to run on AIX. The two platforms I am offered are Linux and Solaris. Management wants to keep the 3494 and all its tapes because of the sunk cost. I have been running ADSM/TSM/ITSM v2/v3/v4/v5 for the past 8 years on a J30 and then the P660 and am perfectly happy with TSM on AIX. The two IBM CEs who work on our hardware are wonderful. Migrating to a different platform is going to be a nightmare. How long will backup be down to export/import 460 clients with 24T of data? Realistically, I know I can only stall it for 2 more years. After we outgrow the P660, the new hardware we buy will run either Solaris or Linux. What is your experience with TSM server running on either one? Thanks in advance, Eliza Lau Virginia Tech Computing Center Blacksburg, VA
Re: Question on LTO-2 dual-path fiber attach drives (AIX platform)
Tom, >From what I understand, LTO2 aren't dual attached drives, so you wouldn't need the Control Path Failover for your server. Now, the 3592's are dual attached, but they are enterprise drives and . Please someone correct me if I'm wrong concerning the dual paths on the drives... Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] Tom Kauffman <[EMAIL PROTECTED] COM> To Sent by: "ADSM: [EMAIL PROTECTED] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Question on LTO-2 dual-path fiber attach drives (AIX platform) 04/20/2004 11:33 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> It is time to upgrade our tape drives - the current lease is coming up for renewal. I will be replacing LTO-1 SCSI drives with LTO-2 fiber drives. Do I need to get the AIX 'Control Path Fallover' option for TSM to properly recognize that there are two paths to a drive and only use one? My current understanding is that Control Path Fallover will allow TSM to continue a process running against a particular tape and tape drive on the second path if the first fails, as opposed to cancelling the process (and possibly flagging the tape as unavailable). Realisticly, how often does a path fail in the real world? We currently have two 2019-F16 switches and will be adding two more with the tape drives. We also have just the one TSM server and are not currently planning on running anything LAN-free. TIA Tom Kauffman NIBCO, Inc
Web client on Netware ANS2613
Hi All, We installed Netware client couple of months ago. During install we tested restore also. Worked OK. Now they needed some files and they cannot connect from web GUI to TSM client on Netware server. Backup works OK, restore works fine from Netware server (TSM command line)itself. When they click on restore in gui, popup window comes up. We put login and pwd and we got ANS2613S "Protocol error occured in communication between browser and client". I'm guessing this is a network problem , not TSM, but I don't know how to troubleshhot this. TSM Server 5.1.9.0 on Windows Netware client 5.2.2.3 Joe Crnjanski Infinity Network Solutions Inc. Phone: 416-235-0931 x26 Fax: 416-235-0265 Web: www.infinitynetwork.com
TDP for Oracle Cost
Hello everyone! I was just wondering if anyone would happen to know an approximate cost of using the TDP for Oracle and RMAN for backup/recovery on Oracle servers? Thanks! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Re: TSM AIX server spewing error messages
Thank you for the explaination. However, what does it all mean ? Why do I get error message that try to address 20-different possibilities of reasons for some failure, that I am not sure I am having ? What does it all mean to me ? Should I just call IBM and have them come figure it out ? The last time I did that, all IBM did was talk me through simple troubleshooting (unplug drive from slot a - plug it into slot b - did that make the problem go away..no, bad drive - we will send you a new one...you plug it in) ! While I don't mind this to a point (I get my hand dirty, all the time), there is a point beyond simple troubleshooting that someone more techincally intimate with the equipment needs to address ! "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 04/20/2004 07:42:21 AM: > >My AIX TSM server (5.2.2.3) just spewed the following error messages. > > > >Talk about schizophrenic/indecisive !! > > > >What gives ? All I was doing is a DB backup. Just inserted and > >initialized this tape. The init went fine. > > > >This is an IBM 3583-L72 with 2-LTO2 drives. > > > >* > > > >04/19/04 15:34:18 ANR8950W Device /dev/rmt3, volume 09 has issued > >the following Warning TapeAlert: The operation has stopped be cause an > >error has occurred while reading or writing data which the drive cannot > >correct. (SESSION: 5496, PROCESS: 17) > ... > > You will find TapeAlert summarized in the IBM 358x Setup and Operator Guide > manuals, with flag values. > > TapeAlert is a patented technology and standard of the American National > Standards Institute (ANSI) that defines conditions and problems that are > experienced by tape drives. The technology enables a server to read TapeAlert > flags from a tape drive through the SCSI interface. > The LTO Ultrium tape drives incorporate such alerts. > TSM is merely responding to the spew coming from the tape drive. > > Looks like we've gone from the obscurant extreme of sense bytes to a > profusion of textual possibilities regarding tape errors. Perhaps some > day we'll get succinct messages saying "Here's what's wrong...". > Better yet, perhaps IBM's Autonomic Computing initiative > (www.ibm.com/autonomic) will some day come to its tape technology and > fix problems itself. > >Richard Sims http://people.bu.edu/rbs
permanent delete of an backuped-up object?
hi all, there has been a method how to permanently delete an already backed-up object, canm someone give me a quick hint? Juraj
Re: Please help me NOT migrate
Hi Ted, Since you are in Blacksburg you know who we are. But for the other folks, Virginia Tech is a state univeristy (The Hokies) and we do things cheap here. I have been offered a SUN Enterprise 250 and a SUN L1000 DLT library with 10(?) slots that will soon be surplused by the other backup system (Legato) after they upgrade to better hardware as a test TSM Solaris server. The users will not tolerate loss of historic data so the only option is to export/import. I can test exporting but the Enterprise 250 doesn't have a 3590 tape drive to import to. I like your idea of renaming one node and importing back to the AIX server. This is my take: 800 new 3590E tapes will have to be purchased for the purpose of export/import. Migration has to be done in one shot since we will have to disconnect the 3494 after the export and connect it to the new Solaris server for the import. During migration all backup/restore have to be stopped since new data to the server will be lost after the export. Down time will be extensive. My recommendation is to set up a new Solaris server and slowly put new clients on it. Then over time we will move all clients to the new server. But I know it won't fly because it will entail buying a new tape library. Eliza Lau Virginia Tech > > Hi Eliza, > > My condolences; I don't envy the position that you're in. I'm not sure > what arguments have been laid out against staying with AIX, but perhaps you > could put some weight on the other pan of the scale by doing some testing > and extrapolating the results to approximate the real costs of migrating to > a new platform. > > It's probably a pretty safe bet that your users at Tech are not willing to > abandon their historical backup data, so you are probably faced with doing > an export/import of data to get that across to whatever new platform you > will go to. Depending o how great a hurry management is to get AIX and/or > IBM server hardware out the door, side-by-side co-existence might be an > option. Not a very attractive one in my mind, but a possibility.) > > Is there a medium-size representative client node that you could perform a > test of the export/import process with? It should be one that has been > active for a while, so that the data is spread across volumes, rather than > being on one or a couple of tapes. This is assuming that you are not using > collocation. If you are, "data spread" should be much less of an > issue. If you don't have a test TSM server that can access the 3590 > drives, it would be a good idea to temporarily rename the node for the > duration of the export so that you can import it to the same server. > > Some factors that you might want to keep in mind as you approach this with > an eye toward presenting the cost(s) of migration: > > Export will not automatically free tapes > on the source server; you'll need > enough tapes (and slots) available to create > the export and to import to the new server. > How much "slack" time do you have on your six drives? > Will you be able to perform these migrations > and still perform the work required to keep > the other backups running on the "old" AIX system? > Even doing these migrations one at a time, will the > downtime for any particular system be prohibitive? > Can your users/applications tolerate that kind of downtime > without > good backups? > > I don't have any hands-on with TSM on either Linux or Solaris, so I can't > speak to the pros or cons of either, but perhaps the costs of the migration > scenario will be persuasive enough to at least slow, if not entirely stop > the pressures to migrate. > > Let us know how you make out with this "adventure". > > Ted > > Ted Byrne > Blacksburg, VA > > > At 10:53 AM 4/20/2004, you wrote: > >TSMers, > > > >Please help me NOT migrate the server to a different platform from AIX. > > > >server: > >4way P660, 3G memory running AIX 5.1 > >3494 with 6 FC 3590E tape drives connected to 2 SAN switches > >90G database at 60% utilized on a Shark > >24T of backup data > >2600 3590E tapes > >460 clients: Windows, Linux, Solaris, AIX > > > >There has been a change in management, and to put it mildly, certain people > >do not like IXX and want to see it out of the machine room. > >I have to put in a strong argument on why TSM has to run on AIX. The two > >platforms I am offered are Linux and Solaris. Management wants to keep the > >3494 and all its tapes because of the sunk cost. > > > >I have been running ADSM/TSM/ITSM v2/v3/v4/v5 for the past 8 years on a > >J30 and then the P660 and am perfectly happy with TSM on AIX. The two IBM > >CEs who work on our hardware are wonderful. Migrating to a different > >platform is going to be a nightmare. How long will backup be > >down to export/import 460 clients with 24T of data? > > >
Flash 10282 has been published
TSM Community : Flash 10282 has been published: http://www-1.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10282 Including the Flash text below : Abstract: TSM Server can not be restarted after running REPAIR STGVOL utility in 5.1.9.0 or 5.2.2.0, if a volume is not specified when the command is issued. Problem: The REPAIR STGVOL utility shipped with TSM 5.1.9.0 and TSM 5.2.2.0 may alter the TSM Server Data Base and prevent the TSM Server from being able to be restarted. Who is Affected: TSM servers, on which REPAIR STGVOL has been run without specifying a volume for the utility to repair. I.E. if this utility is run without specifying any parameters, then the symptoms referenced in PQ86959 will be experienced. TSM Servers affected by this problem will not notice the damage until the TSM Server is stopped and then attempted to be restarted, so it is possible to run with the damage to the Data Base for some time before the problem will be encountered. The fix for PQ86959 is targeted to be fixed in levels 5.1.9.2 and 5.2.2.5 of the TSM Server which should be available by May 24, 2004. Recommendation: If this utility must be run, a volume MUST be specified. If possible do not use this utility until the fix for PQ86959 is available. Here is the information from the APAR; REPAIR STGVOL utility provided with IC37275 in 5.1.9.0 can corrupt the server database and prevent the server from being restarted. If the utility command is entered without specifying a specific volume it will create an AS.Volume.Status entry for disk storage pool volumes that will cause abend0C4 during server startup. ANRD Trace-back of called functions: ANRD 0x00010093D118 AsVolRestart ANRD 0x0001009281B4 AsInit ANRD 0x000100978118 ssInit ANRD 0x000100163BD0 admStartServer ANRD 0x000100055028 main ANRD 0x0001000525BC _start ANRD 0x *UNKNOWN* Do not use the REPAIR STGVOL utility without specifying a volume. Additional keywords: Crash dump signal sig 11 segmentation violation LOCAL FIX: If this problem is encountered a point-in-time(PIT) DB restore will need to be done to a PIT prior to when the REPAIR STGVOL command was issued. Classification: Software Category: Backup and Recovery Platform(s): AS/400 or IBM eServer iSeries; Cross-Platform; Intel PC; Netfinity or IBM eServer xSeries; RS/6000 or IBM eServer pSeries; OS/390 or IBM eServer zSeries S/W Pillar(s): Tivoli O/S: OS/400; AIX; HP-UX; Linux; Solaris; OS/2; Windows; MVS; OS/390; VM; z/OS Keywords: REPAIR STGVOL, IC37275, database, corrupt, ANRD, abend0C4, AS.Volume.Status, Crash, dump, signa, sig 11, segmentation violation, server, restarted Cordially, Sam J. Giallanza Tivoli Certified Consultant Field Issues Manager Field Input Communications (FIC) [EMAIL PROTECTED] 520.799.5512 - T/L 321.5512 Our new web Support site and KB is at : http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
Re: Please help me NOT migrate
From: ADSM: Dist Stor Manager on behalf of Eliza Lau >Please help me NOT migrate the server to a different platform from AIX. All right. 1. The only way to move TSM data from one operating system platform to another is by using the export/import functions. 2. Exporting 24TB of data, even running a direct export from the old TSM server to an import on the new server will take days. 3. How to prove this? Perform a fairly simple test. Create a test TSM server on, say a Linux server. Attach enough disk to the Linux server to hold all data for one decent-sized (say, 20GB) TSM client. Run an export from the old server to the new server. Calculate the amount of data moved and the time it takes to perform the export. You're moving data from tape to disk; now figure (roughly) half again as much time will needed to move data from tape to tape. There. You have a base line that you can show to the pointy-haired bosses and say, "It's going to take us a *long* time to move all of this data." With a 3494, a viable alternative is to add a second TSM server and share the library. Start doing your new backups through the new server, and allow the data on the old server to slowly expire away. You will eventually *have* to do an export to move data (particularly archives), but if you allow six to nine months' worth of expiration on the old server, the export will be a lot less painful. (This scenario's gonna go in the FAQ.) -- Mark Stapleton
Re: Please help me NOT migrate
> All right. > > 1. The only way to move TSM data from one operating system platform to another is by > using the export/import functions. > > 2. Exporting 24TB of data, even running a direct export from the old TSM server to > an import on the new server will take days. > > 3. How to prove this? Perform a fairly simple test. Create a test TSM server on, say > a Linux server. Attach enough disk to the Linux server to hold all data for one > decent-sized (say, 20GB) TSM client. Run an export from the old server to the new > server. Calculate the amount of data moved and the time it takes to perform the > export. You're moving data from tape to disk; now figure (roughly) half again as > much time will needed to move data from tape to tape. Yes, this will be a good test on the test solaris server. I will have some good numbers to show the boss. > > There. You have a base line that you can show to the pointy-haired bosses and say, > "It's going to take us a *long* time to move all of this data." > > With a 3494, a viable alternative is to add a second TSM server and share the > library. Start doing your new backups through the new server, and allow the data on > the old server to slowly expire away. You will eventually *have* to do an export to > move data (particularly archives), but if you allow six to nine months' worth of > expiration on the old server, the export will be a lot less painful. This is something I can look into. I can paritiion the 3494 so each server has its own frame, tape drives, and tapes. But will the 3494 control manager get confused when 2 TSM servers try to talk to it at the same time? Doesn't one has to be the Library Manager while the other the 'slave'? Eliza > > (This scenario's gonna go in the FAQ.) > > -- > Mark Stapleton > >
Re: Please help me NOT migrate
My recommendation is to set up a new Solaris server and slowly put new clients on it. Then over time we will move all clients to the new server. But I know it won't fly because it will entail buying a new tape library. Eliza, Would it be feasible to share the 3494 between servers during the transition if it comes to that? I've never done any significant export/import processing, but I can't imagine that given the total downtime to do a one-shot cutover would be acceptable given the number of nodes and volume of data that you're dealing with. My gut feeling is that the downtime for the cutover would be nothing short of horrific, but that's really a hunch on my part. Ted Ted Byrne Blacksburg, VA
Re: Please help me NOT migrate
From: ADSM: Dist Stor Manager on behalf of Eliza Lau This is something I can look into. I can paritiion the 3494 so each server has its own frame, tape drives, and tapes. But will the 3494 control manager get confused when 2 TSM servers try to talk to it at the same time? Doesn't one has to be the Library Manager while the other the 'slave'? No. The 3494 library manager can handle connections to multiple TSM servers. Using a library manager/library client is not necessary in your case. Consult your 3494 manuals on how to set this up. -- Mark Stapleton
Re: Question on LTO-2 dual-path fiber attach drives (AIX platform)
AIX 'Control Path Fallover' is a feature to allow the library robot control path to automatically fail over to a different drive. The Atape driver provides for load balancing and fail over between different routes to the drive. Orville L. Lantto Datatrend Technologies, Inc. (http://www.datatrend.com) IBM Premier Business Partner 121 Cheshire Lane, Suite 700 Minnetonka, MN 55305 Email: [EMAIL PROTECTED] CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Tom Kauffman <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/20/2004 10:33 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Question on LTO-2 dual-path fiber attach drives (AIX platform) It is time to upgrade our tape drives - the current lease is coming up for renewal. I will be replacing LTO-1 SCSI drives with LTO-2 fiber drives. Do I need to get the AIX 'Control Path Fallover' option for TSM to properly recognize that there are two paths to a drive and only use one? My current understanding is that Control Path Fallover will allow TSM to continue a process running against a particular tape and tape drive on the second path if the first fails, as opposed to cancelling the process (and possibly flagging the tape as unavailable). Realisticly, how often does a path fail in the real world? We currently have two 2019-F16 switches and will be adding two more with the tape drives. We also have just the one TSM server and are not currently planning on running anything LAN-free. TIA Tom Kauffman NIBCO, Inc
Re: Please help me NOT migrate
On Tue, 20 Apr 2004 13:45:03 -0400 Eliza Lau <[EMAIL PROTECTED]> wrote thusly: > > This is something I can look into. I can paritiion the 3494 so each > server has its own frame, tape drives, and tapes. But will the 3494 > control manager get confused when 2 TSM servers try to talk to it at the > same time? Doesn't one has to be the Library Manager while the other > the 'slave'? > > Eliza > Nope...just have to assign different private/scratch categories on the second server from the first. The 3494 as it's own built-in library manager that can handle (I think) 32 attached hosts. -Lloyd -- - Lloyd Dieter- Senior Technology Consultant Registered Linux User 285528 Synergy, Inc. http://www.synergyinc.cc [EMAIL PROTECTED] Main:585-389-1260fax:585-389-1267 -
Re: Please help me NOT migrate
> > No. The 3494 library manager can handle connections to multiple TSM servers. Using a > library manager/library client is not necessary in your case. > > Consult your 3494 manuals on how to set this up. > > -- > Mark Stapleton > > Thanks Mark. This will be in my recommendation. Eliza
Re: Please help me NOT migrate
Doesn't it depend? If she wants to dedicate certain drives to certain TSM servers, she can do that simply with the functions built into the 3590 library. Piece of cake, we do that on all our libraries. If she wants to connect the drives to both the AIX and Solaris host at the same time and have them ~share~ the drives, she would need to use the TSM library manager function so that each TSM server knows who is using the drives at any time. Right? Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lloyd Dieter Sent: Tuesday, April 20, 2004 11:59 AM To: [EMAIL PROTECTED] Subject: Re: Please help me NOT migrate On Tue, 20 Apr 2004 13:45:03 -0400 Eliza Lau <[EMAIL PROTECTED]> wrote thusly: > > This is something I can look into. I can paritiion the 3494 so each > server has its own frame, tape drives, and tapes. But will the 3494 > control manager get confused when 2 TSM servers try to talk to it at > the same time? Doesn't one has to be the Library Manager while the > other the 'slave'? > > Eliza > Nope...just have to assign different private/scratch categories on the second server from the first. The 3494 as it's own built-in library manager that can handle (I think) 32 attached hosts. -Lloyd -- - Lloyd Dieter- Senior Technology Consultant Registered Linux User 285528 Synergy, Inc. http://www.synergyinc.cc [EMAIL PROTECTED] Main:585-389-1260fax:585-389-1267 -
Re: Please help me NOT migrate
Yes. Based on the wording in her post, it sounded like she just wanted to attach another (test) host to the library, which, as you say, is easy. But it also sounded like she was thinking of partitioning the 3494 as you would a 3584, with specific slots assigned to each host, which is not necessary (don't even think you *can* do it that way). -Lloyd On Tue, 20 Apr 2004 12:07:50 -0600 Ben Bullock <[EMAIL PROTECTED]> wrote thusly: > Doesn't it depend? > > If she wants to dedicate certain drives to certain TSM servers, > she can do that simply with the functions built into the 3590 library. > Piece of cake, we do that on all our libraries. > > If she wants to connect the drives to both the AIX and Solaris > host at the same time and have them ~share~ the drives, she would need > to use the TSM library manager function so that each TSM server knows > who is using the drives at any time. > > Right? > > Ben > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Lloyd Dieter > Sent: Tuesday, April 20, 2004 11:59 AM > To: [EMAIL PROTECTED] > Subject: Re: Please help me NOT migrate > > > On Tue, 20 Apr 2004 13:45:03 -0400 > Eliza Lau <[EMAIL PROTECTED]> wrote thusly: > > > > > This is something I can look into. I can paritiion the 3494 so each > > server has its own frame, tape drives, and tapes. But will the 3494 > > control manager get confused when 2 TSM servers try to talk to it at > > the same time? Doesn't one has to be the Library Manager while the > > other the 'slave'? > > > > Eliza > > > > > Nope...just have to assign different private/scratch categories on the > second server from the first. > > The 3494 as it's own built-in library manager that can handle (I think) > 32 attached hosts. > > -Lloyd > > -- > - > Lloyd Dieter- Senior Technology Consultant > Registered Linux User 285528 >Synergy, Inc. http://www.synergyinc.cc [EMAIL PROTECTED] > Main:585-389-1260fax:585-389-1267 > - > -- - Lloyd Dieter- Senior Technology Consultant Registered Linux User 285528 Synergy, Inc. http://www.synergyinc.cc [EMAIL PROTECTED] Main:585-389-1260fax:585-389-1267 -
Re: Question on LTO-2 dual-path fiber attach drives (AIX platform )
Thanks for the clarification, Orville. This looks like an option I can easily justify not buying as it doesn't do as much as I thought it did. Tom Kauffman NIBCO, Inc -Original Message- From: Orville Lantto [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 12:53 PM To: [EMAIL PROTECTED] Subject: Re: Question on LTO-2 dual-path fiber attach drives (AIX platform) AIX 'Control Path Fallover' is a feature to allow the library robot control path to automatically fail over to a different drive. The Atape driver provides for load balancing and fail over between different routes to the drive. Orville L. Lantto Datatrend Technologies, Inc. (http://www.datatrend.com) IBM Premier Business Partner 121 Cheshire Lane, Suite 700 Minnetonka, MN 55305 Email: [EMAIL PROTECTED] CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Tom Kauffman <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/20/2004 10:33 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Question on LTO-2 dual-path fiber attach drives (AIX platform) It is time to upgrade our tape drives - the current lease is coming up for renewal. I will be replacing LTO-1 SCSI drives with LTO-2 fiber drives. Do I need to get the AIX 'Control Path Fallover' option for TSM to properly recognize that there are two paths to a drive and only use one? My current understanding is that Control Path Fallover will allow TSM to continue a process running against a particular tape and tape drive on the second path if the first fails, as opposed to cancelling the process (and possibly flagging the tape as unavailable). Realisticly, how often does a path fail in the real world? We currently have two 2019-F16 switches and will be adding two more with the tape drives. We also have just the one TSM server and are not currently planning on running anything LAN-free. TIA Tom Kauffman NIBCO, Inc
Re: Flash 10282 has been published
Well I'm confused. I can't find REPAIR in the 5.2.2 admin guide or admin ref. Anybody know what it is/how to use it? -Original Message- From: Sam Giallanza [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 1:15 PM To: [EMAIL PROTECTED] Subject: Flash 10282 has been published TSM Community : Flash 10282 has been published: http://www-1.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10282 Including the Flash text below : Abstract: TSM Server can not be restarted after running REPAIR STGVOL utility in 5.1.9.0 or 5.2.2.0, if a volume is not specified when the command is issued. Problem: The REPAIR STGVOL utility shipped with TSM 5.1.9.0 and TSM 5.2.2.0 may alter the TSM Server Data Base and prevent the TSM Server from being able to be restarted. Who is Affected: TSM servers, on which REPAIR STGVOL has been run without specifying a volume for the utility to repair. I.E. if this utility is run without specifying any parameters, then the symptoms referenced in PQ86959 will be experienced. TSM Servers affected by this problem will not notice the damage until the TSM Server is stopped and then attempted to be restarted, so it is possible to run with the damage to the Data Base for some time before the problem will be encountered. The fix for PQ86959 is targeted to be fixed in levels 5.1.9.2 and 5.2.2.5 of the TSM Server which should be available by May 24, 2004. Recommendation: If this utility must be run, a volume MUST be specified. If possible do not use this utility until the fix for PQ86959 is available. Here is the information from the APAR; REPAIR STGVOL utility provided with IC37275 in 5.1.9.0 can corrupt the server database and prevent the server from being restarted. If the utility command is entered without specifying a specific volume it will create an AS.Volume.Status entry for disk storage pool volumes that will cause abend0C4 during server startup. ANRD Trace-back of called functions: ANRD 0x00010093D118 AsVolRestart ANRD 0x0001009281B4 AsInit ANRD 0x000100978118 ssInit ANRD 0x000100163BD0 admStartServer ANRD 0x000100055028 main ANRD 0x0001000525BC _start ANRD 0x *UNKNOWN* Do not use the REPAIR STGVOL utility without specifying a volume. Additional keywords: Crash dump signal sig 11 segmentation violation LOCAL FIX: If this problem is encountered a point-in-time(PIT) DB restore will need to be done to a PIT prior to when the REPAIR STGVOL command was issued. Classification: Software Category: Backup and Recovery Platform(s): AS/400 or IBM eServer iSeries; Cross-Platform; Intel PC; Netfinity or IBM eServer xSeries; RS/6000 or IBM eServer pSeries; OS/390 or IBM eServer zSeries S/W Pillar(s): Tivoli O/S: OS/400; AIX; HP-UX; Linux; Solaris; OS/2; Windows; MVS; OS/390; VM; z/OS Keywords: REPAIR STGVOL, IC37275, database, corrupt, ANRD, abend0C4, AS.Volume.Status, Crash, dump, signa, sig 11, segmentation violation, server, restarted Cordially, Sam J. Giallanza Tivoli Certified Consultant Field Issues Manager Field Input Communications (FIC) [EMAIL PROTECTED] 520.799.5512 - T/L 321.5512 Our new web Support site and KB is at : http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManag er.html
Re: Please help me NOT migrate
It is not necessary to have both the AIX and Solaris host share the drives. They will be dedicated to one host only. This 'sharing' of the library will be temporary (we have heard that one before) during the migration of the AIX server to the new solaris server with export/import. Then the migration can be done over time with both servers in production and without significant downtime. To make matters worse, the 3494 is already full. Tapes will have to be pulled out to make room during the migration. Eliza > > Yes. > > Based on the wording in her post, it sounded like she just wanted to > attach another (test) host to the library, which, as you say, is easy. > > But it also sounded like she was thinking of partitioning the 3494 as you > would a 3584, with specific slots assigned to each host, which is not > necessary (don't even think you *can* do it that way). > > -Lloyd > > > On Tue, 20 Apr 2004 12:07:50 -0600 > Ben Bullock <[EMAIL PROTECTED]> wrote thusly: > > > Doesn't it depend? > > > > If she wants to dedicate certain drives to certain TSM servers, > > she can do that simply with the functions built into the 3590 library. > > Piece of cake, we do that on all our libraries. > > > > If she wants to connect the drives to both the AIX and Solaris > > host at the same time and have them ~share~ the drives, she would need > > to use the TSM library manager function so that each TSM server knows > > who is using the drives at any time. > > > > Right? > > > > Ben > > > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > > Lloyd Dieter > > Sent: Tuesday, April 20, 2004 11:59 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Please help me NOT migrate > > > > > > On Tue, 20 Apr 2004 13:45:03 -0400 > > Eliza Lau <[EMAIL PROTECTED]> wrote thusly: > > > > > > > > This is something I can look into. I can paritiion the 3494 so each > > > server has its own frame, tape drives, and tapes. But will the 3494 > > > control manager get confused when 2 TSM servers try to talk to it at > > > the same time? Doesn't one has to be the Library Manager while the > > > other the 'slave'? > > > > > > Eliza > > > > > > > > > Nope...just have to assign different private/scratch categories on the > > second server from the first. > > > > The 3494 as it's own built-in library manager that can handle (I think) > > 32 attached hosts. > > > > -Lloyd > > > > -- > > - > > Lloyd Dieter- Senior Technology Consultant > > Registered Linux User 285528 > >Synergy, Inc. http://www.synergyinc.cc [EMAIL PROTECTED] > > Main:585-389-1260fax:585-389-1267 > > - > > > > > -- > - > Lloyd Dieter- Senior Technology Consultant > Registered Linux User 285528 >Synergy, Inc. http://www.synergyinc.cc [EMAIL PROTECTED] > Main:585-389-1260fax:585-389-1267 > - >
Re: checkout DB2 backup [Virus checked]
Well, if you problem is just getting them out of the 3484, all you have to do is mark them as OFFSITE and run the CHECKOUT command. Keeping track of them is another matter entirely. If this is something you plan to do regularly, look at a product called Autovault at www.coderelief.com. We use it here for vaulting with TSM. You would put your future DB2 backups into a DIFFERENT tape storage pool, and tell Autovault to manage the vaulting of that storage pool. DRM will do similar for copy pools, but not primary pools. -Original Message- From: Frank Mueller [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 9:14 AM To: [EMAIL PROTECTED] Subject: checkout DB2 backup [Virus checked] Hi *, we want to check out a DB2-backup. We backup our DB2-DB over the DB2-api in the TSM. The data are stored in a 3494 library. Now we want to move the tapes in a other location (out of the library, for example a safe). What is the best way to move the data out of the library??? Best regards, Frank
Re: Flash 10282 has been published
Hi Wanda, try www.ibm.com and searching on: +"repair stgvol" +tsm to find some hits. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Prather, Wanda" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/20/2004 11:54 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Flash 10282 has been published Well I'm confused. I can't find REPAIR in the 5.2.2 admin guide or admin ref. Anybody know what it is/how to use it? -Original Message- From: Sam Giallanza [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 1:15 PM To: [EMAIL PROTECTED] Subject: Flash 10282 has been published TSM Community : Flash 10282 has been published: http://www-1.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10282 Including the Flash text below : Abstract: TSM Server can not be restarted after running REPAIR STGVOL utility in 5.1.9.0 or 5.2.2.0, if a volume is not specified when the command is issued. Problem: The REPAIR STGVOL utility shipped with TSM 5.1.9.0 and TSM 5.2.2.0 may alter the TSM Server Data Base and prevent the TSM Server from being able to be restarted. Who is Affected: TSM servers, on which REPAIR STGVOL has been run without specifying a volume for the utility to repair. I.E. if this utility is run without specifying any parameters, then the symptoms referenced in PQ86959 will be experienced. TSM Servers affected by this problem will not notice the damage until the TSM Server is stopped and then attempted to be restarted, so it is possible to run with the damage to the Data Base for some time before the problem will be encountered. The fix for PQ86959 is targeted to be fixed in levels 5.1.9.2 and 5.2.2.5 of the TSM Server which should be available by May 24, 2004. Recommendation: If this utility must be run, a volume MUST be specified. If possible do not use this utility until the fix for PQ86959 is available. Here is the information from the APAR; REPAIR STGVOL utility provided with IC37275 in 5.1.9.0 can corrupt the server database and prevent the server from being restarted. If the utility command is entered without specifying a specific volume it will create an AS.Volume.Status entry for disk storage pool volumes that will cause abend0C4 during server startup. ANRD Trace-back of called functions: ANRD 0x00010093D118 AsVolRestart ANRD 0x0001009281B4 AsInit ANRD 0x000100978118 ssInit ANRD 0x000100163BD0 admStartServer ANRD 0x000100055028 main ANRD 0x0001000525BC _start ANRD 0x *UNKNOWN* Do not use the REPAIR STGVOL utility without specifying a volume. Additional keywords: Crash dump signal sig 11 segmentation violation LOCAL FIX: If this problem is encountered a point-in-time(PIT) DB restore will need to be done to a PIT prior to when the REPAIR STGVOL command was issued. Classification: Software Category: Backup and Recovery Platform(s): AS/400 or IBM eServer iSeries; Cross-Platform; Intel PC; Netfinity or IBM eServer xSeries; RS/6000 or IBM eServer pSeries; OS/390 or IBM eServer zSeries S/W Pillar(s): Tivoli O/S: OS/400; AIX; HP-UX; Linux; Solaris; OS/2; Windows; MVS; OS/390; VM; z/OS Keywords: REPAIR STGVOL, IC37275, database, corrupt, ANRD, abend0C4, AS.Volume.Status, Crash, dump, signa, sig 11, segmentation violation, server, restarted Cordially, Sam J. Giallanza Tivoli Certified Consultant Field Issues Manager Field Input Communications (FIC) [EMAIL PROTECTED] 520.799.5512 - T/L 321.5512 Our new web Support site and KB is at : http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManag er.html
Re: permanent delete of an backuped-up object?
One method is to define a mgmt class with zero versions deleted, use include/exclude to backup the object and rebind it to the new class, then either delete the object or exclude it from backup, and it will be deleted on the next backup. -Original Message- From: Salak Juraj [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 9:40 AM To: [EMAIL PROTECTED] Subject: permanent delete of an backuped-up object? hi all, there has been a method how to permanently delete an already backed-up object, canm someone give me a quick hint? Juraj
Re: Delete obsolete directories only?
Hi, Debbie, Tab. You'll have to rebind those objects. Since they're inactive, it'll be really fun. In fact, it's probably not worth doing all the steps in Option 2 if you have a lot of objects, but it's a fun exercise anyway. Option 1) This is the easiest if you're a C programmer. Use the TSM API and some custom C code. I haven't tried this, but I don't recall reading anything that says the dsmUpdateObj call has to be used against an active object. The API manual says: "You can also rebind backup copies to a different management class by using the dsmUpdateObj call and the DSM_BACKUPD_MC action." Option 2) Let's say /FSNAME is the filespace name of the inactive object, and OBJECT is the object name. First you create a management class with RETEXTRA and RETONLY of 0, or use an existing one with a short enough retention for your requirements. You create the filesystem /FSNAME. You create a small file in /FSNAME called OBJECT. You back it up using the baclient and bind it to the management class you created. It'll rebind both the file and your inactive database objects with the same HL_NAME and LL_NAME. Then you delete OBJECT from the /FSNAME filesystem, then dsmc inc /FSNAME/OBJECT again, or use the expire command. It'll expire it, then during your next expiration process it'll go away. What gets fun is in Windows, like Tab's problem. You actually have to create a new drive, say, \\servername\q$. Then you create your OBJECT file path and whatnot under there, then on the TSM server do a "rename filesystem" to go from \\servername\f$ to \\servername\q$. Then do your backups, rebinding, and delete/expire, then rename the filesystem back. As I said, it's a lot of fun. Gotchas to watch out for are the possibility of inactivating all your good stuff if you just dsmc inc /FSNAME, or rebinding stuff you don't want rebound. You might want to test first. :-) I've actually used this process to get rid of a few DB2 backups. It was a while ago, so I might be missing a few steps. And in Tab's case, he'll probably want to write a script to create all those directories, rebind, delete, etc. Good luck! Alex Paschal Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Weeks, Debbie [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 6:30 AM To: [EMAIL PROTECTED] Subject: Re: Delete obsolete directories only? Thanks Steve. We have used the expire command, but this only seems to mark them inactive. Because the management class they are assigned to holds the only version forever, or until it knows the file has been deleted, they are marked inactive, but never go away. Any suggestions for completing the process and having them expire completely? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steve Harris Sent: Monday, April 19, 2004 7:12 PM To: [EMAIL PROTECTED] Subject: Re: Delete obsolete directories only? Debbie, I'm not familiar with sql backtrack but... I've used the normal BA client to delete orphan DB2 backups in the past. These are archives and I used the delete archive command. If sql backtrack uses backups rather than archives, then take a look at the ba client expire command Because these are API backups, to address them from the BA client you need to use a special syntax with braces around the "filespace" part of the file name. See the BA client doc for details. Regards Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia >>> [EMAIL PROTECTED] 20/04/2004 0:04:23 >>> I have not seen a response to this question, and I have a similar situation. We had noticed that our filespaces for our Oracle DB backups keep growing in leaps and bounds, and it finally became clear that they were growing faster than would be expected in consideration of the number of databases we have added. Upon investigation I have found that there is an enormous amount of space being used by backups that should have expired, however I cannot delete the entire filespace because that would also eliminate the valid backups. I have found that there seems to be two separate issues at play. One is that upon installing a new version of SQL Backtrack the Oracle admin that handles those profiles used the wrong management class, leaving the backups in limbo on TSM. They have expired from the SQL Backtrack catalog and marked inactive, however, they will never be removed from TSM in their current state. I cannot bind them to the appropriate management class via the usual methods. The other issue is that we seem to have some stragglers from 2001 and 2002, that should have expired, but are still hanging around for some reason. The only way I have found in the documentation to remove these items is by deleting the object by object number from the database. Can anyone tell me if this is the only way to clean up these items, and if that will in fact work to remove them from the tapepool storage? TSM for AIX 5.2.0 TSM for SU
Re: SQLBacktrack Expiry issue
Debbie Your management class setup seems incorrect to me. The only way for a backup to be deleted is that 1. it must expire 2. it must age off through verexists/verdeleted/retextra/retonly If your parameters are such that an expired file never is deleted, then that explains why your backups are taking so much space. They will *never* be deleted. Most api products that use backups generate unique filenames, and so require parameters of 1/0/0/0. This causes the uniquely named backup to be deleted once the product marks it as expired. I don't know that SQLBacktrack is, or is not, in this category. I suggest that you check your sqlbackup documentation and make sure that the management classes are set up as it specifies. Apologies in advance if you've already done this :) Steve. >>> [EMAIL PROTECTED] 21/04/2004 7:32:07 >>> Hi, Debbie, Tab. You'll have to rebind those objects. Since they're inactive, it'll be really fun. In fact, it's probably not worth doing all the steps in Option 2 if you have a lot of objects, but it's a fun exercise anyway. Option 1) This is the easiest if you're a C programmer. Use the TSM API and some custom C code. I haven't tried this, but I don't recall reading anything that says the dsmUpdateObj call has to be used against an active object. The API manual says: "You can also rebind backup copies to a different management class by using the dsmUpdateObj call and the DSM_BACKUPD_MC action." Option 2) Let's say /FSNAME is the filespace name of the inactive object, and OBJECT is the object name. First you create a management class with RETEXTRA and RETONLY of 0, or use an existing one with a short enough retention for your requirements. You create the filesystem /FSNAME. You create a small file in /FSNAME called OBJECT. You back it up using the baclient and bind it to the management class you created. It'll rebind both the file and your inactive database objects with the same HL_NAME and LL_NAME. Then you delete OBJECT from the /FSNAME filesystem, then dsmc inc /FSNAME/OBJECT again, or use the expire command. It'll expire it, then during your next expiration process it'll go away. What gets fun is in Windows, like Tab's problem. You actually have to create a new drive, say, \\servername\q$. Then you create your OBJECT file path and whatnot under there, then on the TSM server do a "rename filesystem" to go from \\servername\f$ to \\servername\q$. Then do your backups, rebinding, and delete/expire, then rename the filesystem back. As I said, it's a lot of fun. Gotchas to watch out for are the possibility of inactivating all your good stuff if you just dsmc inc /FSNAME, or rebinding stuff you don't want rebound. You might want to test first. :-) I've actually used this process to get rid of a few DB2 backups. It was a while ago, so I might be missing a few steps. And in Tab's case, he'll probably want to write a script to create all those directories, rebind, delete, etc. Good luck! Alex Paschal Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Weeks, Debbie [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 6:30 AM To: [EMAIL PROTECTED] Subject: Re: Delete obsolete directories only? Thanks Steve. We have used the expire command, but this only seems to mark them inactive. Because the management class they are assigned to holds the only version forever, or until it knows the file has been deleted, they are marked inactive, but never go away. Any suggestions for completing the process and having them expire completely? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steve Harris Sent: Monday, April 19, 2004 7:12 PM To: [EMAIL PROTECTED] Subject: Re: Delete obsolete directories only? Debbie, I'm not familiar with sql backtrack but... I've used the normal BA client to delete orphan DB2 backups in the past. These are archives and I used the delete archive command. If sql backtrack uses backups rather than archives, then take a look at the ba client expire command Because these are API backups, to address them from the BA client you need to use a special syntax with braces around the "filespace" part of the file name. See the BA client doc for details. Regards Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia >>> [EMAIL PROTECTED] 20/04/2004 0:04:23 >>> I have not seen a response to this question, and I have a similar situation. We had noticed that our filespaces for our Oracle DB backups keep growing in leaps and bounds, and it finally became clear that they were growing faster than would be expected in consideration of the number of databases we have added. Upon investigation I have found that there is an enormous amount of space being used by backups that should have expired, however I cannot delete the entire filespace because that would also eliminate the valid backups. I have found that there seems to be two separate issues at
Re: Change the default database name on TSM server
Hi, Thank for your help. As you said " if you have more than one Oracle database, back up each Oracle target database to its own file space on the Tivoli Storage Manager server". I assume that these Oracle databases are on the same machine. Could you help me to implement, pls ? Thanks in advanced, Nghiatd - Original Message - From: Thomas Rupp, Vorarlberger Illwerke AG To: [EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 2:33 PM Subject: AW: Change the default database name on TSM server Hi, you should use TDPO_FS in tdpo.opt. If you change the filespacename on the TSM server be sure to set TDPO_FS correctly. The filespacename on the TSM server and TDPO_FS have to be in sync. See "Tivoli Data Protection for Oracle - Installation and User's Guide" TDPO_FS This option specifies a file space name on the Tivoli Storage Manager server which TDP for Oracle uses for backup, delete, and restore operations. The file-space name is a string of 1 to 1024 characters. When setting up this option, do not use a directory delimiter in front of the filespace name. If this option is set during TDP for Oracle backup operations, this option must also be set during restore and delete operations. If you have more than one Oracle database, back up each Oracle target database to its own file space on the Tivoli Storage Manager server. The default file space name is adsmorc. HTH Thomas Rupp -Ursprüngliche Nachricht- Von: nghiatd [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 20. April 2004 09:24 An: [EMAIL PROTECTED] Betreff: Change the default database name on TSM server Hi all, I use TDP and RMAN to backup database for Oracle. By default, TSM server storages database that was backuped with name : \adsmorc. I want to change this default name on TSM server. Does anyone know how to change it ? Thanks in advanced ! Nghiatd,
