Re: Backupset restore error
Thanks Andrew, Yes, The original node is also a windows machine and the client was 5.3 I believe. No, I did not use -virtualnodename=logpian I was following some other examples that I found in the Tivoli guide regarding backupset restore. I will try your suggestions. Best Regards! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew Raibeck Sent: Thursday, March 14, 2013 5:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Timothy, You said that the the node's data on the backup set did not come from the system where you are running the restore. Is the original node also Windows? Did the original node back up the data using a later version of TSM client than 6.2? When you started dsmc, did you use the -virtualnodename=logpian ? You need to connect to the TSM server using the node whose data you want to restore. On Windows, the default destination for restore operations is the same as the source. Assuming you want to restore the data to a different machine (not go back to the logpian machine), you need to specify a source and destination; and you should use the -backupsetname= option to specify the backup set name: restore backupset \\logpian\c$\ c:\ -backupsetname=WEEKLYLOGPIANBKUP.950286387 -subdir=yes In this example: \\logpian\c$ is the file space for logpian's C: drive c:\ is the local C: drive. You can also specify C:\someotherdir\ if you want. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support pages: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli +Storage+Manager https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2013-03-14 09:23:30: From: Hughes, Timothy timothy.hug...@oit.state.nj.us To: ADSM-L@vm.marist.edu, Date: 2013-03-14 09:29 Subject: Re: Backupset restore error Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Thanks Adrian, That variation didn't work tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Davis, Adrian Sent: Thursday, March 14, 2013 9:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Try:- restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Best Regards, =Adrian -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: 14 March 2013 12:13 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backupset restore error Hi Steven, Thanks I tried that also still received the same error tsm restore backupset WEEKLYLOGPIANBKUP.950286387- subdir=yes ANS1107E Invalid option/value: '-' tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes ANS1107E Invalid option/value: '-' tsm Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Harris Sent: Wednesday, March 13, 2013 3:40 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Hi Tim in your command there is no space between the backupset name and the -subdir=yes. Could that be the issue? Regards Steve Steven Harris TSM Admin Canberra Australia. On 14/03/2013 4:44 AM, Hughes, Timothy wrote: Hi, I am trying to restore a backupset from a TSM server to a Windows machine using the following command restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes tsm restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... I keep getting the following error. Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. The backupset is there and it has data not sure why it's
Re: Backupset restore error
Mahesh, No, I don't see the error that I am getting in those apar's Best Regards! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tailor, Mahesh C. Sent: Thursday, March 14, 2013 6:19 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error There are/were a bunch of APAR's with backupset restores failures. Is one of them the cause of this failure? http://www-01.ibm.com/support/docview.wss?uid=swg21426379 From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] on behalf of Andrew Raibeck [stor...@us.ibm.com] Sent: Thursday, March 14, 2013 17:45 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backupset restore error Timothy, You said that the the node's data on the backup set did not come from the system where you are running the restore. Is the original node also Windows? Did the original node back up the data using a later version of TSM client than 6.2? When you started dsmc, did you use the -virtualnodename=logpian ? You need to connect to the TSM server using the node whose data you want to restore. On Windows, the default destination for restore operations is the same as the source. Assuming you want to restore the data to a different machine (not go back to the logpian machine), you need to specify a source and destination; and you should use the -backupsetname= option to specify the backup set name: restore backupset \\logpian\c$\ c:\ -backupsetname=WEEKLYLOGPIANBKUP.950286387 -subdir=yes In this example: \\logpian\c$ is the file space for logpian's C: drive c:\ is the local C: drive. You can also specify C:\someotherdir\ if you want. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support pages: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli +Storage+Manager https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2013-03-14 09:23:30: From: Hughes, Timothy timothy.hug...@oit.state.nj.us To: ADSM-L@vm.marist.edu, Date: 2013-03-14 09:29 Subject: Re: Backupset restore error Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Thanks Adrian, That variation didn't work tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Davis, Adrian Sent: Thursday, March 14, 2013 9:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Try:- restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Best Regards, =Adrian -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: 14 March 2013 12:13 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backupset restore error Hi Steven, Thanks I tried that also still received the same error tsm restore backupset WEEKLYLOGPIANBKUP.950286387- subdir=yes ANS1107E Invalid option/value: '-' tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes ANS1107E Invalid option/value: '-' tsm Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Harris Sent: Wednesday, March 13, 2013 3:40 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Hi Tim in your command there is no space between the backupset name and the -subdir=yes. Could that be the issue? Regards Steve Steven Harris TSM Admin Canberra Australia. On 14/03/2013 4:44 AM, Hughes, Timothy wrote: Hi, I am trying to restore a backupset from a TSM server to a Windows machine using the following command restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes tsm restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... I
Re: Backupset restore error
Hi Steven, Thanks I tried that also still received the same error tsm restore backupset WEEKLYLOGPIANBKUP.950286387- subdir=yes ANS1107E Invalid option/value: '-' tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes ANS1107E Invalid option/value: '-' tsm Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Harris Sent: Wednesday, March 13, 2013 3:40 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Hi Tim in your command there is no space between the backupset name and the -subdir=yes. Could that be the issue? Regards Steve Steven Harris TSM Admin Canberra Australia. On 14/03/2013 4:44 AM, Hughes, Timothy wrote: Hi, I am trying to restore a backupset from a TSM server to a Windows machine using the following command restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes tsm restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... I keep getting the following error. Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. The backupset is there and it has data not sure why it's telling me it does not exist or have any data. Anyone have any ever have an issue with restoring a backupset? Fyi- The Windows Client Server is not the one that the backupset was created for. Node Name: logpian Backup Set Name: WEEKLYLOGPIANKUP.950286387 Data Type: File Date/Time: 03/11/13 10:00:32 Retention Period: 31 Device Class Name: LTO3CLASS Description: No Description Has Table of Contents (TOC)?: No TSM Version 6.2 Windows client 6.2.4 Thanks in advance!
Re: Backupset restore error
Try:- restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Best Regards, =Adrian -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: 14 March 2013 12:13 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backupset restore error Hi Steven, Thanks I tried that also still received the same error tsm restore backupset WEEKLYLOGPIANBKUP.950286387- subdir=yes ANS1107E Invalid option/value: '-' tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes ANS1107E Invalid option/value: '-' tsm Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Harris Sent: Wednesday, March 13, 2013 3:40 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Hi Tim in your command there is no space between the backupset name and the -subdir=yes. Could that be the issue? Regards Steve Steven Harris TSM Admin Canberra Australia. On 14/03/2013 4:44 AM, Hughes, Timothy wrote: Hi, I am trying to restore a backupset from a TSM server to a Windows machine using the following command restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes tsm restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... I keep getting the following error. Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. The backupset is there and it has data not sure why it's telling me it does not exist or have any data. Anyone have any ever have an issue with restoring a backupset? Fyi- The Windows Client Server is not the one that the backupset was created for. Node Name: logpian Backup Set Name: WEEKLYLOGPIANKUP.950286387 Data Type: File Date/Time: 03/11/13 10:00:32 Retention Period: 31 Device Class Name: LTO3CLASS Description: No Description Has Table of Contents (TOC)?: No TSM Version 6.2 Windows client 6.2.4 Thanks in advance! DISCLAIMER This message is confidential and intended solely for the use of the individual or entity it is addressed to. If you have received it in error, please contact the sender and delete the e-mail. Please note that we may monitor and check emails to safeguard the Council network from viruses, hoax messages or other abuse of the Council’s systems. To see the full version of this disclaimer please visit the following address: http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm For advice and assistance about online security and protection from internet threats visit the Get Safe Online website at http://www.getsafeonline.org
Re: Backupset restore error
Thanks Adrian, That variation didn't work tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Davis, Adrian Sent: Thursday, March 14, 2013 9:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Try:- restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Best Regards, =Adrian -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: 14 March 2013 12:13 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backupset restore error Hi Steven, Thanks I tried that also still received the same error tsm restore backupset WEEKLYLOGPIANBKUP.950286387- subdir=yes ANS1107E Invalid option/value: '-' tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes ANS1107E Invalid option/value: '-' tsm Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Harris Sent: Wednesday, March 13, 2013 3:40 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Hi Tim in your command there is no space between the backupset name and the -subdir=yes. Could that be the issue? Regards Steve Steven Harris TSM Admin Canberra Australia. On 14/03/2013 4:44 AM, Hughes, Timothy wrote: Hi, I am trying to restore a backupset from a TSM server to a Windows machine using the following command restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes tsm restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... I keep getting the following error. Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. The backupset is there and it has data not sure why it's telling me it does not exist or have any data. Anyone have any ever have an issue with restoring a backupset? Fyi- The Windows Client Server is not the one that the backupset was created for. Node Name: logpian Backup Set Name: WEEKLYLOGPIANKUP.950286387 Data Type: File Date/Time: 03/11/13 10:00:32 Retention Period: 31 Device Class Name: LTO3CLASS Description: No Description Has Table of Contents (TOC)?: No TSM Version 6.2 Windows client 6.2.4 Thanks in advance! DISCLAIMER This message is confidential and intended solely for the use of the individual or entity it is addressed to. If you have received it in error, please contact the sender and delete the e-mail. Please note that we may monitor and check emails to safeguard the Council network from viruses, hoax messages or other abuse of the Council’s systems. To see the full version of this disclaimer please visit the following address: http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm For advice and assistance about online security and protection from internet threats visit the Get Safe Online website at http://www.getsafeonline.org
Re: Backupset restore error
Timothy, You said that the the node's data on the backup set did not come from the system where you are running the restore. Is the original node also Windows? Did the original node back up the data using a later version of TSM client than 6.2? When you started dsmc, did you use the -virtualnodename=logpian ? You need to connect to the TSM server using the node whose data you want to restore. On Windows, the default destination for restore operations is the same as the source. Assuming you want to restore the data to a different machine (not go back to the logpian machine), you need to specify a source and destination; and you should use the -backupsetname= option to specify the backup set name: restore backupset \\logpian\c$\ c:\ -backupsetname=WEEKLYLOGPIANBKUP.950286387 -subdir=yes In this example: \\logpian\c$ is the file space for logpian's C: drive c:\ is the local C: drive. You can also specify C:\someotherdir\ if you want. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support pages: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli +Storage+Manager https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2013-03-14 09:23:30: From: Hughes, Timothy timothy.hug...@oit.state.nj.us To: ADSM-L@vm.marist.edu, Date: 2013-03-14 09:29 Subject: Re: Backupset restore error Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Thanks Adrian, That variation didn't work tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Davis, Adrian Sent: Thursday, March 14, 2013 9:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Try:- restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Best Regards, =Adrian -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: 14 March 2013 12:13 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backupset restore error Hi Steven, Thanks I tried that also still received the same error tsm restore backupset WEEKLYLOGPIANBKUP.950286387- subdir=yes ANS1107E Invalid option/value: '-' tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes ANS1107E Invalid option/value: '-' tsm Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Harris Sent: Wednesday, March 13, 2013 3:40 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Hi Tim in your command there is no space between the backupset name and the -subdir=yes. Could that be the issue? Regards Steve Steven Harris TSM Admin Canberra Australia. On 14/03/2013 4:44 AM, Hughes, Timothy wrote: Hi, I am trying to restore a backupset from a TSM server to a Windows machine using the following command restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes tsm restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... I keep getting the following error. Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. The backupset is there and it has data not sure why it's telling me it does not exist or have any data. Anyone have any ever have an issue with restoring a backupset? Fyi- The Windows Client Server is not the one that the backupset was created for. Node Name: logpian Backup Set Name: WEEKLYLOGPIANKUP.950286387 Data Type: File Date/Time: 03/11/13 10:00:32 Retention Period: 31 Device Class Name: LTO3CLASS Description: No Description Has Table of Contents (TOC)?: No TSM Version 6.2 Windows client 6.2.4 Thanks in advance! DISCLAIMER
Re: Backupset restore error
There are/were a bunch of APAR's with backupset restores failures. Is one of them the cause of this failure? http://www-01.ibm.com/support/docview.wss?uid=swg21426379 From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] on behalf of Andrew Raibeck [stor...@us.ibm.com] Sent: Thursday, March 14, 2013 17:45 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backupset restore error Timothy, You said that the the node's data on the backup set did not come from the system where you are running the restore. Is the original node also Windows? Did the original node back up the data using a later version of TSM client than 6.2? When you started dsmc, did you use the -virtualnodename=logpian ? You need to connect to the TSM server using the node whose data you want to restore. On Windows, the default destination for restore operations is the same as the source. Assuming you want to restore the data to a different machine (not go back to the logpian machine), you need to specify a source and destination; and you should use the -backupsetname= option to specify the backup set name: restore backupset \\logpian\c$\ c:\ -backupsetname=WEEKLYLOGPIANBKUP.950286387 -subdir=yes In this example: \\logpian\c$ is the file space for logpian's C: drive c:\ is the local C: drive. You can also specify C:\someotherdir\ if you want. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support pages: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli +Storage+Manager https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2013-03-14 09:23:30: From: Hughes, Timothy timothy.hug...@oit.state.nj.us To: ADSM-L@vm.marist.edu, Date: 2013-03-14 09:29 Subject: Re: Backupset restore error Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Thanks Adrian, That variation didn't work tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Davis, Adrian Sent: Thursday, March 14, 2013 9:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Try:- restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Best Regards, =Adrian -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: 14 March 2013 12:13 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backupset restore error Hi Steven, Thanks I tried that also still received the same error tsm restore backupset WEEKLYLOGPIANBKUP.950286387- subdir=yes ANS1107E Invalid option/value: '-' tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 -subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. tsm restore backupset WEEKLYLOGPIANBKUP.950286387 - subdir=yes ANS1107E Invalid option/value: '-' tsm Best Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Harris Sent: Wednesday, March 13, 2013 3:40 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupset restore error Hi Tim in your command there is no space between the backupset name and the -subdir=yes. Could that be the issue? Regards Steve Steven Harris TSM Admin Canberra Australia. On 14/03/2013 4:44 AM, Hughes, Timothy wrote: Hi, I am trying to restore a backupset from a TSM server to a Windows machine using the following command restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes tsm restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... I keep getting the following error. Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. The backupset is there and it has data not sure why it's telling me it does not exist or have any data. Anyone have any ever have an issue
Backupset restore error
Hi, I am trying to restore a backupset from a TSM server to a Windows machine using the following command restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes tsm restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... I keep getting the following error. Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. The backupset is there and it has data not sure why it's telling me it does not exist or have any data. Anyone have any ever have an issue with restoring a backupset? Fyi- The Windows Client Server is not the one that the backupset was created for. Node Name: logpian Backup Set Name: WEEKLYLOGPIANKUP.950286387 Data Type: File Date/Time: 03/11/13 10:00:32 Retention Period: 31 Device Class Name: LTO3CLASS Description: No Description Has Table of Contents (TOC)?: No TSM Version 6.2 Windows client 6.2.4 Thanks in advance!
Re: Backupset restore error
Hi Tim in your command there is no space between the backupset name and the -subdir=yes. Could that be the issue? Regards Steve Steven Harris TSM Admin Canberra Australia. On 14/03/2013 4:44 AM, Hughes, Timothy wrote: Hi, I am trying to restore a backupset from a TSM server to a Windows machine using the following command restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes tsm restore backupset WEEKLYLOGPIANBKUP.950286387-subdir=yes Restore function invoked. ANS1247I Waiting for files from the server... I keep getting the following error. Restore Processing Interrupted!! ANS1510W The specified backupset either does not exist, or does not contain file data. The backupset is there and it has data not sure why it's telling me it does not exist or have any data. Anyone have any ever have an issue with restoring a backupset? Fyi- The Windows Client Server is not the one that the backupset was created for. Node Name: logpian Backup Set Name: WEEKLYLOGPIANKUP.950286387 Data Type: File Date/Time: 03/11/13 10:00:32 Retention Period: 31 Device Class Name: LTO3CLASS Description: No Description Has Table of Contents (TOC)?: No TSM Version 6.2 Windows client 6.2.4 Thanks in advance!
Re: backupset - restore permissions
Dear Amit, looks like you are archiving the same tons of files and tons of data again and again. Why no use backups to backup copygroups (same Management class as for archives) set to versioning NOLIMIT, as to make them keep data just like archive copygroups. Then set up incremental backups, which will in fact be virtual full archives, without the load on the database and storage pools. This should really cut the load, keeping restore (instead of retrieve) a very simple and straightforward procedure. Off course, may be hard to sell... Kind regards, Markus -- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet. Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch virenbefallene Software oder E-Mails aus. Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden. __ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail or of parts hereof is strictly forbidden. We have taken precautions to minimize the risk of transmitting software viruses but nevertheless advise you to carry out your own virus checks on any attachment of this message. We accept no liability for loss or damage caused by software viruses except in case of gross negligence or willful behaviour. Any e-mail messages from the Bank are sent in good faith, but shall not be binding or construed as constituting any kind of obligation on the part of the Bank.
Re: backupset - restore permissions
Hi, Why dont you first make a tar file of your data and then archive it? This will keep the TSM DB size very small as for one archive you will have just one entry in TSM database. Of course partial retrieval is not possible in this case. On Sat, Aug 25, 2012 at 8:48 AM, amit jain amit12.j...@gmail.com wrote: Hi, We are planning to change our archive strategy. Planning to do one time full backup and then create two backup sets, latter delete the backups. With this strategy we can have single tsm instance to cover most of our archive needs, as this will not fill up the TSM DB size. Also we can have the archive without having to bother about the archive getting terminated in between and triggering the archive again. Any one knows the downside of backups set apart from the fact that partial restores take longer. Any other issues or suggestions ? What about file permissions ? Somebody told me that on linux the restore may not have same permissions ? We will be using it for archiving big filesets. With version 6.2 TSM DB size has reached about 1TB with 2 archives. So DB size is big driver for us to move to backupsets. Any one using backupssets ? How is the permissions while restore for LINUX filesystems ? Any inputs will be of help. Thanks Amit -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853
Re: backupset - restore permissions
Hi Ashish, Our archive data sizes are about 100TB+, with issues of partial restore, we want to avoid it. Any inputs for the backupsets? Restore permissions ? Thanks Amit On Fri, Aug 24, 2012 at 11:47 PM, ashish sharma ashishsharm...@gmail.comwrote: Hi, Why dont you first make a tar file of your data and then archive it? This will keep the TSM DB size very small as for one archive you will have just one entry in TSM database. Of course partial retrieval is not possible in this case. On Sat, Aug 25, 2012 at 8:48 AM, amit jain amit12.j...@gmail.com wrote: Hi, We are planning to change our archive strategy. Planning to do one time full backup and then create two backup sets, latter delete the backups. With this strategy we can have single tsm instance to cover most of our archive needs, as this will not fill up the TSM DB size. Also we can have the archive without having to bother about the archive getting terminated in between and triggering the archive again. Any one knows the downside of backups set apart from the fact that partial restores take longer. Any other issues or suggestions ? What about file permissions ? Somebody told me that on linux the restore may not have same permissions ? We will be using it for archiving big filesets. With version 6.2 TSM DB size has reached about 1TB with 2 archives. So DB size is big driver for us to move to backupsets. Any one using backupssets ? How is the permissions while restore for LINUX filesystems ? Any inputs will be of help. Thanks Amit -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853
backupset - restore permissions
Hi, We are planning to change our archive strategy. Planning to do one time full backup and then create two backup sets, latter delete the backups. With this strategy we can have single tsm instance to cover most of our archive needs, as this will not fill up the TSM DB size. Also we can have the archive without having to bother about the archive getting terminated in between and triggering the archive again. Any one knows the downside of backups set apart from the fact that partial restores take longer. Any other issues or suggestions ? What about file permissions ? Somebody told me that on linux the restore may not have same permissions ? We will be using it for archiving big filesets. With version 6.2 TSM DB size has reached about 1TB with 2 archives. So DB size is big driver for us to move to backupsets. Any one using backupssets ? How is the permissions while restore for LINUX filesystems ? Any inputs will be of help. Thanks Amit
Re: Ang: [ADSM-L] Backupset restore question - different server OS's
Yes, things tend to move quickly around here and I might be attempting to use TSM in an unconventional manner. I have to move about 90 TB of data from data center A to Data center B. The data centers have dissimilar SAN storage and very limited WAN connectivity between each other. Each server at the new data center will be a new system and needs to be seeded with data from the currently running system. Some servers will only require a few GB of seed data while others will require several hundred GB and a few have several TB of seed data. I have to have a data migration solution ready next week and should begin migration shortly after Labor Day. My Plan in a nutshell: 1. Generate a backupset on a TSM V5.5 AIX server on encrypted 3592 media at data center A 2. Ship the encrypted media to data center B 3. Define a backupset and generate a backupsetTOC(optional) from the encrypted 3592 media on the TSM v6.2 Linux server at Data center B. Data center B has the appropriate encryption keys to decrypt the media. 4. Restore backupset data to the appropriate client from the TSM V6.2 Linux server at Data center B - No TSM DB Upgrades required or planed. The TSM V6.2 Linux server is a fresh install. There are two methods of performing a backupset restore - 1. Attach client to media containing the backupset data OR 2. From a TSM server containing backupset data. (Ref: TSM for AIX V5.5 Admin Guide - pg 454). I plan to perform the second. I plan to move the backupset data from server to serverB as described in TSM for AIX V6.2 Admin Guide pg. 520 as such there should be no issues with DB differences between TSM V5 V6 unless the data written to the backupset media is significantly different. I also ran across IC62418: Backup set and Table of Contents support in Tivoli Storage Manager Version 6.1 which discusses backupset compatibility between V5 TSM servers and V6.1.2 or higher TSM servers in the Problem Conclusion section. Since I have not built the Linux TSM server yet, I cannot test the compatibility of the 3592 media written by AIX and then read (hopefully) by Linux and this has me concerned. It looks like a backupsetTOC is not required but would be nice to have. Your comments are welcome. Thank you, 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:ADSM-L@VM.MARIST.EDU] On Behalf Of Daniel Sparrman Sent: Monday, August 22, 2011 3:54 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Ang: [ADSM-L] Backupset restore question - different server OS's I've read through your question 3 times now and I'm still trying to figure out what you're doing :) You're mentioning creating backupsets. For me, a backupset is a way of restoring a client without having to transfer the data across the LAN. But you're also mentioning TSM servers placed on AIX and Linux respectively. Are you trying to move a TSM server from AIX to Linux? I've never heard of anyone transfering client data betweeen TSM servers using backupsets, I didnt even know it was possible. Did you mix it up and mean export tapes? Cant answer for AIX Linux, but for example AIX Windows wont work since the way the OS writes/reads labels of the tape isnt the same (tried it, didnt work for me, perhaps someone else was more lucky). Is there a reason you dont want to do a server-to-server export? Generally (and I'm only talking from my own experience) tapes, databases and normal volumes arent compatible between OS's. The way they handle tapes are just too different. If you try to explain what you're trying to accomplish, perhaps it's easier to help. Or it's just getting late and I'm too tired :) Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Strand, Neil B. nbstr...@leggmason.com Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Datum: 08/22/2011 20:25 Ärende: [ADSM-L] Backupset restore question - different server OS's I am currently running TSM V5.5 on AIX. I am setting up a TSM V6.2 server on Linux at a new data center. I would like to use backup sets to transfer client data from the old to the new data centers. This backupset data will be used to populate the newly built clients - not as a backup data store. Both the old and new data centers have IBM TS1120 drives in their TS3500 libraries. I don't plan to attach each client to tape drives and would perform the backupset restore via TSM server. Does anyone know or have experienced creating a backup set on a TSM V5 server on AIX and then recovering that backup to a TSM V6 server on Linux? The Linux server
Re: Ang: [ADSM-L] Backupset restore question - different server OS's
On 08/23/2011 11:16 AM, Strand, Neil B. wrote: Yes, things tend to move quickly around here and I might be attempting to use TSM in an unconventional manner. I have to move about 90 TB of data from data center A to Data center B. The data centers have dissimilar SAN storage and very limited WAN connectivity between each other. Each server at the new data center will be a new system and needs to be seeded with data from the currently running system. Some servers will only require a few GB of seed data while others will require several hundred GB and a few have several TB of seed data. I have to have a data migration solution ready next week and should begin migration shortly after Labor Day. My Plan in a nutshell: 1. Generate a backupset on a TSM V5.5 AIX server on encrypted 3592 media at data center A 2. Ship the encrypted media to data center B 3. Define a backupset and generate a backupsetTOC(optional) from the encrypted 3592 media on the TSM v6.2 Linux server at Data center B. Data center B has the appropriate encryption keys to decrypt the media. 4. Restore backupset data to the appropriate client from the TSM V6.2 Linux server at Data center B - No TSM DB Upgrades required or planed. The TSM V6.2 Linux server is a fresh install. This turns on whether the backupset format is as architecture-agnostic as the export format. I would expect the export/import to work across architectures; for the backupset, I wouldn't know where to put my money. I would say that it will either work reliably , or fail immediately. You might attempt it with something sized less than a tape volume, (or even just a few GB, and send it over the WAN) and find out. The encryption et. al. are red herrings in the test process, I'd skip it. (and then test with non-sensitive data, natch) - Allen S. Rout
Backupset restore question - different server OS's
I am currently running TSM V5.5 on AIX. I am setting up a TSM V6.2 server on Linux at a new data center. I would like to use backup sets to transfer client data from the old to the new data centers. This backupset data will be used to populate the newly built clients - not as a backup data store. Both the old and new data centers have IBM TS1120 drives in their TS3500 libraries. I don't plan to attach each client to tape drives and would perform the backupset restore via TSM server. Does anyone know or have experienced creating a backup set on a TSM V5 server on AIX and then recovering that backup to a TSM V6 server on Linux? The Linux server would need to generate a TOC from the tape created by the AIX server. The TSM V6.2 server should be able to work with the backup set. It is the OS tape read/write compatibility that I am unsure of. I don't currently have a Linux box to play with and cannot test this scenario. Your comment is highly welcomed. Thank you, 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. 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.
Ang: [ADSM-L] Backupset restore question - different server OS's
I've read through your question 3 times now and I'm still trying to figure out what you're doing :) You're mentioning creating backupsets. For me, a backupset is a way of restoring a client without having to transfer the data across the LAN. But you're also mentioning TSM servers placed on AIX and Linux respectively. Are you trying to move a TSM server from AIX to Linux? I've never heard of anyone transfering client data betweeen TSM servers using backupsets, I didnt even know it was possible. Did you mix it up and mean export tapes? Cant answer for AIX Linux, but for example AIX Windows wont work since the way the OS writes/reads labels of the tape isnt the same (tried it, didnt work for me, perhaps someone else was more lucky). Is there a reason you dont want to do a server-to-server export? Generally (and I'm only talking from my own experience) tapes, databases and normal volumes arent compatible between OS's. The way they handle tapes are just too different. If you try to explain what you're trying to accomplish, perhaps it's easier to help. Or it's just getting late and I'm too tired :) Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Strand, Neil B. nbstr...@leggmason.com Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Datum: 08/22/2011 20:25 Ärende: [ADSM-L] Backupset restore question - different server OS's I am currently running TSM V5.5 on AIX. I am setting up a TSM V6.2 server on Linux at a new data center. I would like to use backup sets to transfer client data from the old to the new data centers. This backupset data will be used to populate the newly built clients - not as a backup data store. Both the old and new data centers have IBM TS1120 drives in their TS3500 libraries. I don't plan to attach each client to tape drives and would perform the backupset restore via TSM server. Does anyone know or have experienced creating a backup set on a TSM V5 server on AIX and then recovering that backup to a TSM V6 server on Linux? The Linux server would need to generate a TOC from the tape created by the AIX server. The TSM V6.2 server should be able to work with the backup set. It is the OS tape read/write compatibility that I am unsure of. I don't currently have a Linux box to play with and cannot test this scenario. Your comment is highly welcomed. Thank you, 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. 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.
Netware backupset restore
Hi How do you make a netware client restore a backupset of another netware client? Ideally to an assigned temporary directory. Cheers Jim Jim Young - Computer Operations Coordinator IT Operations, Cattles Group IT. Ext. 2424 Cattles plc Registered in England No: 133540 Kingston House, Centre 27 Business Park, Woodhead Road, Birstall, Batley, WF179TD. The views and opinions expressed herein are those of the author and not of Cattles plc or any of its subsidiaries.The content of this e-mail is confidential, may contain privileged material and is intended solely for the recipient(s) named above. If you receive this in error, please notify the sender immediately and delete this e-mail. Please note that neither Cattles plc nor the sender accepts any responsibility for viruses and it is your responsibility to scan the email and attachments(if any). No contracts or agreements may be concluded on behalf of Cattles plc or its subsidiaries by means of email communications. This email has been verified Virus free by Cattles and Sophos Puremessage scanning service.
performance of restore v. retrieve v. backupset restore
We are moving off of one disk array onto another, and I have 3 windows machines that have filesystems that need to be moved. We have come to the conclusion that using TSM to move the data will be the simplest and most straight forward way to do it. I am trying to decide whether to do a plain restore, create a backupset and restore it, or use archive. I am reading the ADSM Quick Facts file to learn about performance issues. The clients are all 5.2.2.0 The server is also 5.2.2.0 on AIX. We have LTO2 tapes in a robot with 6 drives. Each disk volume to be moved is 39.9 G. One is 20% full, one is 50% full, and one is 95% full. Since my tapes hold 200G, if I use a backupset, I will have only 1 tape mount. However, if I use a regular restore, I can have the restore multiple threads and drives (given that maxnummp is high and mountretention is low). I do not have collocation on, but I could change that and force a full backup of the filesystems that need to be moved, so they would be collocated, but that wouldn't be much different than using a backupset, would it? Any advice? Nancy Reeves Technical Support, Wichita State University [EMAIL PROTECTED] 316-978-3860
Re: performance of restore v. retrieve v. backupset restore
== On Thu, 13 Oct 2005 10:57:30 -0500, Nancy Reeves [EMAIL PROTECTED] said: The clients are all 5.2.2.0 The server is also 5.2.2.0 on AIX. We have LTO2 tapes in a robot with 6 drives. Each disk volume to be moved is 39.9 G. One is 20% full, one is 50% full, and one is 95% full. Since my tapes hold 200G, if I use a backupset, I will have only 1 tape mount. However, if I use a regular restore, I can have the restore multiple threads and drives (given that maxnummp is high and mountretention is low). I do not have collocation on, but I could change that and force a full backup of the filesystems that need to be moved, so they would be collocated, but that wouldn't be much different than using a backupset, would it? Any advice? If you MOVE NODEDATA, perhaps to a (temporary) collocated stgpool, then you can get all the data to one place without having to back it all up again. If you've got enough disk, you might want to MOVE NODEDATA again, just before the restore, onto FILE or DISK devclasses. Depending on your tape architecture, it could imprrove your restore speed anywhere from a bit to a lot. In your shoes, I'd shove the data in a FILE devclass with volume size ~5GB just before the restore. Multiple threads, because multiple volumes, and disk's good seek behavior. - Allen S. Rout
Re: performance of restore v. retrieve v. backupset restore
Does MOVE NODEDATA move all files of the node, or just the active ones? Nancy Reeves Technical Support, Wichita State University [EMAIL PROTECTED] 316-978-3860 ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 10/13/2005 11:25:07 AM: == On Thu, 13 Oct 2005 10:57:30 -0500, Nancy Reeves Nancy. [EMAIL PROTECTED] said: The clients are all 5.2.2.0 The server is also 5.2.2.0 on AIX. We have LTO2 tapes in a robot with 6 drives. Each disk volume to be moved is 39.9 G. One is 20% full, one is 50% full, and one is 95% full. Since my tapes hold 200G, if I use a backupset, I will have only 1 tape mount. However, if I use a regular restore, I can have the restore multiple threads and drives (given that maxnummp is high and mountretention is low). I do not have collocation on, but I could change that and force a full backup of the filesystems that need to be moved, so they would be collocated, but that wouldn't be much different than using a backupset, would it? Any advice? If you MOVE NODEDATA, perhaps to a (temporary) collocated stgpool, then you can get all the data to one place without having to back it all up again. If you've got enough disk, you might want to MOVE NODEDATA again, just before the restore, onto FILE or DISK devclasses. Depending on your tape architecture, it could imprrove your restore speed anywhere from a bit to a lot. In your shoes, I'd shove the data in a FILE devclass with volume size ~5GB just before the restore. Multiple threads, because multiple volumes, and disk's good seek behavior. - Allen S. Rout
Re: performance of restore v. retrieve v. backupset restore
== On Thu, 13 Oct 2005 12:03:43 -0500, Nancy Reeves [EMAIL PROTECTED] said: Does MOVE NODEDATA move all files of the node, or just the active ones? All. This makes the payload larger than a backupset, for instance, would generate. - Allen S. Rout
Slow backupset restore, a cry for help
Hello Gentelmen, I have browsed through forums and newsgroups but failed to find an answer. I have read that backupset generation can be a slow process, however, I am experiencing a slow restore from backupset. The backupset generation takes aproximately 8 (3 lto tapes) hours, however, now I see that the dsmsvc.exe I/O read bytes rate is only 1.5MB/sec . This is unbelievebly slow and I cannot find the reason for this. I have read that the previous versions of TSM client (4.*) had problems with backupset performance, but not the 5.1.* release. What can influence the restore performance so drastically ? Why is reading backupset so much slower than generating one ? Regular file restore/backup to tape functions properly and reaches 15MB/s. I do not expect that with the backupset as there is some information processing going on, but no 1.5MB/s while the cpu is almost idle. Environment : IBM LTO3600 single drive Windows 2003 server TSM Version 5, Release 1, Level 5.0 Both the client and server is located on the same machine and has the library connected via scsi. Please help !!! Desperate.
Re: Slow backupset restore, a cry for help
G. Things I would look for. Dont use 127.0.0.1/localhost for TCPserveraddress. This I have found to be slower for TSM backup/restore on some OS's as it is just a test interface. Make sure active virus scanning is turned off. Software based raid will slow things down too. You indicated that single file restorations are fast, so those things above could affect them as well. But if your single files were small the writing of them could be simply cached. When restoring a huge backupset it will quickly fill up hardware/software write caching and will reveal the true speed of your disk drives. I hope this helps. Giedrius Jankauskas [EMAIL PROTECTED] To: [EMAIL PROTECTED] CROLINK.LT cc: Sent by: ADSM: DistSubject: Slow backupset restore, a cry for help Stor Manager [EMAIL PROTECTED] 08/17/2004 06:27 AM Please respond to ADSM: Dist Stor Manager Hello Gentelmen, I have browsed through forums and newsgroups but failed to find an answer. I have read that backupset generation can be a slow process, however, I am experiencing a slow restore from backupset. The backupset generation takes aproximately 8 (3 lto tapes) hours, however, now I see that the dsmsvc.exe I/O read bytes rate is only 1.5MB/sec . This is unbelievebly slow and I cannot find the reason for this. I have read that the previous versions of TSM client (4.*) had problems with backupset performance, but not the 5.1.* release. What can influence the restore performance so drastically ? Why is reading backupset so much slower than generating one ? Regular file restore/backup to tape functions properly and reaches 15MB/s. I do not expect that with the backupset as there is some information processing going on, but no 1.5MB/s while the cpu is almost idle. Environment : IBM LTO3600 single drive Windows 2003 server TSM Version 5, Release 1, Level 5.0 Both the client and server is located on the same machine and has the library connected via scsi. Please help !!! Desperate.
Re: Slow backupset restore, a cry for help
Hi Matthew, All the things you've mentioned are set correctly. The problem lies within the server side, since it does send the data to the client very slowly (and from the task manager I can see that the tsm server process is reading data slowly as hell). There is probably no raid configuration that could be as slow as 1.5MB/sec and mine is about 20mb/sec without using cache. The problem is that while generating 3 tape (300GB) of backupset takes 6-8 hours, restore process is very VERY VVEERRYY slow. It hadn't finished restoring data from a single tape in 8 hours. There are lots of small files, but could that be the problem ? Hasn't anyone had problems with slow backupset restores tsm version 5.1.* and above ? How can I find out what the bottleneck is ? As I have mentioned before - speed of generating backupset, regular backups and regular restores is normal (10-15MB/s) for an LTO drive. Frustrating. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Glanville Sent: Tuesday, August 17, 2004 8:02 PM To: [EMAIL PROTECTED] Subject: Re: Slow backupset restore, a cry for help G. Things I would look for. Dont use 127.0.0.1/localhost for TCPserveraddress. This I have found to be slower for TSM backup/restore on some OS's as it is just a test interface. Make sure active virus scanning is turned off. Software based raid will slow things down too. You indicated that single file restorations are fast, so those things above could affect them as well. But if your single files were small the writing of them could be simply cached. When restoring a huge backupset it will quickly fill up hardware/software write caching and will reveal the true speed of your disk drives. I hope this helps. Giedrius Jankauskas [EMAIL PROTECTED] To: [EMAIL PROTECTED] CROLINK.LT cc: Sent by: ADSM: DistSubject: Slow backupset restore, a cry for help Stor Manager [EMAIL PROTECTED] 08/17/2004 06:27 AM Please respond to ADSM: Dist Stor Manager Hello Gentelmen, I have browsed through forums and newsgroups but failed to find an answer. I have read that backupset generation can be a slow process, however, I am experiencing a slow restore from backupset. The backupset generation takes aproximately 8 (3 lto tapes) hours, however, now I see that the dsmsvc.exe I/O read bytes rate is only 1.5MB/sec . This is unbelievebly slow and I cannot find the reason for this. I have read that the previous versions of TSM client (4.*) had problems with backupset performance, but not the 5.1.* release. What can influence the restore performance so drastically ? Why is reading backupset so much slower than generating one ? Regular file restore/backup to tape functions properly and reaches 15MB/s. I do not expect that with the backupset as there is some information processing going on, but no 1.5MB/s while the cpu is almost idle. Environment : IBM LTO3600 single drive Windows 2003 server TSM Version 5, Release 1, Level 5.0 Both the client and server is located on the same machine and has the library connected via scsi. Please help !!! Desperate.
Re: Slow backupset restore, a cry for help
...I am experiencing a slow restore from backupset... Please... When posting questions regarding restorals, please include the command line(s) or GUI operation you are using, as the particulars of the operation may make a huge difference, as IBM article swg21156683 illustrates in a Unix environment, using wildcards (and, by extrapolation, in any environment where a restoral is being performed via multiple individual commands). Seeing the manner in which the restoral was requested of TSM will help us to better ponder the circumstances. We can't promise to have the answer solely on that basis, but it will give us a better shot at it. thanks, Richard Sims
Re: Slow backupset restore, a cry for help
Also don't forget the Basics 1) Turn Off Anti-Virus on incomming files to the backup client you are restoring.. we ran in to this again Arggg 2) Check Backup CLient / Switch Connections and Backup server Network cards make sure they are forced to Full Duplex... AutoNegotiate kills -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: Tuesday, August 17, 2004 12:54 PM To: [EMAIL PROTECTED] Subject: Re: Slow backupset restore, a cry for help ...I am experiencing a slow restore from backupset... Please... When posting questions regarding restorals, please include the command line(s) or GUI operation you are using, as the particulars of the operation may make a huge difference, as IBM article swg21156683 illustrates in a Unix environment, using wildcards (and, by extrapolation, in any environment where a restoral is being performed via multiple individual commands). Seeing the manner in which the restoral was requested of TSM will help us to better ponder the circumstances. We can't promise to have the answer solely on that basis, but it will give us a better shot at it. thanks, Richard Sims
Re: Slow backupset restore, a cry for help
The problem lies within the server side, since it does send the data to the client very slowly (and from the task manager I can see that the tsm server process is reading data slowly as hell). Wont that speed you see will just adjust itself to what the client can write to the disk? Most of the performance problems I have seen can be tracked down to network problems or disk write speed problems caused by anti-virus software or software raid, be sure you take care of them first. Test the writing to that disk and TCP transfer rates by using somthing else, ftp for instance, just to be sure it is or is not TSM client/server issue. There are lots of small files, but could that be the problem ? Yes, from my experience the more individual files you have the longer everything takes, regardless of the amount of data. It isn't necesarily TSM, but the underlying file system. Logging will slow it down a bit more too. Even the layout of the files in the directory can have an effect, are there 10 million in one directory? I've seen that before it ain't pretty. So just how many files are there? How can I find out what the bottleneck is ? Keep looking, at more than just I/O speeds. memory use is another place things can slow down, is there alot of memory paging/swapping to disk going on? Lots of performance problems can be tracked down to this issue. As I have mentioned before - speed of generating backupset, regular backups and regular restores is normal (10-15MB/s) for an LTO drive. This is why I believe the problem has to do with somthing on the TSM client side and what it is doing. Thats the one thing that's being introduced in the equation when restoring a backup set. Frustrating. This probably means the answer is somthing simple. Hey, are you recovering the backup set using the GUI and a dialup link through a remote access tool? This can slow down restorations too... use the command line at all times unless on the console. Even then, command line is slightly quicker. Matt G.
Re: Slow backupset restore, a cry for help
Matthew, Look into TSM release 4.2.2.13. One of the fixes in this release was for this problem. We sat in on an IBM CritSit for this problem until this was written. Not sure if it will help but here is my experience from this issue. The amount of files, size and directory structure play a huge part in the restore. Many smaller files in deep directory layers will be very slow. There is no table of contents for backupsets. The complete tape or set has to be read for each restore or query, this is why a QUERY BACKUPSETCONTENTS takes almost as long as an actual restore. If you can find someone knowledgeable at IBM about release 4.2.2.13, it may be some help. You can contact me directly and I will give you the contact list level 2 guys at IBM that sat on our CritSit. I know how you feel, in some situations a backupset is the only answer for a specific need and the restore is a big part of that. Mark Bertrand -Original Message- From: Matthew Glanville [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004 1:42 PM To: [EMAIL PROTECTED] Subject: Re: Slow backupset restore, a cry for help The problem lies within the server side, since it does send the data to the client very slowly (and from the task manager I can see that the tsm server process is reading data slowly as hell). Wont that speed you see will just adjust itself to what the client can write to the disk? Most of the performance problems I have seen can be tracked down to network problems or disk write speed problems caused by anti-virus software or software raid, be sure you take care of them first. Test the writing to that disk and TCP transfer rates by using somthing else, ftp for instance, just to be sure it is or is not TSM client/server issue. There are lots of small files, but could that be the problem ? Yes, from my experience the more individual files you have the longer everything takes, regardless of the amount of data. It isn't necesarily TSM, but the underlying file system. Logging will slow it down a bit more too. Even the layout of the files in the directory can have an effect, are there 10 million in one directory? I've seen that before it ain't pretty. So just how many files are there? How can I find out what the bottleneck is ? Keep looking, at more than just I/O speeds. memory use is another place things can slow down, is there alot of memory paging/swapping to disk going on? Lots of performance problems can be tracked down to this issue. As I have mentioned before - speed of generating backupset, regular backups and regular restores is normal (10-15MB/s) for an LTO drive. This is why I believe the problem has to do with somthing on the TSM client side and what it is doing. Thats the one thing that's being introduced in the equation when restoring a backup set. Frustrating. This probably means the answer is somthing simple. Hey, are you recovering the backup set using the GUI and a dialup link through a remote access tool? This can slow down restorations too... use the command line at all times unless on the console. Even then, command line is slightly quicker. Matt G.
Re: Slow backupset restore, a cry for help
Hi Everyone, thanks for sharing your thoughts !!! Richard : you're right, I should have included the commands I used for restore. But since I tried using them all it was only natural that I forgot to mention that. I did try the GUI to restore all contents of the backupset. Seeing that the speed is awful I decided to use the command line interface and used the following command : restore backupset bset-name \\server\c$\* z:\ -subdir=yes . It restored several files from the (beginning of) first tape (3mb total :)) so I know the wildcards are correct. I though that scanning through the tape (command line case, where I restore just the needed files) would be faster than restoring all files with the GUI, but I was wrong. Seeking to the next file and checking if its name fits wildcards take just as much time as restoring it, and with the current speed it would take n days. Charles : there is no antivirus software on the server. Both the client and the server applications are installed on the same machine. I also tried restoring the backupset from a client on a different computer with the same (bad) results. This low speed is experienced only when restoring backupsets, simply restoring the backed up files works at normal speed, therefore it probably is not the network interface. Matthew : it's true that the slow client side would slow down the amount of data the server transfers, but it's probably not the case. I double checked and as I've mentioned the raid system easily deals with 20mb/s. The client hasn't received any new information in 10 hours, which, keeping in mind that the first tape is still mounted, means that the server didn't find any data matching wildcards in that time. 1 tape - more than 10 hours. The total number of objects writtent to the backupset in question is approx. 1.5 million (spreaded through directories), for today's modern times I think that's not much... There is also plenty of memory available and other resources available, also seeing that regular restores perform as expected I doubt that it's resouce problem :( Mark : while searching forums I found that the tsm 4.something version had that problem but since I am using 5.1. I though the problem has been dealt with so I was looking for other clues. I can understand that restoring/seeking through large number of small files can be slower, but the tape drive doesn't use even 1/10 of its reading speed while the cpu is almost idle. I though that after going through the filespace with the small files the restore process will speed up, but with 1.5mb/s and less I was not able to check that theory since the restore process having plenty of time hasn't walked through a single tape yet. ;( Now I cannot cancel the restore without any firm information :) since I've invested much time in it and restarting it will cause it having to seek through the data again. Please, if you have any ideas do not hasitate writing them to me :) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Tuesday, August 17, 2004 8:54 PM To: [EMAIL PROTECTED] Subject: Re: Slow backupset restore, a cry for help ...I am experiencing a slow restore from backupset... Please... When posting questions regarding restorals, please include the command line(s) or GUI operation you are using, as the particulars of the operation may make a huge difference, as IBM article swg21156683 illustrates in a Unix environment, using wildcards (and, by extrapolation, in any environment where a restoral is being performed via multiple individual commands). Seeing the manner in which the restoral was requested of TSM will help us to better ponder the circumstances. We can't promise to have the answer solely on that basis, but it will give us a better shot at it. thanks, Richard Sims
Backupset restore question
Hi I need your help to understand the process of restoring a backupset from a local client. 1. I first created a generate backup and take it offsite 2. Now assume my server is down and need to restore this client 3. From the gui client the option of local restore for backupset is there but need the tape name(did is the name of my device tape ??? and what about parameters like -su=yes and replace=all 4. Can I run from the client command line like: Restore backupset gen_admin.XX su=yes rep=all -loc=tape But what about the tape name I got from the gui ? I know that I miss something please help . Regards Robert Ouen E-mail: [EMAIL PROTECTED]
Backupset restore / TDP for Exchange
Hello, I'm new in this mailing list and my question may have already been answered ... sorry for that. Does anyone know if i can restore a backupset using the GUI of the TDP for Exchange ? And what about using the command line interface ? Is there a way to restore a backupset burned on a cd using the TDP ? Tks Gabriel.
Re: Backupset restore / TDP for Exchange
I'm new in this mailing list and my question may have already been answered ... sorry for that. Does anyone know if i can restore a backupset using the GUI of the TDP for Exchange ? And what about using the command line interface ? Is there a way to restore a backupset burned on a cd using the TDP ? Gabriel, The TDPs do not support backup sets. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] - Never cut what can be untied. - Commit yourself to constant improvement.
Re: Backupset restore / TDP for Exchange
So Del, are you saying that if I have a backupset of a filespace for my Exchange Information Store, and we choose to restore that filespace using the command line restore backupset, then will Exchange not be able to use that restored Info Store or are you just saying that the TDP does not support it? Please clarify or expand because I am very interested in this topic. Thanks, Mark B. -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 27, 2002 11:03 AM To: [EMAIL PROTECTED] Subject: Re: Backupset restore / TDP for Exchange I'm new in this mailing list and my question may have already been answered ... sorry for that. Does anyone know if i can restore a backupset using the GUI of the TDP for Exchange ? And what about using the command line interface ? Is there a way to restore a backupset burned on a cd using the TDP ? Gabriel, The TDPs do not support backup sets. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] - Never cut what can be untied. - Commit yourself to constant improvement.
Re: Backupset restore / TDP for Exchange
So Del, are you saying that if I have a backupset of a filespace for my Exchange Information Store, and we choose to restore that filespace using the command line restore backupset, then will Exchange not be able to use that restored Info Store or are you just saying that the TDP does not support it? Please clarify or expand because I am very interested in this topic. Mark, TDP for Exchange uses the TSM API to send and receive data from the TSM Server. The TSM API does not support backup sets. In order for TDPs to take advantage of backup sets, it will need the TSM API to support backup sets. The TSM BA client does not understand the data stream that the TDPs generate, so it cannot be used to restore the data either. If you did not use TDP for Exchange for backup, i.e., you shut down your Exchange server, did a file level backup of the Exchange files... ...then you can probably get it to work... but TDP for Exchange is not involved and many people cannot afford shutting down the Exchange server for backups. It is a known requirement that customers would like the TDPs to take advantage of backup sets. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] - Never cut what can be untied. - Commit yourself to constant improvement.
Re: Backupset restore / TDP for Exchange
Does that go for all TDP's or just Exchange, and another question, what is the preferred method of retaining data created by TDP's for long term, beyond standard retention settings? Mark -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 27, 2002 1:51 PM To: [EMAIL PROTECTED] Subject: Re: Backupset restore / TDP for Exchange So Del, are you saying that if I have a backupset of a filespace for my Exchange Information Store, and we choose to restore that filespace using the command line restore backupset, then will Exchange not be able to use that restored Info Store or are you just saying that the TDP does not support it? Please clarify or expand because I am very interested in this topic. Mark, TDP for Exchange uses the TSM API to send and receive data from the TSM Server. The TSM API does not support backup sets. In order for TDPs to take advantage of backup sets, it will need the TSM API to support backup sets. The TSM BA client does not understand the data stream that the TDPs generate, so it cannot be used to restore the data either. If you did not use TDP for Exchange for backup, i.e., you shut down your Exchange server, did a file level backup of the Exchange files... ...then you can probably get it to work... but TDP for Exchange is not involved and many people cannot afford shutting down the Exchange server for backups. It is a known requirement that customers would like the TDPs to take advantage of backup sets. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] - Never cut what can be untied. - Commit yourself to constant improvement.
If newer after backupset restore
I have been testing backupset restores for speed followed by standard restores using ifnewer to bring the restored client up to date. This seems to work ok, but I am confused by the amount of data showing as restored. by the ifnewer restore. Query session output during the restore and a final query node f=d after the restore completes are consistent with each other and on my latest test show 13.72 gb. as being sent over the network. But the client statistics show only 5.62 gb. as restored. What is the missing 8.1 gb. This is not a one off. I did the same test last week with similar results. Any thoughts gratefully received. John ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: Backupset Restore
I am having the same problem of restoring from a backupset with a tape drive attached to a client. I was told by support that GUI won't support using a local tape drive to restore from a backupset. Command line should work. But not for me. These are what I have tried: 1) restore backupset \\.\Tape1 backupset_name -loc=tape 2) restore backupset \\.\Tape1\ backupset_name -loc=tape 3) restore backupset \\.\Tape1 \\nodename\c$\file_name -loc=tape 4) restore backupset \\.\Tape1 \\nodename\c$\file_name -loc=tape 5) restore backupset \\.\Tape1\ \\nodename\c$\file_name -loc=tape 6) restore backupset \\.\Tape1\ \\nodename\c$\file_name -loc=tape 7) restore backupset \\.\Tape1 \\nodename\c$\* -loc=tape 8) restore backupset \\.\Tape1 \\nodename\c$\* -loc=tape 9) restore backupset \\.\Tape1\ \\nodename\c$\* -loc=tape 10) restore backupset \\.\Tape1\ \\nodename\c$\* -loc=tape I can actually see that the light on the tape drive is blinking, indicating some activity. But After a few minitues, I would get ANS1933E, Error accessing file or device ''. My client is 4.1 on a win2000 machine and server is 4.1.3 on AIX4.3.3. I am testing using a 8mm tape drive. Tivoli support told me that 8mm and DLT are supported tape device (not LTO). any idea? Jie -Original Message- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 9:55 AM To: [EMAIL PROTECTED] Subject: Re: Backupset Restore So either a actual file or the whole thing?! I am going to try the same command without the * '\\qbssnf11\c$\program~1\' and see what happens. Joe -Original Message- From: Mark Stapleton [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 10:46 AM To: [EMAIL PROTECTED] Subject: Re: Backupset Restore On Wed, 19 Dec 2001 10:10:09 -0500, it was written: I am trying to restore selective directories from a backupset. The tape is accessed, and prompt shows the correct node name, and also a counter of bytes transferred. However this counter stays at zero. My understanding of restoration from backupsets is that you cannot use wildcards to restore anything. You either have to restore specfic files (using a full directory tree), or you can restore the entire backupset's load, but nothing inbetween. -- Mark Stapleton ([EMAIL PROTECTED])
Re: Backupset Restore
I have no problem using the Gui for full backupset restores. Is windows2000 picking up the drive as tape1? Remote Storage in win2000 always starts with Tape0. As for the command prompts below you only need the backupset name if you are attached to the TSM Server and doing the restore. #4 is the one I tried (using single quotes) and the tape drive is accessed and accessed with no restore (but I only left it for 20 minutes - maybe a longer time is req'd). I would suggest tying the gui again, maybe check remote storage to see if something is wrong there. Possible driver problem?? Window's drivers are not always usable. Joe Cascanette The CUmis Group Limited -Original Message- From: Wu, Jie [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 20, 2001 12:35 PM To: [EMAIL PROTECTED] Subject: Re: Backupset Restore I am having the same problem of restoring from a backupset with a tape drive attached to a client. I was told by support that GUI won't support using a local tape drive to restore from a backupset. Command line should work. But not for me. These are what I have tried: 1) restore backupset \\.\Tape1 backupset_name -loc=tape 2) restore backupset \\.\Tape1\ backupset_name -loc=tape 3) restore backupset \\.\Tape1 \\nodename\c$\file_name -loc=tape 4) restore backupset \\.\Tape1 \\nodename\c$\file_name -loc=tape 5) restore backupset \\.\Tape1\ \\nodename\c$\file_name -loc=tape 6) restore backupset \\.\Tape1\ \\nodename\c$\file_name -loc=tape 7) restore backupset \\.\Tape1 \\nodename\c$\* -loc=tape 8) restore backupset \\.\Tape1 \\nodename\c$\* -loc=tape 9) restore backupset \\.\Tape1\ \\nodename\c$\* -loc=tape 10) restore backupset \\.\Tape1\ \\nodename\c$\* -loc=tape I can actually see that the light on the tape drive is blinking, indicating some activity. But After a few minitues, I would get ANS1933E, Error accessing file or device ''. My client is 4.1 on a win2000 machine and server is 4.1.3 on AIX4.3.3. I am testing using a 8mm tape drive. Tivoli support told me that 8mm and DLT are supported tape device (not LTO). any idea? Jie -Original Message- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 9:55 AM To: [EMAIL PROTECTED] Subject: Re: Backupset Restore So either a actual file or the whole thing?! I am going to try the same command without the * '\\qbssnf11\c$\program~1\' and see what happens. Joe -Original Message- From: Mark Stapleton [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 10:46 AM To: [EMAIL PROTECTED] Subject: Re: Backupset Restore On Wed, 19 Dec 2001 10:10:09 -0500, it was written: I am trying to restore selective directories from a backupset. The tape is accessed, and prompt shows the correct node name, and also a counter of bytes transferred. However this counter stays at zero. My understanding of restoration from backupsets is that you cannot use wildcards to restore anything. You either have to restore specfic files (using a full directory tree), or you can restore the entire backupset's load, but nothing inbetween. -- Mark Stapleton ([EMAIL PROTECTED])
Backupset Restore
I am trying to restore selective directories from a backupset. The tape is accessed, and prompt shows the correct node name, and also a counter of bytes transferred. However this counter stays at zero. I am able to use the GUI to restore the WHOLE backup set with no problems. Using 4.2.0 NT client on the restore server and the production server. Server is 4.2.1.6 NT Using restore command: dsmc restore backupset \\.\tape0 \\qbssnf11\c$\progra~1\* -loc=tape It starts to restore, but the indictor is sitting at zero. I went to see if the program files directory was being appended to and it was not. I also searched the ADSM.org and used some of their suggestions with no luck Anything wrong with the above command? Joe
Re: Backupset Restore
On Wed, 19 Dec 2001 10:10:09 -0500, it was written: I am trying to restore selective directories from a backupset. The tape is accessed, and prompt shows the correct node name, and also a counter of bytes transferred. However this counter stays at zero. My understanding of restoration from backupsets is that you cannot use wildcards to restore anything. You either have to restore specfic files (using a full directory tree), or you can restore the entire backupset's load, but nothing inbetween. -- Mark Stapleton ([EMAIL PROTECTED])
Re: Backupset Restore
I am new to this group and to Tivoli, but I successfully used this command yesterday. dsmc restore backupset backupsetname \\machinename\c$}\* I did not have to tell it which tape the set was on, just give it the correct name, this is not the node name but the backupset name which usually the nodename.somegeneratednumber then the individual file to restore. This worked on 4.1.2. I still have plenty of questions myself. Once I had my backup set, I was able to delete the filespace (but retain the node) which frees up space in my diskpool, correct? Once the file space was deleted I was still able to go back to my backupset for a restore. Is this the practiced method for retiring a client so we can keep a snap shot of a retired client for an agreed amount of time? Once the backupset is complete and I have identified the volume, what is the preferred checkout command? Once a backupset has expired, how do I reuse the volume it was on? Hope this helps and hope to hear back from you soon. Thanks, Mark -Original Message- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 9:10 AM To: [EMAIL PROTECTED] Subject: Backupset Restore I am trying to restore selective directories from a backupset. The tape is accessed, and prompt shows the correct node name, and also a counter of bytes transferred. However this counter stays at zero. I am able to use the GUI to restore the WHOLE backup set with no problems. Using 4.2.0 NT client on the restore server and the production server. Server is 4.2.1.6 NT Using restore command: dsmc restore backupset \\.\tape0 \\qbssnf11\c$\progra~1\* -loc=tape It starts to restore, but the indictor is sitting at zero. I went to see if the program files directory was being appended to and it was not. I also searched the ADSM.org and used some of their suggestions with no luck Anything wrong with the above command? Joe
Re: Backupset Restore
Nope, didnt work. It started the restore, but the bytes indictor stayed at zero and nothing was restored. I left it for over 10 minutes just to make sure. Joe -Original Message- From: Adams, Matt (US - Hermitage) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 10:21 AM To: Joe Cascanette Subject: RE: Backupset Restore Try the filespace\filedir in quotes.. dsmc restore backupset \\.\tape0 \\qbssnf11\c$\progra~1\* -loc=tape I learned that quotes are the key in most cases -Original Message- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 9:10 AM To: [EMAIL PROTECTED] Subject: Backupset Restore I am trying to restore selective directories from a backupset. The tape is accessed, and prompt shows the correct node name, and also a counter of bytes transferred. However this counter stays at zero. I am able to use the GUI to restore the WHOLE backup set with no problems. Using 4.2.0 NT client on the restore server and the production server. Server is 4.2.1.6 NT Using restore command: dsmc restore backupset \\.\tape0 \\qbssnf11\c$\progra~1\* -loc=tape It starts to restore, but the indictor is sitting at zero. I went to see if the program files directory was being appended to and it was not. I also searched the ADSM.org and used some of their suggestions with no luck Anything wrong with the above command? Joe - This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
Re: Backupset Restore
Joe, it took me 1 hour and 28 minutes to restore a 264k text file when I did it. Have you ever seen how long it takes to list the contents of a backup set. Remember, the file you are trying to restore from a backupset was backed up as a complete filespace, but it is possible to extract one file if you are using command line. I have not seen this possible in the GUI interface. On my test I didn't use quotes or the -loc parameter. Also note, I specified the filename (did not use an *) I was trying to restore. Hope this helps, Mark -Original Message- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 9:39 AM To: [EMAIL PROTECTED] Subject: Re: Backupset Restore Nope, didnt work. It started the restore, but the bytes indictor stayed at zero and nothing was restored. I left it for over 10 minutes just to make sure. Joe -Original Message- From: Adams, Matt (US - Hermitage) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 10:21 AM To: Joe Cascanette Subject: RE: Backupset Restore Try the filespace\filedir in quotes.. dsmc restore backupset \\.\tape0 \\qbssnf11\c$\progra~1\* -loc=tape I learned that quotes are the key in most cases -Original Message- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 9:10 AM To: [EMAIL PROTECTED] Subject: Backupset Restore I am trying to restore selective directories from a backupset. The tape is accessed, and prompt shows the correct node name, and also a counter of bytes transferred. However this counter stays at zero. I am able to use the GUI to restore the WHOLE backup set with no problems. Using 4.2.0 NT client on the restore server and the production server. Server is 4.2.1.6 NT Using restore command: dsmc restore backupset \\.\tape0 \\qbssnf11\c$\progra~1\* -loc=tape It starts to restore, but the indictor is sitting at zero. I went to see if the program files directory was being appended to and it was not. I also searched the ADSM.org and used some of their suggestions with no luck Anything wrong with the above command? Joe - This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
Re: Backupset Restore
And look at the syntax to see if you can use a -subdir=yes to go below. This is one of those things you get to play with until it works. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Cascanette Sent: Wednesday, December 19, 2001 8:55 AM To: [EMAIL PROTECTED] Subject: Re: Backupset Restore So either a actual file or the whole thing?! I am going to try the same command without the * '\\qbssnf11\c$\program~1\' and see what happens. Joe -Original Message- From: Mark Stapleton [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 10:46 AM To: [EMAIL PROTECTED] Subject: Re: Backupset Restore On Wed, 19 Dec 2001 10:10:09 -0500, it was written: I am trying to restore selective directories from a backupset. The tape is accessed, and prompt shows the correct node name, and also a counter of bytes transferred. However this counter stays at zero. My understanding of restoration from backupsets is that you cannot use wildcards to restore anything. You either have to restore specfic files (using a full directory tree), or you can restore the entire backupset's load, but nothing inbetween. -- Mark Stapleton ([EMAIL PROTECTED])
Re: Backupset Restore
Yep that will work when restoring from the server. I am restoring from a tape unit that is not connected to the server. Joe -Original Message- From: Mark Bertrand [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 10:43 AM To: [EMAIL PROTECTED] Subject: Re: Backupset Restore I am new to this group and to Tivoli, but I successfully used this command yesterday. dsmc restore backupset backupsetname \\machinename\c$}\* I did not have to tell it which tape the set was on, just give it the correct name, this is not the node name but the backupset name which usually the nodename.somegeneratednumber then the individual file to restore. This worked on 4.1.2. I still have plenty of questions myself. Once I had my backup set, I was able to delete the filespace (but retain the node) which frees up space in my diskpool, correct? Once the file space was deleted I was still able to go back to my backupset for a restore. Is this the practiced method for retiring a client so we can keep a snap shot of a retired client for an agreed amount of time? Once the backupset is complete and I have identified the volume, what is the preferred checkout command? Once a backupset has expired, how do I reuse the volume it was on? Hope this helps and hope to hear back from you soon. Thanks, Mark -Original Message- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 9:10 AM To: [EMAIL PROTECTED] Subject: Backupset Restore I am trying to restore selective directories from a backupset. The tape is accessed, and prompt shows the correct node name, and also a counter of bytes transferred. However this counter stays at zero. I am able to use the GUI to restore the WHOLE backup set with no problems. Using 4.2.0 NT client on the restore server and the production server. Server is 4.2.1.6 NT Using restore command: dsmc restore backupset \\.\tape0 \\qbssnf11\c$\progra~1\* -loc=tape It starts to restore, but the indictor is sitting at zero. I went to see if the program files directory was being appended to and it was not. I also searched the ADSM.org and used some of their suggestions with no luck Anything wrong with the above command? Joe
Re: Backupset Restore
So either a actual file or the whole thing?! I am going to try the same command without the * '\\qbssnf11\c$\program~1\' and see what happens. Joe -Original Message- From: Mark Stapleton [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 10:46 AM To: [EMAIL PROTECTED] Subject: Re: Backupset Restore On Wed, 19 Dec 2001 10:10:09 -0500, it was written: I am trying to restore selective directories from a backupset. The tape is accessed, and prompt shows the correct node name, and also a counter of bytes transferred. However this counter stays at zero. My understanding of restoration from backupsets is that you cannot use wildcards to restore anything. You either have to restore specfic files (using a full directory tree), or you can restore the entire backupset's load, but nothing inbetween. -- Mark Stapleton ([EMAIL PROTECTED])
Backupset restore problems
I am having problems restoring a large backupset from an IBM 3583 LTO to a Network Appliance 720. 4.1.2 on the server -- W2K NetFinity 5100 4.1.1 on the client -- Linux We have a switched TCP/IP network The backup set is large -- 80K directories and almost 800K files totaling 350GB. During the restore we are getting about 3.0 GB/hour throughput once we get past the directory creation -- we're going to be here for days to get the full 350GB We've gotten MUCH faster restore times restoring other data -- not backup sets and not 350 GB worth. We've also gotten an ANR8302E error about 150GB into the restore and at IBS request updated our drive firmware to the latest revision. Is there anything inherently goofy / different about restoring from backupset? Is the volume and size of the directories and files causing me problems? Any suggestions?
Re: Backupset restore
Kudos to you, Richard! That is exactly what the problem was! By indicating binary prior to executing the get statement of the ftp, the files came down to the LAN in a format NT could handle. Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org |+--- || Richard Sims | || [EMAIL PROTECTED] | || | || 03/22/2001 | || 03:12 PM | || Please | || respond to | || "ADSM: Dist | || Stor Manager"| || | |+--- | || | To: [EMAIL PROTECTED] | | cc: (bcc: Cheri Howard/AAL) | | Subject: Re: Backupset restore | | I created a backupset writing to a file device class, which generated 4 files on my MVS system. I can restore the backupset from the Server via the GUI with no problem. I then FTP'd the backupset files to my LAN and burned them onto CD. Two things... 1. Your MVS system speaks EBCDIC and your Windows system speaks ASCII; 2. Was the FTP done in Binary mode? I don't have an authoritative answer to your query, but you may be running afoul of the two different cultures. I suspect that the backup set from the mainframe has to be maintained in bit-fidelity for the backup set to be used at the PC, though I don't have the experience to say exactly what must prevail. Richard Sims, BU
Backupset restore
Hi all, I'm attempting to do a local restore of a backupset and am having a problem. Here's the situation: TSM Server: TSM for MVS 3.7.3 TSM client: TSM for Windows 3.7 I created a backupset writing to a file device class, which generated 4 files on my MVS system. I can restore the backupset from the Server via the GUI with no problem. I then FTP'd the backupset files to my LAN and burned them onto CD. When I pop the CD in specify the CD drive as the backupset location, I'm getting the following message: ANS1933E Error accessing file or device Anyone have an idea of what is wrong here? Any help will be greatly appreciated! Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org
Re: Backupset restore
Hi Cheri, Have you tried to copy the file from the burned CD to local disk and then restore from there? How do you create the CD - with session open/close session/...? It may make things complicated. I met this message before when I tried to restore a backupset from tape drive while server and client were on the same machine, and it was solved by creating a FILE device class' backupset. Following are some other cases which gets the same error message. FYI. Regards, Phillip -- IC27617-CUSTOMER UNABLE TO RESTORE BACKUPSET TO LOCAL CLIENT WITH TSM CLIENT 3.7.2 ON NT IF THE BACKUPSET SPANS A VOLUME. IC27809-UNABLE TO RESTORE INDIVIDUAL FILES IN BACKUPSET VIA B/A GUI. IC29680- WHEN A NODE IS RENAMED ON THE SERVER, ANY BACKUPSETS GENERATED FOR IT CAN'T BE RESTORED EVEN THOUGH IT REPORTS SUCCESSFUL. IC29472-DOC NEEDS TO BE UPDATED FOR RESTORING BACKUPSETS USING THE NATIVE NT DEVICE DRIVER TO REFLECT DEVICE NAME OF \\.\TAPEX . IC25937-QUERY BACKUPSET AND RESTORE BACKUPSET EXAMPLES SHOW THE -LOC OPTION WITH INCORRECT SYNTAX. ERROR DESCRIPTION: The books Tivoli Storage manager Using the Backup Archive-Client for windows and unix have incorrect syntax in the examples for for windows and unix have incorrect syntax in the examples for the backupset commands. In the Unix book we have examples for restore backupset and query backupset that use the paramater " -loc=/dev/rmt0 " -loc can only take 'server', 'file', or 'tape'. In the Windows book query backupset has the location parameter taking g:\weeklydata.set as an argument. It can only take 'server' and 'file'. LOCAL FIX: Use the syntax from typing help from the tsm command line. Examples of correct syntax: query backupset "mybackupsetname" -loc=server query backupset /dev/rmt0 -loc=tape IC27164 - RESTORE BACKUPSET WILL NOT WORK FROM THE WIN32 GUI IF THE TSM SERVER IS NOT REACHABLE. TCP/IP FAILURE. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Cheri Howard Sent: Thursday, March 22, 2001 9:07 AM To: [EMAIL PROTECTED] Subject: Backupset restore Hi all, I'm attempting to do a local restore of a backupset and am having a problem. Here's the situation: TSM Server: TSM for MVS 3.7.3 TSM client: TSM for Windows 3.7 I created a backupset writing to a file device class, which generated 4 files on my MVS system. I can restore the backupset from the Server via the GUI with no problem. I then FTP'd the backupset files to my LAN and burned them onto CD. When I pop the CD in specify the CD drive as the backupset location, I'm getting the following message: ANS1933E Error accessing file or device Anyone have an idea of what is wrong here? Any help will be greatly appreciated! Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org
Re: Backupset restore
Thanks for the suggestion, Phillip, but that didn't work either. I copied the backupset from the CD to local disk and specified the local disk as the location for the backupset, and still receive the same error. Has anyone else had this problem? Any ideas on how to resolve? Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org |+--- || Phillip Guan | || pguan@SANSIA| || .NET| || | || 03/22/2001 | || 11:54 AM | || Please | || respond to | || pguan| || | |+--- | || | To: [EMAIL PROTECTED] | | cc: (bcc: Cheri Howard/AAL) | | Subject: Re: Backupset restore | | Hi Cheri, Have you tried to copy the file from the burned CD to local disk and then restore from there? How do you create the CD - with session open/close session/...? It may make things complicated. I met this message before when I tried to restore a backupset from tape drive while server and client were on the same machine, and it was solved by creating a FILE device class' backupset. Following are some other cases which gets the same error message. FYI. Regards, Phillip -- IC27617-CUSTOMER UNABLE TO RESTORE BACKUPSET TO LOCAL CLIENT WITH TSM CLIENT 3.7.2 ON NT IF THE BACKUPSET SPANS A VOLUME. IC27809-UNABLE TO RESTORE INDIVIDUAL FILES IN BACKUPSET VIA B/A GUI. IC29680- WHEN A NODE IS RENAMED ON THE SERVER, ANY BACKUPSETS GENERATED FOR IT CAN'T BE RESTORED EVEN THOUGH IT REPORTS SUCCESSFUL. IC29472-DOC NEEDS TO BE UPDATED FOR RESTORING BACKUPSETS USING THE NATIVE NT DEVICE DRIVER TO REFLECT DEVICE NAME OF \\.\TAPEX . IC25937-QUERY BACKUPSET AND RESTORE BACKUPSET EXAMPLES SHOW THE -LOC OPTION WITH INCORRECT SYNTAX. ERROR DESCRIPTION: The books Tivoli Storage manager Using the Backup Archive-Client for windows and unix have incorrect syntax in the examples for for windows and unix have incorrect syntax in the examples for the backupset commands. In the Unix book we have examples for restore backupset and query backupset that use the paramater " -loc=/dev/rmt0 " -loc can only take 'server', 'file', or 'tape'. In the Windows book query backupset has the location parameter taking g:\weeklydata.set as an argument. It can only take 'server' and 'file'. LOCAL FIX: Use the syntax from typing help from the tsm command line. Examples of correct syntax: query backupset "mybackupsetname" -loc=server query backupset /dev/rmt0 -loc=tape IC27164 - RESTORE BACKUPSET WILL NOT WORK FROM THE WIN32 GUI IF THE TSM SERVER IS NOT REACHABLE. TCP/IP FAILURE. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Cheri Howard Sent: Thursday, March 22, 2001 9:07 AM To: [EMAIL PROTECTED] Subject: Backupset restore Hi all, I'm attempting to do a local restore of a backupset and am having a problem. Here's the situation: TSM Server: TSM for MVS 3.7.3 TSM client: TSM for Windows 3.7 I created a backupset writing to a file device class, which generated 4 files on my MVS system. I can restore the backupset from the Server via the GUI with no problem. I then FTP'd the backupset files to my LAN and burned them onto CD. When I pop the CD in specify the CD drive as the backupset location, I'm getting the following message: ANS1933E Error accessing file or device Anyone have an idea of what is wrong here? Any help will be greatly appreciated! Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org
Re: Backupset restore
ANS1933E Error accessing file or device 'name'. Explanation: An error has occurred while accessing the file or device. System Action: Backup set operation is not completed. User Response: Verify that the file or device exists and is accessible. When you open the backup client to restore from the backupset, is there a BACKUPSET Icon with a + to expand? When I first tried this, for whatever reason, it took a little while to "see" the backupset. If you expand the BACKUPSET +, you should see SERVER and LOCAL. Choose Local hope this helps? Cheri Howard Cheri_HowardTo: [EMAIL PROTECTED] @AAL.ORGcc: Sent by: Subject: Re: Backupset restore "ADSM: Dist Stor Manager" [EMAIL PROTECTED] RIST.EDU 03/22/2001 03:19 PM Please respond to "ADSM: Dist Stor Manager" Thanks for the suggestion, Phillip, but that didn't work either. I copied the backupset from the CD to local disk and specified the local disk as the location for the backupset, and still receive the same error. Has anyone else had this problem? Any ideas on how to resolve? Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org |+--- || Phillip Guan | || pguan@SANSIA| || .NET| || | || 03/22/2001 | || 11:54 AM | || Please | || respond to | || pguan| || | |+--- | || | To: [EMAIL PROTECTED] | | cc: (bcc: Cheri Howard/AAL) | | Subject: Re: Backupset restore | | Hi Cheri, Have you tried to copy the file from the burned CD to local disk and then restore from there? How do you create the CD - with session open/close session/...? It may make things complicated. I met this message before when I tried to restore a backupset from tape drive while server and client were on the same machine, and it was solved by creating a FILE device class' backupset. Following are some other cases which gets the same error message. FYI. Regards, Phillip -- IC27617-CUSTOMER UNABLE TO RESTORE BACKUPSET TO LOCAL CLIENT WITH TSM CLIENT 3.7.2 ON NT IF THE BACKUPSET SPANS A VOLUME. IC27809-UNABLE TO RESTORE INDIVIDUAL FILES IN BACKUPSET VIA B/A GUI. IC29680- WHEN A NODE IS RENAMED ON THE SERVER, ANY BACKUPSETS GENERATED FOR IT CAN'T BE RESTORED EVEN THOUGH IT REPORTS SUCCESSFUL. IC29472-DOC NEEDS TO BE UPDATED FOR RESTORING BACKUPSETS USING THE NATIVE NT DEVICE DRIVER TO REFLECT DEVICE NAME OF \\.\TAPEX . IC25937-QUERY BACKUPSET AND RESTORE BACKUPSET EXAMPLES SHOW THE -LOC OPTION WITH INCORRECT SYNTAX. ERROR DESCRIPTION: The books Tivoli Storage manager Using the Backup Archive-Client for windows and unix have incorrect syntax in the examples for for windows and unix have incorrect syntax in the examples for the backupset commands. In the Unix book we have examples for restore backupset and query backupset that use the paramater " -loc=/dev/rmt0 " -loc can only take 'server', 'file', or 'tape'. In the Windows book query backupset has the location parameter taking g:\weeklydata.set as an argument. It can only take 'server' and 'file'. LOCAL FIX: Use the syntax from typing help from the tsm command line. Examples of correct syntax: query backupset "mybackupsetname" -loc=server query backupset /dev/rmt0 -loc=tape IC27164 - RESTORE BACKUPSET WILL NOT WORK FROM THE WIN32 GUI IF THE TSM SERVER IS NOT REACHABLE. TCP/IP FAILURE. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Cheri Howard Sent: Thursday, March 22, 2001 9:07 AM To: [EMAIL PROTECTED] Subject: Backupset restore Hi all, I'm attempting to do a local restore of a backupset and am having a problem. Here's the situation: TSM Server: TSM for MVS 3.7.3 TSM client: TSM for Windows 3.7 I created a backupset writing to a file device class, which generated 4 files on my MVS system. I can restore the backupset from the Server via the GUI with no problem. I then FTP'd the backupset files to my LAN and burned them on
Re: Backupset Restore of TDP Domino Data
Many thanks to James Richard for your input. You got me thinking of the problem from another angle and here's what I came up with I created a new policy domain for each Domino server, and defined a new nodename for each as well. These new policy domains are set to write straight to the DLT drive. So now, I'll have to run two full backups (one for the 'every-day' data, and the other for 'off-site' data) each weekend, but I'll then be able to restore from these DLT tapes without mucking with the TSM database at all. My regular backups that I've been doing all along don't change at all (still about 5 versions of retention), and handle most restore requests. The 'off-site' DLT's are needed only in the event of a disaster, or when data that no longer exists in the 'every-day' policy domain is needed. To my surprise, the backups straight to DLT were insignificantly slower than our backups to disk -- even during the middle of the day. This all seems too good to be true. Are there any pitfalls that I might have missed? :) Eric L.
Re: Backupset Restore of TDP Domino Data
A 20:09 22/01/2001 -0500, vous avez crit : Many thanks to James Richard for your input. You got me thinking of the problem from another angle and here's what I came up with ... To my surprise, the backups straight to DLT were insignificantly slower than our backups to disk -- even during the middle of the day. Hmmm interesting can you tell me a bit more about your hardware ? i'm facing a performance problem with a F50 with 2 ibm's 3590 (14 MB/sec, 10 GB/tape) and an ATM 155 Mbps network connexion (thus 14 MB/sec too). some guys want me to have backups processed in two steps (client - disk pool via network, then, when finished, internal disk to tape migration on server), what needs considerable amount of disk space on the server, while i believe concurrent backup and migration is as fast (that is, using the disk pool as a buffer), and even that a backup directly to tape would not take that longer... so i'm interested in some details tia, - * - * - * - * - * - * - Mes idees n'engagent que moi (vieux proverbe du Net) Thierry ITTY eMail : [EMAIL PROTECTED] FRANCE
Re: Backupset Restore of TDP Domino Data
James,
Good question. Our primary goal is to find a cost-effective way to
send our data off-site (Domino vanilla NT files). Additionally, we
need to extend our data retention. We can retain only 5 versions of
our Domino db's in our library (which is pretty much full and not
upgradeable), but need to keep 3 months.
We've been creating the backupsets on a DLT stacker. As far as TSM is
concerned, its a manaul library, but there's some intelligence in it
that will mount the next tape when the current tape is filled.
What I'm thinking now is that the best option is to go with the copy
storage pool on the DLT stacker. We'll still have only 5 versions
worth of retention, but at least we'll get the data off-site.
Unless..is there a way for the copy storage pool to live by
retention policies which are different from its backup storage pool?
Thanks,
Eric L.
James
Thompson To: [EMAIL PROTECTED]
mezron@HOTMAcc:
IL.COM Subject: Re: Backupset Restore of TDP
Domino Data
Sent by:
"ADSM: Dist
Stor Manager"
[EMAIL PROTECTED]
RIST.EDU
01/19/01
10:08 PM
Please
respond to
"ADSM: Dist
Stor Manager"
Eric,
Since you are using the TDP for Domino connect agent to perform the
backups,
you can not use backup sets for restore. You have explained the steps
you
are
trying to do, but haven't really stated what business need you are
trying to
fulfill.
Why do you want an extra copy of the domino databases? Is it to
provide
redundancy in case of a restore? If so, a copy storage pool would be
a
better
alternative?
Once again, currently only the backup archive client is aware and can
take
advantage of backupsets. To the server, active versions of files
look all
the same
(it's just data), so you can generate backupsets of api data. But it
is a
waste of a
tape since you will not be able to restore from it in any situation.
James Thompson
- Original Message -
From: "Eric Lindbeck" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 19, 2001 2:38 PM
Subject: Re: Backupset Restore of TDP Domino Data
Hi James,
Thanks for the response. Here's what we're trying to do:
1) Using TDP for Domino, backup our domino databases from a Solaris
client to TSM using the "domdsmc selective * ..." command.
2) Then, on the server side, issue "generate backupset ..." to dump
the active versions of the databases to a manual tape stacker.
3) At this point, I can see the backupset from the server, but not
from the client. The backupset still resides in the library on the
TSM server.
Just got off the phone with TSM support. According to them, when you
create a backupset of data that was backed up via an API (Domino, in
our case), all the data is smushed together into one big object. That
object is in a format that the B/A client cannot understand, making
the restore impossible. So, if it even makes a difference, I must
have missed something along the way to not be able to see the
backupsets from the client in the first place. My only recourse is to
create a copy storage pool, it seems. Any other options?
I should mention that I've had absolutely no problems getting
backupsets to work on our NT filesystem data.
Thanks,
Eric L
James
Thompson To: [EMAIL PROTECTED]
mezron@HOTMAcc:
IL.COM Subject: Re: Backupset
Restore
of TDP Domino Data
Sent by:
"ADSM: Dist
Stor Manager"
[EMAIL PROTECTED]
RIST.EDU
01/19/01
02:47 PM
Please
respond to
"ADSM: Dist
Stor Manager"
Only files that are backed up using a 'dsmc incremental ' or 'dsmc
selective' and only
the active versions of those files are included in a backupset.
If you backed the domino databases up as file using the backup/archive
client,
you should be able to use a backupset generated from that filespace to
restore the
files. Are you using a windows client or unix? Can you query the
backupset from
the server and from the client machine? Are you trying to restore the
backupset
while it is still assigned to the TSM server? Or are you moving the
backupset volumes
to the local machine and trying it from there?
James Thompson
From: Eric Lindbeck
Reply-To: "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
Subject: Backupset Restore of TDP Domino Data
Date: Fri, 19 Jan 2001 11:08:59 -05
Backupset Restore of TDP Domino Data
Greetings *SM'ers, I'm looking for clarification of APAR IC28451. It states that: "There is no support in the [TDP for Domino] API for the backup set format. Therefore, backup set data that was backed up via the API cannot be restored or used." Does this mean that it's not possible to restore the Domino database files at all, even if you just want to treat them like generic file system files and do the restore via a B/A client? I've been trying unsuccessfully to do the restore of Domino BackupSet data-- the B/A client doesn't seem to know that a BackupSet even exists. But I'm hoping that it's just a problem with my client software version (3.7.2). Does anyone else have experience with this? Thanks in advance, Eric S. Lindbeck Data Storage Administrator Network Infrastructure Services SCT
Re: Backupset Restore of TDP Domino Data
Only files that are backed up using a 'dsmc incremental ' or 'dsmc selective' and only the active versions of those files are included in a backupset. If you backed the domino databases up as file using the backup/archive client, you should be able to use a backupset generated from that filespace to restore the files. Are you using a windows client or unix? Can you query the backupset from the server and from the client machine? Are you trying to restore the backupset while it is still assigned to the TSM server? Or are you moving the backupset volumes to the local machine and trying it from there? James Thompson From: Eric Lindbeck <[EMAIL PROTECTED]> Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Backupset Restore of TDP Domino Data Date: Fri, 19 Jan 2001 11:08:59 -0500 Greetings *SM'ers, I'm looking for clarification of APAR IC28451. It states that: "There is no support in the [TDP for Domino] API for the backup set format. Therefore, backup set data that was backed up via the API cannot be restored or used." Does this mean that it's not possible to restore the Domino database files at all, even if you just want to treat them like generic file system files and do the restore via a B/A client? I've been trying unsuccessfully to do the restore of Domino BackupSet data-- the B/A client doesn't seem to know that a BackupSet even exists. But I'm hoping that it's just a problem with my client software version (3.7.2). Does anyone else have experience with this? Thanks in advance, Eric S. Lindbeck Data Storage Administrator Network Infrastructure Services SCT Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: Backupset Restore of TDP Domino Data
Hi James, Thanks for the response. Here's what we're trying to do: 1) Using TDP for Domino, backup our domino databases from a Solaris client to TSM using the "domdsmc selective * ..." command. 2) Then, on the server side, issue "generate backupset ..." to dump the active versions of the databases to a manual tape stacker. 3) At this point, I can see the backupset from the server, but not from the client. The backupset still resides in the library on the TSM server. Just got off the phone with TSM support. According to them, when you create a backupset of data that was backed up via an API (Domino, in our case), all the data is smushed together into one big object. That object is in a format that the B/A client cannot understand, making the restore impossible. So, if it even makes a difference, I must have missed something along the way to not be able to see the backupsets from the client in the first place. My only recourse is to create a copy storage pool, it seems. Any other options? I should mention that I've had absolutely no problems getting backupsets to work on our NT filesystem data. Thanks, Eric L James Thompson To: [EMAIL PROTECTED] mezron@HOTMAcc: IL.COM Subject: Re: Backupset Restore of TDP Domino Data Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] RIST.EDU 01/19/01 02:47 PM Please respond to "ADSM: Dist Stor Manager" Only files that are backed up using a 'dsmc incremental ' or 'dsmc selective' and only the active versions of those files are included in a backupset. If you backed the domino databases up as file using the backup/archive client, you should be able to use a backupset generated from that filespace to restore the files. Are you using a windows client or unix? Can you query the backupset from the server and from the client machine? Are you trying to restore the backupset while it is still assigned to the TSM server? Or are you moving the backupset volumes to the local machine and trying it from there? James Thompson From: Eric Lindbeck Reply-To: "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] Subject: Backupset Restore of TDP Domino Data Date: Fri, 19 Jan 2001 11:08:59 -0500 Greetings *SM'ers, I'm looking for clarification of APAR IC28451. It states that: "There is no support in the [TDP for Domino] API for the backup set format. Therefore, backup set data that was backed up via the API cannot be restored or used." Does this mean that it's not possible to restore the Domino database files at all, even if you just want to treat them like generic file system files and do the restore via a B/A client? I've been trying unsuccessfully to do the restore of Domino BackupSet data-- the B/A client doesn't seem to know that a BackupSet even exists. But I'm hoping that it's just a problem with my client software version (3.7.2). Does anyone else have experience with this? Thanks in advance, Eric S. Lindbeck Data Storage Administrator Network Infrastructure Services SCT Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: Backupset Restore of TDP Domino Data
Eric, Since you are using the TDP for Domino connect agent to perform the backups, you can not use backup sets for restore. You have explained the steps you are trying to do, but haven't really stated what business need you are trying to fulfill. Why do you want an extra copy of the domino databases? Is it to provide redundancy in case of a restore? If so, a copy storage pool would be a better alternative? Once again, currently only the backup archive client is aware and can take advantage of backupsets. To the server, active versions of files look all the same (it's just data), so you can generate backupsets of api data. But it is a waste of a tape since you will not be able to restore from it in any situation. James Thompson - Original Message - From: "Eric Lindbeck" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 19, 2001 2:38 PM Subject: Re: Backupset Restore of TDP Domino Data Hi James, Thanks for the response. Here's what we're trying to do: 1) Using TDP for Domino, backup our domino databases from a Solaris client to TSM using the "domdsmc selective * ..." command. 2) Then, on the server side, issue "generate backupset ..." to dump the active versions of the databases to a manual tape stacker. 3) At this point, I can see the backupset from the server, but not from the client. The backupset still resides in the library on the TSM server. Just got off the phone with TSM support. According to them, when you create a backupset of data that was backed up via an API (Domino, in our case), all the data is smushed together into one big object. That object is in a format that the B/A client cannot understand, making the restore impossible. So, if it even makes a difference, I must have missed something along the way to not be able to see the backupsets from the client in the first place. My only recourse is to create a copy storage pool, it seems. Any other options? I should mention that I've had absolutely no problems getting backupsets to work on our NT filesystem data. Thanks, Eric L James Thompson To: [EMAIL PROTECTED] mezron@HOTMAcc: IL.COM Subject: Re: Backupset Restore of TDP Domino Data Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] RIST.EDU 01/19/01 02:47 PM Please respond to "ADSM: Dist Stor Manager" Only files that are backed up using a 'dsmc incremental ' or 'dsmc selective' and only the active versions of those files are included in a backupset. If you backed the domino databases up as file using the backup/archive client, you should be able to use a backupset generated from that filespace to restore the files. Are you using a windows client or unix? Can you query the backupset from the server and from the client machine? Are you trying to restore the backupset while it is still assigned to the TSM server? Or are you moving the backupset volumes to the local machine and trying it from there? James Thompson From: Eric Lindbeck Reply-To: "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] Subject: Backupset Restore of TDP Domino Data Date: Fri, 19 Jan 2001 11:08:59 -0500 Greetings *SM'ers, I'm looking for clarification of APAR IC28451. It states that: "There is no support in the [TDP for Domino] API for the backup set format. Therefore, backup set data that was backed up via the API cannot be restored or used." Does this mean that it's not possible to restore the Domino database files at all, even if you just want to treat them like generic file system files and do the restore via a B/A client? I've been trying unsuccessfully to do the restore of Domino BackupSet data-- the B/A client doesn't seem to know that a BackupSet even exists. But I'm hoping that it's just a problem with my client software version (3.7.2). Does anyone else have experience with this? Thanks in advance, Eric S. Lindbeck Data Storage Administrator Network Infrastructure Services SCT Get your FREE download of MSN Explorer at http://explorer.msn.com
backupset restore problem
Hi all, We want to test a Lan-free restore and had a problem to restore a backupset, here is the situation: HW: RS6000 43P SW: AIX 4.3.3 TSM server: TSM for AIX 3.7.3.6 TSM client: TSM for AIX 3.7.2.15 Tape drive: HP DLT40e, IBM DLT, 4MM tape ( all manual drives) We created a backupset and we can restore the backupset THROUGH server by: #dsmc restore backupset nodename backupsetname -loc=server but when we run (we tried HP DLT, IBM DLT and 4mm): #dsmc restore backupset /dev/rmt0 -loc=tape we got the following message: ANS1933E Error accessing file or device The TSM server and client are on the same machine. But even I shutdown the TSM server and delete related TSM tape drives, I still got that error message. We have been frustrated this for many days, any help will be great appreciated! Best regards, Phillip Guan Sansia System Solutions Bowers Avenue, Suite 239 Santa Clara, CA 95054 Voice: 408.844.8808 Fax: 408.844.9801
HP DLT tape drive support for backupset restore
Hi all, I created a backupset successfully on HP DLT40e tape drive and can query the content on the tape, but I cannot restore the backupset from it. Our AIX level is 4.3.3.0, TSM server is 3.7.2 and the client is on the same box as server. I wonder if HP DLT40 is supported on TSM 3.7. Thanks a lot! Here are the command and error message: -- dsmc restore backupset /dev/rmt0 -loc=tape Tivoli Storage Manager Command Line Backup Client Interface - Version 3, Release 7, Level 2.0 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Restore function invoked. Node Name: SFAIX2 Restore Processing Interrupted!! ANS1933E Error accessing file or device ''. --- Best regards, Phillip Guan
Re: HP DLT tape drive support for backupset restore
Most of the HP DLT libraries are not supported, well our 40 odd aren't anyway. have a look at: http://www.tivoli.com/support/storage_mgr/adh0dev.htm for supported devices for TSM server 3.7 on HP-UX, or http://www.tivoli.com/support/storage_mgr/ad60dev.htm for supported devices for TSM server 3.7 on AIX. DLT library support is one of my biggest problems with TSM. Michael Gogos Unix Systems Support ANZ Banking Group 227 Toorak Road South Yarra 3141 Victoria, Australia phone: (+613) 9869-6840 fax: (+613) 9869-3447 email: mailto:[EMAIL PROTECTED] -Original Message- From: Phillip Guan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 22, 2000 9:20 AM To: [EMAIL PROTECTED] Subject: HP DLT tape drive support for backupset restore Hi all, I created a backupset successfully on HP DLT40e tape drive and can query the content on the tape, but I cannot restore the backupset from it. Our AIX level is 4.3.3.0, TSM server is 3.7.2 and the client is on the same box as server. I wonder if HP DLT40 is supported on TSM 3.7. Thanks a lot! Here are the command and error message: -- dsmc restore backupset /dev/rmt0 -loc=tape Tivoli Storage Manager Command Line Backup Client Interface - Version 3, Release 7, Level 2.0 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Restore function invoked. Node Name: SFAIX2 Restore Processing Interrupted!! ANS1933E Error accessing file or device ''. --- Best regards, Phillip Guan
