MS Access backend backup
An IT firm are currently setting up an automated backup system for one of my clients.
They are setting it up to do backups several times a day, including during working hours.
I pointed out to him that I'm unhappy about backups being done whilst the backend file is open.
This was his reply:
"The Symantec backup software use Microsoft Volume Shadow Copy Service backups - this is a point in time snapshot of the files - so it doesn't actually backup the file itself, it takes a copy of it. This ensures the no lock-ups or database corruptions."
Is he right? Or is there still a risk of corrupting data?
They are setting it up to do backups several times a day, including during working hours.
I pointed out to him that I'm unhappy about backups being done whilst the backend file is open.
This was his reply:
"The Symantec backup software use Microsoft Volume Shadow Copy Service backups - this is a point in time snapshot of the files - so it doesn't actually backup the file itself, it takes a copy of it. This ensures the no lock-ups or database corruptions."
Is he right? Or is there still a risk of corrupting data?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have found that copying a file while it is open is generally ok. I have never had a problem doing that but I do not know if my environment is the same as yours. . To be sure you should do a test. Using a test database, create an update query (or something to write data) that will take at least 3 seconds, or long enough for you to initiate a copy of the file. Then run the query and initiate copying the file. Once the file is finished copying see if you can open the copy without any errors or corruption. Also close and re-open the source file to see if there is a problem.
Additional factors will be how many simultaneous users are accessing your BE data and also how large are the database files. Lastly, is this a 1000mbps network, 100Mbps and are there any wireless users? This can effect the success or failure. If you have small data files that are less then 10MB in size, they are much more forgiving. Especially if you have 10 or less simultaneous users. Furthermore, I've seen files 50MB in size with 10+ users work just fine on 1000mbps network if you are running nightly repair/compact routines on your data files.
Ultimately doing a test it the best way to determine if there is a concern.
Additional factors will be how many simultaneous users are accessing your BE data and also how large are the database files. Lastly, is this a 1000mbps network, 100Mbps and are there any wireless users? This can effect the success or failure. If you have small data files that are less then 10MB in size, they are much more forgiving. Especially if you have 10 or less simultaneous users. Furthermore, I've seen files 50MB in size with 10+ users work just fine on 1000mbps network if you are running nightly repair/compact routines on your data files.
Ultimately doing a test it the best way to determine if there is a concern.
ASKER