We have been using Plant 3D for the past year along with SQL server 2012. Our IT department is wondering the best way to archive a project once it is complete to get all the project files from our network drive along with all of the database files.
Also, if there is a problem with an active project, what is the best way to restore it from backups to a day or two before?
Is there a "best practice" guide to handling and managing all project files?
Solved! Go to Solution.
Solved by quentin.contreras. Go to Solution.
Backing up a project to archive really depends on where you are keeping all the files that are associated to that particular project. Normally when you create a project Plant 3D builds all the folders and files and stores them in one location. So, in this case you would simply have to zip up the entire project. Then with the SQL database files you would need to create BAK files of the database files. Basically, you would locate the files in SQL right click over the file, select Task and then Back up. There will be a window that appears and you should be able to just select ok to make the .bak file for the database. This will need to be done for EACH database file.
Once you are done making .bak files for each database you might want to just zip all the databases into one file. This will make sure that all the database files are together when you need them. If there are other drawings or files located out of the project then you will need to make sure those save as well to where you are keeping the zipped project and zipped database files.
If there is a problem with an active project it would be best if you knew a particular drawing is causing the problem. Then you would first remove the drawing from the project, then locate the DWG file using Windows Explorer and either delete it or back it up if you need to restore it. Next you would need to close all drawings in the project, make sure no one else is accessing the project and then run a PLANTAUDIT for the project. Then using Windows Explorer place the drawing file where you removed the previous drawing file. Now back in Plant 3D you will want to use the Copy Drawing to Project to place the drawing file back in the project. Of course the steps above only mentioned doing this with one drawing file. However this process can be done with multiple drawings as well.
There is not a best practice guide for handling and managing all the project files for a Plant 3D project. I would recommend that only one person be responsible for this task though if possible. This would ensure set standards are in place and there would be less of a chance of files being saved outside of where they need to be located.
Quentin Contreras
Technical Support Specialist
Hi Quentin,
In the case of Plant 3D integration with Vault, how do you recommend to backup the plant 3D data?
Thanks!
I'm looking into this as well and I guess it depends on what you expect your lifecycle/archival requirements to be.
You could, leave everything in the Vault and use its lifecycle management tools to ensure it is archived. If you wanted to just clear all the databases off your production PLANT3D SQL server, you could back them up and store the backups in your archive location. To spin the project backup, you'd restore the databases then edit the .DLK files in Vault to match whatever SQL instance you restored to.
Another way would be to detach the project from Vault and perform a pack and go on the project. At that point, you could just dump the resulting files of both actions into your archival storage.
Can't find what you're looking for? Ask the community or share your knowledge.