Jump to content
Sign in to follow this  

Does A Backup Take Longer When Files Are Locked?

Recommended Posts



We have a Windows 2000 Server box which hosts a SQL Server. When the Server is up, naturally most of the tables and databases are in use, and cannot be backed up. We rely on the SQL Server application to manage live backups of the databases to another location, which Retrospect backs up.


However, I'm wondering if this machine's backups take longer to complete because these files are failing to be backed up. It's obviously a waste of time for Retrospect to back up these folders, but how *much* of a waste of time? Is there a way to quantify this?


Should I actually exclude the directory holding all of the databases from being backed up, and if so, would that appreciably increase the speed of my backups for this machine?

Share this post

Link to post
Share on other sites



It should not make much differnce at all. As soon as Retrospect tries to scan the files it will get a "file in use" error and move right along. I'd just let it go. If your backups are taking too long we should probably look into other possible causes.



Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this