Just wanna hear on how do you guys do your back-up and restoration in PDMS. Got confuse in this matter because as far as I know there is no dump file in PDMS just like in Oracle.
Forget incremental, backup all under XXX000 directory - if all you care about is database files. If you want draft and iso, do the whole project folder.
Hello,
Can you all explian how to keep the backup of the project. Since there are a lot number of new user in my project and i fear some one may delete something. I want to know.........
AA) How to keep a backup of my project and what data i have to keep ?
BB) Do i need to keep it daily then how can i schedule it ?
[QUOTE=Mirzaab;11714]Hello,
Can you all explian how to keep the backup of the project. Since there are a lot number of new user in my project and i fear some one may delete something. I want to know.........
AA) How to keep a backup of my project and what data i have to keep ?
BB) Do i need to keep it daily then how can i schedule it ?
Hello, As my knowledge you keep the back up by using DB listing from utility.
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.
[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.
