Aaron et al;
I would like to see more information posted regarding the administrator's side of things. A how-to, if you would. Recovery of models, best method of project recovery from corruption, proper backup routines, custom report authoring, spec how-to, central vs. distributed projects, software requirements and best performing, best setup method.
I am currently racking my brain on the best method to move a project from one server to another. Perhaps you could help me out. I would like to keep all of the models in the same place. There are thousands of models, so moving them out of their position and reimporting them seems futile. Is there a method to move to a new server, the project paths only? This is a distributed project setup.
Thank you...
Hello Mission,
One thing I would like to point out is that we do have a blog post of some basic practices in AutoPLANT. It goes over a varity of areas in AutoPLANT and I feel it might help answer some of your questions. I will also point out that it isn't completed, we have had to put a hold on finishing it up for other reasons. Because of this hold, the Maintenance section hasn't been posted yet. But it still has a good bit of information that might help you in other areas.
http://communities.bentley.com/Communities/Other_Communities/Bentley_AutoPLANT/b/bentley_autoplant-blog/default.aspx
One the Project moving, you mention the "Project paths only". Are you referring to just the project database itself or all the project paths excluding the drawings? There are multiple ways to move a project, the safest way would be to package the project using Project Packager. The down side to using Packager is that it will package up all the models, which can take some time and if they are not moving, then it may not be the best option for you. Please provide a bit more information on what exactly is needed for this move and what would be changing (server name, database instance, etc...).
Glen, Richard,
Thank you for the replies. I have read the existing blog for AutoPlant and love how it is shaping up.
Currently I am trying to move a project ROOT to another server. So, I have server2\autoplant_project\project-folders... and I would like to move it to server3\autoplant_project\project-folders... The drawings are already on server3 and mapped to the users (ALIAS points to mapped drive). I would like to move the project ROOT, but leave the drawing ALIASes the same.
Can I just change the paths in Project Manager after moving the root? I have already moved the SQL databases to the new server, so that isn't an issue.
Eventually I would like to merge the projects into a central as they are all for the same client and the initial setup was based on plant location per project which isn't functional.
Thanks,
Mission
Hi MIssion,
If you have moved the files and the SQL server database you have done the hard work.
Just move the root and open the project from teh new root and all should be well.
AutoPLANT is designed to have several root locations, so moving a root is generally painless as long as the SQL / Oracle server remain static.
Glen
Hello Tomasz,
Please see steps below to accomplish move to new server.
How to change an AutoPLANT Piping project database to a new SQL Server
Regards
Dinesh Solanki