Plant 3D Data Recovery Plan with Vault

Customer Name
Plant 3D and Vault Disaster Recovery
Contents
Strategies crucial to protecting your data .................................................................................................... 3
How to back up your Environment ............................................................................................................... 3
Vault Backups ............................................................................................................................................ 3
Full Backup ............................................................................................................................................ 3
Incremental Backup .............................................................................................................................. 3
Configuration File backups........................................................................................................................ 3
Vault Multi-Site Environment backups ..................................................................................................... 3
Plant 3D Backups....................................................................................................................................... 4
SQL Databases ....................................................................................................................................... 4
Project files ........................................................................................................................................... 4
Catalogs ................................................................................................................................................. 4
Monitor your environment to prevent a disaster......................................................................................... 5
Vault software ........................................................................................................................................... 5
Vault server log files .............................................................................................................................. 5
Microsoft SQL Server log files ............................................................................................................... 5
DWG iFilter Log files .............................................................................................................................. 5
WEB Logs ............................................................................................................................................... 6
Job Processor Log files .......................................................................................................................... 6
Plant 3D Software ..................................................................................................................................... 6
Microsoft SQL Server Log Files .............................................................................................................. 6
Project Audit ......................................................................................................................................... 6
Plant Database Replication on SQL Server ............................................................................................ 6
Windows Event logs .................................................................................................................................. 6
Proper strategies to recover from a disaster ................................................................................................ 7
Recovering a lost Plant 3D SQL server in a replicated environment ........................................................ 7
Recovering a lost Vault server in a replicated environment..................................................................... 7
Recovering from a total environment loss ............................................................................................... 7
Before the Restore .................................................................................................................................... 7
Vault Restore with ADMS.......................................................................................................................... 7
Plant 3D Database restore ........................................................................................................................ 8
Post restore ............................................................................................................................................... 8
Vault ...................................................................................................................................................... 8
Before Testing Plant 3D ........................................................................................................................ 8
Test the Restore ........................................................................................................................................ 8
Start new backups..................................................................................................................................... 8
Strategies crucial to protecting your data
Due to their tightly integrated nature within their respective databases, special care must be taken
when backing up a Vault with Plant 3D Environment.
• Make sure that all Vault and Plant3d databases are present in each replicated site where
possible. This will create true redundancy in the environment and greatly reduce the time
needed to recover from a disaster at 1 of the locations
• Backups of the Vault(s) and Plant 3d database(s) MUST be performed at the same time and,
when possible, with no users accessing the Plant 3d files. If backups are performed at different
times you may not be able to successfully access project files in the Vault as there could be new
or different records in the Vault and Plant 3d databases.
How to back up your Environment
Vault Backups
Use the backup tool available in the ADMS (Autodesk Data Management Server).
It is important to note that this tool backs up not only the Vault database and settings but also your file
store so the backup size can be quite large.
Within ADMS there are two types of ways to back up the Vault they are detailed below.
Full Backup
•
•
The best method is that of a Full backup. This backs up all Vault databases, settings and file
store at the point in time of the backup. Always make sure you check the “Validate the
backed up files”, shown below, to ensure that your backup is successful and can be
recovered.
A Full backup can take a significant amount of time depending on the size of your
database/file store and should not be run during production hours as the extra activity may
impact normal Vault activities.
Incremental Backup
•
An Incremental backup only backs up changes that have occurred since the last backup. It is
much faster than a Full backup but you cannot restore from it unless you have both the Full
backup it reference AND any other Incremental backups that have occurred since then. An
Incremental backup is best suited for the performance hit of a Full backup makes it unrealistic to
run during production hours. As with a Full backup make sure to validate the file.
Configuration File backups
Make sure you are backing up your web.config(located in the Vault installation folder of your primary
ADMS server) file if it has been customized as well as any configuration files for add-ins you may be
using. These will not be backed up as part of the ADMS backup tool.
All Plant 3D files are all stored in the Vault and do not need a separate backup.
Vault Multi-Site Environment backups
There are special Considerations that must be accounted for when backing up a multi-site environment
replication:
•
•
Autodesk best practice is to perform all backup and restore operations at a single site that is the
publisher in a multi-site environment.
While possible to backup remote sites it is not recommended as long as the publisher has all
Vaults enabled this will not be a problem.
Plant 3D Backups
SQL Databases
The project SQL database backup is performed using Microsoft SQL Server Management Studio manually
or through scheduled backup tasks. All five of the Plant 3D project databases must be backed up on each
project for a complete backup. The database suffixes will be:
<DATABASE PREFIX>_Iso
<DATABASE PREFIX>_Misc
<DATABASE PREFIX>_Ortho
<DATABASE PREFIX>_Piping
<DATABASE PREFIX>_PnId
Project files
The Plant 3D project drawings, configuration files, and specification sheets are stored within the Vault.
The files will be included up with Vault backup.
Catalogs
Project catalogs are not contained within Vault. If you are using a shared content folder on a network
location this folder will need to be included with the backup. i.e., C:\AutoCAD Plant 3D 2016 Content\*.*
Monitor your environment to prevent a disaster
It is recommended that you actively monitor your environment in order to proactively surface issues and
resolve them before they cause a serious error. There are 3 areas that you should focus on:
Vault software
You should make sure to review ADMS logs to check for replication errors and that backups worked
successfully. Logs for items related to Vault are listed below:
Vault server log files
o
o
There are four different Vault related log files, each of these is described in full detail below.
The files below will be found in one of two folder locations based on your operating system:
• In Microsoft Windows™ XP / Server 2003
C:\Documents and Settings\All Users\Application Data\Autodesk\VaultServer\FileStore
• In Microsoft Windows 7 / Server 2008 / Server 2008 R2
C:\ProgramData\Autodesk\VaultServer\Filestore
Vlog-YYYYMMDD.txt
o This file collects any server-side problems relevant to Check-in, Check-out, Get Latest Version,
Undo Check-out, Advanced Search and other operations performed from within Vault Explorer
or one of the supported product add-ins are written into these log files.
ADMSConsoleLog-YYYYMMDD.txt
o This file collects any server-side problems relevant to backup, restore, re-index, purge or other
operations performed within Autodesk Vault Server Console are written into these logs.
Emaillog-YYYYMMDD.txt
o This file collects Email sent from the server.
licensingLog.txt
o This file collects Licensing errors
Microsoft SQL Server log files
o
The SQL logs are named sequentially with the most recent (current) file being named error log
followed by errorlog.1 then errorlog.2 and so on.
• Folder location and file names:
▪ C:\Program Files\Microsoft SQL Server\%SQL_INSTANCE%\LOG
OR
▪ C:\Program Files\Microsoft SQL Server\%SQL_INSTANCE%\MSSQL\Log
DWG iFilter Log files
o
These are log files maintained by the various iFilters used when performing some Vault
operations like re-index. These log files can be helpful when troubleshooting problems with
block attributes or properties not indexing as expected in Vault Explorer.
• Folder location and file names:
Depending on your server setup, your iFilter log files will be contained in
C:\Windows\Temp\
OR
%TEMP%\DWGFILT.*.log
WEB Logs
o
o
o
Extended Web Logging is not enabled by default. If you have enabled it the default location is
here:
IIS 6 or earlier
C:\WINDOWS\system32\LogFiles\W3SVC1 – for the Default Web site communication.
C:\WINDOWS\system32\LogFiles\HTTPERR – for IIS errors logs.
IIS 7 or later
C:\inetpub\logs\LogFiles\W3SVC1
Job Processor Log files
C:\Program Files\Autodesk\Vault <version>\Explorer\JobProcessor.log
Plant 3D Software
Microsoft SQL Server Log Files
The Plant 3D SQL Server log files can be viewed from Microsoft SQL Server Management Studio or
directly from the log file location. The default location is:
D:\MSSQL2012\MSSQL11.INSTANCENAME\MSSQL\DATA\
Project Audit
The Plant 3D audit project (CMD: AUDITPROJECT) process will check the information in the project
databases against the project drawings. Any records in the database that do not belong to a drawing will
be purged out during the audit.
Plant Database Replication on SQL Server
The Plant SQL database synchronization log file is saved to: C:\ProgramData\Autodesk\AutoCAD Plant
3D\Replication on the server hosting the synchronization service. Conflicts are identified in the log file.
Windows Event logs
o
Making sure your operating system is working correctly is an important step in making sure that
your system is healthy. System and application logs should be reviewed at least monthly to
ensure that there are no major errors and that windows updates are installing correctly.
• System Event log
• Application Event Log
• Windows update log
Proper strategies to recover from a disaster
Recovering a lost Plant 3D SQL server in a replicated environment
Assuming all databases were correctly in sync then you will need to break all replication settings
from the previous server and create a new replication set from the “surviving server’ that pushes all
databases to your new server. All databases should be replicated between the two servers again. All
projects that pointed to the “lost” server will need to be pointed to the “new” server after it is built or to
the “surviving” server on an interim basis.
Recovering a lost Vault server in a replicated environment
There are two possible scenarios for a lost Vault server:
• Lost Publisher: If the publisher is lost then a support case must be opened with
Autodesk support and there must be an available subscriber with all Vaults enabled and
in sync. Assuming both items are true Autodesk support should be able to convert the
existing subscriber to a publisher.
o If there is not an available subscriber then the publisher will have to be restored
from a backup and all subscribers will have to be wiped and reseeded from the
restored publisher.
• Lost Subscriber: If a subscriber is lost then the associated workgroup will need to be
removed from the ADMS on the publisher. A new server built and added as a workgroup
and then replication started again. Once all databases have replicated the server will be
available to be used.
Recovering from a total environment loss
Before the Restore
o
Before you start a restore there are some important questions to answer:
• Are you able to name the new server the same as the old server? If this is not possible
you need to contact Autodesk support.
• Is the new server the same OS and service pack level as before? This is important to
make sure the restore will work successfully
• Is the SQL installation the same edition, version, and service pack level as before? This is
important to make sure the restore will work successfully
• Did the backups you will be using to restore occur at the same time for plant and Vault?
If not you will need to contact Autodesk support.
o
Before starting the Vault restore, perform the following:
• Install the Autodesk® Vault server software.
▪ Make sure to follow the readme’s to make sure no steps are missed and no
special actions are required between service packs.
• Install all hot fixes and/or services packs that were installed on the original server.
• Clear local cache on all workstations and clear workspaces
Vault Restore with ADMS
o
o
From within ADMS start a Restore with the Backup and Restore Wizard
Choose Full Restore
o
o
Choose the location of the backup file and where the database and file store should be restored.
Then click finish.
Based on the size of your database and file store it could take quite a long time to finish your
restore.
Plant 3D Database restore
After the Vault is restored you will need to restore the Plant 3D databases
• As with Vault the server OS name and SQL instance should be the same what is was prior to the
disaster
• Review all SQL logins and restore any custom logins as needed
Post restore
Vault
•
Once all databases and the file stores have been restored, start the ADMS Console to verify all
databases can be seen. If any databases need to be migrated, a migration dialog will appear and
you should migrate the database.
Before Testing Plant 3D
Before opening a restored project perform the following maintenance steps on each workstation using
Plant 3D:
• Purge the local data cache
• Clear the Vault local workspace
Test the Restore
After the restore is successful make sure you test the Vault. The easiest way to do this check a file in and
out of the Vault and add a new file to the Vault. If both of these actions work successfully your Vault
should be ready for use.
Start new backups
After you restore your environment make sure you restart your backup schedule immediately!
Download PDF
Similar pages