bnapier Posted February 27, 2003 Report Share Posted February 27, 2003 We have been using the same backup scripts now for about 2 years. We have a Windows 2000 server with an Onstream DI-30 tape backup using Retrospect Workgroup 5.1. Back when things were working normally our backup would occur in about 6 hrs with 23 minutes of idle/loading/preparing time. This was to backup 19 GB. The amount of data to be backed up has grown only to 21 GB, but the backup takes over 10 hours (we usually have to abort it), and the idle/loading/preparing time is now over 2 1/2 hours! What could be the cause of this? Quote Link to comment Share on other sites More sharing options...
AmyJ Posted March 5, 2003 Report Share Posted March 5, 2003 Are you backing up NTFS permissions (on by default with server operating systems)? The backup of NTFS permissions on a large server can take a very long time. Try a backup with this option turned off (options>more choices) and see what the performance is like. NTFS permissions, registry backup, scanning, matching, tape loading, tape rewind are included with the idle/loading/preparing. Quote Link to comment Share on other sites More sharing options...
bnapier Posted March 5, 2003 Author Report Share Posted March 5, 2003 I'm sorry, I should have followed up. No, we are not backing up NTFS permissions. Well, actually we do that on Sundays, but every other day we do not. We found the cause of the problem was actually another service that starts running 2 hours prior to retrospect and it was taking 100% of the CPU for several hours. Not Retrospects fault! ;-) Quote Link to comment Share on other sites More sharing options...
AmyJ Posted March 5, 2003 Report Share Posted March 5, 2003 Thanks for the update! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.