Re: MPIO for tape libraries
Mehdi, >>> Does defining logical tape drives helps eliminating this single point of failure such that if during client backup the fiber connection of drive fails, another tape drive in the library takes over the operation? Okay, the quote from the Redbook below may have misled you in this case: a 'logical tape library' as you describe below is quite different to the concept you describe as a logical tape drive, it is how IBM describe their library partitioning. Here, creating 'logical libraries' (i.e. a library partition) will allow you to share a single physical library amongst, for example, Netbackup, Mainframe and TSM applications and the partitioning is managed by the library itself (e.g. with ALMS in a TS3500/3584) and has nothing to do with any virtualisation/logical definitions within TSM or the OS. The tape drives themselves here are not virtualised: you're still accessing a *physical* tape drive device, and a failure of a physical LTO drive, or the path to it, will still result in that path/drive going offline - potentially interrupting a data movement operation, although as Steven has also pointed out, TSM's normally pretty hot on these and may retry the operation on a different drive. Hope that helps, /DMc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mehdi Salehi Sent: 12 October 2009 06:42 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] MPIO for tape libraries For logical tape libraries, please look at this excerpt from SG24-5946-06: " Multiple logical libraries are an effective way for the library to simultaneously back up and restore data from heterogeneous applications. For example, the library can be partitioned so that it processes: - Commands from Application 1 (about Department X) in Logical Library A - Commands from Application 2 (about Department Y) in Logical Library B - Commands from Application 3 (about Department Z) in Logical Library C In this configuration, the storage slots and drives in each logical library are dedicated to that library and are not shared among other libraries. Commands issued by the applications travel to the library through three unique control paths. Thus, the data processing for: - Department X is confined to the storage slots and drives in Logical Library A - Department Y is confined to the storage slots and drives in Logical Library B - Department Z is confined to the storage slots and drives in Logical Library C" No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.421 / Virus Database: 270.14.3/2415 - Release Date: 10/11/09 06:39:00 -Original Message- From: David McClelland [mailto:t...@networkc.co.uk] Sent: 11 October 2009 18:18 To: 'ADSM: Dist Stor Manager' Subject: RE: [ADSM-L] MPIO for tape libraries I'm not quite sure I know what you mean by 'defining logical tape drives', without a VTL or somesuch. Can you expand technically upon what you mean? >From my experience, the majority of failures involving tape drives have been down to drive/head mechanics failure or tape cartridge errors (although I note that this seems to be increasingly uncommon these days), rather than physical fiber component failure. In these instances, any amount of multi-pathing can't help and you need to make sure that you have enough spare capacity in your library/design to cope, and an alerting/support process in place which can recognise it and get it resolved as quickly as possible. Given that most of your backup clients will (presumably) initially write to TSM-managed disk storage pools (except SAN Storage Agents and perhaps NDMPs etc) hopefully a drive failure won't have a direct impact upon a client backup data integrity, as TSM tends to be pretty precious about this when performing migrations/data movement operations involving tapes. /DMc -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mehdi Salehi Sent: 11 October 2009 17:13 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] MPIO for tape libraries Thanks David, you made a good point about single fiber connections of LTO drives. Does defining logical tape drives helps eliminating this single point of failure such that if during client backup the fiber connection of drive fails, another tape drive in the library takes over the operation?
SANergy with TSM 6.1
Hi, Which version of SANergy is compatible with TSM 6.1? I could not find enough information about SANergy except the old practical guide (June 2001)! Thanks
snapdiff
Hi All, I'm currently looking into the snapdiff feature of the TSM 6.1 client. My customer is still running TSM server version 5.4, so I was looking into the requirements for using the 6.1 client and the snapdiff feature. Does anyone know if there is any dependancy on a specific server version to be able to use the snapdiff feature? -- Met vriendelijke groeten/Kind regards, Remco Post r.p...@plcs.nl
Re: snapdiff
Have you tried to search in Internet? For example: http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&uid=swg21392122&loc=en_US&cs=UTF-8&lang=en Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Remco Post Sent: Monday, October 12, 2009 1:27 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] snapdiff Hi All, I'm currently looking into the snapdiff feature of the TSM 6.1 client. My customer is still running TSM server version 5.4, so I was looking into the requirements for using the 6.1 client and the snapdiff feature. Does anyone know if there is any dependancy on a specific server version to be able to use the snapdiff feature? -- Met vriendelijke groeten/Kind regards, Remco Post r.p...@plcs.nl Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
Re: snapdiff
On 12 okt 2009, at 12:36, Grigori Solonovitch wrote: Have you tried to search in Internet? For example: http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&uid=swg21392122&loc=en_US&cs=UTF-8&lang=en Where does this document list TSM server level requirements? I've searched the TSM client manual, the TSM wiki and whatever google could turn up. Since google reported that some people were actually experimenting with snapdiff, I'd thought to ask the list as well Hi All, I'm currently looking into the snapdiff feature of the TSM 6.1 client. My customer is still running TSM server version 5.4, so I was looking into the requirements for using the 6.1 client and the snapdiff feature. Does anyone know if there is any dependancy on a specific server version to be able to use the snapdiff feature? -- Met vriendelijke groeten/Kind regards, Remco Post r.p...@plcs.nl
instrumentation for the server?
Hello, I am currently analyzing a TSM server which uses 100% CPU on 4 cores when doing client backups. Almost all of it is privileged times, but there are very few IO's and low disk queues for both stgpools, db and log. Are there any trace flags similar to the client testflag instrument:detail but for the server that will allow me to see what the server is spending time on? I've been looking in the problem determination guide but cant find any flag similar to instrument_detail except for 'instr' which isnt documented and only gives me DB LATCHes. -km
Re: instrumentation for the server?
I once saw this when we had set BUFPOOLSIZE way too high.Giving the TSM server lots of memory starved the OS for memory; things slowed down horribly until we set BUFPOOLSIZE back to the Performance-tuning-guide recommendations ( I forget - 1/4 of available memory?) On Mon, Oct 12, 2009 at 7:58 AM, km wrote: > Hello, > > I am currently analyzing a TSM server which uses 100% CPU on 4 cores > when doing client backups. Almost all of it is privileged times, but > there are very few IO's and low disk queues for both stgpools, db and log. > > Are there any trace flags similar to the client testflag instrument:detail > but for the server that will allow me to see what the server is spending > time on? > > I've been looking in the problem determination guide but cant find any > flag similar to instrument_detail except for 'instr' which isnt documented > and only gives me DB LATCHes. > > -km > -- Lindsay Morris Principal TSMworks Tel. 1-859-539-9900 lind...@tsmworks.com
Re: snapdiff
The "Migrating from earlier versions" section near the beginning of the client manual discusses the topic of which servers are supported with the 5.5 client (5.5 or 6.1). Alternatively see http://www.ibm.com/support/docview.wss?uid=swg21053218 In theory the SnapDiff functionality should work with a 5.4 server (we are not aware of any feature-wise limitations in this regard). However, as the above item will indicate, 6.1 client and 5.4 server is not an officially supported configuration. 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/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" wrote on 10/12/2009 06:46:53 AM: > [image removed] > > Re: snapdiff > > Remco Post > > to: > > ADSM-L > > 10/12/2009 06:47 AM > > Sent by: > > "ADSM: Dist Stor Manager" > > Please respond to "ADSM: Dist Stor Manager" > > On 12 okt 2009, at 12:36, Grigori Solonovitch wrote: > > > Have you tried to search in Internet? > > > > For example: > > > > http://www-01.ibm.com/support/docview.wss? > rs=663&context=SSGSG7&uid=swg21392122&loc=en_US&cs=UTF-8&lang=en > > > > > > Where does this document list TSM server level requirements? I've > searched the TSM client manual, the TSM wiki and whatever google could > turn up. Since google reported that some people were actually > experimenting with snapdiff, I'd thought to ask the list as well > > > > > > Hi All, > > > > > > > > I'm currently looking into the snapdiff feature of the TSM 6.1 client. > > > > My customer is still running TSM server version 5.4, so I was looking > > > > into the requirements for using the 6.1 client and the snapdiff > > > > feature. Does anyone know if there is any dependancy on a specific > > > > server version to be able to use the snapdiff feature? > > > > -- > Met vriendelijke groeten/Kind regards, > > Remco Post > r.p...@plcs.nl
Re: Date, time and number format
You should not add things to your options files which are not defined as valid for your software. DATEformat, NUMberformat, and TIMEformat have been obsolete specifications since TSM 3.7, when such controls were transferred to locale settings. The Options table may evidence the options, though not even coded in your server options file, apparently by virtue of some legacy server software. Richard Sims On Oct 12, 2009, at 1:33 AM, Grigori Solonovitch wrote: Hello Everybody, I have TSM Server 5.5.3.0 under AIX 5.3. "select * from options" gives: OPTION_NAME: DateFormat OPTION_VALUE: ? OPTION_NAME: TimeFormat OPTION_VALUE: ? OPTION_NAME: NumberFormat OPTION_VALUE: ? I have in dsmserv.opt file: DATEformat 1 TIMEformat 1 NUMberformat 1 I do not know from where we have "?" in TSM Server table. What is this?
Re: instrumentation for the server?
Go to the link in my sig and do a search on: performance tuning information 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/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" wrote on 10/12/2009 07:58:58 AM: > [image removed] > > instrumentation for the server? > > km > > to: > > ADSM-L > > 10/12/2009 08:05 AM > > Sent by: > > "ADSM: Dist Stor Manager" > > Please respond to "ADSM: Dist Stor Manager" > > Hello, > > I am currently analyzing a TSM server which uses 100% CPU on 4 cores > when doing client backups. Almost all of it is privileged times, but > there are very few IO's and low disk queues for both stgpools, db and log. > > Are there any trace flags similar to the client testflag instrument:detail > but for the server that will allow me to see what the server is spending > time on? > > I've been looking in the problem determination guide but cant find any > flag similar to instrument_detail except for 'instr' which isnt documented > and only gives me DB LATCHes. > > -km
Re: snapdiff
Andy, thanks. I'm aware of the official support issue, I'll urge the customer to upgrade the servers to 5.5. On 12 okt 2009, at 14:38, Andrew Raibeck wrote: The "Migrating from earlier versions" section near the beginning of the client manual discusses the topic of which servers are supported with the 5.5 client (5.5 or 6.1). Alternatively see http://www.ibm.com/support/docview.wss?uid=swg21053218 In theory the SnapDiff functionality should work with a 5.4 server (we are not aware of any feature-wise limitations in this regard). However, as the above item will indicate, 6.1 client and 5.4 server is not an officially supported configuration. 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/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" wrote on 10/12/2009 06:46:53 AM: [image removed] Re: snapdiff Remco Post to: ADSM-L 10/12/2009 06:47 AM Sent by: "ADSM: Dist Stor Manager" Please respond to "ADSM: Dist Stor Manager" On 12 okt 2009, at 12:36, Grigori Solonovitch wrote: Have you tried to search in Internet? For example: http://www-01.ibm.com/support/docview.wss? rs=663&context=SSGSG7&uid=swg21392122&loc=en_US&cs=UTF-8&lang=en Where does this document list TSM server level requirements? I've searched the TSM client manual, the TSM wiki and whatever google could turn up. Since google reported that some people were actually experimenting with snapdiff, I'd thought to ask the list as well Hi All, I'm currently looking into the snapdiff feature of the TSM 6.1 client. My customer is still running TSM server version 5.4, so I was looking into the requirements for using the 6.1 client and the snapdiff feature. Does anyone know if there is any dependancy on a specific server version to be able to use the snapdiff feature? -- Met vriendelijke groeten/Kind regards, Remco Post r.p...@plcs.nl -- Met vriendelijke groeten/Kind regards, Remco Post r.p...@plcs.nl
Re: Date, time and number format
Our TSM Server was upgraded from previous versions many times, so maybe it is coming from there. According to dsmserv.opt.smp in TSM 6.1.2 DATEFORMAT, TIMEFORMAT and NUMBERFORMAT are still used for z/OS. Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Monday, October 12, 2009 3:41 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Date, time and number format You should not add things to your options files which are not defined as valid for your software. DATEformat, NUMberformat, and TIMEformat have been obsolete specifications since TSM 3.7, when such controls were transferred to locale settings. The Options table may evidence the options, though not even coded in your server options file, apparently by virtue of some legacy server software. Richard Sims On Oct 12, 2009, at 1:33 AM, Grigori Solonovitch wrote: > Hello Everybody, > > I have TSM Server 5.5.3.0 under AIX 5.3. > > "select * from options" gives: > > OPTION_NAME: DateFormat > OPTION_VALUE: ? > > OPTION_NAME: TimeFormat > OPTION_VALUE: ? > > OPTION_NAME: NumberFormat > OPTION_VALUE: ? > > I have in dsmserv.opt file: > > DATEformat 1 > TIMEformat 1 > NUMberformat 1 > > I do not know from where we have "?" in TSM Server table. > What is this? Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
Re: snapdiff
-Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Remco Post Sent: Monday, October 12, 2009 8:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] snapdiff Andy, A teammate successfully implemented snapdiff in our storage environment. He used the 6.1 client with our TSM servers running on 5.5.1.0; his setup works flawlessly. He will be presenting on snapdiff at the next TSMUG. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com thanks. I'm aware of the official support issue, I'll urge the customer to upgrade the servers to 5.5. On 12 okt 2009, at 14:38, Andrew Raibeck wrote: > The "Migrating from earlier versions" section near the beginning of > the client manual discusses the topic of which servers are supported > with the > 5.5 client (5.5 or 6.1). Alternatively see > http://www.ibm.com/support/docview.wss?uid=swg21053218 > > In theory the SnapDiff functionality should work with a 5.4 server (we > are not aware of any feature-wise limitations in this regard). > However, as the above item will indicate, 6.1 client and 5.4 server is > not an officially supported configuration. > > 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/i...@ibmus Internet > e-mail: stor...@us.ibm.com > > IBM Tivoli Storage Manager support web page: > http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageM > anager.html > > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > "ADSM: Dist Stor Manager" wrote on 10/12/2009 > 06:46:53 AM: > >> [image removed] >> >> Re: snapdiff >> >> Remco Post >> >> to: >> >> ADSM-L >> >> 10/12/2009 06:47 AM >> >> Sent by: >> >> "ADSM: Dist Stor Manager" >> >> Please respond to "ADSM: Dist Stor Manager" >> >> On 12 okt 2009, at 12:36, Grigori Solonovitch wrote: >> >>> Have you tried to search in Internet? >>> >>> For example: >>> >>> http://www-01.ibm.com/support/docview.wss? >> rs=663&context=SSGSG7&uid=swg21392122&loc=en_US&cs=UTF-8&lang=en >>> >>> >> >> Where does this document list TSM server level requirements? I've >> searched the TSM client manual, the TSM wiki and whatever google >> could turn up. Since google reported that some people were actually >> experimenting with snapdiff, I'd thought to ask the list as well >>> >>> >>> Hi All, >>> >>> >>> >>> I'm currently looking into the snapdiff feature of the TSM 6.1 >>> client. >>> >>> My customer is still running TSM server version 5.4, so I was >>> looking >>> >>> into the requirements for using the 6.1 client and the snapdiff >>> >>> feature. Does anyone know if there is any dependancy on a specific >>> >>> server version to be able to use the snapdiff feature? >>> >> >> -- >> Met vriendelijke groeten/Kind regards, >> >> Remco Post >> r.p...@plcs.nl -- Met vriendelijke groeten/Kind regards, Remco Post r.p...@plcs.nl IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
Re: instrumentation for the server?
Yeah, I'm leaning towards memory or maybe network right now. I'm seeing some of these during client backups: ANR0132E smnode.c(27085): Memory allocation failed: object sessP->qryBuf, size 1048576. (SESSION: 5518) This is on a win32 system so 2GB mem is max. I'll try reducing the bufpool to give TSM some more of those gigs and doing some instrumentation for tonights backups. -km On 12/10, Lindsay Morris wrote: > I once saw this when we had set BUFPOOLSIZE way too high.Giving the TSM > server lots of memory starved the OS for memory; things slowed down horribly > until we set BUFPOOLSIZE back to the Performance-tuning-guide > recommendations ( I forget - 1/4 of available memory?) > > > On Mon, Oct 12, 2009 at 7:58 AM, km wrote: > > > Hello, > > > > I am currently analyzing a TSM server which uses 100% CPU on 4 cores > > when doing client backups. Almost all of it is privileged times, but > > there are very few IO's and low disk queues for both stgpools, db and log. > > > > Are there any trace flags similar to the client testflag instrument:detail > > but for the server that will allow me to see what the server is spending > > time on? > > > > I've been looking in the problem determination guide but cant find any > > flag similar to instrument_detail except for 'instr' which isnt documented > > and only gives me DB LATCHes. > > > > -km > > > > > > -- > Lindsay Morris > Principal > TSMworks > Tel. 1-859-539-9900 > lind...@tsmworks.com
Re: instrumentation for the server?
Thank you. I had forgotten that instrumentation was implemented as its own command. On 12/10, Andrew Raibeck wrote: > Go to the link in my sig and do a search on: > >performance tuning information > > 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/i...@ibmus > Internet e-mail: stor...@us.ibm.com > > IBM Tivoli Storage Manager support web page: > http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html > > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > "ADSM: Dist Stor Manager" wrote on 10/12/2009 > 07:58:58 AM: > > > [image removed] > > > > instrumentation for the server? > > > > km > > > > to: > > > > ADSM-L > > > > 10/12/2009 08:05 AM > > > > Sent by: > > > > "ADSM: Dist Stor Manager" > > > > Please respond to "ADSM: Dist Stor Manager" > > > > Hello, > > > > I am currently analyzing a TSM server which uses 100% CPU on 4 cores > > when doing client backups. Almost all of it is privileged times, but > > there are very few IO's and low disk queues for both stgpools, db and > log. > > > > Are there any trace flags similar to the client testflag > instrument:detail > > but for the server that will allow me to see what the server is spending > > time on? > > > > I've been looking in the problem determination guide but cant find any > > flag similar to instrument_detail except for 'instr' which isnt > documented > > and only gives me DB LATCHes. > > > > -km
How to backup open log files in exchange
Hello all, I have to configure TSM backup for Microsoft exchange server.The problem is that TSM BAC client is unable to backup open files and the mail admin requires these files to be backed up anyway.According to him, all log files , whcih are always open are needed for recovery.So , my question is that , do we have anyway through which we can backup open files in exchange? Thanks in advance for your reply. -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853
Re: How to backup open log files in exchange
HEllo, you can't backup database files or other files that change during processing with the normal client. For that you need an application specific client, called a TDP in the TSM world, that can backup the application via it's supported backup API. For Exchange, please see: http://www-01.ibm.com/software/tivoli/products/storage-mgr-mail/ -km On 12/10, ashish sharma wrote: > Hello all, > > I have to configure TSM backup for Microsoft exchange server.The problem is > that TSM BAC client is unable to backup open files and the mail admin > requires these files to be backed up anyway.According to him, all log files > , whcih are always open are needed for recovery.So , my question is that , > do we have anyway through which we can backup open files in exchange? > > Thanks in advance for your reply. > > -- > Best Regards > Ashish Sharma > ST Microelectronics Ltd. > 919717003853
Re: How to backup open log files in exchange
Ashish, Changing the serialization parameter in your backup copygroup definition from shrstatic or static to shrdynamic or dynamic will force TSM to backup open files; HOWEVER, there is no guarantee that you will be able to make use of the backed up open files in the case of restore. You should NOT backup exchange with the regular Baclient. You could make of use of Tivoli Data Protection for Exchange or FastBack to backup Exchange. Both products require a license. Look at the following site for TDP for Exchange http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp under Storage Manager for Mail >> Data Protection for Microsoft Exchange Server Installation BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ashish sharma Sent: Monday, October 12, 2009 9:25 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] How to backup open log files in exchange Hello all, I have to configure TSM backup for Microsoft exchange server.The problem is that TSM BAC client is unable to backup open files and the mail admin requires these files to be backed up anyway.According to him, all log files , whcih are always open are needed for recovery.So , my question is that , do we have anyway through which we can backup open files in exchange? Thanks in advance for your reply. -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853 IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
Re: TSM 5.4 or 6.1
Compromise: Go to TSM 5.5 and use the 5.4 client on older machines. TSM 6.1 from what I'm hearing, isn't exactly an environment I'd want to go to at the moment. And, you can, as Wanda has said, use the 6.1 clients where it makes sense to. See Ya' Howard > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf > Of Mehdi Salehi > Sent: Saturday, October 10, 2009 8:05 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] TSM 5.4 or 6.1 > > One of our customers is planning to buy TSM for their AIX 5.2 systems. > The > problem is that the newest version of TSM what supports AIX 5.2 is TSM > 5.4. > Two solutions: > - upgrade AIX systems to 5.3 or 6.1 > - forget about TSM 6.1 and use TSM 5.4 > You know the application side people are unwilling to move their > environment. I am looking for convincing highlights to motivate them to > upgrade their operating systems instead of downgrading TSM side. What > features of TSM 6.1 do you think could be interesting from executive's > point > of view?
Re: snapdiff
Hi all, for information, I've implemented snapdiff but in a TSM v6.1 only environment (client and server) and we're going on production. There are a couple of limitations and requirements (for ex. the ntfs support only, the UTF8 page code, the permissions on the filer ...etc.) that you should be careful and nothing is clearly documented ... but when it works, it works fine! Be aware that you'll have to be using latest version of Ontap (7.3.1.x). Thanks, ___ Olivier LEVAN, Infrastructure IT Specialist IBM Global Technology Services 227 - 11TH Avenue SW CALGARY AB T2R 1R9 Tel.: (403) 539-3782 Fax: (845) 559-6763 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Remco Post Sent: Monday, October 12, 2009 8:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] snapdiff Andy, A teammate successfully implemented snapdiff in our storage environment. He used the 6.1 client with our TSM servers running on 5.5.1.0; his setup works flawlessly. He will be presenting on snapdiff at the next TSMUG. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com thanks. I'm aware of the official support issue, I'll urge the customer to upgrade the servers to 5.5. On 12 okt 2009, at 14:38, Andrew Raibeck wrote: > The "Migrating from earlier versions" section near the beginning of > the client manual discusses the topic of which servers are supported > with the > 5.5 client (5.5 or 6.1). Alternatively see > http://www.ibm.com/support/docview.wss?uid=swg21053218 > > In theory the SnapDiff functionality should work with a 5.4 server (we > are not aware of any feature-wise limitations in this regard). > However, as the above item will indicate, 6.1 client and 5.4 server is > not an officially supported configuration. > > 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/i...@ibmus Internet > e-mail: stor...@us.ibm.com > > IBM Tivoli Storage Manager support web page: > http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageM > anager.html > > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > "ADSM: Dist Stor Manager" wrote on 10/12/2009 > 06:46:53 AM: > >> [image removed] >> >> Re: snapdiff >> >> Remco Post >> >> to: >> >> ADSM-L >> >> 10/12/2009 06:47 AM >> >> Sent by: >> >> "ADSM: Dist Stor Manager" >> >> Please respond to "ADSM: Dist Stor Manager" >> >> On 12 okt 2009, at 12:36, Grigori Solonovitch wrote: >> >>> Have you tried to search in Internet? >>> >>> For example: >>> >>> http://www-01.ibm.com/support/docview.wss? >> rs=663&context=SSGSG7&uid=swg21392122&loc=en_US&cs=UTF-8&lang=en >>> >>> >> >> Where does this document list TSM server level requirements? I've >> searched the TSM client manual, the TSM wiki and whatever google >> could turn up. Since google reported that some people were actually >> experimenting with snapdiff, I'd thought to ask the list as well >>> >>> >>> Hi All, >>> >>> >>> >>> I'm currently looking into the snapdiff feature of the TSM 6.1 >>> client. >>> >>> My customer is still running TSM server version 5.4, so I was >>> looking >>> >>> into the requirements for using the 6.1 client and the snapdiff >>> >>> feature. Does anyone know if there is any dependancy on a specific >>> >>> server version to be able to use the snapdiff feature? >>> >> >> -- >> Met vriendelijke groeten/Kind regards, >> >> Remco Post >> r.p...@plcs.nl -- Met vriendelijke groeten/Kind regards, Remco Post r.p...@plcs.nl
Migration for Windows-based installation
All, We have a TSM server that's running out of steam, and nearing the end of its expected reliable life. We have Version 5, Release 3, Level 4.6 installed, with various levels of clients installed on our servers. The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow PATA, and the OS is Win2k Pro. Definitely not ideal. The tape robot is a Spectralogic T50, with two LTO3 drives and 25 slots, out of which we expect to get much more life. We expect to replace the server with a new Dell server with 3tb of SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. I'd like to get to the newest in the 5.x series on the new server, since the talk on this list about moving to 6.x indicates to me that we'd be better off staying at 5.x for now. I've been casting about, and can't seem to find documentation on how to migrate the setup to the new machine. Does anyone have a pointer to good documentation on doing this? Frankly, we've been given a quote by a VAR, and though the number of hours they are quoting seem reasonable, the price they're asking to work with us on this is beyond our budget. Thanks Kurt
Re: Migration for Windows-based installation
Are you looking purely at a lift and shift hardware change here, or at a clean installation of TSM Server (at 5.5.3 for example) and migrating clients into the new instance? Cheers, /David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: 12 October 2009 18:54 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Migration for Windows-based installation All, We have a TSM server that's running out of steam, and nearing the end of its expected reliable life. We have Version 5, Release 3, Level 4.6 installed, with various levels of clients installed on our servers. The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow PATA, and the OS is Win2k Pro. Definitely not ideal. The tape robot is a Spectralogic T50, with two LTO3 drives and 25 slots, out of which we expect to get much more life. We expect to replace the server with a new Dell server with 3tb of SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. I'd like to get to the newest in the 5.x series on the new server, since the talk on this list about moving to 6.x indicates to me that we'd be better off staying at 5.x for now. I've been casting about, and can't seem to find documentation on how to migrate the setup to the new machine. Does anyone have a pointer to good documentation on doing this? Frankly, we've been given a quote by a VAR, and though the number of hours they are quoting seem reasonable, the price they're asking to work with us on this is beyond our budget. Thanks Kurt No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.421 / Virus Database: 270.14.3/2415 - Release Date: 10/12/09 04:01:00
Re: snapdiff
On 12 okt 2009, at 19:13, Olivier Levan wrote: Hi all, for information, I've implemented snapdiff but in a TSM v6.1 only environment (client and server) and we're going on production. There are a couple of limitations and requirements (for ex. the ntfs support only, the UTF8 page code, the permissions on the filer ...etc.) that you should be careful and nothing is clearly documented ... but when it works, it works fine! On the TSM wiki I found a powerpoint on new client features. This is quite informative on the issues that you mention. Be aware that you'll have to be using latest version of Ontap (7.3.1.x). I know, that's another issue in my plan. Thanks, -- Met vriendelijke groeten, Remco Post r.p...@plcs.nl +31 6 248 21 622
BA Client error - CreateFile() returned '5'
Hello everyone, I am trying to track down a client backup error. TSM Server 5.5.1, AIX 5.3.0.0 TSM ba Client 5.5.1.0, Win2K3 R2 SP2 - The server is part of an HP Polyserver cluster. We have excluded the Polyserve related mountpoints. We have not edited the registry. I am trying to figure out if the error I see is caused by the same root problem as mentioned in IC 56269. My error: 10/12/2009 00:12:04 ANS5250E An unexpected error was encountered. TSM function name : NTSecurityReadV2 TSM function : CreateFile() returned '5' for file 'C:\WINDOWS\microsoft.net\Framework64\v2.0.50727\CONFIG\security.config. cch.6528.2904562' -- - IC 56269 describes this error - "The TSM Backup-Archive client reports the following error during backup in some cases: ANS1228E Sending of object 'filename' failed ANS4007E Error processing 'filename': access to the object is denied In this case, the error happened on all objects when backing up a EMC NAS share mounted in read-only mode through CIFS." -- This error message is different. The file is not a CIFS share, but in on the C: drive. However, the details of IC56269 describe a problem with the value for dwDesiredAccess that is passed to the MS API function "CreateFile()". The value TSM uses is for a Read/Write operation, could result in CreateFile() returning an access denied error incorrectly. MS recommends a different value that only request Read access. -- ?? Is this the same issue, or should I open a case with IBM? George Huebschman Legg Mason IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
Re: Migration for Windows-based installation
I'd prefer to be able to migrate server data as much as possible, including the diskpool, but if it it would be an incredibly difficult maneuver (or take inordinate amounts of time, say on the order of more than a 4-day weekend) and/or the downside of losing the diskpool is relatively minor, I could potentially live without it. I would also contemplate keeping the current TSM server version on the new machine and upgrading immediately after implementation if that would be of benefit. We back up fewer than 10 servers, but one is our Exchange 2003 server at roughly 200gb and is a full backup every night, and the other is our file server at over 2tb, though on a nightly basis it normally does around 25-50gb. Does that answer your question? Kurt On Mon, Oct 12, 2009 at 11:18, David McClelland wrote: > Are you looking purely at a lift and shift hardware change here, or at a > clean installation of TSM Server (at 5.5.3 for example) and migrating clients > into the new instance? > > Cheers, > > /David Mc > London, UK > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt > Buff > Sent: 12 October 2009 18:54 > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Migration for Windows-based installation > > All, > > We have a TSM server that's running out of steam, and nearing the end > of its expected reliable life. We have Version 5, Release 3, Level 4.6 > installed, with various levels of clients installed on our servers. > The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow > PATA, and the OS is Win2k Pro. Definitely not ideal. > > The tape robot is a Spectralogic T50, with two LTO3 drives and 25 > slots, out of which we expect to get much more life. > > We expect to replace the server with a new Dell server with 3tb of > SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. > > I'd like to get to the newest in the 5.x series on the new server, > since the talk on this list about moving to 6.x indicates to me that > we'd be better off staying at 5.x for now. > > I've been casting about, and can't seem to find documentation on how > to migrate the setup to the new machine. > > Does anyone have a pointer to good documentation on doing this? > > Frankly, we've been given a quote by a VAR, and though the number of > hours they are quoting seem reasonable, the price they're asking to > work with us on this is beyond our budget. > > Thanks > > Kurt > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.421 / Virus Database: 270.14.3/2415 - Release Date: 10/12/09 > 04:01:00 >
Re: Migration for Windows-based installation
Start from scratch. Install TSM at the level you would like, move and configure the library. Point the clients at the new server and go. That first backup will necessarily be a full. Will take longer than usual, but easy. This method allows you go "clean up" your database. Keep the old server around until the data expires. Clearly, there are more details, especially since you are going to re-use the library on the new STORServer (oops, I mean TSM Server). The overall concept is sound. For sites of your size I like this method as it is simple and gets me a brand new, pristine database. This will become important next year when you migrate to TSM 6.2. Besides, a clean start is always a good thing. This topic has been covered earlier and in much more detail. You might peruse the archives to see what you can find. My name will show up along with others like Wanda who have been through this many times. Thanks, Kelly Lipp Chief Technical Officer www.storserver.com 719-266-8777 x7105 STORServer solves your data backup challenges. Once and for all. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: Monday, October 12, 2009 1:02 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migration for Windows-based installation I'd prefer to be able to migrate server data as much as possible, including the diskpool, but if it it would be an incredibly difficult maneuver (or take inordinate amounts of time, say on the order of more than a 4-day weekend) and/or the downside of losing the diskpool is relatively minor, I could potentially live without it. I would also contemplate keeping the current TSM server version on the new machine and upgrading immediately after implementation if that would be of benefit. We back up fewer than 10 servers, but one is our Exchange 2003 server at roughly 200gb and is a full backup every night, and the other is our file server at over 2tb, though on a nightly basis it normally does around 25-50gb. Does that answer your question? Kurt On Mon, Oct 12, 2009 at 11:18, David McClelland wrote: > Are you looking purely at a lift and shift hardware change here, or at a > clean installation of TSM Server (at 5.5.3 for example) and migrating clients > into the new instance? > > Cheers, > > /David Mc > London, UK > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt > Buff > Sent: 12 October 2009 18:54 > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Migration for Windows-based installation > > All, > > We have a TSM server that's running out of steam, and nearing the end > of its expected reliable life. We have Version 5, Release 3, Level 4.6 > installed, with various levels of clients installed on our servers. > The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow > PATA, and the OS is Win2k Pro. Definitely not ideal. > > The tape robot is a Spectralogic T50, with two LTO3 drives and 25 > slots, out of which we expect to get much more life. > > We expect to replace the server with a new Dell server with 3tb of > SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. > > I'd like to get to the newest in the 5.x series on the new server, > since the talk on this list about moving to 6.x indicates to me that > we'd be better off staying at 5.x for now. > > I've been casting about, and can't seem to find documentation on how > to migrate the setup to the new machine. > > Does anyone have a pointer to good documentation on doing this? > > Frankly, we've been given a quote by a VAR, and though the number of > hours they are quoting seem reasonable, the price they're asking to > work with us on this is beyond our budget. > > Thanks > > Kurt > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.421 / Virus Database: 270.14.3/2415 - Release Date: 10/12/09 > 04:01:00 >
Re: BA Client error - CreateFile() returned '5'
Hello, I encountered the same problem a while ago. Searching for "security.config.cch backup" with Google shows that this is a common problem. I suspect that these files are locked or have even been deleted while locked/in use by another process. As per Microsoft Knowledge Base, "The files that have the extension .cch are dynamically generated and do not have to be backed up or restored." http://support.microsoft.com/default.aspx?scid=kb;en-us;815168 Rainer Schöpf On Mon, 12 Oct 2009 at 14:31 -0400, Huebschman, George J. wrote: > Hello everyone, I am trying to track down a client backup error. > > TSM Server 5.5.1, AIX 5.3.0.0 > TSM ba Client 5.5.1.0, Win2K3 R2 SP2 - The server is part of an HP > Polyserver cluster. We have excluded the Polyserve related mountpoints. > We have not edited the registry. > > I am trying to figure out if the error I see is caused by the > same root problem as mentioned in IC 56269. > My error: > 10/12/2009 00:12:04 ANS5250E An unexpected error was > encountered. >TSM function name : NTSecurityReadV2 >TSM function : CreateFile() returned '5' for file > 'C:\WINDOWS\microsoft.net\Framework64\v2.0.50727\CONFIG\security.config. > cch.6528.2904562' > > -- > > - IC 56269 describes this error - > "The TSM Backup-Archive client reports the following error during > backup in some cases: > ANS1228E Sending of object 'filename' failed > ANS4007E Error processing 'filename': access to the object is > denied > In this case, the error happened on all objects when backing up > a EMC NAS share mounted in read-only mode through CIFS." > > -- > > This error message is different. > The file is not a CIFS share, but in on the C: drive. > > However, the details of IC56269 describe a problem with the value for > dwDesiredAccess that is passed to the MS API function "CreateFile()". > The value TSM uses is for a Read/Write operation, could result in > CreateFile() returning an > access denied error incorrectly. MS recommends a different value that > only request Read access. > > -- > > > ?? Is this the same issue, or should I open a case with IBM? > > George Huebschman > Legg Mason > > IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason > therefore recommends that you do not send any confidential or sensitive > information to us via electronic mail, including social security numbers, > account numbers, or personal identification numbers. Delivery, and or timely > delivery of Internet mail is not guaranteed. Legg Mason therefore recommends > that you do not send time sensitive > or action-oriented messages to us via electronic mail. > > This message is intended for the addressee only and may contain privileged > or confidential information. Unless you are the intended recipient, you may > not use, copy or disclose to anyone any information contained in this > message. If you have received this message in error, please notify the > author by replying to this message and then kindly delete the message. Thank > you. >
Re: Migration for Windows-based installation
So, what happens to all the tapes I have offsite at Iron Mountain, and the archives I have stored in my basement vault, etc. I'll be perusing the archives as you suggest, but this isn't exactly crystalline to me just yet. A complicating factor that I hadn't realized until I did a bit of digging just now is that the current database holds references to a *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that we migrated from some years ago. Would the procedure you're suggesting clean that up? Kurt On Mon, Oct 12, 2009 at 12:10, Kelly Lipp wrote: > Start from scratch. Install TSM at the level you would like, move and > configure the library. Point the clients at the new server and go. That > first backup will necessarily be a full. Will take longer than usual, but > easy. > > This method allows you go "clean up" your database. > > Keep the old server around until the data expires. > > Clearly, there are more details, especially since you are going to re-use the > library on the new STORServer (oops, I mean TSM Server). The overall concept > is sound. For sites of your size I like this method as it is simple and gets > me a brand new, pristine database. This will become important next year when > you migrate to TSM 6.2. Besides, a clean start is always a good thing. > > This topic has been covered earlier and in much more detail. You might > peruse the archives to see what you can find. My name will show up along > with others like Wanda who have been through this many times. > > Thanks, > > Kelly Lipp > Chief Technical Officer > www.storserver.com > 719-266-8777 x7105 > STORServer solves your data backup challenges. > Once and for all. > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt > Buff > Sent: Monday, October 12, 2009 1:02 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Migration for Windows-based installation > > I'd prefer to be able to migrate server data as much as possible, > including the diskpool, but if it it would be an incredibly difficult > maneuver (or take inordinate amounts of time, say on the order of more > than a 4-day weekend) and/or the downside of losing the diskpool is > relatively minor, I could potentially live without it. > > I would also contemplate keeping the current TSM server version on the > new machine and upgrading immediately after implementation if that > would be of benefit. > > We back up fewer than 10 servers, but one is our Exchange 2003 server > at roughly 200gb and is a full backup every night, and the other is > our file server at over 2tb, though on a nightly basis it normally > does around 25-50gb. > > Does that answer your question? > > Kurt > > On Mon, Oct 12, 2009 at 11:18, David McClelland wrote: >> Are you looking purely at a lift and shift hardware change here, or at a >> clean installation of TSM Server (at 5.5.3 for example) and migrating >> clients into the new instance? >> >> Cheers, >> >> /David Mc >> London, UK >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >> Kurt Buff >> Sent: 12 October 2009 18:54 >> To: ADSM-L@VM.MARIST.EDU >> Subject: [ADSM-L] Migration for Windows-based installation >> >> All, >> >> We have a TSM server that's running out of steam, and nearing the end >> of its expected reliable life. We have Version 5, Release 3, Level 4.6 >> installed, with various levels of clients installed on our servers. >> The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow >> PATA, and the OS is Win2k Pro. Definitely not ideal. >> >> The tape robot is a Spectralogic T50, with two LTO3 drives and 25 >> slots, out of which we expect to get much more life. >> >> We expect to replace the server with a new Dell server with 3tb of >> SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. >> >> I'd like to get to the newest in the 5.x series on the new server, >> since the talk on this list about moving to 6.x indicates to me that >> we'd be better off staying at 5.x for now. >> >> I've been casting about, and can't seem to find documentation on how >> to migrate the setup to the new machine. >> >> Does anyone have a pointer to good documentation on doing this? >> >> Frankly, we've been given a quote by a VAR, and though the number of >> hours they are quoting seem reasonable, the price they're asking to >> work with us on this is beyond our budget. >> >> Thanks >> >> Kurt >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 8.5.421 / Virus Database: 270.14.3/2415 - Release Date: 10/12/09 >> 04:01:00 >> >
Re: Migration for Windows-based installation
Okay, another fun question for you Kurt, investigating some alternative lines of simply migrating your current TSM server instance to new hardware: is the disk upon which your current TSM database/recovery log/storage pool live internal to your old server, or is it instead hosted upon external disk and thus (potentially) relatively feasible to 'introduce' to your new hardware? /DMc -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: 12 October 2009 21:09 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migration for Windows-based installation So, what happens to all the tapes I have offsite at Iron Mountain, and the archives I have stored in my basement vault, etc. I'll be perusing the archives as you suggest, but this isn't exactly crystalline to me just yet. A complicating factor that I hadn't realized until I did a bit of digging just now is that the current database holds references to a *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that we migrated from some years ago. Would the procedure you're suggesting clean that up? Kurt On Mon, Oct 12, 2009 at 12:10, Kelly Lipp wrote: > Start from scratch. Install TSM at the level you would like, move and > configure the library. Point the clients at the new server and go. That > first backup will necessarily be a full. Will take longer than usual, but > easy. > > This method allows you go "clean up" your database. > > Keep the old server around until the data expires. > > Clearly, there are more details, especially since you are going to re-use the > library on the new STORServer (oops, I mean TSM Server). The overall concept > is sound. For sites of your size I like this method as it is simple and gets > me a brand new, pristine database. This will become important next year when > you migrate to TSM 6.2. Besides, a clean start is always a good thing. > > This topic has been covered earlier and in much more detail. You might > peruse the archives to see what you can find. My name will show up along > with others like Wanda who have been through this many times. > > Thanks, > > Kelly Lipp > Chief Technical Officer > www.storserver.com > 719-266-8777 x7105 > STORServer solves your data backup challenges. > Once and for all. > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt > Buff > Sent: Monday, October 12, 2009 1:02 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Migration for Windows-based installation > > I'd prefer to be able to migrate server data as much as possible, > including the diskpool, but if it it would be an incredibly difficult > maneuver (or take inordinate amounts of time, say on the order of more > than a 4-day weekend) and/or the downside of losing the diskpool is > relatively minor, I could potentially live without it. > > I would also contemplate keeping the current TSM server version on the > new machine and upgrading immediately after implementation if that > would be of benefit. > > We back up fewer than 10 servers, but one is our Exchange 2003 server > at roughly 200gb and is a full backup every night, and the other is > our file server at over 2tb, though on a nightly basis it normally > does around 25-50gb. > > Does that answer your question? > > Kurt > > On Mon, Oct 12, 2009 at 11:18, David McClelland wrote: >> Are you looking purely at a lift and shift hardware change here, or at a >> clean installation of TSM Server (at 5.5.3 for example) and migrating >> clients into the new instance? >> >> Cheers, >> >> /David Mc >> London, UK >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >> Kurt Buff >> Sent: 12 October 2009 18:54 >> To: ADSM-L@VM.MARIST.EDU >> Subject: [ADSM-L] Migration for Windows-based installation >> >> All, >> >> We have a TSM server that's running out of steam, and nearing the end >> of its expected reliable life. We have Version 5, Release 3, Level 4.6 >> installed, with various levels of clients installed on our servers. >> The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow >> PATA, and the OS is Win2k Pro. Definitely not ideal. >> >> The tape robot is a Spectralogic T50, with two LTO3 drives and 25 >> slots, out of which we expect to get much more life. >> >> We expect to replace the server with a new Dell server with 3tb of >> SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. >> >> I'd like to get to the newest in the 5.x series on the new server, >> since the talk on this list about moving to 6.x indicates to me that >> we'd be better off staying at 5.x for now. >> >> I've been casting about, and can't seem to find documentation on how >> to migrate the setup to the new machine. >> >> Does anyone have a pointer to good documentation on doing this? >> >> Frankly, we've been given a quote by a VAR, and though the number of >> hours the
Re: Migration for Windows-based installation
When we migrated to a new server and LTO4 from LTO1, we installed all of the new stuff and tested the hardware with the TSM version we were running. When that was working well, we drained all of the disk pools, backed up the database from the existing server, shut it down, attached the old tape drives to the new server, restored the database, brought it up, deleted all of the old disk pools, defined new disk pools for the new hardware, defined the new tape drives, set up new devclasses and storage pools, changed the domains to point to the new devices and migration hierarchy, tested backups and restores, and set up move data jobs to move data from the LTO1's back to disk pools where it would then migrate to the new LTO4s. Once the LTO1's were empty, we detached the library and recycled the old tapes. The upgrade to a newer TSM could occur on the old server or the new, but best probably not at the same time as the hardware cutover. Starting from scratch was not an option for us as we have files with multi-year retentions. Bob. PS - If you have references to tapes that no longer exist, there are methods (google is your friend) to delete references to them. The method of deletion may depend on how the data was stored (primary/copypool/backupset/db backup/other). Once the references are gone, you should delete the storage pools and device classes that are obsolete. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: Monday, October 12, 2009 3:09 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migration for Windows-based installation So, what happens to all the tapes I have offsite at Iron Mountain, and the archives I have stored in my basement vault, etc. I'll be perusing the archives as you suggest, but this isn't exactly crystalline to me just yet. A complicating factor that I hadn't realized until I did a bit of digging just now is that the current database holds references to a *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that we migrated from some years ago. Would the procedure you're suggesting clean that up? Kurt On Mon, Oct 12, 2009 at 12:10, Kelly Lipp wrote: > Start from scratch. Install TSM at the level you would like, move and configure the library. Point the clients at the new server and go. That first backup will necessarily be a full. Will take longer than usual, but easy. > > This method allows you go "clean up" your database. > > Keep the old server around until the data expires. > > Clearly, there are more details, especially since you are going to re-use the library on the new STORServer (oops, I mean TSM Server). The overall concept is sound. For sites of your size I like this method as it is simple and gets me a brand new, pristine database. This will become important next year when you migrate to TSM 6.2. Besides, a clean start is always a good thing. > > This topic has been covered earlier and in much more detail. You might peruse the archives to see what you can find. My name will show up along with others like Wanda who have been through this many times. > > Thanks, > > Kelly Lipp > Chief Technical Officer > www.storserver.com > 719-266-8777 x7105 > STORServer solves your data backup challenges. > Once and for all. > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf > Of Kurt Buff > Sent: Monday, October 12, 2009 1:02 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Migration for Windows-based installation > > I'd prefer to be able to migrate server data as much as possible, > including the diskpool, but if it it would be an incredibly difficult > maneuver (or take inordinate amounts of time, say on the order of more > than a 4-day weekend) and/or the downside of losing the diskpool is > relatively minor, I could potentially live without it. > > I would also contemplate keeping the current TSM server version on the > new machine and upgrading immediately after implementation if that > would be of benefit. > > We back up fewer than 10 servers, but one is our Exchange 2003 server > at roughly 200gb and is a full backup every night, and the other is > our file server at over 2tb, though on a nightly basis it normally > does around 25-50gb. > > Does that answer your question? > > Kurt > > On Mon, Oct 12, 2009 at 11:18, David McClelland wrote: >> Are you looking purely at a lift and shift hardware change here, or at a clean installation of TSM Server (at 5.5.3 for example) and migrating clients into the new instance? >> >> Cheers, >> >> /David Mc >> London, UK >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf >> Of Kurt Buff >> Sent: 12 October 2009 18:54 >> To: ADSM-L@VM.MARIST.EDU >> Subject: [ADSM-L] Migration for Windows-based installation >> >> All, >> >> We have a TSM server that's running out of steam, and nearing the end >> of its expected reliable
Re: Migration for Windows-based installation
Disk for the current TSM server is IDE/PATA in a RAID5 array internal to the machine - though the OS is on a (eep!) single IDE/PATA drive connected to the motherboard. Kurt On Mon, Oct 12, 2009 at 13:19, David McClelland wrote: > Okay, another fun question for you Kurt, investigating some alternative lines > of simply migrating your current TSM server instance to new hardware: is the > disk upon which your current TSM database/recovery log/storage pool live > internal to your old server, or is it instead hosted upon external disk and > thus (potentially) relatively feasible to 'introduce' to your new hardware? > > /DMc > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt > Buff > Sent: 12 October 2009 21:09 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Migration for Windows-based installation > > So, what happens to all the tapes I have offsite at Iron Mountain, and > the archives I have stored in my basement vault, etc. > > I'll be perusing the archives as you suggest, but this isn't exactly > crystalline to me just yet. > > A complicating factor that I hadn't realized until I did a bit of > digging just now is that the current database holds references to a > *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that > we migrated from some years ago. > > Would the procedure you're suggesting clean that up? > > Kurt > > On Mon, Oct 12, 2009 at 12:10, Kelly Lipp wrote: >> Start from scratch. Install TSM at the level you would like, move and >> configure the library. Point the clients at the new server and go. That >> first backup will necessarily be a full. Will take longer than usual, but >> easy. >> >> This method allows you go "clean up" your database. >> >> Keep the old server around until the data expires. >> >> Clearly, there are more details, especially since you are going to re-use >> the library on the new STORServer (oops, I mean TSM Server). The overall >> concept is sound. For sites of your size I like this method as it is simple >> and gets me a brand new, pristine database. This will become important next >> year when you migrate to TSM 6.2. Besides, a clean start is always a good >> thing. >> >> This topic has been covered earlier and in much more detail. You might >> peruse the archives to see what you can find. My name will show up along >> with others like Wanda who have been through this many times. >> >> Thanks, >> >> Kelly Lipp >> Chief Technical Officer >> www.storserver.com >> 719-266-8777 x7105 >> STORServer solves your data backup challenges. >> Once and for all. >> >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >> Kurt Buff >> Sent: Monday, October 12, 2009 1:02 PM >> To: ADSM-L@VM.MARIST.EDU >> Subject: Re: [ADSM-L] Migration for Windows-based installation >> >> I'd prefer to be able to migrate server data as much as possible, >> including the diskpool, but if it it would be an incredibly difficult >> maneuver (or take inordinate amounts of time, say on the order of more >> than a 4-day weekend) and/or the downside of losing the diskpool is >> relatively minor, I could potentially live without it. >> >> I would also contemplate keeping the current TSM server version on the >> new machine and upgrading immediately after implementation if that >> would be of benefit. >> >> We back up fewer than 10 servers, but one is our Exchange 2003 server >> at roughly 200gb and is a full backup every night, and the other is >> our file server at over 2tb, though on a nightly basis it normally >> does around 25-50gb. >> >> Does that answer your question? >> >> Kurt >> >> On Mon, Oct 12, 2009 at 11:18, David McClelland wrote: >>> Are you looking purely at a lift and shift hardware change here, or at a >>> clean installation of TSM Server (at 5.5.3 for example) and migrating >>> clients into the new instance? >>> >>> Cheers, >>> >>> /David Mc >>> London, UK >>> >>> -Original Message- >>> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >>> Kurt Buff >>> Sent: 12 October 2009 18:54 >>> To: ADSM-L@VM.MARIST.EDU >>> Subject: [ADSM-L] Migration for Windows-based installation >>> >>> All, >>> >>> We have a TSM server that's running out of steam, and nearing the end >>> of its expected reliable life. We have Version 5, Release 3, Level 4.6 >>> installed, with various levels of clients installed on our servers. >>> The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow >>> PATA, and the OS is Win2k Pro. Definitely not ideal. >>> >>> The tape robot is a Spectralogic T50, with two LTO3 drives and 25 >>> slots, out of which we expect to get much more life. >>> >>> We expect to replace the server with a new Dell server with 3tb of >>> SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. >>> >>> I'd like to get to the newest in the 5.x series on the new server, >>> since the talk
Re: Migration for Windows-based installation
For my last migration to new hardware I built a new system and used export/import server to server. Worked very well. Doesn’t work if you have only one library though. However, you are looking for an alternate method. I'd recommend upgrading to TSM 5.5 first. Especially if you run into problems and have to call IBM for support. This is a really simplified step by step. Build your new system: Install the same version of TSm that you have on the old system. On old server: Perform a DB backup to a blank tape. Two for redundancy. Backup volhist. Backup devconfig Take down TSM on your old TSM server Document all tape drive/library information and drivers. Copy db files to the new system, reclog volumes and diskpool volumes. If you are really familiar with TSM you can minimize the amount of diskpool volumes to be copied first. Copy the contents of your server directory to the new system. Verify that your copied dsmserv.dsk file reflects the new location of the DB files and log files. If everything was done correctly and verified properly you should be able to start up your TSM database. Then you will have to redefine your library and drives. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: Monday, October 12, 2009 3:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Migration for Windows-based installation Disk for the current TSM server is IDE/PATA in a RAID5 array internal to the machine - though the OS is on a (eep!) single IDE/PATA drive connected to the motherboard. Kurt On Mon, Oct 12, 2009 at 13:19, David McClelland wrote: > Okay, another fun question for you Kurt, investigating some alternative lines > of simply migrating your current TSM server instance to new hardware: is the > disk upon which your current TSM database/recovery log/storage pool live > internal to your old server, or is it instead hosted upon external disk and > thus (potentially) relatively feasible to 'introduce' to your new hardware? > > /DMc > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt > Buff > Sent: 12 October 2009 21:09 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Migration for Windows-based installation > > So, what happens to all the tapes I have offsite at Iron Mountain, and > the archives I have stored in my basement vault, etc. > > I'll be perusing the archives as you suggest, but this isn't exactly > crystalline to me just yet. > > A complicating factor that I hadn't realized until I did a bit of > digging just now is that the current database holds references to a > *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that > we migrated from some years ago. > > Would the procedure you're suggesting clean that up? > > Kurt > > On Mon, Oct 12, 2009 at 12:10, Kelly Lipp wrote: >> Start from scratch. Install TSM at the level you would like, move and >> configure the library. Point the clients at the new server and go. That >> first backup will necessarily be a full. Will take longer than usual, but >> easy. >> >> This method allows you go "clean up" your database. >> >> Keep the old server around until the data expires. >> >> Clearly, there are more details, especially since you are going to re-use >> the library on the new STORServer (oops, I mean TSM Server). The overall >> concept is sound. For sites of your size I like this method as it is simple >> and gets me a brand new, pristine database. This will become important next >> year when you migrate to TSM 6.2. Besides, a clean start is always a good >> thing. >> >> This topic has been covered earlier and in much more detail. You might >> peruse the archives to see what you can find. My name will show up along >> with others like Wanda who have been through this many times. >> >> Thanks, >> >> Kelly Lipp >> Chief Technical Officer >> www.storserver.com >> 719-266-8777 x7105 >> STORServer solves your data backup challenges. >> Once and for all. >> >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >> Kurt Buff >> Sent: Monday, October 12, 2009 1:02 PM >> To: ADSM-L@VM.MARIST.EDU >> Subject: Re: [ADSM-L] Migration for Windows-based installation >> >> I'd prefer to be able to migrate server data as much as possible, >> including the diskpool, but if it it would be an incredibly difficult >> maneuver (or take inordinate amounts of time, say on the order of more >> than a 4-day weekend) and/or the downside of losing the diskpool is >> relatively minor, I could potentially live without it. >> >> I would also contemplate keeping the current TSM server version on the >> new machine and upgrading immediately after implementation if that >> would be of benefit. >> >> We back up fewer than 10 servers, but one is our Exchange 2003 server >> at roughly 200gb and is a full backup every night, and the other is >> our file server at over 2tb, thou
Re: Migration for Windows-based installation
Yeah, as I dig into this it becomes more complicated. We have a number of pools: Disk Pools: diskpool Sequential Access Storage Pools: ltopool 8mmpool1 (which needs to die) archivepool ltoarchive reclaimpool Copy Storage pools: copypool ltocopy We have several devclasses, too: Disk Device Class Disk File Device Class ReclaimClass 8MM Device Clases 8mmclass1 LTO Device Class LTO The 8mm stuff really needs to go away, I think, especially since Treefrog we had was traded in to get the T50. We also have data that is archived on the LTO tapes, and that we'll need for at least 4 more years - financial stuff, doncha know. Kurt On Mon, Oct 12, 2009 at 13:24, Bob Levad wrote: > When we migrated to a new server and LTO4 from LTO1, we installed all of the > new stuff and tested the hardware with the TSM version we were running. > When that was working well, we drained all of the disk pools, backed up the > database from the existing server, shut it down, attached the old tape > drives to the new server, restored the database, brought it up, deleted all > of the old disk pools, defined new disk pools for the new hardware, defined > the new tape drives, set up new devclasses and storage pools, changed the > domains to point to the new devices and migration hierarchy, tested backups > and restores, and set up move data jobs to move data from the LTO1's back to > disk pools where it would then migrate to the new LTO4s. Once the LTO1's > were empty, we detached the library and recycled the old tapes. The upgrade > to a newer TSM could occur on the old server or the new, but best probably > not at the same time as the hardware cutover. > > Starting from scratch was not an option for us as we have files with > multi-year retentions. > > Bob. > > PS - If you have references to tapes that no longer exist, there are methods > (google is your friend) to delete references to them. The method of > deletion may depend on how the data was stored > (primary/copypool/backupset/db backup/other). Once the references are gone, > you should delete the storage pools and device classes that are obsolete. > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Kurt Buff > Sent: Monday, October 12, 2009 3:09 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Migration for Windows-based installation > > So, what happens to all the tapes I have offsite at Iron Mountain, and the > archives I have stored in my basement vault, etc. > > I'll be perusing the archives as you suggest, but this isn't exactly > crystalline to me just yet. > > A complicating factor that I hadn't realized until I did a bit of digging > just now is that the current database holds references to a > *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that we > migrated from some years ago. > > Would the procedure you're suggesting clean that up? > > Kurt > > On Mon, Oct 12, 2009 at 12:10, Kelly Lipp wrote: >> Start from scratch. Install TSM at the level you would like, move and > configure the library. Point the clients at the new server and go. That > first backup will necessarily be a full. Will take longer than usual, but > easy. >> >> This method allows you go "clean up" your database. >> >> Keep the old server around until the data expires. >> >> Clearly, there are more details, especially since you are going to re-use > the library on the new STORServer (oops, I mean TSM Server). The overall > concept is sound. For sites of your size I like this method as it is simple > and gets me a brand new, pristine database. This will become important next > year when you migrate to TSM 6.2. Besides, a clean start is always a good > thing. >> >> This topic has been covered earlier and in much more detail. You might > peruse the archives to see what you can find. My name will show up along > with others like Wanda who have been through this many times. >> >> Thanks, >> >> Kelly Lipp >> Chief Technical Officer >> www.storserver.com >> 719-266-8777 x7105 >> STORServer solves your data backup challenges. >> Once and for all. >> >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf >> Of Kurt Buff >> Sent: Monday, October 12, 2009 1:02 PM >> To: ADSM-L@VM.MARIST.EDU >> Subject: Re: [ADSM-L] Migration for Windows-based installation >> >> I'd prefer to be able to migrate server data as much as possible, >> including the diskpool, but if it it would be an incredibly difficult >> maneuver (or take inordinate amounts of time, say on the order of more >> than a 4-day weekend) and/or the downside of losing the diskpool is >> relatively minor, I could potentially live without it. >> >> I would also contemplate keeping the current TSM server version on the >> new machine and upgrading immediately after
Re: Migration for Windows-based installation
I'll have to work through a fair amount to understand what you've outlined, but it seems doable. I think pruning volhist and devconfig first might be a good idea, if for no other reason than to cut down on the confusion. Thanks for the input. I'll most likely be back for more information. Kurt On Mon, Oct 12, 2009 at 14:03, Ochs, Duane wrote: > For my last migration to new hardware I built a new system and used > export/import server to server. > Worked very well. Doesn’t work if you have only one library though. > > However, you are looking for an alternate method. > > I'd recommend upgrading to TSM 5.5 first. Especially if you run into problems > and have to call IBM for support. > > > This is a really simplified step by step. > Build your new system: > Install the same version of TSm that you have on the old system. > On old server: > Perform a DB backup to a blank tape. Two for redundancy. > Backup volhist. > Backup devconfig > Take down TSM on your old TSM server > Document all tape drive/library information and drivers. > > Copy db files to the new system, reclog volumes and diskpool volumes. > If you are really familiar with TSM you can minimize the amount of diskpool > volumes to be copied first. > Copy the contents of your server directory to the new system. > > Verify that your copied dsmserv.dsk file reflects the new location of the DB > files and log files. > > If everything was done correctly and verified properly you should be able to > start up your TSM database. > > Then you will have to redefine your library and drives. > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt > Buff > Sent: Monday, October 12, 2009 3:37 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Migration for Windows-based installation > > Disk for the current TSM server is IDE/PATA in a RAID5 array internal > to the machine - though the OS is on a (eep!) single IDE/PATA drive > connected to the motherboard. > > Kurt > > On Mon, Oct 12, 2009 at 13:19, David McClelland wrote: >> Okay, another fun question for you Kurt, investigating some alternative >> lines of simply migrating your current TSM server instance to new hardware: >> is the disk upon which your current TSM database/recovery log/storage pool >> live internal to your old server, or is it instead hosted upon external disk >> and thus (potentially) relatively feasible to 'introduce' to your new >> hardware? >> >> /DMc >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >> Kurt Buff >> Sent: 12 October 2009 21:09 >> To: ADSM-L@VM.MARIST.EDU >> Subject: Re: [ADSM-L] Migration for Windows-based installation >> >> So, what happens to all the tapes I have offsite at Iron Mountain, and >> the archives I have stored in my basement vault, etc. >> >> I'll be perusing the archives as you suggest, but this isn't exactly >> crystalline to me just yet. >> >> A complicating factor that I hadn't realized until I did a bit of >> digging just now is that the current database holds references to a >> *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that >> we migrated from some years ago. >> >> Would the procedure you're suggesting clean that up? >> >> Kurt >> >> On Mon, Oct 12, 2009 at 12:10, Kelly Lipp wrote: >>> Start from scratch. Install TSM at the level you would like, move and >>> configure the library. Point the clients at the new server and go. That >>> first backup will necessarily be a full. Will take longer than usual, but >>> easy. >>> >>> This method allows you go "clean up" your database. >>> >>> Keep the old server around until the data expires. >>> >>> Clearly, there are more details, especially since you are going to re-use >>> the library on the new STORServer (oops, I mean TSM Server). The overall >>> concept is sound. For sites of your size I like this method as it is simple >>> and gets me a brand new, pristine database. This will become important >>> next year when you migrate to TSM 6.2. Besides, a clean start is always a >>> good thing. >>> >>> This topic has been covered earlier and in much more detail. You might >>> peruse the archives to see what you can find. My name will show up along >>> with others like Wanda who have been through this many times. >>> >>> Thanks, >>> >>> Kelly Lipp >>> Chief Technical Officer >>> www.storserver.com >>> 719-266-8777 x7105 >>> STORServer solves your data backup challenges. >>> Once and for all. >>> >>> >>> -Original Message- >>> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >>> Kurt Buff >>> Sent: Monday, October 12, 2009 1:02 PM >>> To: ADSM-L@VM.MARIST.EDU >>> Subject: Re: [ADSM-L] Migration for Windows-based installation >>> >>> I'd prefer to be able to migrate server data as much as possible, >>> including the diskpool, but if it it would be an incredibly difficult >>> maneuver (or take inordinate amounts of time, s
