Re: Sloooow Restore; Problem Fixed; it was network card speed/duplex mismatch
Thanks for everyone's help. Regards, Orin Orin Rehorst * e-mail: [EMAIL PROTECTED] ( Phone: (713)670-2443 7Fax: (713)670-2457 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Leigh Reed Sent: Friday, November 03, 2006 11:46 AM To: ADSM-L@VM.MARIST.EDU Subject: Sloooow Restore Orin, OK, so it's not the same box. I would still try a move nodedata to a disk storage pool for the purpose of eliminating the tape and drive performance. Depending on the occupancy of the TDP node, this could take some time. I assume that you have installed the same version of Baclient and TDP on the temp restore box and that you have copied the opt files and the tdpexc.conf to this box. If you have accepted the default configuration settings regards performance, you may want to revisit these, also you may want to adapt them to suit the resources of this temp h/w (although your problem seems more fundamental than this) Lastly, did you have compression set on the TDP for the backup. When restoring back, the temp machine will need to use CPU resource to uncompress the data. If it is an old machine of low spec it will labour. Do you have compression set on the target NTFS filesystem? Version of Exchange ? Version Baclient? Version of TDP? Leigh
Sloooow Restore
Orin, OK, so it's not the same box. I would still try a move nodedata to a disk storage pool for the purpose of eliminating the tape and drive performance. Depending on the occupancy of the TDP node, this could take some time. I assume that you have installed the same version of Baclient and TDP on the temp restore box and that you have copied the opt files and the tdpexc.conf to this box. If you have accepted the default configuration settings regards performance, you may want to revisit these, also you may want to adapt them to suit the resources of this temp h/w (although your problem seems more fundamental than this) Lastly, did you have compression set on the TDP for the backup. When restoring back, the temp machine will need to use CPU resource to uncompress the data. If it is an old machine of low spec it will labour. Do you have compression set on the target NTFS filesystem? Version of Exchange ? Version Baclient? Version of TDP? Leigh
Re: Sloooow Restore
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orin Rehorst >Whoa. I left a big detail out. This is a restore to a temporary Exchange >server to recover a lost inbox. > >I copied a big file between the TSM server and target. It went quickly, >so I don't think it is a network / NIC issue. Standard Operating Procedure: when you're restoring a large database (which Exchange data resides in), the first part of the restore process is the client machine formatting the space prior to moving data. Until the formatting is done (and it could be quite a while for a large space), no data will move. There have been numerous threads on this list about this pheonomenon with SQL and Oracle database restores. Exchange is no different. (BTW, there has been a thread in the last week here. If you're using a current version of Exchange, you can restore a database to a recovery storage group on your production Exchange server rather than to a temporary server.) -- Mark Stapleton ([EMAIL PROTECTED]) Senior TSM consultant
Re: Sloooow Restore
Whoa. I left a big detail out. This is a restore to a temporary Exchange server to recover a lost inbox. I copied a big file between the TSM server and target. It went quickly, so I don't think it is a network / NIC issue. TIA Orin Rehorst -Original Message- From: Orin Rehorst Sent: Friday, November 03, 2006 9:03 AM To: 'ADSM: Dist Stor Manager' Subject: RE: Slw Restore The system repeats this cycle. It restores about 30 MB in 1 minute 45 seconds. Then "Waiting for TSM server" appears on the client for about 10 seconds. The restore process initially timed out after 80 MB until I bumped the dsmserv.opt parms up (commitimeout to 600 and idletimeout to 45). TIA Orin Rehorst -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stef Coene Sent: Friday, November 03, 2006 8:06 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Slw Restore On Friday 03 November 2006 14:55, Orin Rehorst wrote: > TDP for Exchange backs up at 8 MB per second. > > It restores at 8 MB in 56 seconds! > > What may be wrong? Maybe the SAN Maybe the LAN Maybe the TSM server version Maybe the TSM client version Maybe the tape library Maybe the disk pool Maybe the bits are lost in space More info plz. Stef
Re: Sloooow Restore
I think you probably need to adopt a process of elimination. Firstly, you say that it backs up at 8MBps. You don't mention whether you have 100fdx or GB NIC, but at 100fdx this throughput is OK. Next, are you restoring back to the same server that you have backed up from. If so, this more or less eliminates your target h/w and network settings (apart from the overhead of writing to disk as opposed to reading) If you are restoring back to different h/w then as previously mentioned, check the NIC settings and network. Perhaps perform FTP of a largish file(s) from target server to TSM server. So, assuming you are restoring back to the same H/W from whence your backup was taken, I now assume that your backup was going to diskpool and not exceeding the maxsize threshold of storagepool. If so, why not try to move nodedata from the primary pool tape to the primary pool disk. Make sure you don't have the migration threshold set low. Check the throughput of the move nodedata and then attempt the restore from the diskpool. If thoughput is improved from disk, then try to force the restore from a different drive to eliminate drive from equation. Also run cleaning tape through drive. Attempt move data from primary tape to different tape to eliminate specific tape issue. Have you noticed issues with your migration to tape throughput lately. I guess the key thing is to determine whether you have an across the board throughput issue with your tape operations, or it is indeed localised to this 1 TDP restore. Leigh -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orin Rehorst Sent: 03 November 2006 13:56 To: ADSM-L@VM.MARIST.EDU Subject: [SPAM: 4.000] [ADSM-L] Sloooow Restore TDP for Exchange backs up at 8 MB per second. It restores at 8 MB in 56 seconds! What may be wrong? Environment: OS Win2003, TSM 5.3.2, IBM tape library 3583 LTO 1. TIA Orin Rehorst
Re: Sloooow Restore
It may be worth turning accounting on, and checking the accounting log to see where the delay actually resides. Then focusing your attention on certain components of the infrastructure. _ Ian Smith SAN/TSM Specialist -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orin Rehorst Sent: 03 November 2006 15:03 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Slw Restore The system repeats this cycle. It restores about 30 MB in 1 minute 45 seconds. Then "Waiting for TSM server" appears on the client for about 10 seconds. The restore process initially timed out after 80 MB until I bumped the dsmserv.opt parms up (commitimeout to 600 and idletimeout to 45). TIA Orin Rehorst -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stef Coene Sent: Friday, November 03, 2006 8:06 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Sloooow Restore On Friday 03 November 2006 14:55, Orin Rehorst wrote: > TDP for Exchange backs up at 8 MB per second. > > It restores at 8 MB in 56 seconds! > > What may be wrong? Maybe the SAN Maybe the LAN Maybe the TSM server version Maybe the TSM client version Maybe the tape library Maybe the disk pool Maybe the bits are lost in space More info plz. Stef _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: Sloooow Restore
Had a similar problem with our TDP for exchange..I would start looking at your network adapter. Check duplex settings on adapter.Would stay away from auto-negotiate...Make sure adapter duplex settings are consistent with switch port speed and duplex settings...if everything looks good there, run diagnostics on NIC...In our case it turns on we had a problem with our network adapter. When we went to replace the bad network adapter, another network adapter stopped working and we didn't even touch it. That led us to believe the motherboard was shot. Replaced motherboard, backups were normal again. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orin Rehorst Sent: November 03, 2006 10:03 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Sloooow Restore The system repeats this cycle. It restores about 30 MB in 1 minute 45 seconds. Then "Waiting for TSM server" appears on the client for about 10 seconds. The restore process initially timed out after 80 MB until I bumped the dsmserv.opt parms up (commitimeout to 600 and idletimeout to 45). TIA Orin Rehorst -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stef Coene Sent: Friday, November 03, 2006 8:06 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Slw Restore On Friday 03 November 2006 14:55, Orin Rehorst wrote: > TDP for Exchange backs up at 8 MB per second. > > It restores at 8 MB in 56 seconds! > > What may be wrong? Maybe the SAN Maybe the LAN Maybe the TSM server version Maybe the TSM client version Maybe the tape library Maybe the disk pool Maybe the bits are lost in space More info plz. Stef
Re: Sloooow Restore
Here are some things you could consider; http://tsmwiki.com/tsmwiki/RestorePerformance Matt. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of Orin Rehorst > Sent: 03 November 2006 15:03 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Slw Restore > > The system repeats this cycle. It restores about 30 MB in 1 minute 45 > seconds. Then "Waiting for TSM server" appears on the client for about > 10 seconds. > > The restore process initially timed out after 80 MB until I bumped the > dsmserv.opt parms up (commitimeout to 600 and idletimeout to 45). > > TIA > Orin Rehorst > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of > Stef Coene > Sent: Friday, November 03, 2006 8:06 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Slw Restore > > On Friday 03 November 2006 14:55, Orin Rehorst wrote: > > TDP for Exchange backs up at 8 MB per second. > > > > It restores at 8 MB in 56 seconds! > > > > What may be wrong? > Maybe the SAN > > Maybe the LAN > > Maybe the TSM server version > > Maybe the TSM client version > > Maybe the tape library > > Maybe the disk pool > > Maybe the bits are lost in space > > > > > More info plz. > > > Stef > > > > This email is confidential and may be privileged. If you are not the intended recipient please notify the sender immediately and delete the email from your computer. You should not copy the email, use it for any purpose or disclose its contents to any other person. Please note that any views or opinions presented in this email may be personal to the author and do not necessarily represent the views or opinions of Digica. It is the responsibility of the recipient to check this email for the presence of viruses. Digica accepts no liability for any damage caused by any virus transmitted by this email. UK: Phoenix House, Colliers Way, Nottingham, NG8 6AT UK Reception Tel: + 44 (0) 115 977 1177 Support Centre: 0845 607 7070 Fax: + 44 (0) 115 977 7000 http://www.digica.com SOUTH AFRICA: Building 3, Parc du Cap, Mispel Road, Bellville, 7535, South Africa Tel: + 27 (0) 21 957 4900 Fax: + 27 (0) 21 948 3135 http://www.digica.com
Re: Sloooow Restore
The system repeats this cycle. It restores about 30 MB in 1 minute 45 seconds. Then "Waiting for TSM server" appears on the client for about 10 seconds. The restore process initially timed out after 80 MB until I bumped the dsmserv.opt parms up (commitimeout to 600 and idletimeout to 45). TIA Orin Rehorst -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stef Coene Sent: Friday, November 03, 2006 8:06 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Sloooow Restore On Friday 03 November 2006 14:55, Orin Rehorst wrote: > TDP for Exchange backs up at 8 MB per second. > > It restores at 8 MB in 56 seconds! > > What may be wrong? Maybe the SAN Maybe the LAN Maybe the TSM server version Maybe the TSM client version Maybe the tape library Maybe the disk pool Maybe the bits are lost in space More info plz. Stef
Re: Sloooow Restore
On Friday 03 November 2006 14:55, Orin Rehorst wrote: > TDP for Exchange backs up at 8 MB per second. > > It restores at 8 MB in 56 seconds! > > What may be wrong? Maybe the SAN Maybe the LAN Maybe the TSM server version Maybe the TSM client version Maybe the tape library Maybe the disk pool Maybe the bits are lost in space More info plz. Stef
Sloooow Restore
TDP for Exchange backs up at 8 MB per second. It restores at 8 MB in 56 seconds! What may be wrong? Environment: OS Win2003, TSM 5.3.2, IBM tape library 3583 LTO 1. TIA Orin Rehorst
