Company P Drive Backup

  • Thread starter accessuser via AccessMonster.com
  • Start date
A

accessuser via AccessMonster.com

I think my company has backups for p drives and my access database is going
to be placed on the p drive. Does this mean i am all good? I've been
researching days about backup solutions, but seems so hard to find. All i
need is to have the backup run once a day, which i think my company does it
on the P drive, do I still need another backup codes?. Please give me some
suggestion. Thanks.
 
D

Daniel

This is a conversation you need to have with your network admin. If they do
a backup of the drive where your db is located then yes you don't really
require anything more...

This said, restoring backups, depending on the organisation, can take some
time. If this is a critical database then you might still want to do some
form of a backup yourself.

Once again, depending on the importance of your db, the frequency of the
backup performed by your IT dept. might not be often enough, so once again
you may want/need to do so yourself. however, most often you can talk with
your IT dept and they should be capable of making backups of your particular
db/directory... on the frequency you need. Once again, you need to talk
with your IT Admin.

Daniel P
 
A

accessuser via AccessMonster.com

Thanks. That's what i wanted to make sure before I call.
 
L

Larry Linson

accessuser via AccessMonster.com said:
I think my company has backups for p drives and my
access database is going to be placed on the p drive.
Does this mean i am all good? I've been researching
days about backup solutions, but seems so hard to find.
All i need is to have the backup run once a day, which
i think my company does it on the P drive, do I still
need another backup codes?. Please give me some
suggestion. Thanks.
Click to expand...

If this is a production database and you simply want to protect the data,
and, if your database will be closed... not open (and potentially in the
midst of an operation)... when the copy is performed, that may be
sufficient. If your database may be open and performing an operation, it may
restore but be "corrupted" and may or may not be "repairable". In that
case, you'll need to investigate other approahes to backup to ensure it is
copied when it is not open.

When I am _developing_ (creating or maintaining) a database, I back up no
less often than the amount of change that I am willing to re-enter if I
cause, or the system causes, a crash. That is, separate and apart from the
normal "server backups".

I hope you are planning to split the database into back and front ends...
front end consisting of the Queries, Forms, Reports, Macros, and Modules and
the back end consisting of Tables, Relationships, and Data. For more on
this subject, see MVP Tony Toews' website,
http://www.granite.ab.ca/accsmstr.htm.

Larry Linson
Microsoft Access MVP
 
Top