Volume Shadow Copy & Access Corruption

L

Lee

We have an Access 2003 database that has gotten corrupted
several times since being upgraded from an Access 2000
database AND being placed on a new server with the Volume
Shadow Copy service enabled. Does anyone know if VSS is
compatible with Access 2003 databases? Has anyone seen it
cause corruption? Can anyone post links to articles/MS
KBs that discuss the topic?

Thanks

-Lee
 
6

'69 Camaro

Hi, Lee.

One shouldn't copy an Access database while it's in use, because the copy
could be corrupted. This happens when the database is in the process of
writing a transaction to disk, but hasn't completed it. A repair operation
on the database copy might not succeed in rolling back the incomplete
transaction.

For best results, make backups and copies of Access databases after all
users and processes have closed the database file.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
L

Lee

Not concerned with the shadow copies themselves. The
problem we're having is that the ORIGINAL file (not the
Shadow copy restored file) is corrupting at seemingly
random intervals that the developer thinks are close to
the shadow copy snapshot times. I'm not so sure. In
anycase, is the following statement true:

VSS will not corrupt or damage Access Databases. However,
Access databases restored from shadow copy may be
corrupted.
 
L

Lynn Trapp

You might search support.microsoft.com for "Volume Shadow Copy", then. That
search returns several hits.
 
T

Tony Toews

Lee said:
We have an Access 2003 database that has gotten corrupted
several times since being upgraded from an Access 2000
database AND being placed on a new server with the Volume
Shadow Copy service enabled. Does anyone know if VSS is
compatible with Access 2003 databases? Has anyone seen it
cause corruption? Can anyone post links to articles/MS
KBs that discuss the topic?

This problem may not have anything to do with the VSC. I'd also
consider the OpLocks problem.

Corrupt Microsoft Access MDB Causes - OpLocks
http://www.granite.ab.ca/access/corruption/causesoplocks.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
6

'69 Camaro

Hi, Lee.
is the following statement true:
VSS will not corrupt or damage Access Databases. However,
Access databases restored from shadow copy may be
corrupted.

I have no proof whether the VSS will or will not corrupt or damage Access
databases. From what I understand of how the VSS operates, the copy of the
file is made as soon as the data is written to disk. This _shouldn't_ cause
any interference with the original file. However, the copy may contain
incomplete transactions, which may require Jet to repair the database copy
the next time it's opened, which may not succeed in fixing the corruption.

There are so many _other_ causes of corruption that I would focus on what
else is going on with the database that might cause corruption in the
original file. Only after eliminating those other possibilities would I
return to the VSS to investigate how it might be interfering with the
original database file.

Situations that commonly cause corruption are lost network connections while
Jet is writing data to disk, faulty network interface cards, turning off the
computer's power when the Access database application is still running,
multiple users accessing the same database file from across the network
(each workstation should have its own copy of the front end linked to the
back end database file, which contains the tables, on the network),
opportunistic locking enabled on the Windows server, saving a modified
database application object (such as a Form, Report, or Module) while other
users are using the database application, compacting the database from a
workstation across the network to the server (one should always compact the
database while logged in on the computer where the file is located), and
reaching the 2 GB file size limit.

You'll find many links and much information about database corruption by
checking this Web page:

http://www.granite.ab.ca/access/corruptmdbs.htm

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top