[AccessD] Hourly Backups Of Access Data

Paul,

The critical issue I see with Jet is that you can't guarantee that your
backup data will be in a consistent state while users are in the database.
Jet simply can't be trusted to keep everything straight with the read/write
locks or cascade updates/deletes that could be in progress when you initiate
your backup.

This applies as much to backing up the mdb files as it would to any of the
other proposed solutions, in my opinion.

If live backups are an overriding concern, consider moving your backend to
MSDE/SQL Server. With its transaction logging and dynamic backup
capabilities, you can implement a much more reliable and transparent backup
policy.

Otherwise, kick 'em out!

See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300216
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k/htm
l/acmsdeop.asp

-Ken

-----Original Message-----
From: John Bartow [mailto:john at winhaven.net]
Sent: Monday, November 03, 2003 12:08 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Hourly Backups Of Access Data


Paul,
I just looked at my backup routine but it won't work for you, uses
CompactDatabase. Guess I should create a new one.

(Thinking out loud here) how about:
Create a routine to export all of the tables and data to a new DB. That
shouldn't affect any of the users.

Create a seperate routine that clears the tables and imports/appends it all
back in just in case you need to restore the data. If that case arises it
would probably mean the users can't get in anyway - otherwise you would have
to kick them all out.

This would alleviate worrying about relationships, etc.

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of
> paul.hartland at fsmail.net
> Sent: Monday, November 03, 2003 11:00 AM
> To: accessd
> Subject: [AccessD] Hourly Backups Of Access Data
>
>
> To all,
> Is there anyway I can create a backup of all the tables in a
> database, without bringing all the users out of the database.
> Paul
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>