TSM Server Software differences
Hi List Members, we want to upgrade our Windows TSM Server (Extended Edition) from Version 5.2.4.2 to Version 5.4.1.x. I asked our authorized colleague for downloading the TSM Server Base Version 5.4.0. Now he told me, there are to Versions: -IBM Tivoli Storage Manager V5.4 Windows Server, Multilingual(C97LVML) -IBM Tivoli Storage Manager Extended Edition v5.4 Quick Start, Windows, Multilingual(C97KHML) Can you tell me, what the difference between this two Versions? With kind regards, Boris Herrmann
Unable to delete volhist entries
Hi TSMer's, At our TSM Server 5.3.4 on AIX 5.3 we use a deviceclass devtype FILE for database snapshots. tsm: TSM1q devclass FILE32G f=d Device Class Name: FILE32G Device Access Strategy: Sequential Storage Pool Count: 0 Device Type: FILE Format: DRIVE Est/Max Capacity (MB): 32,768.0 Mount Limit: 20 Mount Wait (min): Mount Retention (min): Label Prefix: Library: Directory: /usr/tivoli/tsm/server/pools/file Server Name: Retry Period: Retry Interval: Shared: High-level Address: Minimum Capacity: WORM: No Drive Encryption: Scaled Capacity: Last Update by (administrator): TSMADMIN Last Update Date/Time: 05/24/2006 11:55:52 And there is one snapshot: tsm: TSM1q volhist t=dbs Date/Time: 01/08/2007 15:52:41 Volume Type: DBSNAPSHOT Backup Series: 2 Backup Operation: 0 Volume Seq: 1 Device Class: FILE32G Volume Name: /usr/tivoli/tsm/server/pools/file/68267961.DBS Volume Location: Command: Date/Time: 01/08/2007 15:52:41 Volume Type: DBSNAPSHOT Backup Series: 2 Backup Operation: 0 Volume Seq: 2 Device Class: FILE32G Volume Name: /usr/tivoli/tsm/server/pools/file/68268400.DBS Volume Location: Command: Date/Time: 01/08/2007 15:52:41 Volume Type: DBSNAPSHOT Backup Series: 2 Backup Operation: 0 Volume Seq: 3 Device Class: FILE32G Volume Name: /usr/tivoli/tsm/server/pools/file/68269158.DBS Volume Location: Command: Date/Time: 01/08/2007 15:52:41 Volume Type: DBSNAPSHOT Backup Series: 2 Backup Operation: 0 Volume Seq: 4 Device Class: FILE32G Volume Name: /usr/tivoli/tsm/server/pools/file/68269707.DBS Volume Location: Command: Date/Time: 01/08/2007 15:52:41 Volume Type: DBSNAPSHOT Backup Series: 2 Backup Operation: 0 Volume Seq: 5 Device Class: FILE32G Volume Name: /usr/tivoli/tsm/server/pools/file/68270170.DBS Volume Location: Command: Date/Time: 01/08/2007 15:52:41 Volume Type: DBSNAPSHOT Backup Series: 2 Backup Operation: 0 Volume Seq: 6 Device Class: FILE32G Volume Name: /usr/tivoli/tsm/server/pools/file/68270899.DBS Volume Location: Command: To delete that snapshot from volhist we entered following: tsm: TSM1del volhist todate=today totime=now type=DBSNAPSHOT devclass=FILE32G ANR6978E DELETE VOLHISTORY: Invalid device class FILE32G. ANS8001I Return code 3. After that we ommited the DEVC: tsm: TSM1del volhist todate=today totime=now type=DBSNAPSHOT Do you wish to proceed? (Yes (Y)/No (N)) y ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. Any suggestions how to delete the entries ? TIA, Otto TSM Administration Medical University of Vienna
Re: TSM Server Software differences
IBM Tivoli Storage Manager Extended Edition v5.4 Quick Start, Windows, Multilingual(C97KHML) is documentation AFAIK On 10/1/07, Herrmann, Boris [EMAIL PROTECTED] wrote: Hi List Members, we want to upgrade our Windows TSM Server (Extended Edition) from Version 5.2.4.2 to Version 5.4.1.x. I asked our authorized colleague for downloading the TSM Server Base Version 5.4.0. Now he told me, there are to Versions: -IBM Tivoli Storage Manager V5.4 Windows Server, Multilingual(C97LVML) -IBM Tivoli Storage Manager Extended Edition v5.4 Quick Start, Windows, Multilingual(C97KHML) Can you tell me, what the difference between this two Versions? With kind regards, Boris Herrmann
AW: [ADSM-L] TSM Server Software differences
Yes, you are right! I've told my colleague to download the Quick Start SW. It's a collection of documentation ;-) Thanks... Boris -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von goc Gesendet: Montag, 1. Oktober 2007 10:57 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] TSM Server Software differences IBM Tivoli Storage Manager Extended Edition v5.4 Quick Start, Windows, Multilingual(C97KHML) is documentation AFAIK On 10/1/07, Herrmann, Boris [EMAIL PROTECTED] wrote: Hi List Members, we want to upgrade our Windows TSM Server (Extended Edition) from Version 5.2.4.2 to Version 5.4.1.x. I asked our authorized colleague for downloading the TSM Server Base Version 5.4.0. Now he told me, there are to Versions: -IBM Tivoli Storage Manager V5.4 Windows Server, Multilingual(C97LVML) -IBM Tivoli Storage Manager Extended Edition v5.4 Quick Start, Windows, Multilingual(C97KHML) Can you tell me, what the difference between this two Versions? With kind regards, Boris Herrmann
Re: Adding new 3292JA to ATL as scratch tapes
Hi Troy, I think you have to label the tapes: labe libv library name label of the tape checkin=scr With regards, Ruud Meuleman -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Allen Cross (YSU) Sent: Friday, September 28, 2007 7:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Adding new 3292JA to ATL as scratch tapes ADSM-L, I've tried both of these commands: checkin libvolume ysuatl01 a00100 search=no status=scratch checklabel=yes devtype=3592 checkin libvolume ysuatl01 search=yes volrange=a00100,a00119 status=scratch checklabel=yes devtype=3592 Do I need to do something under AIX first? I've inserted them in the library. How can I verify that they are in Insert Mode? Sincerely, Troy Troy Allen Cross Manager, Operations Technical Support Youngstown State University 410 Meshel Hall, Computer Services One University Plaza Youngstown, OH 44555 -Original Message- From: Troy Allen Cross (YSU) [mailto:[EMAIL PROTECTED] Sent: Thursday, September 27, 2007 5:07 PM To: 'ADSM-L@VM.MARIST.EDU' Subject: Adding new 3292JA to ATL as scratch tapes ADSM-l, What TSM commands must I execute to properly add new 3292JA tapes to my ATL as scratch tapes? Thanks in advance, Troy Troy Allen Cross Manager, Operations Technical Support Youngstown State University 410 Meshel Hall, Computer Services One University Plaza Youngstown, OH 44555
Re: Tivoli SQL Server 2000 Restore Question*
Del, Thanks again for your response. Tim Del Hoobler wrote: Tim, Yes... you are on the right track. Take a look in the appendices of the Data Protection for SQL User's Guide. It shows how to restore master and msdb. Note: When you restore master, you will see an error at the end of the restore procedure. That is normal. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 09/28/2007 02:22:18 PM: Default *SQL Server 2000 Restore Question* I am restoring a SQL Server 2000 from scratch. The server has been built and SQL has been installed and service packed to the appropriate level. I am ready to restore the databases now to the fresh installation of SQL Server. Is this the correct procedure when only the default databases exist? Start SQL in single user mode. Restore Master database. Start SQL in multi user mode and restore msdb and model. Restore the database files? Thanks for any help or suggestions in advance! TSM 5.3 Windows 2000 advance server TDP 5.2.4 Tivoli Client 5.3.4
Re: Unable to delete volhist entries
On Oct 1, 2007, at 4:48 AM, Otto Chvosta wrote: ... ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. Any suggestions how to delete the entries ? Otto - There is really one entry, for a single backup series (#2), consisting of multiple volumes. As TSM documentation says, it doesn't want you to destroy your last/only database backup. (See Technote 1083952.) You could supplant the old snapshot with a new one, or try adding FORCE=Yes to the delete. Richard Sims http://people.bu.edu/rbs/
ANS1035S Options file dsm.opt could not be found
Hello all We recently a a problem with a Windows server in a Cluster enivronment and the client had to change one of the drives that was being backed up (lomagicionquorum for drive q to drive w) we changed the dsm.opt file to point to the W drive but the backup is still missing. The following error is in the dsmerror.log. ANS1035S Options file 'q:\tsm\dsm.opt' could not be found. ANS1035S Options file 'q:\tsm\dsm.opt' could not be found. ANS1035S Options file 'q:\tsm\dsm.opt' could not be found. ANS1035S Options file 'q:\tsm\dsm.opt' could not be found. ANS1035S Options file 'q:\tsm\dsm.opt' could not be found. ANS1035S Options file 'q:\tsm\dsm.opt' could not be found. ANS1035S Options file 'q:\tsm\dsm.opt' could not be found. ANS1035S Options file 'q:\tsm\dsm.opt' could not be found. I have read some posts and Richard sims facts but they seem to refer to the UNIX environment. How do we get this to back up the q drive? Is there something else that needs to be updated? Thanks for any help or suggestions in Advance. TSM server 5.3.4 AIX 5.3 TSM Windows client 5.3.4 Windows server 2003
Re: Unable to delete volhist entries
In the help of del volh command, you can find : DBSnapshot Specifies to delete only records that contain information about volumes used for snapshot database backups, and that meet the specified date and time criteria. The latest snapshot database backup will not be deleted. DEVclass=classname Specifies the device class name that was used to create the database backups. This optional parameter can be used to delete database backups created using a server-to-server virtual volume device class. The type of the device class must be SERVER. This parameter can only be used to delete volume history entries of type BACKUPFULL, BACKUPINCR, or DBSNAPSHOT. A full, incremental, or snapshot database backup volume is eligible to be deleted if all of the following conditions are met: + The device class used to create the database backup volume matches the specified device class + The volume was created on or before the specified date and time + The volume is not part of the latest full plus incremental database backup series if the specified volume type is DBBackup, or snapshot database backup series if the volume type is DBSnapshot You can try : del volh t=dbs force=y tod=today Regards, Pierre Cayé -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Richard Sims Envoyé : lundi 1 octobre 2007 13:18 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] Unable to delete volhist entries On Oct 1, 2007, at 4:48 AM, Otto Chvosta wrote: ... ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. Any suggestions how to delete the entries ? Otto - There is really one entry, for a single backup series (#2), consisting of multiple volumes. As TSM documentation says, it doesn't want you to destroy your last/only database backup. (See Technote 1083952.) You could supplant the old snapshot with a new one, or try adding FORCE=Yes to the delete. Richard Sims http://people.bu.edu/rbs/
Re: DB2 Logs in TSM
Thanks for the help! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob Booth Sent: Thursday, September 27, 2007 10:02 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] DB2 Logs in TSM On Thu, Sep 27, 2007 at 09:23:33AM -0500, Collins, Brenda wrote: Good morning! Does anyone have a select command that would let me see all the archive logs that exist within TSM for a DB2 node ? Somehow they have logs for a particular database under two different node names. They don't know when it was changed but need to know how many logs are out there under the old node name. (Of course, they need a restore from one of them as well.) TSM Server 5.4.0.2 TSM Client 5.4.0.0 DB2 8.0 Select * from archives where node_name=XX That is usually what I use on our DB2 nodes. hth, bob ___ CONFIDENTIALITY AND PRIVACY NOTICE Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com
moving a 3494 library (resend)
didn't get a ack, so resending... There are two TSM servers, one at SiteA, the 2nd at SiteB SiteA manages two 3494 tape libraries, one at SiteA and the 2nd at SiteB (connected via longwave fibre), and is the tape library manager for both TSM servers. The 3494 at SiteB is defined at shared. All the volumes on the tape library at SiteB are now owned by the TSM server at SiteB. The goal is to remove the client instance and have ServerB locally manage the library, and retain its current volumes. The suggested procedure / sequence is: 1). Checkout the vols in the library at SiteB 2). Remove the 3494 defs for the 3494 at SiteB from the TSM server at SiteA 3). Remove and redefine the library on the TSM server at SiteB (non-shared) 4). Checkin the vols (private) in SiteB 5). Remove references in volhist on SiteA to volumes in 3494 in SiteB. Anyone see a problem with this sequence?
moving a 3494 library
There are two TSM servers, one at SiteA, the 2nd at SiteB SiteA manages two 3494 tape libraries, one at SiteA and the 2nd at SiteB (connected via longwave fibre), and is the tape library manager for both TSM servers. The 3494 at SiteB is defined at shared. All the volumes on the tape library at SiteB are now owned by the TSM server at SiteB. The goal is to remove the client instance and have ServerB locally manage the library, and retain its current volumes. The suggested procedure / sequence is: 1). Checkout the vols in the library at SiteB 2). Remove the 3494 defs for the 3494 at SiteB from the TSM server at SiteA 3). Remove and redefine the library on the TSM server at SiteB (non-shared) 4). Checkin the vols (private) in SiteB 5). Remove references in volhist on SiteA to volumes in 3494 in SiteB. Anyone see a problem with this sequence?
AW: [ADSM-L] Unable to delete volhist entries
Thank you ! In the future I'll read a little bit slower ;-) ( ... latest snapshot database backup will not be deleted.) Regards, Otto -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von CAYE PIERRE Gesendet: Montag, 1. Oktober 2007 13:40 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] Unable to delete volhist entries In the help of del volh command, you can find : DBSnapshot Specifies to delete only records that contain information about volumes used for snapshot database backups, and that meet the specified date and time criteria. The latest snapshot database backup will not be deleted. DEVclass=classname Specifies the device class name that was used to create the database backups. This optional parameter can be used to delete database backups created using a server-to-server virtual volume device class. The type of the device class must be SERVER. This parameter can only be used to delete volume history entries of type BACKUPFULL, BACKUPINCR, or DBSNAPSHOT. A full, incremental, or snapshot database backup volume is eligible to be deleted if all of the following conditions are met: + The device class used to create the database backup volume matches the specified device class + The volume was created on or before the specified date and time + The volume is not part of the latest full plus incremental database backup series if the specified volume type is DBBackup, or snapshot database backup series if the volume type is DBSnapshot You can try : del volh t=dbs force=y tod=today Regards, Pierre Cayé -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Richard Sims Envoyé : lundi 1 octobre 2007 13:18 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] Unable to delete volhist entries On Oct 1, 2007, at 4:48 AM, Otto Chvosta wrote: ... ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. Any suggestions how to delete the entries ? Otto - There is really one entry, for a single backup series (#2), consisting of multiple volumes. As TSM documentation says, it doesn't want you to destroy your last/only database backup. (See Technote 1083952.) You could supplant the old snapshot with a new one, or try adding FORCE=Yes to the delete. Richard Sims http://people.bu.edu/rbs/
Re: AW: [ADSM-L] Unable to delete volhist entries
But a force works. I just tried it. :) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Otto Chvosta Sent: Monday, October 01, 2007 10:06 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] AW: [ADSM-L] Unable to delete volhist entries Thank you ! In the future I'll read a little bit slower ;-) ( ... latest snapshot database backup will not be deleted.) Regards, Otto -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von CAYE PIERRE Gesendet: Montag, 1. Oktober 2007 13:40 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] Unable to delete volhist entries In the help of del volh command, you can find : DBSnapshot Specifies to delete only records that contain information about volumes used for snapshot database backups, and that meet the specified date and time criteria. The latest snapshot database backup will not be deleted. DEVclass=classname Specifies the device class name that was used to create the database backups. This optional parameter can be used to delete database backups created using a server-to-server virtual volume device class. The type of the device class must be SERVER. This parameter can only be used to delete volume history entries of type BACKUPFULL, BACKUPINCR, or DBSNAPSHOT. A full, incremental, or snapshot database backup volume is eligible to be deleted if all of the following conditions are met: + The device class used to create the database backup volume matches the specified device class + The volume was created on or before the specified date and time + The volume is not part of the latest full plus incremental database backup series if the specified volume type is DBBackup, or snapshot database backup series if the volume type is DBSnapshot You can try : del volh t=dbs force=y tod=today Regards, Pierre Cayé -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Richard Sims Envoyé : lundi 1 octobre 2007 13:18 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] Unable to delete volhist entries On Oct 1, 2007, at 4:48 AM, Otto Chvosta wrote: ... ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. Any suggestions how to delete the entries ? Otto - There is really one entry, for a single backup series (#2), consisting of multiple volumes. As TSM documentation says, it doesn't want you to destroy your last/only database backup. (See Technote 1083952.) You could supplant the old snapshot with a new one, or try adding FORCE=Yes to the delete. Richard Sims http://people.bu.edu/rbs/ - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
AW: [ADSM-L] Adding new 3292JA to ATL as scratch tapes
AIX mtlib command to list all tapes which are category insert (3494): # mtlib -l /dev/lmcp0 -qC -s FF00 Regards, Otto -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Troy Allen Cross (YSU) Gesendet: Freitag, 28. September 2007 19:49 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] Adding new 3292JA to ATL as scratch tapes ADSM-L, I've tried both of these commands: checkin libvolume ysuatl01 a00100 search=no status=scratch checklabel=yes devtype=3592 checkin libvolume ysuatl01 search=yes volrange=a00100,a00119 status=scratch checklabel=yes devtype=3592 Do I need to do something under AIX first? I've inserted them in the library. How can I verify that they are in Insert Mode? Sincerely, Troy Troy Allen Cross Manager, Operations Technical Support Youngstown State University 410 Meshel Hall, Computer Services One University Plaza Youngstown, OH 44555 -Original Message- From: Troy Allen Cross (YSU) [mailto:[EMAIL PROTECTED] Sent: Thursday, September 27, 2007 5:07 PM To: 'ADSM-L@VM.MARIST.EDU' Subject: Adding new 3292JA to ATL as scratch tapes ADSM-l, What TSM commands must I execute to properly add new 3292JA tapes to my ATL as scratch tapes? Thanks in advance, Troy Troy Allen Cross Manager, Operations Technical Support Youngstown State University 410 Meshel Hall, Computer Services One University Plaza Youngstown, OH 44555
Migration question
I have a question that I feel a little stupid in asking. What is the difference between migration and backup primary (disk) to copy (tape)? I am working on changing my scheduling up and the recommended order of steps I was given is: Backup clients Migration Backup primary to copy Backup db Expiration Reclamation Start all over again Thanks!
Re: Migration question
Migration involves moving between primary storage pools. The conventional situation was ( before VTLs) a site would have a hierarchy of storage. The clients would back up to disks to permits a large number of concurrent backups, then those backups to disk would be migrated to tape. Both are primary storage pools. Copypools are copies of data in primary storage pools. Their purpose is to provide for the loss of data in the primary pools and are populated using backup stg to the copypool. Fio example, a tape volume goes bad in your primary storage pool, you can recover it from the copypool. Copypools are also used at some sites for vaulting. The copies of the primary data that is created on the copypools is sent offsite. - Original Message - From: Dollens, Bruce [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 01, 2007 12:35 PM Subject: [ADSM-L] Migration question I have a question that I feel a little stupid in asking. What is the difference between migration and backup primary (disk) to copy (tape)? I am working on changing my scheduling up and the recommended order of steps I was given is: Backup clients Migration Backup primary to copy Backup db Expiration Reclamation Start all over again Thanks!
Re: Migration question
Migration moves the data from one primary pool to another. A storage pool backup is copying the data from a primary storage pool to a copy storage pool. Mark Remeta -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dollens, Bruce Sent: Monday, October 01, 2007 12:36 PM To: ADSM-L@VM.MARIST.EDU Subject: Migration question I have a question that I feel a little stupid in asking. What is the difference between migration and backup primary (disk) to copy (tape)? I am working on changing my scheduling up and the recommended order of steps I was given is: Backup clients Migration Backup primary to copy Backup db Expiration Reclamation Start all over again Thanks! Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately. Please be advised that someone other than the intended recipients, including a third-party in the Seligman organization and government agencies, may review all electronic communications to and from this address.
Domino Password problem. Confused
Hi there. I am confused with this password for domino. After running well for sometime, message as below will appeared. I have 6 notes server backup via TSM. All of the will have this problem after sometime. If query via TSM CLI . q eve * * , the backup shows completed. If check from the log, show Authentication failure. What I always do to store the password are: 1. At domino CLI : domdsmc q dbb /adsmpwd=x 2. At TSM CLI: update node NOTES1 x The question arises, which password has expired, TSM NODE or API domino? How to make both of them password never expire. ( For TSM node, update node NOTES1 admin passexp=0 ) for domino ? I gather info from internet, says the domino password file is corrupted. Is there any relation with the above statement which I mention? Thanks in advance. Zul Malaysia. TSM Server Ver 5.3.0.0 AIX 5.3 == IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino Version 5, Release 3, Level 0.0 (C) Copyright IBM Corporation 1999, 2004. All rights reserved. ACD5221I The /usr/tivoli/tsm/client/domino/bin/domdsmc_notes/dominc.log log file has been pruned successfully. Starting Domino database backup... Initializing Domino connection... Querying Domino for a list of databases, please wait... Logging on to the Tivoli Storage Manager server, please wait... ACD5025E PASSWORDACCESS is Generate. Either the stored password is incorrect or there is no stored password. If you do not have a stored password, use of the -ADSMPWD=xxx option will set and store your password. Total Domino databases inspected: 3,373 Total Domino databases backed up: 0 Total Domino databases excluded: 0 Total Domino backup objects expired: 0 Throughput rate: 0.00 Kb/Sec Total bytes transferred: 0 Elapsed processing time: 0.00 Secs ANS1025E (RC137) Session rejected: Authentication failure =
Re: Migration question
And about your sequence list. - Expiration will trigger the reclamations - You might want to schedule your backup primary to copy prior to your migration. Assuming you are backing up to disk, then migrating to tape. That way, you avoid the overhead of mounts of tapes when you are creating copypool volumes from primary storage pool volumes ( that have been migrated from disk to tape.). - Original Message - From: Dollens, Bruce [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 01, 2007 12:35 PM Subject: [ADSM-L] Migration question I have a question that I feel a little stupid in asking. What is the difference between migration and backup primary (disk) to copy (tape)? I am working on changing my scheduling up and the recommended order of steps I was given is: Backup clients Migration Backup primary to copy Backup db Expiration Reclamation Start all over again Thanks!
Re: Migration question
hi Bruce, migration *MOVES* your clients' data from a PRIMARY storage pool to a NEXT PRIMARY storage pool, e.g. from DISK to a primary TAPE pool. backup stgpool *COPIES* clients' data stored on a PRIMARY pool to a COPY pool (that has to be SEQUENTIAL, i.e. a tape pool). after the successful backup of a primary storage pool, you will have 2 copies of data on TSM server, and you can send the 2nd copy to an off-site location (vault). see: help migrate stg help backup stg hope it helps. regards Gabriel Peter On 1 Oct 2007, 18:35, Dollens, Bruce wrote: I have a question that I feel a little stupid in asking. What is the difference between migration and backup primary (disk) to copy (tape)? I am working on changing my scheduling up and the recommended order of steps I was given is: Backup clients Migration Backup primary to copy Backup db Expiration Reclamation Start all over again Thanks!
Re: Domino Password problem. Confused
There is only one password, the TSM Node Password. When the password expires, a new password is automatically generated by the domino CLI. If you update the TSM Node password with 'update node', then you will have to store the new password with 'domdsmc query adsm -adsmpwd=x' command. If you want the password never to expire, set the passexp=0. Eduardo hshahizul [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/01/2007 10:19 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Domino Password problem. Confused Hi there. I am confused with this password for domino. After running well for sometime, message as below will appeared. I have 6 notes server backup via TSM. All of the will have this problem after sometime. If query via TSM CLI . q eve * * , the backup shows completed. If check from the log, show Authentication failure. What I always do to store the password are: 1. At domino CLI : domdsmc q dbb /adsmpwd=x 2. At TSM CLI: update node NOTES1 x The question arises, which password has expired, TSM NODE or API domino? How to make both of them password never expire. ( For TSM node, update node NOTES1 admin passexp=0 ) for domino ? I gather info from internet, says the domino password file is corrupted. Is there any relation with the above statement which I mention? Thanks in advance. Zul Malaysia. TSM Server Ver 5.3.0.0 AIX 5.3 == IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino Version 5, Release 3, Level 0.0 (C) Copyright IBM Corporation 1999, 2004. All rights reserved. ACD5221I The /usr/tivoli/tsm/client/domino/bin/domdsmc_notes/dominc.log log file has been pruned successfully. Starting Domino database backup... Initializing Domino connection... Querying Domino for a list of databases, please wait... Logging on to the Tivoli Storage Manager server, please wait... ACD5025E PASSWORDACCESS is Generate. Either the stored password is incorrect or there is no stored password. If you do not have a stored password, use of the -ADSMPWD=xxx option will set and store your password. Total Domino databases inspected: 3,373 Total Domino databases backed up: 0 Total Domino databases excluded: 0 Total Domino backup objects expired: 0 Throughput rate: 0.00 Kb/Sec Total bytes transferred: 0 Elapsed processing time: 0.00 Secs ANS1025E (RC137) Session rejected: Authentication failure =
Re: Library slot count manipulation in TSM
Not proving you ignorant at all, guess I was just blessed. :) Here was the order of events. 1. Slots were changed (by Sepaton support) on VTL side in XML from 400 to 1000 2. TSM was halted 3. TSM server was rebooted 4. TSM was brought back up 5. 'show slots' in TSM showed 1000. The output was still 400 before the halt/reboot 6. Cartridges (196) were created with the VTL GUI. 7. 'Label libvol' worked successfully I did not have to delete and re-create anything in TSM. :) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Friday, September 28, 2007 3:03 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Library slot count manipulation in TSM Chip, I hope I am not proven ignorant in this case, but I don't think there is a way to update the slot count without deleting the drives/path/library, and then redefining them. The reason is that when the library path is first defined is when TSM queries the library device and receives back a list of the element numbers of the library. There is an element number assigned to each slot, tape drive, and I/O slot. TSM uses the element numbers from the resulting list to know what instructions it can give the library robot. I am not aware of a way to update that list on the fly. The good news is you don't have to reboot the TSM instance to do this, just quiet down all the tape drives so nothing is using the drives or library, then delete it and recreate it. If you haven't already done this, now would be a good time to trap all the commands used to delete and redefine the library from the activity log, and put them in a macro or text file for reuse in the future. It can save you a lot of typing the next time you have upgrade the library. Best Regards, John D. Schneider Sr. System Administrator - Storage Sisters of Mercy Health System 3637 South Geyer Road St. Louis, MO. 63127 Email: [EMAIL PROTECTED] Office: 314-364-3150, Cell: 314-486-2359 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bell, Charles (Chip) Sent: Friday, September 28, 2007 2:39 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Library slot count manipulation in TSM How does TSM know how many slots are available, say, from the output of the 'show slots' command below? I have a Sepaton VTL, and I would like to expand the slot count from the Sepaton side from 400 to 1000. What could I do from the TSM side to see the 1000 slots and not have to delete drives/paths/library definitions for the library (3584_vtl1) shown below? Reboot the TSM server? Perhaps just an audit library? It would great to not even have to reboot the TSM server, but we can if necessary. It's less of a pain than rebuilding the library environment from the TSM side. tsm: TSMshow slots 3584_vtl1 PVR slot information for library 3584_VTL1. Library : 3584_VTL1 Product Id : 03584L32 Support module : 4 Mount count : 1 Drives : 16 Slots: 400 Changers : 1 Import/Exports : 32 God bless you!!! Chip Bell Network Engineer I IBM Tivoli Certified Deployment Professional Baptist Health System Birmingham, AL - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
help, cannot restore files...
Hello everyone, I am trying to restore files for a Linux server, TSM client 5.3.3.0. Apparently the file system: /p01/app/ibm/was/appserver/node01 file system no longer exists on this system and no data was ever backed up under this directory, but there IS a file system called: /p01/app/ibm/was/appserver and this file system contains a subdirectory called node01 and this IS where the data had been backed up under. When doing a restore from the command line and from the Client GUI it says that No files match the query but I can see them down the /p01/app/ibm/was/appserver file system under the /node01 subdirectory. Any suggestions on what can be done so that I can get this data to restore to /tmp? Any suggestions are appreciated! Thanks! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: help, cannot restore files...
Here is a guess Check for links in the directory path. TSM will not follow links by default. Usually when I can't see something down a path, there ends up being a link (hard or soft) in the path. Once you find the ~real~ location of the data you should be able to restore it. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Monday, October 01, 2007 12:49 PM To: ADSM-L@VM.MARIST.EDU Subject: help, cannot restore files... Hello everyone, I am trying to restore files for a Linux server, TSM client 5.3.3.0. Apparently the file system: /p01/app/ibm/was/appserver/node01 file system no longer exists on this system and no data was ever backed up under this directory, but there IS a file system called: /p01/app/ibm/was/appserver and this file system contains a subdirectory called node01 and this IS where the data had been backed up under. When doing a restore from the command line and from the Client GUI it says that No files match the query but I can see them down the /p01/app/ibm/was/appserver file system under the /node01 subdirectory. Any suggestions on what can be done so that I can get this data to restore to /tmp? Any suggestions are appreciated! Thanks! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: help, cannot restore files...
place {} around the filesystem. This denotes the filespace in which tsm
will look.
example:
files in /usr/local/bin/newapp.
filesystem actually is /usr/local
you would specify,
{/usr/local}/bin/newapp
hope that is clear as mud.
Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, October 01, 2007 2:49 PM
To: ADSM-L@VM.MARIST.EDU
Subject: help, cannot restore files...
Hello everyone,
I am trying to restore files for a Linux server, TSM client 5.3.3.0.
Apparently the file system: /p01/app/ibm/was/appserver/node01 file
system
no longer exists on this system and no data was ever backed up under
this
directory, but there IS a file system called: /p01/app/ibm/was/appserver
and this file system contains a subdirectory called node01 and this IS
where the data had been backed up under. When doing a restore from the
command line and from the Client GUI it says that No files match the
query
but I can see them down the /p01/app/ibm/was/appserver file system under
the /node01 subdirectory. Any suggestions on what can be done so that I
can get this data to restore to /tmp? Any suggestions are appreciated!
Thanks!
Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III
Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]
Re: help, cannot restore files...
Joni,
Specify the filesystem with brackets and then include the subdir
after
Dsmc q backup {/p01/app/ibm/was/appserver}/node01/userstuff.
Ref: unix BA install and user guide - Chapter 4 - Backup, Additional
considerations
Cheers,
Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, October 01, 2007 2:49 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] help, cannot restore files...
Hello everyone,
I am trying to restore files for a Linux server, TSM client 5.3.3.0.
Apparently the file system: /p01/app/ibm/was/appserver/node01 file
system no longer exists on this system and no data was ever backed up
under this directory, but there IS a file system called:
/p01/app/ibm/was/appserver and this file system contains a subdirectory
called node01 and this IS where the data had been backed up under. When
doing a restore from the command line and from the Client GUI it says
that No files match the query but I can see them down the
/p01/app/ibm/was/appserver file system under the /node01 subdirectory.
Any suggestions on what can be done so that I can get this data to
restore to /tmp? Any suggestions are appreciated!
Thanks!
Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security numbers,
account numbers, or personal identification numbers. Delivery, and or timely
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
that you do not send time sensitive
or action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain privileged or
confidential information. Unless you are the intended recipient, you may not
use, copy or disclose to anyone any information contained in this message. If
you have received this message in error, please notify the author by replying
to this message and then kindly delete the message. Thank you.
Re: help, cannot restore files...
Hi Ben, I would think the same thing too, but it still doesn't work. Here is what I can see: Location where data resides and was backed up from: /p01/app/ibm/was/appserver and then it goes to the subdir of /node01/.../.../... The only problem is that when a restore is attempted it says it cannot find any matches, but I can physically see the data within the TSM client. It just won't let me restore it. Here is how it is mounted on the linux server: chln793|/p01/app/ibm/was/appserver df -k | grep appserver /dev/mapper/datavg1-appserverlv 17546044 9112708 8255080 53% /p01/app/ibm/was/appserver I guess I'm confused why it won't restore the data. I don't see any links to this data. The only thing is that from the TSM server I do see a file system that used to exist: /p01/app/ibm/was/appserver/node01 and I'm not sure if this is causing a conflict with the restore or not? Any ideas? Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Ben Bullock [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/01/2007 02:53 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: help, cannot restore files... Here is a guess Check for links in the directory path. TSM will not follow links by default. Usually when I can't see something down a path, there ends up being a link (hard or soft) in the path. Once you find the ~real~ location of the data you should be able to restore it. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Monday, October 01, 2007 12:49 PM To: ADSM-L@VM.MARIST.EDU Subject: help, cannot restore files... Hello everyone, I am trying to restore files for a Linux server, TSM client 5.3.3.0. Apparently the file system: /p01/app/ibm/was/appserver/node01 file system no longer exists on this system and no data was ever backed up under this directory, but there IS a file system called: /p01/app/ibm/was/appserver and this file system contains a subdirectory called node01 and this IS where the data had been backed up under. When doing a restore from the command line and from the Client GUI it says that No files match the query but I can see them down the /p01/app/ibm/was/appserver file system under the /node01 subdirectory. Any suggestions on what can be done so that I can get this data to restore to /tmp? Any suggestions are appreciated! Thanks! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: help, cannot restore files...
do a q backup -subdir=yes 'your directory' - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 01, 2007 2:48 PM Subject: [ADSM-L] help, cannot restore files... Hello everyone, I am trying to restore files for a Linux server, TSM client 5.3.3.0. Apparently the file system: /p01/app/ibm/was/appserver/node01 file system no longer exists on this system and no data was ever backed up under this directory, but there IS a file system called: /p01/app/ibm/was/appserver and this file system contains a subdirectory called node01 and this IS where the data had been backed up under. When doing a restore from the command line and from the Client GUI it says that No files match the query but I can see them down the /p01/app/ibm/was/appserver file system under the /node01 subdirectory. Any suggestions on what can be done so that I can get this data to restore to /tmp? Any suggestions are appreciated! Thanks! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Fw: help, cannot restore files...
Joni, I think you need to do a redirected restore (restore to alternate location), as the filesystem/directory isn't the same, even though the whole path is. Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 10/01/2007 03:05 PM - ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 10/01/2007 03:00:24 PM: Hi Ben, I would think the same thing too, but it still doesn't work. Here is what I can see: Location where data resides and was backed up from: /p01/app/ibm/was/appserver and then it goes to the subdir of /node01/.../.../... The only problem is that when a restore is attempted it says it cannot find any matches, but I can physically see the data within the TSM client. It just won't let me restore it. Here is how it is mounted on the linux server: chln793|/p01/app/ibm/was/appserver df -k | grep appserver /dev/mapper/datavg1-appserverlv 17546044 9112708 8255080 53% /p01/app/ibm/was/appserver I guess I'm confused why it won't restore the data. I don't see any links to this data. The only thing is that from the TSM server I do see a file system that used to exist: /p01/app/ibm/was/appserver/node01 and I'm not sure if this is causing a conflict with the restore or not? Any ideas? Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Ben Bullock [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/01/2007 02:53 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: help, cannot restore files... Here is a guess Check for links in the directory path. TSM will not follow links by default. Usually when I can't see something down a path, there ends up being a link (hard or soft) in the path. Once you find the ~real~ location of the data you should be able to restore it. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Monday, October 01, 2007 12:49 PM To: ADSM-L@VM.MARIST.EDU Subject: help, cannot restore files... Hello everyone, I am trying to restore files for a Linux server, TSM client 5.3.3.0. Apparently the file system: /p01/app/ibm/was/appserver/node01 file system no longer exists on this system and no data was ever backed up under this directory, but there IS a file system called: /p01/app/ibm/was/appserver and this file system contains a subdirectory called node01 and this IS where the data had been backed up under. When doing a restore from the command line and from the Client GUI it says that No files match the query but I can see them down the /p01/app/ibm/was/appserver file system under the /node01 subdirectory. Any suggestions on what can be done so that I can get this data to restore to /tmp? Any suggestions are appreciated! Thanks! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: help, cannot restore files...
hmmm, at least on AIX, TSM backups by mount point, so TSM should have it under: /p01/app/ibm/was/appserver If it was backed up, then umounted, it may be set inactive try: q backup -inact=yes dir structure - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 01, 2007 3:00 PM Subject: Re: [ADSM-L] help, cannot restore files... Hi Ben, I would think the same thing too, but it still doesn't work. Here is what I can see: Location where data resides and was backed up from: /p01/app/ibm/was/appserver and then it goes to the subdir of /node01/.../.../... The only problem is that when a restore is attempted it says it cannot find any matches, but I can physically see the data within the TSM client. It just won't let me restore it. Here is how it is mounted on the linux server: chln793|/p01/app/ibm/was/appserver df -k | grep appserver /dev/mapper/datavg1-appserverlv 17546044 9112708 8255080 53% /p01/app/ibm/was/appserver I guess I'm confused why it won't restore the data. I don't see any links to this data. The only thing is that from the TSM server I do see a file system that used to exist: /p01/app/ibm/was/appserver/node01 and I'm not sure if this is causing a conflict with the restore or not? Any ideas? Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Ben Bullock [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/01/2007 02:53 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: help, cannot restore files... Here is a guess Check for links in the directory path. TSM will not follow links by default. Usually when I can't see something down a path, there ends up being a link (hard or soft) in the path. Once you find the ~real~ location of the data you should be able to restore it. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Monday, October 01, 2007 12:49 PM To: ADSM-L@VM.MARIST.EDU Subject: help, cannot restore files... Hello everyone, I am trying to restore files for a Linux server, TSM client 5.3.3.0. Apparently the file system: /p01/app/ibm/was/appserver/node01 file system no longer exists on this system and no data was ever backed up under this directory, but there IS a file system called: /p01/app/ibm/was/appserver and this file system contains a subdirectory called node01 and this IS where the data had been backed up under. When doing a restore from the command line and from the Client GUI it says that No files match the query but I can see them down the /p01/app/ibm/was/appserver file system under the /node01 subdirectory. Any suggestions on what can be done so that I can get this data to restore to /tmp? Any suggestions are appreciated! Thanks! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: help, cannot restore files...
Which user are you? Being able to see but not restore files sometimes can mean that you are not a privileged enough user to restore the data. TSM file restores adhere to unix file permissions. When in doubt, try it as root. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Monday, October 01, 2007 1:00 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: help, cannot restore files... Hi Ben, I would think the same thing too, but it still doesn't work. Here is what I can see: Location where data resides and was backed up from: /p01/app/ibm/was/appserver and then it goes to the subdir of /node01/.../.../... The only problem is that when a restore is attempted it says it cannot find any matches, but I can physically see the data within the TSM client. It just won't let me restore it. Here is how it is mounted on the linux server: chln793|/p01/app/ibm/was/appserver df -k | grep appserver /dev/mapper/datavg1-appserverlv 17546044 9112708 8255080 53% /p01/app/ibm/was/appserver I guess I'm confused why it won't restore the data. I don't see any links to this data. The only thing is that from the TSM server I do see a file system that used to exist: /p01/app/ibm/was/appserver/node01 and I'm not sure if this is causing a conflict with the restore or not? Any ideas? Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Ben Bullock [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/01/2007 02:53 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: help, cannot restore files... Here is a guess Check for links in the directory path. TSM will not follow links by default. Usually when I can't see something down a path, there ends up being a link (hard or soft) in the path. Once you find the ~real~ location of the data you should be able to restore it. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Monday, October 01, 2007 12:49 PM To: ADSM-L@VM.MARIST.EDU Subject: help, cannot restore files... Hello everyone, I am trying to restore files for a Linux server, TSM client 5.3.3.0. Apparently the file system: /p01/app/ibm/was/appserver/node01 file system no longer exists on this system and no data was ever backed up under this directory, but there IS a file system called: /p01/app/ibm/was/appserver and this file system contains a subdirectory called node01 and this IS where the data had been backed up under. When doing a restore from the command line and from the Client GUI it says that No files match the query but I can see them down the /p01/app/ibm/was/appserver file system under the /node01 subdirectory. Any suggestions on what can be done so that I can get this data to restore to /tmp? Any suggestions are appreciated! Thanks! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: help, cannot restore files...
Hey Everyone,
Using the { } worked! Thank you so much for your quick responses! I
really appreciate it!
Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III
Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]
Strand, Neil B. [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
10/01/2007 02:55 PM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: help, cannot restore files...
Joni,
Specify the filesystem with brackets and then include the subdir
after
Dsmc q backup {/p01/app/ibm/was/appserver}/node01/userstuff.
Ref: unix BA install and user guide - Chapter 4 - Backup, Additional
considerations
Cheers,
Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, October 01, 2007 2:49 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] help, cannot restore files...
Hello everyone,
I am trying to restore files for a Linux server, TSM client 5.3.3.0.
Apparently the file system: /p01/app/ibm/was/appserver/node01 file
system no longer exists on this system and no data was ever backed up
under this directory, but there IS a file system called:
/p01/app/ibm/was/appserver and this file system contains a subdirectory
called node01 and this IS where the data had been backed up under. When
doing a restore from the command line and from the Client GUI it says
that No files match the query but I can see them down the
/p01/app/ibm/was/appserver file system under the /node01 subdirectory.
Any suggestions on what can be done so that I can get this data to
restore to /tmp? Any suggestions are appreciated!
Thanks!
Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security numbers,
account numbers, or personal identification numbers. Delivery, and or
timely delivery of Internet mail is not guaranteed. Legg Mason therefore
recommends that you do not send time sensitive
or action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain privileged
or confidential information. Unless you are the intended recipient, you
may not use, copy or disclose to anyone any information contained in this
message. If you have received this message in error, please notify the
author by replying to this message and then kindly delete the message.
Thank you.
Re: help, cannot restore files...
-Ben Bullock wrote: - Which user are you? Being able to see but not restore files sometimes can mean that you are not a privileged enough user to restore the data. TSM file restores adhere to unix file permissions. When in doubt, try it as root. The TSM policy is even stricter than this. The only users allowed to restore a file are root and the owner of the file. Other userscannot restore the file even if they have write access to it.
How do I determine session statistics for client events
Hello - I am trying to determine the query or select command which will report detailed statistics for client events. I have a report containing data returned from query event * * begind=today-1 I assumed that the last session details reported by the query node command was reporting statistics for the client event sessions, but now I am not sure. I compared the activity log ANR4961I message total bytes transferred for the session to the q node to the bytes in the summary table for the node and to the last session bytes received for the node. The ANR4961I message total bytes transferred matches the bytes in the summary table, but the last session bytes received from query node is different. What type of session populates these last session fields reported by the query node? How might I capture client event session statistics similar to the last session statistics reported by q node node-name f=d command? Thanks, Lucia Lucia Burke Senior Systems Analyst/ Programmer Sharp HealthCare 3571 Corporate Court San Diego, CA 92123 (858)627-5081 [EMAIL PROTECTED]
Re: Migration question
On 02/10/2007, at 2:35 AM, Dollens, Bruce wrote: I have a question that I feel a little stupid in asking. What is the difference between migration and backup primary (disk) to copy (tape)? Other people have already answered, so I won't bother. :) I am working on changing my scheduling up and the recommended order of steps I was given is: Backup clients Migration Backup primary to copy Backup db Expiration Reclamation Start all over again I'd change that order slightly to: Backup clients Backup disk pool(s) Migration Backup tape pool(s) Backup db Expiration Reclamation Repeat ad nauseum. Better to backup the storage pool data while it's still on disk, rather than to flush it out to tape and then back it up - saves on the amount of data read from tape. Some data may well still flush down to tape before the first backup stgpool runs, which is why you want to backup the tape pool as well after migration is complete.
Re: How do I determine session statistics for client events
On Oct 1, 2007, at 5:47 PM, Lucia Burke wrote: How might I capture client event session statistics similar to the last session statistics reported by q node node-name f=d command? Simply activate TSM Accounting, whereby you automatically capture all session stats. Richard Sims
Re: moving a 3494 library
You don't address making sure the 3494 will allow access by the TSM server at site B. [RC] On Oct 1, 2007, at 7:30 AM, Larry Clark wrote: There are two TSM servers, one at SiteA, the 2nd at SiteB SiteA manages two 3494 tape libraries, one at SiteA and the 2nd at SiteB (connected via longwave fibre), and is the tape library manager for both TSM servers. The 3494 at SiteB is defined at shared. All the volumes on the tape library at SiteB are now owned by the TSM server at SiteB. The goal is to remove the client instance and have ServerB locally manage the library, and retain its current volumes. The suggested procedure / sequence is: 1). Checkout the vols in the library at SiteB 2). Remove the 3494 defs for the 3494 at SiteB from the TSM server at SiteA 3). Remove and redefine the library on the TSM server at SiteB (non- shared) 4). Checkin the vols (private) in SiteB 5). Remove references in volhist on SiteA to volumes in 3494 in SiteB. Anyone see a problem with this sequence?
Re: Domino Password problem. Confused
Thanks for your explanation. I will try. Tq. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Eduardo Esteban Sent: Tuesday, October 02, 2007 1:56 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Domino Password problem. Confused There is only one password, the TSM Node Password. When the password expires, a new password is automatically generated by the domino CLI. If you update the TSM Node password with 'update node', then you will have to store the new password with 'domdsmc query adsm -adsmpwd=x' command. If you want the password never to expire, set the passexp=0. Eduardo hshahizul [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/01/2007 10:19 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Domino Password problem. Confused Hi there. I am confused with this password for domino. After running well for sometime, message as below will appeared. I have 6 notes server backup via TSM. All of the will have this problem after sometime. If query via TSM CLI . q eve * * , the backup shows completed. If check from the log, show Authentication failure. What I always do to store the password are: 1. At domino CLI : domdsmc q dbb /adsmpwd=x 2. At TSM CLI: update node NOTES1 x The question arises, which password has expired, TSM NODE or API domino? How to make both of them password never expire. ( For TSM node, update node NOTES1 admin passexp=0 ) for domino ? I gather info from internet, says the domino password file is corrupted. Is there any relation with the above statement which I mention? Thanks in advance. Zul Malaysia. TSM Server Ver 5.3.0.0 AIX 5.3 == IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino Version 5, Release 3, Level 0.0 (C) Copyright IBM Corporation 1999, 2004. All rights reserved. ACD5221I The /usr/tivoli/tsm/client/domino/bin/domdsmc_notes/dominc.log log file has been pruned successfully. Starting Domino database backup... Initializing Domino connection... Querying Domino for a list of databases, please wait... Logging on to the Tivoli Storage Manager server, please wait... ACD5025E PASSWORDACCESS is Generate. Either the stored password is incorrect or there is no stored password. If you do not have a stored password, use of the -ADSMPWD=xxx option will set and store your password. Total Domino databases inspected: 3,373 Total Domino databases backed up: 0 Total Domino databases excluded: 0 Total Domino backup objects expired: 0 Throughput rate: 0.00 Kb/Sec Total bytes transferred: 0 Elapsed processing time: 0.00 Secs ANS1025E (RC137) Session rejected: Authentication failure =
