Re: Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1
Thanks Carlo and every one, this issue has now been resolved. Eric from Level2 helped us get the server back online. What had happened was that when we upgraded TSM, DB2 was still running. Even though TSM is halted, DB2 still runs in the background. IBM is planning to fix this issue in future fix pack's. To correct the issue he had us run following command, which updated db2 and eventually fixed the problem. /opt/tivoli/tsm/db2/instance/db2iupdt Thanks Abid -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Carlo Zanelli Sent: Wednesday, June 22, 2011 3:47 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 Seems all ok on bd2 license. Please check the db2diag*.log for messages like this: 2010-08-22-22.23.53.019777-420 I28327494A470 LEVEL: Severe PID : 188630 TID : 258 PROC : db2wdog 0 INSTANCE: tsminst1 NODE : 000 EDUID : 258 EDUNAME: db2wdog 0 FUNCTION: DB2 UDB, oper system services, sqloWatchDogSetup, probe:110 DATA #1 : String, 148 bytes Setting the effective userid to root failed. During tsm startup. In this case is a fs mount problem, please follow the resolution listed below: https://www-304.ibm.com/support/docview.wss?uid=swg21209278&wv=1 And let we know, Carlo. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Abid Ilias Sent: mercoledì 22 giugno 2011 21:56 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 Here the output. $ db2licm -l Product name: "DB2 Enterprise Server Edition" License type: "Restricted" Expiry date: "Permanent" Product identifier: "db2ese" Version information: "9.7" Thanks Abid -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Carlo Zanelli Sent: Wednesday, June 22, 2011 2:44 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 Could you please run db2licm -l and report the output. 10x Carlo. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Abid Ilias Sent: mercoledì 22 giugno 2011 21:33 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 Hello Carlo, Answers are below... Thanks Abid Ilias Storage Systems Administrator IT Services - University of Chicago Work: 773-702-0246 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Carlo Zanelli Sent: Wednesday, June 22, 2011 2:13 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 Hi Abid, too few informations to give you some help. a)What is the OS/Version? AIX 6100-06-05-1115 b) Is the TSM in cluster? No c) If so, is it in HACMP? No d)Wath are the steps you have done for the upgrading? Our AIX admin ran the install.bin, here the out put from lslpp -l|grep TSM tivoli.tsm.server 6.2.2.30 COMMITTED TSM Server 6.2.1.0 COMMITTED TSM Server License 6.2.1.0 COMMITTED TSM Server License Runtime 6.2.2.30 COMMITTED TSM Server Messages, locale tivoli.tsm.server 6.2.2.30 COMMITTED TSM Server e)Have you recataloged the db2 ? No Kindly, Carlo. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Abid Ilias Sent: mercoledì 22 giugno 2011 21:03 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 We have up upgraded TSM from 6.2 to 6.2.2.30 and are not able to start the server. I have a PMR open with IBM, checking to see if someone has encountered this. Any thoughts and suggestions would be appreciated. $ dsmserv ANR7800I DSMSERV generated at 17:54:46 on Apr 15 2011. Tivoli Storage Manager for AIX Version 6, Release 2, Level 2.30 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2010. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I Subsystem process ID is 5963934. ANR0900I Processing options file /home/stagg/tsminst1/dsmserv.opt. ANR7811I Using instance directory /home/stagg/tsminst1. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0151W Failure starting database manager. ANR0279S The database manager failed to start. The database manager license key is invalid or was removed. Regards Abid - Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute nel messaggio e negli eventuali allegati sono rise
Re: Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1
Here the output. $ db2licm -l Product name: "DB2 Enterprise Server Edition" License type: "Restricted" Expiry date: "Permanent" Product identifier: "db2ese" Version information: "9.7" Thanks Abid -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Carlo Zanelli Sent: Wednesday, June 22, 2011 2:44 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 Could you please run db2licm -l and report the output. 10x Carlo. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Abid Ilias Sent: mercoledì 22 giugno 2011 21:33 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 Hello Carlo, Answers are below... Thanks Abid Ilias Storage Systems Administrator IT Services - University of Chicago Work: 773-702-0246 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Carlo Zanelli Sent: Wednesday, June 22, 2011 2:13 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 Hi Abid, too few informations to give you some help. a)What is the OS/Version? AIX 6100-06-05-1115 b) Is the TSM in cluster? No c) If so, is it in HACMP? No d)Wath are the steps you have done for the upgrading? Our AIX admin ran the install.bin, here the out put from lslpp -l|grep TSM tivoli.tsm.server 6.2.2.30 COMMITTED TSM Server 6.2.1.0 COMMITTED TSM Server License 6.2.1.0 COMMITTED TSM Server License Runtime 6.2.2.30 COMMITTED TSM Server Messages, locale tivoli.tsm.server 6.2.2.30 COMMITTED TSM Server e)Have you recataloged the db2 ? No Kindly, Carlo. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Abid Ilias Sent: mercoledì 22 giugno 2011 21:03 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 We have up upgraded TSM from 6.2 to 6.2.2.30 and are not able to start the server. I have a PMR open with IBM, checking to see if someone has encountered this. Any thoughts and suggestions would be appreciated. $ dsmserv ANR7800I DSMSERV generated at 17:54:46 on Apr 15 2011. Tivoli Storage Manager for AIX Version 6, Release 2, Level 2.30 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2010. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I Subsystem process ID is 5963934. ANR0900I Processing options file /home/stagg/tsminst1/dsmserv.opt. ANR7811I Using instance directory /home/stagg/tsminst1. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0151W Failure starting database manager. ANR0279S The database manager failed to start. The database manager license key is invalid or was removed. Regards Abid - Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute nel messaggio e negli eventuali allegati sono riservate al/ai destinatario/i indicato/i. Nel caso di erroneo recapito, si chiede cortesemente a chi legge di dare immediata comunicazione al mittente e di cancellare il presente messaggio e gli eventuali allegati. Si invita ad astenersi dall'effettuare: inoltri, copie, distribuzioni e divulgazioni non autorizzate del presente messaggio e degli eventuali allegati. -- According to Italian law (D.Lgs 196/2003) information contained in this message and any attachment contained therein is addressed exclusively to the intended recipient. If you have received this message in error would you please inform immediately the sender and delete the message and its attachments. You are also requested not to make copies, nor to forward the message and its attachments or disclose their content unless authorised. - Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute nel messaggio e negli eventuali allegati sono riservate al/ai destinatario/i indicato/i. Nel caso di erroneo recapito, si chiede cortesemente a chi legge di dare immediata comunicazione al mittente e di cancellare il presente messaggio e gli eventuali allegati. Si invita ad astenersi dall'effettuare: inoltri, copie, distribuzioni e divulgazioni non autorizzate del presente messaggio e degli eventuali allegati. -- According to Italian law (D.Lgs 196/2003) information contained in this message and any attachment contained therein is addressed exclusively to the intended recipient. If you have received this message in error would you
Re: Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1
Hello Carlo, Answers are below... Thanks Abid Ilias Storage Systems Administrator IT Services - University of Chicago Work: 773-702-0246 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Carlo Zanelli Sent: Wednesday, June 22, 2011 2:13 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 Hi Abid, too few informations to give you some help. a)What is the OS/Version? AIX 6100-06-05-1115 b) Is the TSM in cluster? No c) If so, is it in HACMP? No d)Wath are the steps you have done for the upgrading? Our AIX admin ran the install.bin, here the out put from lslpp -l|grep TSM tivoli.tsm.server 6.2.2.30 COMMITTED TSM Server 6.2.1.0 COMMITTED TSM Server License 6.2.1.0 COMMITTED TSM Server License Runtime 6.2.2.30 COMMITTED TSM Server Messages, locale tivoli.tsm.server 6.2.2.30 COMMITTED TSM Server e)Have you recataloged the db2 ? No Kindly, Carlo. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Abid Ilias Sent: mercoledì 22 giugno 2011 21:03 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1 We have up upgraded TSM from 6.2 to 6.2.2.30 and are not able to start the server. I have a PMR open with IBM, checking to see if someone has encountered this. Any thoughts and suggestions would be appreciated. $ dsmserv ANR7800I DSMSERV generated at 17:54:46 on Apr 15 2011. Tivoli Storage Manager for AIX Version 6, Release 2, Level 2.30 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2010. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I Subsystem process ID is 5963934. ANR0900I Processing options file /home/stagg/tsminst1/dsmserv.opt. ANR7811I Using instance directory /home/stagg/tsminst1. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0151W Failure starting database manager. ANR0279S The database manager failed to start. The database manager license key is invalid or was removed. Regards Abid - Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute nel messaggio e negli eventuali allegati sono riservate al/ai destinatario/i indicato/i. Nel caso di erroneo recapito, si chiede cortesemente a chi legge di dare immediata comunicazione al mittente e di cancellare il presente messaggio e gli eventuali allegati. Si invita ad astenersi dall'effettuare: inoltri, copie, distribuzioni e divulgazioni non autorizzate del presente messaggio e degli eventuali allegati. -- According to Italian law (D.Lgs 196/2003) information contained in this message and any attachment contained therein is addressed exclusively to the intended recipient. If you have received this message in error would you please inform immediately the sender and delete the message and its attachments. You are also requested not to make copies, nor to forward the message and its attachments or disclose their content unless authorised.
Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1
We have up upgraded TSM from 6.2 to 6.2.2.30 and are not able to start the server. I have a PMR open with IBM, checking to see if someone has encountered this. Any thoughts and suggestions would be appreciated. $ dsmserv ANR7800I DSMSERV generated at 17:54:46 on Apr 15 2011. Tivoli Storage Manager for AIX Version 6, Release 2, Level 2.30 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2010. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I Subsystem process ID is 5963934. ANR0900I Processing options file /home/stagg/tsminst1/dsmserv.opt. ANR7811I Using instance directory /home/stagg/tsminst1. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0151W Failure starting database manager. ANR0279S The database manager failed to start. The database manager license key is invalid or was removed. Regards Abid
Access to Management Class for TSM Clients
We have some longer management classes defined in a policy domain for some specific purpose, but our management does not want TSM clients to see or use them. Our management wants the TSM admins to have this control and bind the data to different management class as per requests. I have not seen any way to prevent users from doing this. Is there a way to prevent TSM clients from using a management class other than default. Any input would be greatly appreciated. Thanks Abid
Restore NTFS data to a NAS Filler
We have a request from one of our user to restore the data stored in TSM by a windows Client to a NAS filler. I have not seen any option of doing so in TSM, I would appreciate if you can shed some light on this. Abid
How to verify that the TSM Client Data is encrypted in the TSM Server
Hello TSM Group Is there any other way to find out if the data is encrypted in TSM Server other than looking into the activity log.We are enabled the encryption option at the client end and it seem to work on AIX and having problem getting it to work on Linux platform. ANE4991I (Session: 375407, Node: HANDEL-DB) TDP Oracle AIX ANU0599 TDP for Oracle: (798816): =>(handel-db) ANU2526I Backup details for backup piece /oracle//TRACSDEV_DB_0205_k2l58c1u_1_1.bkp (database "TRACSDEV"). Total bytes sent: 5055971328. Total processing time: 00:07:29. Throughput rate: 10996.60Kb/Sec. Compressed: No . Encryption: AES_128BIT. LAN-Free: No.(SESSION: 375407) Thanks Abid
Re: Data retention period 60days
Since the node has to have authority to delete the backup data, you need to set the 'backdel' field to yes for the node in question. Default is no. Sent from my iPhone On Jan 21, 2010, at 7:02 PM, "Gee, Norman" wrote: > We let RMAN handle the deletion of backup sets and pieces. Every > backup > has an unique set and piece name and will never be duplicated. RMAN > will tell the TSM server when to expire the backups. > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On > Behalf Of > Kelly Lipp > Sent: Thursday, January 21, 2010 1:31 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Data retention period 60days > > Figure out which management class is governing your Oracle backups. Q > node nodename where nodename is the name the client uses to identify > itself. Check to see which policy domain the node is in. > > Q copy domainname f=d > > You'll probably see verexists=2, verdel=1 retextra=30 retonly=60. > > The most accurate settings for a 60 day retention (which is a long > time > for a database IMHO) should be > > verexists=60, verdel=60 retextra=60 retonly=60 > > So, > > Update copy domainname policysetname magagementclassname STANDARD > verexists=60 verdel=60 retextra=60 retonly=60 > > Then activate the policyset: > > Activate policyset domainname policysetname > > And you're done. > > It is likely that the policyset and managementclassname is STANDARD as > well. If I had set up your system the commands would look like > > Update copy ORACLE STANDARD STANDARD STANDARD verexists=60 verdel=60 > retextra=60 retonly=60 > Activate ORACLE STANDARD > > Kelly Lipp > Chief Technology Officer > www.storserver.com > 719-266-8777 x7105 > STORServer solves your data backup challenges. > Once and for all. > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On > Behalf Of > Sujatha chk > Sent: Thursday, January 21, 2010 12:43 PM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Data retention period 60days > > Hi Gurus, > > we backup our oracle database using rman to TAPE by TSM media > management. Currently Backup Retention policy has been set to 30 > days. > Please guide me on how to configure Back up Retention period to 60 > days? > > -Sujatha > > +-- > > |This was sent by sujatha@gmail.com via Backup Central. > |Forward SPAM to ab...@backupcentral.com. > +-- >
TSM Client Version 6.1.0.0
FYI I have downloaded and installed the new TSM Client version 6 on a Windows XP, the web GUI is coming up blank, I think it is broke. Also now the Admin Command line link is missing, although the Backup Archive command line is working. Thanks Abid Ilias TSM Administrator Networking Services and Information Technology The University of Chicago Phone: 773-702-0246
Re: Changing a Node´s password
>From the TSM Server command line Upd node Thanks Abid Ilias Networking Services and Information Technology The University of Chicago -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Tuesday, March 24, 2009 2:09 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Changing a Node´s password Hi list, Is there any way to change the TSM password for a Node without knowing the current password? Thanks Mario
Re: TSM Library Manager
Also turn the SAN Discovery option ON, we have figured out that the only way SAN Discovery would work was to run TSM as Root in UNIX. If you have SAN Discovery option ON, it is supposed to fix any discrepancy. I would make a spread sheet of all devices for library manager/client and update the path definition on Library manager to reflect that. Here is any example of one, in this case the rmt number match for Library Manager and clinet. When you define a drive leave the default for "serial" option and for the path definition use "autodetect=yes" which is not default. Drive Name Frame Row Element No Manager Client DR5218 1 1 257 rmt7rmt7 DR5167 1 2 258 6 6 DR5467 1 3 259 3 3 DR5457 1 4 260 0 0 DR5460 1 5 261 2 2 DR5475 1 6 262 5 5 DR5136 1 7 263 11 11 DR5304 1 8 264 12 12 DR5316 1 9 265 13 13 DR5335 1 10 266 14 14 DR5337 1 11 267 15 15 DR5338 1 12 268 16 16 DR0074 2 1 269 8 8 DR0053 2 2 270 9 9 DR0120 2 3 271 17 17 DR9931 2 4 272 18 18 DR0049 2 5 273 10 10 DR9995 2 6 274 19 19 DR5876 2 7 275 1 1 DR5956 2 8 276 4 4 DR5342 2 9 277 20 20 DR5846 2 10 278 21 21 Thanks Abid Ilias TSM Administrator Networking Services and Information Technology The University of Chicago -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of David E Ehresman Sent: Tuesday, March 10, 2009 12:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library Manager Are you comparing the element number/serial number on each rmt device on the client with the path definition for the client on the library manager. rmt2 on the manager is not necessarily the same as rmt2 on the client and the path statements on the library manager have to resolve any differences. David >>> "Morris.Marshael" 3/10/2009 1:11 PM >>> I checked the drives to see what element numbers they were pointing to and checked the library to see what element they were showing for the drives, all are in sync. Thanks, Marshael -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Tuesday, March 10, 2009 1:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Library Manager I've seen something similar in the non sharing environment if the element number to drive relationship is whacked. For instance, you suggest that the drive at /rmt0 is element 256 when in reality it's 257. The library is instructed to mount a tape in element 256 and then TSM looks for tape in /rmt0. Verify that the paths and element numbers actually line-up correctly. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Morris.Marshael Sent: Tuesday, March 10, 2009 10:24 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Library Manager I have setup a library manager in TSM. This server is TSM 5.5.2 I am setting up a library client and it also has TSM 5.5.2. The TSM library manager is using the drives with no problem. I have setup the paths for the library client and I'm having problems with the client. The server, when requested, will mount a tape from the client and change ownership to the client name. Within the client activity log I get: ANR0408I Session 15 started for server LIBRARYSERVER (AIX-RS/6000) (Tcp/Ip) for library sharing. ANR0409I Session 15 ended for server LIBRARYSERVER (AIX-RS/6000). ANR8779E Unable to open drive rmt2, error number=2. ANR0409I Session 3 ended for server LIBRARYSERVER (AIX-RS/6000). ANR1404W Scratch volume mount request denied - mount failed. Librarymanager tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP)
Re: EXPORT node toserver
TSM has made a major change for the exporting the node between servers in version 5.5, where you restart the export node process that was suspended because or error. I think in your case mergefilespace=yes option will work so, the data doesn't get duplicated, but the entire process will start from the beginning (unfortunately). Abid -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane Sent: Thursday, July 03, 2008 10:28 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] EXPORT node toserver I'm using TSM 5.4.3 . -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Abid Ilias Sent: Thursday, July 03, 2008 10:25 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: EXPORT node toserver If you are using TSM Server version 5.5 export node will start from where it left off. You can use mergefilespace option also so it will not duplicate. Also issue following command on the source server ' q export ' to see the status of the export. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane Sent: Thursday, July 03, 2008 10:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] EXPORT node toserver I ran an export node toserver and it errored 1/3 of the way into 200gb of data. Are there any steps that need to be taken in order to restart this other than mergefilespace ? Will any of my archive data be duplicated on the target server ?
Re: EXPORT node toserver
If you are using TSM Server version 5.5 export node will start from where it left off. You can use mergefilespace option also so it will not duplicate. Also issue following command on the source server ' q export ' to see the status of the export. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane Sent: Thursday, July 03, 2008 10:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] EXPORT node toserver I ran an export node toserver and it errored 1/3 of the way into 200gb of data. Are there any steps that need to be taken in order to restart this other than mergefilespace ? Will any of my archive data be duplicated on the target server ?
LANFree Implementaion
I am trying to get LANFree work on one of our Windows 2003 machine, but running into issues. I have installed all the required software. Our scenario is as follows Library Manager - This is where the paths are defined from the storage agent(node) to the Tape drives Library Client - This is where the node is registered and the dataread/datawrite is set to LANFree. This node is in a domain where the copy destination of backup copy group is pointing to a Tape Storage pool. Node - Windows 2003 machine (this is where the storage agent is running) and TSM backup client software installed and configured for the Node. When ever I kick off the backup, my paths for that storage agent go offline with the following error code. This is part of the activity log from the Library Client 04/17/08 12:14:15 ANR8963E (Session: 6166, Origin: LYMAN_STA) Unable to find path to match the serial number defined for drive DR5516 in library CAPEKLIB1 . (SESSION: 6166) 04/17/08 12:14:15 ANR0408I (Session: 6166, Origin: LYMAN_STA) Session 27 started for server NECLM (AIX-RS/6000) (Tcp/Ip) for library sharing. (SESSION: 6166) 04/17/08 12:14:15 ANR0409I (Session: 6166, Origin: LYMAN_STA) Session 27 ended for server NECLM (AIX-RS/6000). (SESSION: 6166) 04/17/08 12:14:15 ANR8873E (Session: 6166, Origin: LYMAN_STA) The path from source LYMAN_STA to destination DR5516 (mt7.0.0.2) is taken offline. (SESSION: 6166) This is the log from the client. ANS1228E Sending of object '\\lyman\d$\rm_mounts\healy\edrive\mount\sg1data\Program Files\Microsoft\Exchange Server\Storage Group 1\CatalogData-17e0dbd1-58f0-4608-97ef-1e493e832a15-cd14e744-98a7-44b9-87 0f-f77675d52d8d\00010001.ci' failed ANS1312E Server media mount not possible ANS0350E The current client configuration does not comply with the value of the DATAWRITEPATH or DATAREADPATH server option for this node If would appreciate if someone can shed some light on it. Thanks Abid Ilias TSM Administrator 773-702-0246
Deleted Node
One of the node was deleted on our server last Thursday. And now our customer wants a file from the node. Is there any way to get that file restored from the deleted node. I appreciate any input. Thanks Abid Ilias TSM Administrator University of Chicago
