Access Database Backups (multiple)

[evilradish]

I have recently made a career change and now work with access. With no prior exp this has been an intimidating 1st month
I would like to create my 1st new db from scratch.

I want to create an access database to manage all my critical database backups as currently we have around 2000+ on the network. From what i can see a majority are dead (as over the next 2 years we will be migrating backends to sql)

Some of the features I would like to include are:

database to be automatic
scheduled daily, weekly jobs
all databases managed within a table.. location, freq of backup etc...

Does this sound possible or am i barking up the wrong tree

I have searched the forum and seen loads of methods for backing up but not in this style (hence me asking this question)

Also if you have an extra min could you give me a brief overview on how you would set this up

Thank You

 

[MarkK]

2000 databases??? Sounds like someone might have been using them like Excel files?
But what you suggest sounds totally reasonable. But you have a few distinct problems...
1) Maintain info on each database, including it's current location, backup location, backup frequency and so on. This'll be a database you create.
2) Perform the back ups.
3) Data collection, not a trivial matter if you have 2000 source files, and therefore 2000 destination locations, etc...
But it seems a bit of a make-work project too, to have such fine control over backups on this scale. Why not put everything in one folder and back it all up all the time?

 

[evilradish]

yes from what I can see each team had their own dev person and there databases that should not even exist.

As I said steep learning curve as databases are new to me

As for the locations of the databases I did a little cheat and in the space of an hour managed to collect every path of each db.

I have created a table in a new access db with columns for handling the jobs (frequency, time path status... etc)

I think with the help of people here. when I complete this database I will upload for other people to use as I have seen none here.

My next issue is how to have my database constantly polling to see if the next job needs to be run. How does one go about setting that up?

As for putting all in one folder this will not be possible. Main reason being there are loads of other databases that these feed to and from so I do not want to break any chains (as I don't fully understand yet)


Small fish in a big pond?......i think so

 

[MarkK]

Well, all the best with it. Post back if you need more info.