Migrating/moving data from one server to another.
Hi All! We have an old IBM aix server with TSM 5.2.2 server and plan to move/migrate this to a new server and tape library. Info: Old system:F80 ibm server, TSM 5.2.2, 3575 library, L24 drives. New system: P520, TSM 5.2.x, 3582 L23 library, 2xLTO3 drives. 2,5 TB disk for stgpools and db etc. We want to migrate the old server to the new one, keeping the data but not the hardware/tapes/library. Our plan is to install a new tsm server on the new hardware and somehow copy the data for the nodes to the new, keeping all backupdata. Is the a best practise/redbook or other information available regarding this. Erik Björndell Zetup by Semcon
Re: Migrating/moving data from one server to another.
Hi Erik, You can do this in two ways (brief). 1. Setup server-to-server communication between the old and the new server. Do an 'export server' to get all policy information to the new server and redirect all backups to the new hardware. Do exports on all monthly/yearly and archive data to the new server. Daily backps expire. 2.Do a DB restore on the new server. Connect both the new and old library on the new server and start to 'move data' or move nodedata' from L24 to LTO. Last solution seems easiest to me. And you dont need to maintain a second server. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Erik Björndell Sent: den 9 maj 2006 11:31 To: ADSM-L@VM.MARIST.EDU Subject: Migrating/moving data from one server to another. Hi All! We have an old IBM aix server with TSM 5.2.2 server and plan to move/migrate this to a new server and tape library. Info: Old system:F80 ibm server, TSM 5.2.2, 3575 library, L24 drives. New system: P520, TSM 5.2.x, 3582 L23 library, 2xLTO3 drives. 2,5 TB disk for stgpools and db etc. We want to migrate the old server to the new one, keeping the data but not the hardware/tapes/library. Our plan is to install a new tsm server on the new hardware and somehow copy the data for the nodes to the new, keeping all backupdata. Is the a best practise/redbook or other information available regarding this. Erik Björndell Zetup by Semcon --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: Migrating/moving data from one server to another.
A second note. Search the archives for more hints about this matter. Admin Guide is always usefull too. :-) //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Erik Björndell Sent: den 9 maj 2006 11:31 To: ADSM-L@VM.MARIST.EDU Subject: Migrating/moving data from one server to another. Hi All! We have an old IBM aix server with TSM 5.2.2 server and plan to move/migrate this to a new server and tape library. Info: Old system:F80 ibm server, TSM 5.2.2, 3575 library, L24 drives. New system: P520, TSM 5.2.x, 3582 L23 library, 2xLTO3 drives. 2,5 TB disk for stgpools and db etc. We want to migrate the old server to the new one, keeping the data but not the hardware/tapes/library. Our plan is to install a new tsm server on the new hardware and somehow copy the data for the nodes to the new, keeping all backupdata. Is the a best practise/redbook or other information available regarding this. Erik Björndell Zetup by Semcon --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
5.3 reclaim command
Hello all, I have been testing the 5.3 reclaim stgpool command but for some reason it seems reclaim more than 3 volumes. The script/command that I use is below. RECLaim STGpool R3592POOL THreshold=30 - OFFSITERECLAIMlimit=3 Has anyone used this command with success? Thanks for any help in Advance! TSM 5.3.3 Aix 5.3
Re: Migrating/moving data from one server to another.
Splendid. Your answers helped me to get on track. I think we will somehow use the export node,server,policy commands, Like exporting policys and mgmt etc. Then modify them to suit our new environmen. As we cant connect the old lib to the new server (separate buildings and the old library is heavy as an elephant) we must use server to server exports. Regards, Erik Björndell Systems Specialist __ zetup by Semcon Kardanvägen 37 SE-461 38 TROLLHÄTTAN Sweden Phone +46(0)520-40 08 00 Moblie +46(0)736-84 04 06 E-mail [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Wahlstedt Sent: den 9 maj 2006 12:47 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migrating/moving data from one server to another. A second note. Search the archives for more hints about this matter. Admin Guide is always usefull too. :-) //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Erik Björndell Sent: den 9 maj 2006 11:31 To: ADSM-L@VM.MARIST.EDU Subject: Migrating/moving data from one server to another. Hi All! We have an old IBM aix server with TSM 5.2.2 server and plan to move/migrate this to a new server and tape library. Info: Old system:F80 ibm server, TSM 5.2.2, 3575 library, L24 drives. New system: P520, TSM 5.2.x, 3582 L23 library, 2xLTO3 drives. 2,5 TB disk for stgpools and db etc. We want to migrate the old server to the new one, keeping the data but not the hardware/tapes/library. Our plan is to install a new tsm server on the new hardware and somehow copy the data for the nodes to the new, keeping all backupdata. Is the a best practise/redbook or other information available regarding this. Erik Björndell Zetup by Semcon --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. !DSPAM:4460569152656115218568!
Re: 5.3 reclaim command
Hi, Is R3592POOL a primary or copypool? OFFSITERECLAIMlimit is only valid for copypools. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: den 9 maj 2006 13:18 To: ADSM-L@VM.MARIST.EDU Subject: 5.3 reclaim command Hello all, I have been testing the 5.3 reclaim stgpool command but for some reason it seems reclaim more than 3 volumes. The script/command that I use is below. RECLaim STGpool R3592POOL THreshold=30 - OFFSITERECLAIMlimit=3 Has anyone used this command with success? Thanks for any help in Advance! TSM 5.3.3 Aix 5.3 --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: 5.3 reclaim command
Henrik, It is a copypool. Henrik Wahlstedt wrote: > Hi, > > Is R3592POOL a primary or copypool? OFFSITERECLAIMlimit is only valid > for copypools. > > //Henrik > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Timothy Hughes > Sent: den 9 maj 2006 13:18 > To: ADSM-L@VM.MARIST.EDU > Subject: 5.3 reclaim command > > Hello all, > > I have been testing the 5.3 reclaim stgpool command but for some reason > it seems reclaim more than 3 volumes. > The script/command that I use is below. > > RECLaim STGpool R3592POOL THreshold=30 - > OFFSITERECLAIMlimit=3 > > Has anyone used this command with success? > > Thanks for any help in Advance! > > TSM 5.3.3 > Aix 5.3 > > --- > The information contained in this message may be CONFIDENTIAL and is > intended for the addressee only. Any unauthorised use, dissemination of the > information or copying of this message is prohibited. If you are not the > addressee, please notify the sender immediately by return e-mail and delete > this message. > Thank you.
Data Protection for SQL - Windows x64 Package is now available
Data Protection for SQL - Windows x64 Package is now available For those of you that have asked about the Windows "x64" version of Data Protection for SQL... it is now available. This package has been tested on AMD64 and EM64T hardware. You can obtain the package through Passport Advantage. The package name is: IBM Tivoli Storage Manager for Databases V5.3.3 (Data Protection for Microsoft SQL), Windows, Multiplatform (C913CML) 08-May-2006 Thanks, Del Del Hoobler Tivoli Storage Manager Development IBM Corporation
Novell question !!!!!!
Hi to all I have a Netware server with sys: and vol1: local volumes and mounted a disk on a clariion storage EV1: Here the output of the command Q FILES tsm> q files # Last Incr Date TypeFile Space Name --- -- --- 1 00/00/ 00:00:00 NTWFS NWCC-CL2\EV1: 2 05/06/2006 22:00:04 NovellSMS NWCC-CL2\SERVER SPECIFIC INFO 3 05/06/2006 22:34:38 NTW:LONG NWCC-CL2\SYS: 4 05/02/2006 22:34:04 NTW:LONG NWCC-CL2\VOL1: Few questions, I did an online backup of EV1: without any problems , I connect the client via internet http://xxx.xx.xx.xx:1581 and saw the directories and files on the restore panel, my first question is why when I load the backup I see just the local volumes sys: and vol1: (I have in my dsm.opt the line DOMAIN all-localEV1:) and after changes I unload and load dsmcad .. My second question is why in the restore panel I see directories with long names (+8) in dos format xx~1. My tsm client version is 5.3.012 and my Netware server version is 6.5 Any help will be appreciate . Regards Robert Ouzen
Re: TDP MSSQL on X86-64
Data Protection for SQL - Windows x64 Package is now available For those of you that have asked about the Windows "x64" version of Data Protection for SQL... it is now available. This package has been tested on AMD64 and EM64T hardware. You can obtain the package through Passport Advantage. The package name is: IBM Tivoli Storage Manager for Databases V5.3.3 (Data Protection for Microsoft SQL), Windows, Multiplatform (C913CML) 08-May-2006 Thanks, Del Del Hoobler Tivoli Storage Manager Development IBM Corporation "ADSM: Dist Stor Manager" wrote on 04/07/2006 01:03:23 PM: > Hello, > > The TDP for MSSQL referred to is for SQL Server 2005? > Is there X86-64 bit TSM Client? > > Thanks, > Yi > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del > Hoobler > Sent: Tuesday, March 28, 2006 4:11 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TDP MSSQL on X86-64 > > Hi Paul, > > As Steve said... this is something we are working on right now. > > Look for something in the next month or so... standard disclaimers apply, > i.e. this is not a guarantee and IBM reserves the right to > change these dates and plans. > > Thanks, > > Del > > > > "ADSM: Dist Stor Manager" wrote on 03/28/2006 > 03:37:49 PM: > > > Hello all, > > > > > > > > > > > >Does somebody have any info about the release of a TDP for SQL Server > > on x86_64? I know there is a version that runs on IA64 (Itanium), but we > > are starting to get several requests from customers who are installing > > W2K3 64bit/SQL Server 64bit on their new Xeon Servers and naturally > > want to back up their databases. > >
Re: TDP MSSQL on X86-64
Thank You! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Tuesday, May 09, 2006 8:47 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: TDP MSSQL on X86-64 Data Protection for SQL - Windows x64 Package is now available For those of you that have asked about the Windows "x64" version of Data Protection for SQL... it is now available. This package has been tested on AMD64 and EM64T hardware. You can obtain the package through Passport Advantage. The package name is: IBM Tivoli Storage Manager for Databases V5.3.3 (Data Protection for Microsoft SQL), Windows, Multiplatform (C913CML) 08-May-2006 Thanks, Del Del Hoobler Tivoli Storage Manager Development IBM Corporation "ADSM: Dist Stor Manager" wrote on 04/07/2006 01:03:23 PM: > Hello, > > The TDP for MSSQL referred to is for SQL Server 2005? > Is there X86-64 bit TSM Client? > > Thanks, > Yi > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del > Hoobler > Sent: Tuesday, March 28, 2006 4:11 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TDP MSSQL on X86-64 > > Hi Paul, > > As Steve said... this is something we are working on right now. > > Look for something in the next month or so... standard disclaimers apply, > i.e. this is not a guarantee and IBM reserves the right to > change these dates and plans. > > Thanks, > > Del > > > > "ADSM: Dist Stor Manager" wrote on 03/28/2006 > 03:37:49 PM: > > > Hello all, > > > > > > > > > > > >Does somebody have any info about the release of a TDP for SQL Server > > on x86_64? I know there is a version that runs on IA64 (Itanium), but we > > are starting to get several requests from customers who are installing > > W2K3 64bit/SQL Server 64bit on their new Xeon Servers and naturally > > want to back up their databases. > >
Re: DR Question -
We have DR implemented here running 5.2.3 in a Windows environment. Been running like a charm for over 2 years. We have daily offsite tapes going so that if something happens, we loose very little data. The DR module also produces a daily DR plan for you in case of a disaster. Tells you exactly what is needed and what to run so you are back in production in a timely matter. Bob Martoncik Lucas County Information Services 419-213-4633 >>> [EMAIL PROTECTED] 5/8/2006 3:53:10 PM >>> We have TSM 5.3.0.0. on AIX and backup about 177 WINTEL servers , We would like to implement DR module..has any body had any experience with DR manager ? Any insight. Currently we do weekly backup and copy prime copy on site pool to backup offsite backup copy pool along with TSM server database then we send offsite copy backup pool ( for DR purposes ) to offsite storage. Our DR pools are about 135 lto2 tapes. We have three such pools in rotation. IS there any better way to do DR strategy ? Thanks, Ashok
Re: Redirecting Output of NetWare Console dsmc to a File ?
The only method I can think of off the top of my head is to put the command in a schedule, and associate that server to it. The output will show up in sys:\tivoli\tsm\client\ba\dsmsched.log >>> [EMAIL PROTECTED] 5/9/2006 1:57 AM >>> Hello TSM+NetWare Experts, is there a way to put the output of, for example, "dsmc q backup" on the NetWare 6 console into a file? Or, if not, can I use another OS's TSM client? I didn't succeed with Linux and MS Windows TSM clients. Thank you all. Rainer -- Rainer Wolf eMail: [EMAIL PROTECTED] kiz - Abt. Infrastruktur Tel/Fax: ++49 731 50-22482/22471 Universitaet Ulm wwweb: http://kiz.uni-ulm.de Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: 5.3 reclaim command
It make take more than 3 primary pool tapes to reclaim 3 offsite tapes. >>> [EMAIL PROTECTED] 5/9/2006 7:17:45 AM >>> Hello all, I have been testing the 5.3 reclaim stgpool command but for some reason it seems reclaim more than 3 volumes. The script/command that I use is below. RECLaim STGpool R3592POOL THreshold=30 - OFFSITERECLAIMlimit=3 Has anyone used this command with success? Thanks for any help in Advance! TSM 5.3.3 Aix 5.3
Re: 5.3 reclaim command
On May 9, 2006, at 7:17 AM, Timothy Hughes wrote: I have been testing the 5.3 reclaim stgpool command but for some reason it seems reclaim more than 3 volumes. ... Tim - It would be healthy to have definitive information on the presumed problem. Please review what the operation actually did, from the Activity Log and evidence of the offsite copy storage pool volumes going to Pending state as a result. I'm wondering if what you are seeing is more than three Onsite volumes being mounted to satisfy the data movement of the contents of the offsite volumes. And take into account the circumstances when files span volumes. If you find hard evidence to contradict what the OFFSITERECLAIMlimit is supposed to do, by all means file a report with TSM Support. Richard Sims
Re: Novell question !!!!!!
sys: & vol1: appear to be getting recognized as "long filename" filesystems under the "Type" column, while ev1: isn't. Is EV1: an nss volume, or traditional? In my case, I've got a couple servers attached to ibm ds4300's (fastt600), where sys: is local, and vol1: is on the san. When I do a "q files", both sys: and vol1: are listed as type "NTW:LONG" even though vol1: isn't a local volume. If it turns out that the EV1: volume just never got the "Long" namespace added to it, you can do a "load long", then "add name space long to ev1:". If EV1: is an nss volume, I'm not quite sure what happened.they're supposed to have the LONG namespace added by default. >>> [EMAIL PROTECTED] 5/9/2006 7:42 AM >>> Hi to all I have a Netware server with sys: and vol1: local volumes and mounted a disk on a clariion storage EV1: Here the output of the command Q FILES tsm> q files # Last Incr Date Type File Space Name --- -- --- 1 00/00/ 00:00:00 NTWFS NWCC-CL2\EV1: 2 05/06/2006 22:00:04 NovellSMS NWCC-CL2\SERVER SPECIFIC INFO 3 05/06/2006 22:34:38 NTW:LONG NWCC-CL2\SYS: 4 05/02/2006 22:34:04 NTW:LONG NWCC-CL2\VOL1: Few questions, I did an online backup of EV1: without any problems , I connect the client via internet http://xxx.xx.xx.xx:1581 and saw the directories and files on the restore panel, my first question is why when I load the backup I see just the local volumes sys: and vol1: (I have in my dsm.opt the line DOMAIN all-local EV1:) and after changes I unload and load dsmcad .. My second question is why in the restore panel I see directories with long names (+8) in dos format xx~1. My tsm client version is 5.3.012 and my Netware server version is 6.5 Any help will be appreciate . Regards Robert Ouzen Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: Novell question !!!!!!
Hi Troy Here what I got running VOLUMES in the Netware server: 3 local FAT volumes mounted Mounted Volumes Name Spaces Flags SYS DOS, MAC, NFS, LONG NSS _ADMINDOS, MAC, NFS, LONG NSS P VOL1 DOS, MAC, NFS, LONG NSS EV2 DOS, MAC, NFS, LONG NSS EV1 DOS, MAC, NFS, LONG NSS 5 volumes mounted Can you explain a little beat more about "load long" ? It is a novell command And how to add name space long to EV1: Can you send me an example ! Thanks in advance . Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, May 09, 2006 4:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! sys: & vol1: appear to be getting recognized as "long filename" filesystems under the "Type" column, while ev1: isn't. Is EV1: an nss volume, or traditional? In my case, I've got a couple servers attached to ibm ds4300's (fastt600), where sys: is local, and vol1: is on the san. When I do a "q files", both sys: and vol1: are listed as type "NTW:LONG" even though vol1: isn't a local volume. If it turns out that the EV1: volume just never got the "Long" namespace added to it, you can do a "load long", then "add name space long to ev1:". If EV1: is an nss volume, I'm not quite sure what happened.they're supposed to have the LONG namespace added by default. >>> [EMAIL PROTECTED] 5/9/2006 7:42 AM >>> Hi to all I have a Netware server with sys: and vol1: local volumes and mounted a disk on a clariion storage EV1: Here the output of the command Q FILES tsm> q files # Last Incr Date Type File Space Name --- -- --- 1 00/00/ 00:00:00 NTWFS NWCC-CL2\EV1: 2 05/06/2006 22:00:04 NovellSMS NWCC-CL2\SERVER SPECIFIC INFO 3 05/06/2006 22:34:38 NTW:LONG NWCC-CL2\SYS: 4 05/02/2006 22:34:04 NTW:LONG NWCC-CL2\VOL1: Few questions, I did an online backup of EV1: without any problems , I connect the client via internet http://xxx.xx.xx.xx:1581 and saw the directories and files on the restore panel, my first question is why when I load the backup I see just the local volumes sys: and vol1: (I have in my dsm.opt the line DOMAIN all-local EV1:) and after changes I unload and load dsmcad .. My second question is why in the restore panel I see directories with long names (+8) in dos format xx~1. My tsm client version is 5.3.012 and my Netware server version is 6.5 Any help will be appreciate . Regards Robert Ouzen Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: Migrating/moving data from one server to another.
Erik - The following Redbooks Technote may help: http://www.redbooks.ibm.com/abstracts/TIPS0401.html Richard Sims
Re: Novell question !!!!!!
Unfortunately, it doesn't appear that my suggestion applies to you. EV1: is an NSS volume, and already has the LONG namespace loaded on it. In the old days on Traditional Volumes, it didn't always default to that. Might be worth opening a ticket with novell for that one. >>> [EMAIL PROTECTED] 5/9/2006 9:05 AM >>> Hi Troy Here what I got running VOLUMES in the Netware server: 3 local FAT volumes mounted Mounted Volumes Name Spaces Flags SYS DOS, MAC, NFS, LONG NSS _ADMIN DOS, MAC, NFS, LONG NSS P VOL1 DOS, MAC, NFS, LONG NSS EV2 DOS, MAC, NFS, LONG NSS EV1 DOS, MAC, NFS, LONG NSS 5 volumes mounted Can you explain a little beat more about "load long" ? It is a novell command And how to add name space long to EV1: Can you send me an example ! Thanks in advance . Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, May 09, 2006 4:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! sys: & vol1: appear to be getting recognized as "long filename" filesystems under the "Type" column, while ev1: isn't. Is EV1: an nss volume, or traditional? In my case, I've got a couple servers attached to ibm ds4300's (fastt600), where sys: is local, and vol1: is on the san. When I do a "q files", both sys: and vol1: are listed as type "NTW:LONG" even though vol1: isn't a local volume. If it turns out that the EV1: volume just never got the "Long" namespace added to it, you can do a "load long", then "add name space long to ev1:". If EV1: is an nss volume, I'm not quite sure what happened.they're supposed to have the LONG namespace added by default. >>> [EMAIL PROTECTED] 5/9/2006 7:42 AM >>> Hi to all I have a Netware server with sys: and vol1: local volumes and mounted a disk on a clariion storage EV1: Here the output of the command Q FILES tsm> q files # Last Incr Date Type File Space Name --- -- --- 1 00/00/ 00:00:00 NTWFS NWCC-CL2\EV1: 2 05/06/2006 22:00:04 NovellSMS NWCC-CL2\SERVER SPECIFIC INFO 3 05/06/2006 22:34:38 NTW:LONG NWCC-CL2\SYS: 4 05/02/2006 22:34:04 NTW:LONG NWCC-CL2\VOL1: Few questions, I did an online backup of EV1: without any problems , I connect the client via internet http://xxx.xx.xx.xx:1581 and saw the directories and files on the restore panel, my first question is why when I load the backup I see just the local volumes sys: and vol1: (I have in my dsm.opt the line DOMAIN all-local EV1:) and after changes I unload and load dsmcad .. My second question is why in the restore panel I see directories with long names (+8) in dos format xx~1. My tsm client version is 5.3.012 and my Netware server version is 6.5 Any help will be appreciate . Regards Robert Ouzen Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you. Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: DR Question - Wintel Servers
This site uses a combination - image backups (Ghost or Acronis) for DR backups of some machines, TSM for others. Take a look at the latest TSM client manual at the section on recovery using ASR. This is a Microsoft function that is supported by TSM for Win2003 and XP machines. You have to follow the instructions carefully, and practice to get the hang of it. But, assuming you are restoring to like hardware, it works really well. The biggest problem with DR for Windows machines is if you have unlike hardware at the DR site. There are hacks available in the Microsoft Knowledge Base, but Microsoft doesn't SUPPORT restoring a Windows machine to unlike hardware. The only product that SUPPORTS Windows DR across unlike hardware is the Christie Bare-Metal restore product, which is an add-on to TSM. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nancy L Backhaus Sent: Monday, May 08, 2006 1:27 PM To: ADSM-L@VM.MARIST.EDU Subject: DR Question - Wintel Servers Trying to get a feel out in the TSM world of how many rely of us rely on only TSM for restoring Wintel Operating Systems verses using NT Backup Utility for Disaster Recovery. Background: TSM Server 5.3.2.2 :TSM Operating System AIX 5.3 125 Wintel Servers, Windows 2003 and Windows 2000, a couple WinNT TSM Versions , Mixed 5.3.2.2, 5.2.3.5, 5.2.2.0, 4.1.2.0, and 3.1.0.7 AIX - we use mksysb/nim Nancy Backhaus Enterprise Systems HealthNow, NY 716-887-7979 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: Redirecting Output of NetWare Console dsmc to a File ?
>>> On 5/9/2006 at 12:57 AM, [EMAIL PROTECTED] wrote: > Hello TSM+NetWare Experts, > > is there a way to put the output of, for example, > "dsmc q backup" on the NetWare 6 console into a file? > > Or, if not, can I use another OS's TSM client? > I didn't succeed with Linux and MS Windows TSM clients. > > Thank you all. > Rainer > > -- > > Rainer Wolf eMail: [EMAIL PROTECTED] > kiz - Abt. Infrastruktur Tel/Fax: ++49 731 50-22482/22471 > Universitaet Ulm wwweb:http://kiz.uni-ulm.de Try appending (CLIB_OPT)/>sys:test.out to your command. Something like: dsmc q backup (CLIB_OPT)/>sys:test.out --Matt
Re: 5.3 reclaim command
Thanks Henrik, David and Richard I think it is using more than 3 (onsite) primary tapes. I am going to review this further to make sure. regards Richard Sims wrote: > On May 9, 2006, at 7:17 AM, Timothy Hughes wrote: > > > I have been testing the 5.3 reclaim stgpool command but > > for some reason it seems reclaim more than 3 volumes. ... > > Tim - > > It would be healthy to have definitive information on the presumed > problem. Please review what the operation actually did, from the > Activity Log and evidence of the offsite copy storage pool volumes > going to Pending state as a result. I'm wondering if what you are > seeing is more than three Onsite volumes being mounted to satisfy the > data movement of the contents of the offsite volumes. And take into > account the circumstances when files span volumes. If you find hard > evidence to contradict what the OFFSITERECLAIMlimit is supposed to > do, by all means file a report with TSM Support. > > Richard Sims
Re: Novell question !!!!!!
Robert The only thing I'd suggest is to make sure you're at the latest SMS update level which I believe is still TSA5UP19. There have been a bunch of fixes in the last couple of releases. 19 is newer than the modules in SP5. Hope that helps, Andrew Ferris Network Support Analyst iCAPTURE Research Centre University of British Columbia >>> [EMAIL PROTECTED] 5/9/2006 7:22:04 am >>> Unfortunately, it doesn't appear that my suggestion applies to you. EV1: is an NSS volume, and already has the LONG namespace loaded on it. In the old days on Traditional Volumes, it didn't always default to that. Might be worth opening a ticket with novell for that one. >>> [EMAIL PROTECTED] 5/9/2006 9:05 AM >>> Hi Troy Here what I got running VOLUMES in the Netware server: 3 local FAT volumes mounted Mounted Volumes Name Spaces Flags SYS DOS, MAC, NFS, LONG NSS _ADMIN DOS, MAC, NFS, LONG NSS P VOL1 DOS, MAC, NFS, LONG NSS EV2 DOS, MAC, NFS, LONG NSS EV1 DOS, MAC, NFS, LONG NSS 5 volumes mounted Can you explain a little beat more about "load long" ? It is a novell command And how to add name space long to EV1: Can you send me an example ! Thanks in advance . Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, May 09, 2006 4:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! sys: & vol1: appear to be getting recognized as "long filename" filesystems under the "Type" column, while ev1: isn't. Is EV1: an nss volume, or traditional? In my case, I've got a couple servers attached to ibm ds4300's (fastt600), where sys: is local, and vol1: is on the san. When I do a "q files", both sys: and vol1: are listed as type "NTW:LONG" even though vol1: isn't a local volume. If it turns out that the EV1: volume just never got the "Long" namespace added to it, you can do a "load long", then "add name space long to ev1:". If EV1: is an nss volume, I'm not quite sure what happened.they're supposed to have the LONG namespace added by default. >>> [EMAIL PROTECTED] 5/9/2006 7:42 AM >>> Hi to all I have a Netware server with sys: and vol1: local volumes and mounted a disk on a clariion storage EV1: Here the output of the command Q FILES tsm> q files # Last Incr Date Type File Space Name --- -- --- 1 00/00/ 00:00:00 NTWFS NWCC-CL2\EV1: 2 05/06/2006 22:00:04 NovellSMS NWCC-CL2\SERVER SPECIFIC INFO 3 05/06/2006 22:34:38 NTW:LONG NWCC-CL2\SYS: 4 05/02/2006 22:34:04 NTW:LONG NWCC-CL2\VOL1: Few questions, I did an online backup of EV1: without any problems , I connect the client via internet http://xxx.xx.xx.xx:1581 and saw the directories and files on the restore panel, my first question is why when I load the backup I see just the local volumes sys: and vol1: (I have in my dsm.opt the line DOMAIN all-local EV1:) and after changes I unload and load dsmcad .. My second question is why in the restore panel I see directories with long names (+8) in dos format xx~1. My tsm client version is 5.3.012 and my Netware server version is 6.5 Any help will be appreciate . Regards Robert Ouzen Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you. Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: Novell question !!!!!!
Andrew I install TSA5UP19 and still I see in volume EV1: the filenames in Dos format , by the way in SYS: and Vol1: volumes no problem I got long filename! Thanks Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Ferris Sent: Tuesday, May 09, 2006 5:57 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! Robert The only thing I'd suggest is to make sure you're at the latest SMS update level which I believe is still TSA5UP19. There have been a bunch of fixes in the last couple of releases. 19 is newer than the modules in SP5. Hope that helps, Andrew Ferris Network Support Analyst iCAPTURE Research Centre University of British Columbia >>> [EMAIL PROTECTED] 5/9/2006 7:22:04 am >>> Unfortunately, it doesn't appear that my suggestion applies to you. EV1: is an NSS volume, and already has the LONG namespace loaded on it. In the old days on Traditional Volumes, it didn't always default to that. Might be worth opening a ticket with novell for that one. >>> [EMAIL PROTECTED] 5/9/2006 9:05 AM >>> Hi Troy Here what I got running VOLUMES in the Netware server: 3 local FAT volumes mounted Mounted Volumes Name Spaces Flags SYS DOS, MAC, NFS, LONG NSS _ADMIN DOS, MAC, NFS, LONG NSS P VOL1 DOS, MAC, NFS, LONG NSS EV2 DOS, MAC, NFS, LONG NSS EV1 DOS, MAC, NFS, LONG NSS 5 volumes mounted Can you explain a little beat more about "load long" ? It is a novell command And how to add name space long to EV1: Can you send me an example ! Thanks in advance . Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, May 09, 2006 4:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! sys: & vol1: appear to be getting recognized as "long filename" filesystems under the "Type" column, while ev1: isn't. Is EV1: an nss volume, or traditional? In my case, I've got a couple servers attached to ibm ds4300's (fastt600), where sys: is local, and vol1: is on the san. When I do a "q files", both sys: and vol1: are listed as type "NTW:LONG" even though vol1: isn't a local volume. If it turns out that the EV1: volume just never got the "Long" namespace added to it, you can do a "load long", then "add name space long to ev1:". If EV1: is an nss volume, I'm not quite sure what happened.they're supposed to have the LONG namespace added by default. >>> [EMAIL PROTECTED] 5/9/2006 7:42 AM >>> Hi to all I have a Netware server with sys: and vol1: local volumes and mounted a disk on a clariion storage EV1: Here the output of the command Q FILES tsm> q files # Last Incr Date Type File Space Name --- -- --- 1 00/00/ 00:00:00 NTWFS NWCC-CL2\EV1: 2 05/06/2006 22:00:04 NovellSMS NWCC-CL2\SERVER SPECIFIC INFO 3 05/06/2006 22:34:38 NTW:LONG NWCC-CL2\SYS: 4 05/02/2006 22:34:04 NTW:LONG NWCC-CL2\VOL1: Few questions, I did an online backup of EV1: without any problems , I connect the client via internet http://xxx.xx.xx.xx:1581 and saw the directories and files on the restore panel, my first question is why when I load the backup I see just the local volumes sys: and vol1: (I have in my dsm.opt the line DOMAIN all-local EV1:) and after changes I unload and load dsmcad .. My second question is why in the restore panel I see directories with long names (+8) in dos format xx~1. My tsm client version is 5.3.012 and my Netware server version is 6.5 Any help will be appreciate . Regards Robert Ouzen Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you. Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: Novell question !!!!!!
Did the volume get created new on this netware 6.5 server, or it get created earlier, on a previous version of netware (and was eventually migrated to nw6.5)? >>> [EMAIL PROTECTED] 5/9/2006 11:25 AM >>> Andrew I install TSA5UP19 and still I see in volume EV1: the filenames in Dos format , by the way in SYS: and Vol1: volumes no problem I got long filename! Thanks Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Ferris Sent: Tuesday, May 09, 2006 5:57 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! Robert The only thing I'd suggest is to make sure you're at the latest SMS update level which I believe is still TSA5UP19. There have been a bunch of fixes in the last couple of releases. 19 is newer than the modules in SP5. Hope that helps, Andrew Ferris Network Support Analyst iCAPTURE Research Centre University of British Columbia >>> [EMAIL PROTECTED] 5/9/2006 7:22:04 am >>> Unfortunately, it doesn't appear that my suggestion applies to you. EV1: is an NSS volume, and already has the LONG namespace loaded on it. In the old days on Traditional Volumes, it didn't always default to that. Might be worth opening a ticket with novell for that one. >>> [EMAIL PROTECTED] 5/9/2006 9:05 AM >>> Hi Troy Here what I got running VOLUMES in the Netware server: 3 local FAT volumes mounted Mounted Volumes Name Spaces Flags SYS DOS, MAC, NFS, LONG NSS _ADMIN DOS, MAC, NFS, LONG NSS P VOL1 DOS, MAC, NFS, LONG NSS EV2 DOS, MAC, NFS, LONG NSS EV1 DOS, MAC, NFS, LONG NSS 5 volumes mounted Can you explain a little beat more about "load long" ? It is a novell command And how to add name space long to EV1: Can you send me an example ! Thanks in advance . Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, May 09, 2006 4:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! sys: & vol1: appear to be getting recognized as "long filename" filesystems under the "Type" column, while ev1: isn't. Is EV1: an nss volume, or traditional? In my case, I've got a couple servers attached to ibm ds4300's (fastt600), where sys: is local, and vol1: is on the san. When I do a "q files", both sys: and vol1: are listed as type "NTW:LONG" even though vol1: isn't a local volume. If it turns out that the EV1: volume just never got the "Long" namespace added to it, you can do a "load long", then "add name space long to ev1:". If EV1: is an nss volume, I'm not quite sure what happened.they're supposed to have the LONG namespace added by default. >>> [EMAIL PROTECTED] 5/9/2006 7:42 AM >>> Hi to all I have a Netware server with sys: and vol1: local volumes and mounted a disk on a clariion storage EV1: Here the output of the command Q FILES tsm> q files # Last Incr Date Type File Space Name --- -- --- 1 00/00/ 00:00:00 NTWFS NWCC-CL2\EV1: 2 05/06/2006 22:00:04 NovellSMS NWCC-CL2\SERVER SPECIFIC INFO 3 05/06/2006 22:34:38 NTW:LONG NWCC-CL2\SYS: 4 05/02/2006 22:34:04 NTW:LONG NWCC-CL2\VOL1: Few questions, I did an online backup of EV1: without any problems , I connect the client via internet http://xxx.xx.xx.xx:1581 and saw the directories and files on the restore panel, my first question is why when I load the backup I see just the local volumes sys: and vol1: (I have in my dsm.opt the line DOMAIN all-local EV1:) and after changes I unload and load dsmcad .. My second question is why in the restore panel I see directories with long names (+8) in dos format xx~1. My tsm client version is 5.3.012 and my Netware server version is 6.5 Any help will be appreciate . Regards Robert Ouzen Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you. Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached
Re: Novell question !!!!!!
Frank I don't know I will ask the Novell administrator . Regards Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, May 09, 2006 7:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! Did the volume get created new on this netware 6.5 server, or it get created earlier, on a previous version of netware (and was eventually migrated to nw6.5)? >>> [EMAIL PROTECTED] 5/9/2006 11:25 AM >>> Andrew I install TSA5UP19 and still I see in volume EV1: the filenames in Dos format , by the way in SYS: and Vol1: volumes no problem I got long filename! Thanks Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Ferris Sent: Tuesday, May 09, 2006 5:57 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! Robert The only thing I'd suggest is to make sure you're at the latest SMS update level which I believe is still TSA5UP19. There have been a bunch of fixes in the last couple of releases. 19 is newer than the modules in SP5. Hope that helps, Andrew Ferris Network Support Analyst iCAPTURE Research Centre University of British Columbia >>> [EMAIL PROTECTED] 5/9/2006 7:22:04 am >>> Unfortunately, it doesn't appear that my suggestion applies to you. EV1: is an NSS volume, and already has the LONG namespace loaded on it. In the old days on Traditional Volumes, it didn't always default to that. Might be worth opening a ticket with novell for that one. >>> [EMAIL PROTECTED] 5/9/2006 9:05 AM >>> Hi Troy Here what I got running VOLUMES in the Netware server: 3 local FAT volumes mounted Mounted Volumes Name Spaces Flags SYS DOS, MAC, NFS, LONG NSS _ADMIN DOS, MAC, NFS, LONG NSS P VOL1 DOS, MAC, NFS, LONG NSS EV2 DOS, MAC, NFS, LONG NSS EV1 DOS, MAC, NFS, LONG NSS 5 volumes mounted Can you explain a little beat more about "load long" ? It is a novell command And how to add name space long to EV1: Can you send me an example ! Thanks in advance . Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, May 09, 2006 4:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! sys: & vol1: appear to be getting recognized as "long filename" filesystems under the "Type" column, while ev1: isn't. Is EV1: an nss volume, or traditional? In my case, I've got a couple servers attached to ibm ds4300's (fastt600), where sys: is local, and vol1: is on the san. When I do a "q files", both sys: and vol1: are listed as type "NTW:LONG" even though vol1: isn't a local volume. If it turns out that the EV1: volume just never got the "Long" namespace added to it, you can do a "load long", then "add name space long to ev1:". If EV1: is an nss volume, I'm not quite sure what happened.they're supposed to have the LONG namespace added by default. >>> [EMAIL PROTECTED] 5/9/2006 7:42 AM >>> Hi to all I have a Netware server with sys: and vol1: local volumes and mounted a disk on a clariion storage EV1: Here the output of the command Q FILES tsm> q files # Last Incr Date Type File Space Name --- -- --- 1 00/00/ 00:00:00 NTWFS NWCC-CL2\EV1: 2 05/06/2006 22:00:04 NovellSMS NWCC-CL2\SERVER SPECIFIC INFO 3 05/06/2006 22:34:38 NTW:LONG NWCC-CL2\SYS: 4 05/02/2006 22:34:04 NTW:LONG NWCC-CL2\VOL1: Few questions, I did an online backup of EV1: without any problems , I connect the client via internet http://xxx.xx.xx.xx:1581 and saw the directories and files on the restore panel, my first question is why when I load the backup I see just the local volumes sys: and vol1: (I have in my dsm.opt the line DOMAIN all-local EV1:) and after changes I unload and load dsmcad .. My second question is why in the restore panel I see directories with long names (+8) in dos format xx~1. My tsm client version is 5.3.012 and my Netware server version is 6.5 Any help will be appreciate . Regards Robert Ouzen Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you. Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unau
A Data Stream Can Not Be Opened
We recently moved some Netware 6.0 servers to a new TSM server. We also upgraded their clients to the latest for their platform/OS, 5.2.4.10 (5.2.5 just came out after we upgraded). The TSM server is Linux 5.3.2 The owners of the servers say they have the latest TSA modules. They are still using TSA600 vs TSAFS (the readme says this should be OK). Yes, the NDS ID being used supposedly has full authority over these servers. Ever since the move, we constantly get these errors: TSA600.NLM 6.0. 306 A Data Stream Can Not Be Opened I have redone the TSM.PWD file numerous times, to no avail ! I did not have these errors with the previous client (5.1.x) and the old TSM server (MVS 5.2.4) The only close hit I found on the Tivoli support website was in reference to the 5.2.2.9 client (1208746) and compresses NSS volumes and the recommend "solution" was "Do not use the TSM client version 5.2.2.9 with the latest TSA600.NLM"..no help for this situation ! Does this problem exists with all of the 5.2.x clients ? These errors seem to always occur on the SYS: volumes, especially with their ZENWORKS directory but usually all over. Any suggestions ? I am getting tired of seeing thousands of error messages from these boxes, every day.
Media in a backup set?
Is there an easy way to figure out which media go with which backup sets (and in which order?), or do I have to be really rigorous about culling the information from the server logs? I can see from Q LIBVOL which media are backupset media, but I don't yet see a way to see which tapes go with each other. TSM 5.2 on an AIX platform, if it matters. Thanks, Nick
Re: Media in a backup set?
- Nick Laflamme wrote: - >Is there an easy way to figure out which media go with which backup >sets (and in which order?), or do I have to be really rigorous about >culling the information from the server logs? I can see from Q LIBVOL >which media are backupset media, but I don't yet see a way to see >which tapes go with each other. The 'query volhistory' command and the 'volhistory' SQL table will provide this information, albeit in a somewhat clumsy way.
Re: Novell question !!!!!!
Hi Check out your tsafs.nlm start-up settings. It must be set to ClusterEnable No (as TSM is in Novell terms a not cluster aware application. Only ArcServe and BackupExec are.) If this is set to yes volumes with long filenames will be backed up in 8.3. This means TSM will not recognise changes in long filenames. But it will restore the first backed up long filename. Cheers Marco Kind Regards Marco Malgarini Malga Consulting -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Robert Ouzen Ouzen Sent: Wednesday, 10 May 2006 00:05 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Novell question !! Hi Troy Here what I got running VOLUMES in the Netware server: 3 local FAT volumes mounted Mounted Volumes Name Spaces Flags SYS DOS, MAC, NFS, LONG NSS _ADMINDOS, MAC, NFS, LONG NSS P VOL1 DOS, MAC, NFS, LONG NSS EV2 DOS, MAC, NFS, LONG NSS EV1 DOS, MAC, NFS, LONG NSS 5 volumes mounted Can you explain a little beat more about "load long" ? It is a novell command And how to add name space long to EV1: Can you send me an example ! Thanks in advance . Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Tuesday, May 09, 2006 4:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Novell question !! sys: & vol1: appear to be getting recognized as "long filename" filesystems under the "Type" column, while ev1: isn't. Is EV1: an nss volume, or traditional? In my case, I've got a couple servers attached to ibm ds4300's (fastt600), where sys: is local, and vol1: is on the san. When I do a "q files", both sys: and vol1: are listed as type "NTW:LONG" even though vol1: isn't a local volume. If it turns out that the EV1: volume just never got the "Long" namespace added to it, you can do a "load long", then "add name space long to ev1:". If EV1: is an nss volume, I'm not quite sure what happened.they're supposed to have the LONG namespace added by default. >>> [EMAIL PROTECTED] 5/9/2006 7:42 AM >>> Hi to all I have a Netware server with sys: and vol1: local volumes and mounted a disk on a clariion storage EV1: Here the output of the command Q FILES tsm> q files # Last Incr Date Type File Space Name --- -- --- 1 00/00/ 00:00:00 NTWFS NWCC-CL2\EV1: 2 05/06/2006 22:00:04 NovellSMS NWCC-CL2\SERVER SPECIFIC INFO 3 05/06/2006 22:34:38 NTW:LONG NWCC-CL2\SYS: 4 05/02/2006 22:34:04 NTW:LONG NWCC-CL2\VOL1: Few questions, I did an online backup of EV1: without any problems , I connect the client via internet http://xxx.xx.xx.xx:1581 and saw the directories and files on the restore panel, my first question is why when I load the backup I see just the local volumes sys: and vol1: (I have in my dsm.opt the line DOMAIN all-local EV1:) and after changes I unload and load dsmcad .. My second question is why in the restore panel I see directories with long names (+8) in dos format xx~1. My tsm client version is 5.3.012 and my Netware server version is 6.5 Any help will be appreciate . Regards Robert Ouzen Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: Media in a backup set?
I use an SQL query to get the info SELECT VOLHISTORY.VOLUME_NAME, BACKUPSETS.BACKUPSET_NAME,BACKUPSETS.DATE_TIME, BACKUPSETS.DESCRIPTION FROM VOLHISTORY,BACKUPSETS WHERE VOLHISTORY.TYPE='BACKUPSET' AND VOLHISTORY.DATE_TIME=BACKUPSETS.DATE_TIME ORDER BY BACKUPSETS.DATE_TIME DESC Give that a try! Chris Thomas Denier <[EMAIL PROTECTED]> on 10/05/2006 06:09:52 Please respond to "ADSM: Dist Stor Manager" To: ADSM-L@VM.MARIST.EDU cc:(bcc: Chris Pasztor/HCS) Subject: Re: [ADSM-L] Media in a backup set? - Nick Laflamme wrote: - >Is there an easy way to figure out which media go with which backup >sets (and in which order?), or do I have to be really rigorous about >culling the information from the server logs? I can see from Q LIBVOL >which media are backupset media, but I don't yet see a way to see >which tapes go with each other. The 'query volhistory' command and the 'volhistory' SQL table will provide this information, albeit in a somewhat clumsy way.
Re: Throttling back TSM client
Paul, I know it's been a while since you posted this but I wanted to share my insights. We've received the same complaints. The problem is not TSM per se, but the fact that I/O is interrupt-based and the interrupt service routines run at high-priority. This also affects any scan process, including anti-virus. For years, the AV writers set their software to scan at the lowest possible priority, only to have it create a huge impact on the machine anyway. No matter how low a priority the process runs, once it tells the storage system to read a file, that file read will run at high priority until it completes the transaction. On the network, there is another factor to consider, that was discussed recently by Intel engineers in one of the IEEE computer magazines. Incoming network data ends up being placed in memory by the NIC driver without being cached by the CPU. When the NIC generates the interrupt telling the CPU to process the received data, its absence in every level of CPU cache causes a cache miss and at today's clock cycles, a stall of several hundred cycles while the addresses and data make their way into the cache hierarchy. Since at the start of every standard TSM backup, the client receives over the network the list of files already known to TSM, that qualifies as "incoming data". Outgoing data is less of a factor since the processor is setting up the data in the various buffers. Therefore, what we've chosen to do is this: * provide a set of hourly schedules spread between 8 pm and 5 am; a PC - CAD workstation in our case - can be set to "backup no earlier than xxx". If I have an engineer who frequently works till 8 pm, I can schedule his PC to backup at 11 pm, for example. We also have a special "noon" backup schedule for docked laptops. * tune TCP window size to reduce the number of acknowledgements; * tune the client aggregation settings to minimize the number of data bursts; we have our system set to create 48 MB aggregates by default. The larger the aggregate, the fewer number of transfers will be made, but the more memory will be needed to buffer the aggregate under construction. * turn off anti-virus scanning on files "when opened for backup"; all PCs have real-time scan enabled so it isn't necessary to re-scan when backing up. Hope this helps. Tab Trepagnier TSM Administrator Laitram LLC "ADSM: Dist Stor Manager" wrote on 04/25/2006 01:13:58 PM: > We have a small number of users here who are complaining that when a > TSM backup runs on their client system, it monopolizes use of their > network card. They are looking for a way to throttle back TSM's use > of the network. Has anyone else run into this? Any ideas? The only > thing I've come up with is to configure a secondary NIC at 10MB/s and > point these users at that card. This seems crude to me, so other > ideas would be welcome. > > ..Paul > > > -- > Paul ZarnowskiPh: 607-255-4757 > Manager, Storage Systems Fx: 607-255-8521 > 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
