Re: Cannot delete node
Much ado about nothing ;-)) > -Message d'origine- > De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De > la part de Joni Moyer > Envoyé : jeudi 20 septembre 2007 20:55 > À : ADSM-L@VM.MARIST.EDU > Objet : Re: [ADSM-L] Cannot delete node > > Hey! > > I went back and ran the command again and this time it seems > to have cleaned up all file systems. This might've been an > error on my part. When I did the q occ and didn't see any > data I must've thought I deleted everything when in fact I > must not have. > > Thanks everyone! > > > Joni Moyer > Highmark > Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 > Fax: (717) 302-9826 > [EMAIL PROTECTED] > > > > > "Andrew Raibeck" <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" > 09/20/2007 02:51 PM > Please respond to > "ADSM: Dist Stor Manager" > > > To > ADSM-L@VM.MARIST.EDU > cc > > Subject > Re: Cannot delete node > > > > > > > I don't understand... this looks like Q FILESPACE F=D > output... is this current? If so, the file spaces are still there. > > Regards, > > Andy > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Product Development Level 3 > Team Lead Internal Notes e-mail: Andrew > Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] > > IBM Tivoli Storage Manager support web page: > http://www.ibm.com/software/sysmgmt/products/support/IBMTivoli > StorageManager.html > > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > "ADSM: Dist Stor Manager" wrote on 09/20/2007 > 11:24:29 AM: > > > Hi Kevin, > > > > This is a retired AIX server that has been shut down some time ago. > > > > Node Name: BUMBLEB > > Platform: AIX > >Client OS Level: 5.2 > > Client Version: Version 5, Release 2, Level 2.0 > > Policy Domain Name: RETIRED > > Last Access Date/Time: 10/04/05 15:17:47 > > Days Since Last Access: 716 > > Password Set Date/Time: 06/30/05 07:30:51 > > > > Node Name: BUMBLEB > > Filespace Name: / > > Hexadecimal Filespace Name: > >FSID: 1 > >Platform: AIX > > Filespace Type: UFS > > Is Filespace Unicode?: No > > Capacity (MB): 375.9 > >Pct Util: 80.8 > > Last Backup Start Date/Time: > > Days Since Last Backup Started: > >Last Backup Completion Date/Time: > >Days Since Last Backup Completed: > > Last Full NAS Image Backup Completion Date/Time: > > Days Since Last Full NAS Image Backup Completed: > > > > Node Name: BUMBLEB > > Filespace Name: /var > > Hexadecimal Filespace Name: > >FSID: 2 > >Platform: AIX > > Filespace Type: UFS > > Is Filespace Unicode?: No > > Capacity (MB): 469.6 > >Pct Util: 50.7 > > Last Backup Start Date/Time: > > Days Since Last Backup Started: > >Last Backup Completion Date/Time: > >Days Since Last Backup Completed: > > Last Full NAS Image Backup Completion Date/Time: > > Days Since Last Full NAS Image Backup Completed: > > > > Node Name: BUMBLEB > > Filespace Name: /opt > > Hexadecimal Filespace Name: > >FSID: 3 > >Platform: AIX > > Filespace Type: UFS > > Is Filespace Unicode?: No > > Capacity (MB): 6,367.2 > >Pct Util: 25.9 > > Last Backup Start Date/Time: > > Days Since Last Backup Started: > >Last Backup Completion Date/Time: > >Days Since Last Backup Completed: > > Last Full NAS Image Backup Completion Date/Time: > > Days Since Last Full NAS Image Backup Completed: > > > > Node Name: BUMBLEB > > Filespace Name: /u01 > > Hexadecimal Filespace Name: > >FSID: 4 > >Platform:
Re: Question about LANFree and multiple servers/libraries
bump. what i manage to do is starting another STA server on new LLADDRESS (port) now waiting to see what will happen :-) On 9/19/07, goc <[EMAIL PROTECTED]> wrote: > hi , thanks for replying ... > basically what i want to do is to be able backup lanfree to both TSM > servers for different nodes from one (hppbckp (STA)) server, so i can > manipulate the workload > > thanks, > goran > > On 9/19/07, CAYE PIERRE <[EMAIL PROTECTED]> wrote: > > What do you want to do ? > > > > Keep the sta connected on TSM01 ? Why ? > > Make incr backups on TSM02 ? with sta ? Without ? > > > > > -Message d'origine- > > > De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De > > > la part de goc > > > Envoyé : mercredi 19 septembre 2007 12:22 > > > À : ADSM-L@VM.MARIST.EDU > > > Objet : [ADSM-L] Question about LANFree and multiple servers/libraries > > > > > > hi gurus, i have following situation > > > > > > 2 tsm 5.4.1 servers on AIX each with two LTO librs. with LTO3 drives > > > > > > 1 storage agent on HPUX for supercoolfast data movement :-) > > > > > > exported domain,nodes ... from TSM01 to TSM02 ...everything > > > is okay, defined drives,paths (new rmt logical names on > > > second TSM02 servers because the rmt** were the same as on > > > first TSM01 server), enterprise networking works okay, really > > > everything IS okay ... until ... > > > > > > ... i changed the > > > > > > TCPServeraddress axptsm01 > > > TCPServeraddress axptsm02 > > > > > > to redirect backups to new server/libr !! > > > > > > the dsmc -se=sdb_ca kept connecting me to TSM01 server ! > > > i realized that i don't need tcp serveraddress because it > > > connects to STA and looks for destination TSM backup server, right? > > > > > > HOW TO make change and redirect new lan free backups to new > > > tsm server ? > > > > > > do i have to bring up another STA on the same machine and > > > define it on TSM02 (new one) ? > > > is that possible ? > > > > > > IS there another solution? > > > > > > --> [EMAIL PROTECTED]:/opt/tivoli/tsm/StorageAgent/bin # more dsmsta.opt > > > > > > SERVERNAME TSM01 > > > DEVCONFIG devconfig.out > > > COMMmethod TCPIP > > > TCPPort 1511 > > > > > > --> [EMAIL PROTECTED]:/opt/tivoli/tsm/StorageAgent/bin # more > > > devconfig.out > > > > > > set staname STA_4 > > > set stapassword password > > > set stahladdress hppbckp.vipnet.hr > > > set stalladdress 1511 > > > define server TSM01 serverpassword=password > > > hladdress=axptsm01 lladdress=1500 > > > > > > > > > --> the full stanza on STA server (it acts as backup server) > > > > > > SERVERNAME sdb_ca > > > ENABLELANFREE yes > > > COMMmethod TCPip > > > LANFREETCPPort 1511 > > > *LANFREESHMPORT 1511 > > > LANFREECOMMMETHOD TCPip > > > *LANFREECOMMMETHOD sharedmem > > > LANFREETCPServeraddress hppbckp > > > TCPPort1500 > > > TCPServeraddress axptsm01 > > > NodeName sdb_ca > > > inclexcl /usr/local/etc/inclexcl.sdb > > > Mailprog /usr/bin/mail root > > > Schedlogname /var/adm/dsmsched_cad.sdb > > > Schedlogretention 35 D > > > ERRORLOGNAM/var/adm/dsmerror_sdb.log > > > errorlogretention 35 D > > > QUERYSCHED 12 > > > MANAGEDSERVICESschedule webclient > > > PASSWORDACCESS Generate > > > COMPRESSIONNo > > > RESOURCEUTIL 6 > > > > > > > > > BIG thanks for any tips or even better a solution :-) > > > > > > goran > > > > > >
Re: Question about LANFree and multiple servers/libraries
Sorry, too busy... so you want to define two nodes, each one using a different STA, and all that on the same machine... I'd never configure two sta on the same machine and it is not possible. There are no way to use two different base directory for your sta. You can't indicate an other option file than the default one. And, last, the sta create a lock file on the sta base directory, so it is not possible, even if you script something to "bluff" the sta, to start a second one... Pierre > -Message d'origine- > De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De > la part de goc > Envoyé : vendredi 21 septembre 2007 13:14 > À : ADSM-L@VM.MARIST.EDU > Objet : Re: [ADSM-L] Question about LANFree and multiple > servers/libraries > > bump. > > what i manage to do is starting another STA server on new > LLADDRESS (port) now waiting to see what will happen :-) > > On 9/19/07, goc <[EMAIL PROTECTED]> wrote: > > hi , thanks for replying ... > > basically what i want to do is to be able backup lanfree to > both TSM > > servers for different nodes from one (hppbckp (STA)) > server, so i can > > manipulate the workload > > > > thanks, > > goran > > > > On 9/19/07, CAYE PIERRE <[EMAIL PROTECTED]> wrote: > > > What do you want to do ? > > > > > > Keep the sta connected on TSM01 ? Why ? > > > Make incr backups on TSM02 ? with sta ? Without ? > > > > > > > -Message d'origine- > > > > De : ADSM: Dist Stor Manager > [mailto:[EMAIL PROTECTED] De la > > > > part de goc Envoyé : mercredi 19 septembre 2007 12:22 À : > > > > ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] Question about > LANFree and > > > > multiple servers/libraries > > > > > > > > hi gurus, i have following situation > > > > > > > > 2 tsm 5.4.1 servers on AIX each with two LTO librs. with LTO3 > > > > drives > > > > > > > > 1 storage agent on HPUX for supercoolfast data movement :-) > > > > > > > > exported domain,nodes ... from TSM01 to TSM02 ...everything is > > > > okay, defined drives,paths (new rmt logical names on > second TSM02 > > > > servers because the rmt** were the same as on first > TSM01 server), > > > > enterprise networking works okay, really everything IS okay ... > > > > until ... > > > > > > > > ... i changed the > > > > > > > > TCPServeraddress axptsm01 > > > > TCPServeraddress axptsm02 > > > > > > > > to redirect backups to new server/libr !! > > > > > > > > the dsmc -se=sdb_ca kept connecting me to TSM01 server ! > > > > i realized that i don't need tcp serveraddress because > it connects > > > > to STA and looks for destination TSM backup server, right? > > > > > > > > HOW TO make change and redirect new lan free backups to new tsm > > > > server ? > > > > > > > > do i have to bring up another STA on the same machine > and define > > > > it on TSM02 (new one) ? > > > > is that possible ? > > > > > > > > IS there another solution? > > > > > > > > --> [EMAIL PROTECTED]:/opt/tivoli/tsm/StorageAgent/bin # more > > > > --> dsmsta.opt > > > > > > > > SERVERNAME TSM01 > > > > DEVCONFIG devconfig.out > > > > COMMmethod TCPIP > > > > TCPPort 1511 > > > > > > > > --> [EMAIL PROTECTED]:/opt/tivoli/tsm/StorageAgent/bin # more > > > > --> devconfig.out > > > > > > > > set staname STA_4 > > > > set stapassword password > > > > set stahladdress hppbckp.vipnet.hr set stalladdress 1511 define > > > > server TSM01 serverpassword=password > > > > hladdress=axptsm01 lladdress=1500 > > > > > > > > > > > > --> the full stanza on STA server (it acts as backup server) > > > > > > > > SERVERNAME sdb_ca > > > > ENABLELANFREE yes > > > > COMMmethod TCPip > > > > LANFREETCPPort 1511 > > > > *LANFREESHMPORT 1511 > > > > LANFREECOMMMETHOD TCPip > > > > *LANFREECOMMMETHOD sharedmem > > > > LANFREETCPServeraddress hppbckp > > > > TCPPort1500 > > > > TCPServeraddress axptsm01 > > > > NodeName sdb_ca > > > > inclexcl /usr/local/etc/inclexcl.sdb > > > > Mailprog /usr/bin/mail root > > > > Schedlogname /var/adm/dsmsched_cad.sdb > > > > Schedlogretention 35 D > > > > ERRORLOGNAM/var/adm/dsmerror_sdb.log > > > > errorlogretention 35 D > > > > QUERYSCHED 12 > > > > MANAGEDSERVICESschedule webclient > > > > PASSWORDACCESS Generate > > > > COMPRESSIONNo > > > > RESOURCEUTIL 6 > > > > > > > > > > > > BIG thanks for any tips or even better a solution :-) > > > > > > > > goran > > > > > > > > > >
TS3310 LT03 to MSL 6060 LT03
hello all, I have a customer on tsm aix 5.3.5 using TS3310 and wants to DR to a system with MSL 6060. They tested 6 months ago successfully on LT02 with a 3583, but have since migrated to LT03. TSM recovers ok but when restores are run - when they finish the drive frequently becomes stuck - left sticking out of drive and then tsm seems to get the tape, put it in slot, back in drive, back in slot and the library hangs sometimes, tsm hangs too. Tried 3 different MSL's with same result. Found an advisory for similar in 5.1.3 but not mentioned since. Using IBM tapes if that's relevant. any ideas anyone? regards Nigel (UK)
Re: TS3310 LT03 to MSL 6060 LT03
Nigel, Which version of the TSM Device Drivers are you using? Can you verify that the correct TSM Device Drivers are being used on the Tape and Medium Changer devices? I have had a custormer who was also DRM-ing to an MSL6060 and they had very similar problems and found out that it was a combi of OS (W2K3), HP device drivers and TSM Device Driver. So maybe you should experiment with older versions of the TSM Device Driver. On which platform is TSM Server running? Met vriendelijke groet, with kind regards, Richard van Denzel. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nigel Howard Sent: 21 September 2007 14:02 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TS3310 LT03 to MSL 6060 LT03 hello all, I have a customer on tsm aix 5.3.5 using TS3310 and wants to DR to a system with MSL 6060. They tested 6 months ago successfully on LT02 with a 3583, but have since migrated to LT03. TSM recovers ok but when restores are run - when they finish the drive frequently becomes stuck - left sticking out of drive and then tsm seems to get the tape, put it in slot, back in drive, back in slot and the library hangs sometimes, tsm hangs too. Tried 3 different MSL's with same result. Found an advisory for similar in 5.1.3 but not mentioned since. Using IBM tapes if that's relevant. any ideas anyone? regards Nigel (UK)
Re: TS3310 LT03 to MSL 6060 LT03
Richard, yes, I think these are window/tsm issues - i am running aix. -- . regards, _/ Nigel On Fri, 21 Sep 2007, Richard van Denzel wrote: Nigel, Which version of the TSM Device Drivers are you using? Can you verify that the correct TSM Device Drivers are being used on the Tape and Medium Changer devices? I have had a custormer who was also DRM-ing to an MSL6060 and they had very similar problems and found out that it was a combi of OS (W2K3), HP device drivers and TSM Device Driver. So maybe you should experiment with older versions of the TSM Device Driver. On which platform is TSM Server running? Met vriendelijke groet, with kind regards, Richard van Denzel. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nigel Howard Sent: 21 September 2007 14:02 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TS3310 LT03 to MSL 6060 LT03 hello all, I have a customer on tsm aix 5.3.5 using TS3310 and wants to DR to a system with MSL 6060. They tested 6 months ago successfully on LT02 with a 3583, but have since migrated to LT03. TSM recovers ok but when restores are run - when they finish the drive frequently becomes stuck - left sticking out of drive and then tsm seems to get the tape, put it in slot, back in drive, back in slot and the library hangs sometimes, tsm hangs too. Tried 3 different MSL's with same result. Found an advisory for similar in 5.1.3 but not mentioned since. Using IBM tapes if that's relevant. any ideas anyone? regards Nigel (UK)
questions on Sessions
Hello. Can you tell me that it is always true everytime you kick off a backup be it from the server side or client side that it always shows 2 sessons of the same node on the Command Line Administrative Interface? I noticed that WFSB03 does not have two sessions and thoughput is slow or am I too impatient? I have kicked off a backup from the server side calling WFSB03 to run the backup now and I only see one session. Any explanation for the single session? Thanks. tsm: TSMEARTH>q sess Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - 6 Tcp/Ip IdleW 2.2 M 257 1.5 M Serv- AIX-RS/- TSMSKY er 6000 8 Tcp/Ip Run 0 S1.4 M 257 Serv- AIX-RS/- TSMSKY er 6000 194 Tcp/Ip IdleW 20.0 H 469 341 Node WinNTMAIL1TDP 214 Tcp/Ip Run 0 S 42.5 K 1.1 T Node TDP Dom- MAIL1TDP ino 1,802 Tcp/Ip IdleW0 S1.1 G 30.1 M Node WinNTWFSB03 2,178 Tcp/Ip Run 0 S 60.0 K 519 Admin WinNTWONGAV Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860)862-8164 (cell) (860)961-6976 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **
Re: questions on Sessions
It looks like TSM is scanning the node. The server has sent 1.1G. I do not remember seeing more than one session until the node starts sending data. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, September 21, 2007 1:12 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] questions on Sessions Hello. Can you tell me that it is always true everytime you kick off a backup be it from the server side or client side that it always shows 2 sessons of the same node on the Command Line Administrative Interface? I noticed that WFSB03 does not have two sessions and thoughput is slow or am I too impatient? I have kicked off a backup from the server side calling WFSB03 to run the backup now and I only see one session. Any explanation for the single session? Thanks. tsm: TSMEARTH>q sess Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - 6 Tcp/Ip IdleW 2.2 M 257 1.5 M Serv- AIX-RS/- TSMSKY er 6000 8 Tcp/Ip Run 0 S1.4 M 257 Serv- AIX-RS/- TSMSKY er 6000 194 Tcp/Ip IdleW 20.0 H 469 341 Node WinNTMAIL1TDP 214 Tcp/Ip Run 0 S 42.5 K 1.1 T Node TDP Dom- MAIL1TDP ino 1,802 Tcp/Ip IdleW0 S1.1 G 30.1 M Node WinNTWFSB03 2,178 Tcp/Ip Run 0 S 60.0 K 519 Admin WinNTWONGAV Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860)862-8164 (cell) (860)961-6976 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: questions on Sessions
Andy, I am having issues backing up WFSB03. It has Journaling on d$ . I have been keeping close watch on the throughput but it looks like it is slowing down. Is there a way to find out if the session is still alive? The 'IdleW ' state concerns me as this is the 3 time I tried to get this node backed up properly. Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 03:34:11.00 Bytes sent/second: 90192.2094000466889 Bytes received/second: 2453.0828729281767 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 03:34:43.00 Bytes sent/second: 89968.1911821780641 Bytes received/second: 2446.9993014049522 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 03:39:53.00 Bytes sent/second: 87854.2738573485939 Bytes received/second: 2389.5944819222314 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 03:58:21.00 Bytes sent/second: 81047.8967205090553 Bytes received/second: 2204.7728130899937 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 04:04:37.00 Bytes sent/second: 78971.6911494174558 Bytes received/second: 2148.3951761259112 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 04:09:10.00 Bytes sent/second: 77529.6740468227424 Bytes received/second: 2109.2382608695652 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 04:11:50.00 Bytes sent/second: 76708.7549305095962 Bytes received/second: 2086.9471872931833 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 04:18:32.00 Bytes sent/second: 74720.9205131511088 Bytes received/second: 2032.9682826199071 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 04:39:40.00 Bytes sent/second: 69074.8576281287246 Bytes received/second: 1879.6541120381406 Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860)862-8164 (cell) (860)961-6976 Andy Huebner <[EMAIL PROTECTED] ONLABS.COM>To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Re: [ADSM-L] questions on Sessions 09/21/2007 02:34 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> It looks like TSM is scanning the node. The server has sent 1.1G. I do not remember seeing more than one session until the node starts sending data. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, September 21, 2007 1:12 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] questions on Sessions Hello. Can you tell me that it is always true everytime you kick off a backup be it from the server side or client side that it always shows 2 sessons of the same node on the Command Line Administrative Interface? I noticed that WFSB03 does not have two sessions and thoughput is slow or am I too impatient? I have kicked off a backup from the server side calling WFSB03 to run the backup now and I only see one session. Any explanation for the single session? Thanks. tsm: TSMEARTH>q sess Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - 6 Tcp/Ip IdleW 2.2 M 257 1.5 M Serv- AIX-RS/- TSMSKY er 6000 8 Tcp/Ip Run 0 S1.4 M 257 Serv- AIX-RS/- TSMSKY er 6000 194 Tcp/Ip IdleW 20.0 H 469 341 Node WinNTMAIL1TDP 214 Tcp/Ip Run 0 S 42.5 K 1.1 T Node TDP Dom- MAIL1TDP ino 1,802 Tcp/Ip IdleW0 S1.1 G 30.1 M Node WinNTWFSB03 2,178 Tcp/Ip Run 0 S 60.0 K 519 Admin WinNTWONGAV Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382
Re: questions on Sessions
Avy... In TSM whenever you open a browser a "parent" session gets started on the TSM server. Also when a schedule kicks off a parent session will open. If TCP/IP failures occur the parent session tries to re-establich communications with the server. The main thing to remember is the parent session initializes child sessions to send data to the TSM server. When you specify multiple backup streams (using resourceutil option)... each new stream that is generated is a new child session. On 9/21/07, Avy Wong <[EMAIL PROTECTED]> wrote: > > Hello. > Can you tell me that it is always true everytime you kick off a > backup be it from the server side or client side that it always shows 2 > sessons of the same node on the Command Line Administrative Interface? I > noticed that WFSB03 does not have two sessions and thoughput is slow or > am > I too impatient? I have kicked off a backup from the server side calling > WFSB03 to run the backup now and I only see one session. Any explanation > for the single session? > Thanks. > > > tsm: TSMEARTH>q sess > > Sess Comm. Sess Wait Bytes Bytes Sess > Platform Client Name > Number Method StateTimeSent Recvd Type > -- -- -- -- --- --- - > > 6 Tcp/Ip IdleW 2.2 M 257 1.5 M Serv- > AIX-RS/- TSMSKY > er > 6000 > 8 Tcp/Ip Run 0 S1.4 M 257 Serv- > AIX-RS/- TSMSKY > er > 6000 > > > 194 Tcp/Ip IdleW 20.0 H 469 341 Node > WinNTMAIL1TDP > 214 Tcp/Ip Run 0 S 42.5 K 1.1 T Node > TDP Dom- MAIL1TDP > ino > > 1,802 Tcp/Ip IdleW0 S1.1 G 30.1 M Node > WinNTWFSB03 > > 2,178 Tcp/Ip Run 0 S 60.0 K 519 Admin > WinNTWONGAV > > Avy Wong > Business Continuity Administrator > Mohegan Sun > 1 Mohegan Sun Blvd > Uncasville, CT 06382 > (860)862-8164 > (cell) (860)961-6976 > > ** > The information contained in this message may be privileged and > confidential and > protected from disclosure. If the reader of this message is not the > intended recipient, or > an employee or agent responsible for delivering this message to the > intended recipient, > you are hereby notified that any dissemination, distribution, or copy of > this > communication is strictly prohibited. If you have received this > communication in error, > please notify us immediately by replying to the message and deleting it > from your > computer. > > ** > -- Regards, Sunmansun Brocade Certified Fabric Professional 4Gbit/sec --BCFP IBM Certified Deployment Professional -- TSM V5.3 IBM Certified Storage Administrator -- TSM V5
Re: questions on Sessions
I do not know how to tell if a session is alive other than if it is moving data. If your journaled backup is getting slower, that may be a problem with the journal file. When I have this happen I stop and start the journal service to clear the file, but that is another story... Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, September 21, 2007 1:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] questions on Sessions Andy, I am having issues backing up WFSB03. It has Journaling on d$ . I have been keeping close watch on the throughput but it looks like it is slowing down. Is there a way to find out if the session is still alive? The 'IdleW ' state concerns me as this is the 3 time I tried to get this node backed up properly. Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 03:34:11.00 Bytes sent/second: 90192.2094000466889 Bytes received/second: 2453.0828729281767 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 03:34:43.00 Bytes sent/second: 89968.1911821780641 Bytes received/second: 2446.9993014049522 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 03:39:53.00 Bytes sent/second: 87854.2738573485939 Bytes received/second: 2389.5944819222314 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 03:58:21.00 Bytes sent/second: 81047.8967205090553 Bytes received/second: 2204.7728130899937 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 04:04:37.00 Bytes sent/second: 78971.6911494174558 Bytes received/second: 2148.3951761259112 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 04:09:10.00 Bytes sent/second: 77529.6740468227424 Bytes received/second: 2109.2382608695652 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 04:11:50.00 Bytes sent/second: 76708.7549305095962 Bytes received/second: 2086.9471872931833 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 04:18:32.00 Bytes sent/second: 74720.9205131511088 Bytes received/second: 2032.9682826199071 Session: 1802 Client: WFSB03 State: IdleW Elapsed Time: 0 04:39:40.00 Bytes sent/second: 69074.8576281287246 Bytes received/second: 1879.6541120381406 Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860)862-8164 (cell) (860)961-6976 Andy Huebner <[EMAIL PROTECTED] ONLABS.COM> To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Re: [ADSM-L] questions on Sessions 09/21/2007 02:34 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> It looks like TSM is scanning the node. The server has sent 1.1G. I do not remember seeing more than one session until the node starts sending data. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, September 21, 2007 1:12 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] questions on Sessions Hello. Can you tell me that it is always true everytime you kick off a backup be it from the server side or client side that it always shows 2 sessons of the same node on the Command Line Administrative Interface? I noticed that WFSB03 does not have two sessions and thoughput is slow or am I too impatient? I have kicked off a backup from the server side calling WFSB03 to run the backup now and I only see one session. Any explanation for the single session? Thanks. tsm: TSMEARTH>q sess Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - 6 Tcp/Ip IdleW 2.2 M 257 1.5 M Serv- AIX-RS/- TSMSKY er 6000 8 Tcp/Ip Run 0 S1.4 M 257 Serv- AIX-RS/- TSMSKY er 6000 194 Tcp/Ip IdleW 20.0 H 469 341 Node WinNTMAIL1TDP
Re: questions on Sessions
On Sep 21, 2007, at 2:58 PM, Avy Wong wrote: I am having issues backing up WFSB03. It has Journaling on d $ . I have been keeping close watch on the throughput but it looks like it is slowing down. Is there a way to find out if the session is still alive? The 'IdleW ' state concerns me as this is the 3 time I tried to get this node backed up properly. Avy - When posting, please supply the full info regarding a problem... You imply that the prior two attempts failed to back up the node: what condition or error was encountered in the presumed failures in the prior attempts? Consider the amount of inventory information being sent from the TSM server to the client: The client ostensibly needs to hold that info in memory, and if this is a modestly implemented computer, then the amount of real memory is probably limited, with a lot already being consumed by the OS and other apps on the machine; and if so, then virtual memory is being increasingly used, and certainly things will slow down. A good look at the Task Manager on that system may be revealing. This may be a very imbalanced Windows system, with far more data than it has realistic memory to deal with it all. Refer back to Andy's posting from yesterday afternoon. You seem to have a single Producer session chugging away, doing its best to collect the Active Files inventory from the server before starting traversal of the file system seeking backup candidates. And, with over a GB of data already having been sent from TSM server to client, this doesn't sound like a JBB to me. Richard Sims at Boston University
Backing up unavailable file systems causes objects to become inactive.
Greetings, I know this is "working as designed", but I was hoping someone might have a work-a-round. Several times over the last 10 or so years, we have had file systems on servers cause problems and become unavailable, either through inadvertent dismounts or hardware issues. If we don't catch this quickly, TSM's behavior in these cases leaves something to be desired. TSM will assume that we have thrown away our data and will happily inactivate all of it's backed up objects. When we discover the problem, we are faced with backing up the data again (unless it was a true disk failure) and even if it is a recovery scenario, we need to do a point in time restore, as all active data has been inactivated (also followed by another complete backup). What I'm looking for is ideas as to what I could do to automatically cancel any active backup job if a file system becomes unavailable for whatever reason. Perhaps in some future version of TSM, a flag could be added for each domain statement to fail the backup and keep the previously stored data unless something explicit was entered to confirm the intent to expire. Thanks for listening...Any thoughts? Bob Levad Winnebago Industries, Inc. This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.
Re: INCLUDE.ENCRYPT and the Encryptkey
When encryption is done by the client, the key is stored somewhere on the client machine (with Windows, it's encrypted and stored in the registry. For *IX, I think it's in /etc somewhere, also encrypted). If you try to restore a file(s) to the same machine, the TSM client gets the encryption key from its hiding place in the registry and decrypts the file on the fly. If you try to restore to any OTHER machine, the TSM client won't find that key stored on the machine, and when you start the restore process you will be prompted for the encryption key. If you have data that has been encrypted with different keys, you're going to have a heck of a time getting through the restore. If you don't know the key, you won't get the data back at all. TDP's are different; you don't provide the key, it's created on the fly and stored in the TSM DB, so you don't need to know what it is. W > I must admit I'm a bit confused on this option. Maybe someone who's used > can give some advice. The questions I have revolve around testing in a > DR environment where the server name on the other end would be different > but the dsm.opt 'would' have the same name as the node at another site > so as to be able restore that data. We currently export tapes for this > process so I'm wondering how to get the data restored at the DR site > once imported there if the data is encrypted. I've been reading the > "readme" for one of the client 5.3 levels along with other things I can > find, and although somewhat clear a bit confusing. > > > > Has anyone performed this type of data transfer at a DR site and if so > what kind f issues did you run in to? Any specifics are welcome if you > actually have the steps in place. > > > > Thanks, > > > > Geoff Gill > TSM Administrator > PeopleSoft Sr. Systems Administrator > SAIC M/S-G1b > (858)826-4062 > Email: [EMAIL PROTECTED] > > >
Re: Backing up unavailable file systems causes objects to become inactive.
Write a script in your language of choice that compares the mount list with a list of crucial filesystems like "/etc/ filesystems_crucial_to_backup" Launch this script from the preschedulecmd, and if it returns a non- zero code, the backup won't run. For extra surety, you can look for files that should always be found on a mounted filesystem, or look for files you've written to the underlying mount point that you hope you never see. [RC] On Sep 21, 2007, at 2:22 PM, Bob Levad wrote: Greetings, I know this is "working as designed", but I was hoping someone might have a work-a-round. Several times over the last 10 or so years, we have had file systems on servers cause problems and become unavailable, either through inadvertent dismounts or hardware issues. If we don't catch this quickly, TSM's behavior in these cases leaves something to be desired. TSM will assume that we have thrown away our data and will happily inactivate all of it's backed up objects. When we discover the problem, we are faced with backing up the data again (unless it was a true disk failure) and even if it is a recovery scenario, we need to do a point in time restore, as all active data has been inactivated (also followed by another complete backup). What I'm looking for is ideas as to what I could do to automatically cancel any active backup job if a file system becomes unavailable for whatever reason. Perhaps in some future version of TSM, a flag could be added for each domain statement to fail the backup and keep the previously stored data unless something explicit was entered to confirm the intent to expire. Thanks for listening...Any thoughts? Bob Levad Winnebago Industries, Inc. This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.
