Who is making my backups

Joe8915

Registered User.
Local time
Today, 15:26
Joined
Sep 9, 2002
Messages
820
:mad:Is there anyway, I can tell who is making my backups. Is there any thing I can use to find out who is creating a backup. I have sent out emails to the users, but no one will confess who is doing yet. I have 200 users now. I have talk to our IT people, they mention it would take a lot of there time to track it down.

Does anyone know if there anything I can do?

Thanks
 
In the most general scenario an automated batch would run once a night which backs up the server. I this what you mean?
 
We need a little more info before we can help you.

WHat sort of backup is being made. Could it be a routine backup made by IT as part of their policy.
 
:mad:Is there anyway, I can tell who is making my backups. Is there any thing I can use to find out who is creating a backup. I have sent out emails to the users, but no one will confess who is doing yet. I have 200 users now. I have talk to our IT people, they mention it would take a lot of there time to track it down.

Does anyone know if there anything I can do?

Thanks

Are they titled db1.mdb, db2.mdb, etc.?
 
boblarson.................
Wow, thanks for the quick reply. I am running 2007. The name of the Database PD2001 and it creates a backup called PD2001backup.

Rabbie......
No, its not a routine backup made by IT


Kenhigg...............
No, its not a batch file. IT would notify me if its something that they are doing.

I think it has to do with one of the users. I have installed a IDLE time off, which works great. All it does, if a user shows no activity for 15 minutes, it will logg them off. I thought maybe that would cure the problem, but no avail. The database is secure as much as I can make it secure. If I can just find out who is making that folder, my problem will be solved.

Any input whould be most appreciated
 
Do you have any type of logging in your database, if not I might put in something to log the PCname, LANID, time, and database name of each user entering the database and log that to either a local table or a central table on the back-end. With that info you could see who is using the database, and if anyone is using the backup database you could see that to.
 
Can you view the file properties and see when it was created and maybe the owner? Also, sometimes when a fatal error occurs Windows will do an automated backup. With a name like PD2001backup this could be what is creating it...
 
is the db split between front & back?

can you see the backup once it's made?
 
Ken, thanks for the interest
I can only see the time and date it was created. It sounds like I won't be able to find out who created it.

would that be your conclusion as well?
 
Vodka

No, I don't have a FE or BE.

Yes, I can see the backup
 
If it always puts 'backup' on the end then yes that would be my guess... I suppose you've ask your users if the ever get an error?

An yes the BE/FE thing is a good idea (IMHO)...
 
Bob, you are so right on splitting the Database. Since converting to Access 2007 from 2003, its been very unstable, very slow as well, it also bloats up. Meaning from 120 Meg to twice the size, every day. So I compact and repair every morining, then it goes back down to the 120 meg.

I guess I just don't have the confidence in our servers. You know how that goes, everyone like to point the finger on why its slow. Some IT people tell me its there sever, some will tell me its our computer and others will tell you its window 2007.

So who do you believe? All I know I have 200 users or so, that I have to keep happy and keep the database running. I will say, I never had any problems with 2003, it almost ran itself. But with 2007 ouch, very sensitive.

I think in time I will spilt database, but as for right now, I think I will leave it alone.

On saying that, I do respect your ideas and thoughts. Been around here along enough, respect and go with alot of your ideas and suggestions.
 
I'm surprised you didn't have trouble before if all were using the same database. While I was at a major healthcare company, I found out someone was doing the same thing for over 100 users (even was split but the frontend was on the server and all were running it from there). I then created my frontend auto update enabling tool so that you would not have to worry about users having the latest frontend. All you have to do is make changes to the master and then change the version number in two tables. Then the users, the next time they log in, will get a message that their frontend is out of date, it will close, delete the file, copy the new one down from the network location, and automatically reopen for them. Works great. We used to have a corrupted database at least once a week. Since I put it on there, there have been NO instances of corruption. You can get the database here, on my website: http://www.btabdevelopment.com/main/MyFreeAccessTools/tabid/78/Default.aspx Be sure to download the documentation and CAREFULLY go through it to set it up as it is easy to miss a step.
 
Bob, I guess I should tell you, not all the users are in the database at one time. I think the most I ever had was twenty at the same time.
 
Bob, I guess I should tell you, not all the users are in the database at one time. I think the most I ever had was twenty at the same time.

That's still 19 more than should be in, in the current configuration.
 
But, it's your skin - not mine. Personally, I wouldn't risk it. It is just so susceptible to corruption if you don't have it split and the FE on the user's machine.
 
I notice that you are compacting every day. Don't forget that Access will make a backup before doing the Compact. Maybe thats where the backups are coming from.
 
bob

out of interest i put code in my start up form (rough and ready) to test the drive letter

if it is above H (say), I assume its a network drive, and quit the app with a suitable message

"Please do not run the network copy etc etc"
 

Users who are viewing this thread

Back
Top Bottom