[QUOTE=yar_nl;13449]For back-up you should back-up the project everyday. The weekly /monthly back-up should be in a fireproof safe. Or you can store somewhere else. Ie not in the same building/location.
Hth,
Raymond
I rely on the IT dept to back-up the server data as normal, daily, weekly, monthly etc. As Administrators I think it is outside our remit to be the backup provider. However, as I trust no-one I also copy the project, sometimes nightly, sometimes weekly, depending if its Global or not, the satellites of course act as back-up anyway.
Personally I also copy the project to my C drive (or some other local place).
Pdms is very robust and unless someone really screws up you can usually get data back by using reconfigure, or back track changes. Where it becomes a problem is when you have multiple users in one db and someone deletes something then wants it back, but a backtrack would lose everyone else's data. We normally have a local copy project, so I could copy the db to that then backtrack, datal out and then run the macro into the real project, thereby getting the users deleted data back and not losing everyone else's stuff.
If the building burns down and the Company havent had the sense to have a robust data protection regime they get what they deserve.
[QUOTE=yar_nl;13449]For back-up you should back-up the project everyday. The weekly /monthly back-up should be in a fireproof safe. Or you can store somewhere else. Ie not in the same building/location.
Hth,
Raymond
I rely on the IT dept to back-up the server data as normal, daily, weekly, monthly etc. As Administrators I think it is outside our remit to be the backup provider. However, as I trust no-one I also copy the project, sometimes nightly, sometimes weekly, depending if its Global or not, the satellites of course act as back-up anyway.
Personally I also copy the project to my C drive (or some other local place).
Pdms is very robust and unless someone really screws up you can usually get data back by using reconfigure, or back track changes. Where it becomes a problem is when you have multiple users in one db and someone deletes something then wants it back, but a backtrack would lose everyone else's data. We normally have a local copy project, so I could copy the db to that then backtrack, datal out and then run the macro into the real project, thereby getting the users deleted data back and not losing everyone else's stuff.
If the building burns down and the Company havent had the sense to have a robust data protection regime they get what they deserve.
