Introduction What is Microsoft Data Protection Manager (DPM)? The Microsoft Data Protection Manager is a member of the Microsoft System Center family of management products. DPM provides continuous data protection for Microsoft server application and file servers as well as Windows desktops and laptops. DPM enables rapid and reliable recovery from easily accessible disk storage in minutes instead of waiting on less-reliable tapes. For more information including system requirements, visit Microsoft System Center Data Protection Manager. How Does it Work with Autodesk Vault? The Autodesk Vault server databases and file store can be backed up using the Data Protection Manager by installing the DPM Agent on the system holding the databases and file store. After the agent is installed, configure the databases and file store to backup as a protection group and set the schedule. 1
Preparing Vault to Use DPM Preparing the Databases Autodesk Vault databases are set to the Simple recovery model by default when they are created. The Simple recovery model doesn t use the transaction log files for backup. If the databases are set to the Full recovery model, SQL Server maintains the transaction logs for the databases, allowing log backups to be taken. With the Full recovery model the logs must be truncated manually; otherwise, they will continue to grow. When a database is added to a protection group, DPM detects the recovery model that the database is configured to use. DPM does not allow log, or incremental backups for databases configured in the simple recovery model. Log backups are only allowed for databases configured in the full recovery model. If you plan to use the full recovery model, it is recommended that you configure the recovery model prior to adding the database to a protection group. If it is configured after it is added to the protection group, DPM will not perform incremental backups of the database. To change the recovery model of a database that is already in a protection group: 1. Open the DPM Administrator Console. 2. Select the Protection tab. 3. Expand the protection group and right-click on the vault database. 4. Select the Stop protection of member option. Do not delete the replicas on disk. 5. In the SQL Management Studio right click on the vault database and select Properties. 6. On the Options page, change the recovery model and click the OK button to save the changes. 7. In the DPM Administrator Console, modify the original protection group and add the modified database. When protecting SQL Server databases that are configured to use the full recovery model, DPM creates a protected folder on the SQL Server. This folder is created in the same location as the first log file (*.ldf) of each protected database. This folder is used as a temporary store for logs during SQL Server log backup and SQL Server log restore by DPM. If DPM finds the folder missing, DPM will re-create the folder. Recovery points are created based on the synchronization frequency when the database is set to the full recovery model. When the database is set to the Simple recovery model, recovery points are based on the recovery point schedule. Note: When a new vault is created on a protected SQL Server computer, this database will not be added automatically to the DPM protection group. However this database can be added to an existing protecting group without impacting the current protected resources or schedules. Preparing the File Store The Autodesk Vault file store is located at c:\documents and settings\all Users\.. The DPM may have a problem backing up this location so the file store may have to be moved to the root directory of a drive if it is on the same computer as the Vault data management server. 2
Preparing DPM Install and Configure DPM See the DPM Setup Guide for instructions for installation and configuration instructions. These instructions will include allocation of disk storage and tape library configuration. Backing up a Single Autodesk Vault Site Connecting DPM to Backup Autodesk Vault A single Autodesk Vault site is a single location that has a single Autodesk Vault server installation without any file store replicated sites. After you have completed the installation of the DPM, you will need to install the DPM Agent on the system where Microsoft SQL Server is installed and on the system where the file store is located. After the DPM Agent is installed a reboot may be required. After the system has rebooted, start the DPM Administrator Console on the DPM server. 1. In the DPM Administrator Console, select the Protection tab. 2. Select the Create protection group option in the Select Item list in the right pane. 3. Click Next when the Welcome to the New Protection Group Wizard appears. 4. In the Select Group Members page, expand the server where the MS SQL database is located. 5. Select the KnowledgeVaultMaster, all vault and library databases. Note: Any vaults added after the protection group is created will need to be manually added to the protection group. 6. Select the top level file store directory. The file store folder is located at C:\Users\All Users\Autodesk\VaultServer\Filestore by default. Note: Do NOT add the Indexes folder as a part of the protection group. When you add the top level file store folder, new vault file store folders will be backed up automatically with the protection group. ** The DPM server may have problems backing up the file store from this location. If this occurs, you should move the file store just off the root of a drive on the server. For example: C:\filestore. 7. Click Next. 8. In the Select Data Protection Method, give the protection group a name and select the method you want to use to back up the databases and files. It is recommended to use a combination of disk and tape to back up the vault files for short-term and long-term archives. 9. Specify your short-term protection goals. a. Retention range is the duration of time for which the data should be available for recovery. DPM retains recovery points for the duration specified in the retention range. Any day that the replica is not consistent does not count toward the retention range. When DPM protection is stopped temporarily because the replica is inconsistent, DPM does not delete expired recovery points until protection resumes. 3
b. Synchronization frequency is how often the DPM server will synchronize the replica with your protected server. The default is every 15 minutes, which means that the DPM server will never be more than 15 minutes behind the computer it is protecting. c. Specify the file recovery points based on the schedule that is set or modify them to by clicking the Modify button. DPM can store a maximum of 64 recovery points for each file member of a protection group. The wizard will not allow you to configure more than 64 recovery points. 10. Click Next. 11. Review the amount of space allocated to protect the vault data. See Planning Protection Groups in the DP< Planning Guide for guidelines on allocating disk space. 12. Click Next. 13. Specify your long-term protection goals. The retention range can be set between 1 and 99 years. In the Frequency of backup box, select the backup frequency you want. The backup frequency is based on the specified retention range. a. When the retention range is 1 99 years, you can select backups to occur daily, weekly, bi-weekly, monthly, quarterly, half-yearly, or yearly. 14. Click Next. When the retention range is 1 11 months, you can select backups to occur daily, weekly, bi-weekly, or monthly. When the retention range is 1 4 weeks, you can select backups to occur daily or weekly. 15. In the Select Library and Tape Details page, select the library you want to use for the tape backups. 16. Click Next. 17. Now choose a replica creation method. 18. Click Next to finish the protection group creation. Optional: You may want to backup the Connectivity.ADMSConsole.exe.config and web. config files. These files store unique settings that may not be stored in the vault databases. The files can be found in the following locations: Connectivity.ADMSConsole.exe.config - <install path>\adms [Edition] 20XX Web.config - <install path>\ ADMS [Edition] 20XX\Server\Web\Services 4
Restoring a Single Autodesk Vault Site Restoring Autodesk Vault from a System Crash If your original Vault server has crashed and you have to perform a restore to a different server, perform the following: DPM Server steps: 1. Open the DPM Administrator Console. 2. Open the Protection tab and expand the protection group that contains the vault databases and file store. 3. Select the file store member and select Create recovery point. 4. In the Create recovery point dialog, select Create a recovery point without synchronizing. This will create a recovery point with all data currently on the DPM server from the last synchronization. New Server steps: 1. Set up the new server with the identical server name as the vault server that has crashed. 2. Install Autodesk Vault Server and all hot fixes and service packs that were previously installed prior to the server going down. 3. Install the DPM Agent and reconnect it to the DPM server. Note: You may have to install the agent manually. If so, follow the instructions in this Microsoft Article: Installing Protection Agents Manually. Recovery steps: 1. In the DPM Administrator Console, select the Recovery tab. 2. Expand the Recoverable data tree in the left pane and select the KnowledgeVaultMaster database. 3. In the middle pane select the date and recovery time. 4. Select the database name in the grid then select the Recover option in the Actions pane. 5. In the Recovery window, select the Recover to original instance of SQL Server then click Next. 6. On the Specify Database State page select the Leave database operational option and click Next. 7. Click Next on the Specify Recovery Options. 8. Click Recover on the Summary page. 9. Repeat steps 1-8 for each vault and library database and be sure to select the same date and time as the KnowledgeVaultMaster database. 10. Next the file store needs to be recovered if it was on the same server as the databases. In the Recovery tab, select the directory where the file store is located under All Protected Volumes. 11. Select the same recovery date as the databases you have restored. 12. Select the file store folder then select the Recover option. 5
Restoring a Single Autodesk Vault Site (continued) 13. Click Next on the Review Recovery Selection. 14. Select Recover to the original location. 15. Click Next on the Specify Recovery Options page. If you are recovering to a remote file store that still exist you can select the Skip option in the Existing version recovery behavior section. 16. Select the Recover button to start restoring the file store. Post Recover Steps: 1. 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. 2. With the ADMS Console closed, open a command prompt window. 3. Navigate to <installdir>\autodesk\adms 20XX\ADMS Console directory. 4. At the prompt type: Connectivity.ADMSConsole.exe -VUusername -VPpassword -Ovalidatefilestore This command runs a validation on the file store and databases This will validate all of the files in the database against the files in the file store. If any files are missing, a dialog will appear with a list of missing files. This list will also be written to the ADMS server log. To see if the command is still running, open the Windows Task Manager and look for Connectivity.ADMSConsole.exe in the Processes tab. 5. If any files are missing, you can look at previous recovery points and restore the necessary files. 6
Preparing DPM Install and Configure DPM See the DPM Setup Guide for installation and configuration instructions. These instructions will include disk storage allocation and tape library configuration. Backing up a Full Replication Publisher Connecting DPM to Backup Autodesk Vault In a full replication configuration it is important to back up the publisher s vault databases as well as two of the Microsoft SQL system databases. This section explains everything needed to perform a proper backup on the Publisher server. Replication Configuration: It is recommended that you use the following configuration to make it easier to restore a replicated environment. 1. An Active Directory user account should be used for all replication credentials. 2. All servers participating in the replication configuration should be in the same domain or in trusted domains. 3. Run the Microsoft SQL Service under a domain user account. 4. Create a script to back up the SQL Service Master Key. Back Up the Service Master Key: The service master key is the root of the encryption hierarchy in SQL Server. It should be backed up and stored in a secure, off-site location. Creating this backup should be one of the first administrative actions performed on the server. BACKUP SERVICE MASTER KEY (Transact-SQL) Exports the service master key. Transact-SQL Syntax Conventions BACKUP SERVICE MASTER KEY TO FILE = path_to_file ENCRYPTION BY PASSWORD = password Arguments FILE = path_to_file Specifies the complete path, including file name, to the file to which the service master key will be exported. This may be a local path or a UNC path to a network location PASSWORD = password Is the password used to encrypt the service master key in the backup file. This password is subject to complexity checks. For more information, see Password Policy. Remarks The service master key should be backed up and stored in a secure, off-site location. Creating this backup should be one of the first administrative actions performed on the server. 7
Permissions Requires CONTROL SERVER permission on the server. Examples In the following example, the service master key is backed up to a file. BACKUP SERVICE MASTER KEY TO FILE = c:\temp_backups\keys\service_master_ key ENCRYPTION BY PASSWORD = 3dH85Hhk003GHk2597gheij4 ; The service master key should be backed up on a regular basis. You will need to create a Windows Task scheduled on a regular basis to accomplish this. Back Up the SQL Databases After you have completed the installation of the DPM, you will need to install the DPM Agent on the system where Microsoft SQL Server is installed and on the system where the file store is located. After the DPM Agent is installed, a reboot may be required. After the system has rebooted, start the DPM Administrator Console on the DPM server. 1. In the DPM Administrator Console, select the Protection tab. 2. Select the Create protection group option in the Select Item list in the right pane. 3. Click Next when the Welcome to the New Protection Group Wizard appears. 4. In the Select Group Members page, expand the server where the MS SQL database is located. Select the MSDB, Master, KnowledgeVaultMaster and all vault and library databases. Note: Any vaults added after the protection group has been create will need to be manually added to the protection group. 5. Select the distribution database named Autodeskreplication. 6. Select the top level file store directory. The file store folder is found at C:\Users\All Users\Autodesk\VaultServer\Filestore by default. Note: Do NOT add the Indexes folder as a part of the protection group. When you add the top level file store folder, new vault file store folders will be backed up automatically with the protection group. ** The DPM server may have problems backing up the file store from this location. If this occurs, you should move the file store just off the root of a drive on the server. For example: C:\filestore. 7. Find and select the share folder setup for the SQL replication snap shots. 8. Select the folder where you store the SQL service master key. 9. Click Next. 10. In the Select Data Protection Method, give the protection group a name and select the method you want to use to backup the databases and files. It is recommended to use a combination of disk and tape to backup the vault files for short-term and long-term archives. 8
11. Specify your short-term protection goals. a. Retention range is the duration of time for which the data should be available for recovery. DPM retains recovery points for the duration specified in the retention range. Any day that the replica is not consistent does not count toward the retention range. When DPM protection is stopped temporarily because the replica is inconsistent, DPM does not delete expired recovery points until protection resumes. b. Synchronization frequency is how often the DPM server will synchronize the replica with your protected server. The default is every 15 minutes, which means that the DPM server will never be more than 15 minutes behind the computer it is protecting. c. Specify the file recovery points based on the schedule that is set or modify them to by clicking the Modify button. DPM can store a maximum of 64 recovery points for each file member of a protection group. The wizard will not allow you to configure more than 64 recovery points. 12. Click Next. 13. Review the amount of space allocated to protect the vault data. For guidelines about allocating disk space, in the DPM Planning Guide, see Planning Protection Groups. 14. Click Next. 15. Specify your long-term protection goals. The retention range can be set between 1 and 99 years. In the Frequency of backup box, select the backup frequency you want. The backup frequency is based on the specified retention range. a. When the retention range is 1 99 years, you can select backups to occur daily, weekly, bi-weekly, monthly, quarterly, half-yearly, or yearly. 16. Click Next. When the retention range is 1 11 months, you can select backups to occur daily, weekly, bi-weekly, or monthly. When the retention range is 1 4 weeks, you can select backups to occur daily or weekly. 17. In the Select Library and Tape Details page, select the library you want to use for the tape backups. 18. Click Next. 19. Now choose a replica creation method. 20. Click Next to finish the protection group creation. Optional: You may want to backup the Connectivity.ADMSConsole.exe.config and web. config files. These files store unique settings that may not be stored in the vault databases. The files can be found in the following locations: Connectivity.ADMSConsole.exe.config - <install path>\adms [Edition] 20XX Web.config - <install path>\ ADMS [Edition] 20XX\Server\Web\Services 9
Recovering Full Replicated Environment Preparing the Server These instructions are for recovering a full replicated environment on the SQL publisher. DPM Server steps: 1. Open the DPM Administrator Console. 2. Open the Protection tab and expand the protection group that contains the vault databases and file store. 3. Select the file store member and select Create recovery point. 4. In the Create recovery point dialog, select Create a recovery point without synchronizing. This will create a recovery point with all data currently on the DPM server from the last synchronization. 5. Repeat steps 3 and 4 for all folders in the protection group. 6. Stop the protection group in the DPM Administrator Console by right-clicking on the protection group for Autodesk Vault server and select Stop protection of group. Be sure to retain the replicas of the group. This will be used to perform the restore. Install the DPM Agent Manually If the DPM Server is already aware of the old server and believes that it is still attached, then the DPM Protection agent has to be installed manually on the new server. To install a protection agent manually: 1. On the computer on which you want to install the protection agent, we recommend that you map a network drive to the DPM server. For example, from the command prompt, type net use Z: \\DPM1\c$. (Change DPM1 to your DPM server name.) 2. On the protected computer, from the command prompt, change the directory (CD) to z:\program Files\Microsoft DPM\DPM\Agents\RA\2.0.5820.0\i386 (if you have a 64-bit computer, use AM64), and then type DpmAgentInstaller.exe <DPM server name>. For example: DPMAgentInstaller.exe DPM1.Fully.qualified.domain OR On a 64-bit computer, type DPMAgentInstaller_amd64.exe <DPM server name>. Note: If you use the DPM server name in the command line, DPM installs the protection agent and configures the security permissions for the DPM server. 3. You can perform a non-interactive installation by specifying a /q parameter after the DpmAgentInstaller.exe command. For example, type DpmAgentInstaller.exe /q <DPM server name>. 4. Restart the protected server. Note: The following step is not required if you specified the DPM server in Step 1. 5. To complete the protection agent configuration for the appropriate DPM server and firewall settings, from the command prompt, type <drive letter>:\program Files\Microsoft Data Protection Manager\DPM\bin\SetDpmServer.exe dpmservername <DPM server name>. 10
For example: SetDpmServer.exe dpmservername DPM01 Where DPM01 is the actual DPM server name. 6. On the DPM server, from the DPM Management Shell prompt, type Attach- ProductionServer.ps1 <DPM server name> <production server name> <user name> <password> <domain>. Note: The password parameter is not required and we recommend that you do not provide it. DPM will prompt you for a password, which will not appear on the screen. However, you can provide the password if you want to use the script to install a protection agent on a large number of servers. If you are attaching the protected computer on a different domain, you must specify the fully qualified domain name. For example, Computer1.Domain1.corp.microsoft.com, where Computer1 is the name of the protected computer, and Domain1.corp.microsoft.com is the domain to which you are attaching the computer. 7. The required configurations to protect the production computer are created. DPM Administrator Console now displays the production computer. Configuring the Vault Server 1. Re-install the Microsoft Windows Server edition on a new server machine. Give it the same computer name as the original server and join the domain. 2. Install the same version of Microsoft SQL Server as the original server. Install any Microsoft service packs and/or hot fixes that were previously installed. 3. Install the same version of Autodesk Vault server and install any service packs and/or hot fixes that were previously installed. Recovery steps for the Publisher: 1. Create the share folder for the SQL replication snapshots. Apply all user security on the folder and share it. 2. In the DPM Administrator Console, select the Recovery tab. 3. Expand the Recoverable data tree in the left pane and select the Master database. 4. In the middle pane select the date and recovery time. 5. Select the database name in the grid then select the Recover option in the Actions pane. 6. In the Recovery window select the Recover to original instance of SQL Server. Click Next. 7. On the Specify Database State page select the Leave database operational option and click Next. 8. Click Next on the Specify Recovery Options. 9. Click Recover on the Summary page. 10. Repeat steps 1-9 for the MSDB, Master, AutodeskReplication, KnowledgeVaultMaster and each vault and library database. Select the same date and time as the KnowledgeVaultMaster database. 11. In the Recovery tab, select the directory where the SQL replication snap shot share is located under All Protected Volumes. 12. Select the same recovery date as the databases you have restored. 13. Select the SQL snap shot shared folder then select the Recover option. 11
14. Click Next on the Review Recovery Selection. 15. Select Recover to the original location. 16. Click Next on the Specify Recovery Options page. If you are recovering to a remote file store that still exists, you can select the Skip option in the Existing version recovery behavior section. 17. Select the Recover button to start restoring the SQL replication snap shot folder. 18. The file store needs to be recovered if it was on the same server as the databases. In the Recovery tab, select the directory where the file store is located under All Protected Volumes. 19. Select the same recovery date as the databases you have restored. 20. Select the file store folder, then select the Recover option. 21. Click Next on the Review Recovery Selection. 22. Select Recover to the original location. 23. Click Next on the Specify Recovery Options page. If you are recovering to a remote file store that still exists, you can select the Skip option in the Existing version recovery behavior section. 24. Select the Recover button to start restoring the file store. Recovery steps for the Subscriber: 1. In the DPM Administrator Console, select the Recovery tab. 2. Expand the Recoverable data tree in the left pane and select the Master database. 3. In the middle pane select the date and recovery time. 4. Select the database name in the grid, and then select the Recover option in the Actions pane. 5. In the Recovery window select the Recover to original instance of SQL Server. Click Next. 6. On the Specify Database State page select the Leave database operational option. Click Next. 7. Click Next on the Specify Recovery Options. 8. Click Recover on the Summary page. 9. Repeat steps 1-8 for the MSDB, Master, KnowledgeVaultMaster, and each vault and library database. Select the same date and time as the KnowledgeVaultMaster database. 10. The file store needs to be recovered if it was on the same server as the databases. In the Recovery tab, select the directory where the file store is located under All Protected Volumes. 11. Select the same recovery date as the databases you have restored. 12. Select the file store folder then select the Recover option. 13. Click Next on the Review Recovery Selection. 14. Select Recover to the original location. 12
15. Click Next on the Specify Recovery Options page. If you are recovering to a remote file store that still exists, you can select the Skip option in the Existing version recovery behavior section. 16. Select the Recover button to start restoring the file store. Post Recover Steps: 1. 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. 2. With the ADMS Console closed, open a command prompt window. 3. Navigate to <installdir>\autodesk\adms 20XX\ADMS Console directory. 4. At the prompt type: Connectivity.ADMSConsole.exe -VUusername -VPpassword -Ovalidatefilestore This command runs a validation on the file store and databases. This will validate all of the files recorded in the database against the files in the file store. If any files are missing, a dialog will appear with a list of missing files. This list will also be written to in the server s console log. To see if the command is still running, open the Windows Task Manager and look for Connectivity.ADMSConsole.exe in the Processes tab. 5. If any files are missing, you can look at previous recovery points and restore the necessary files. Important Things to Know: It is very important to restore within the default 14 day retention period. If you are restoring a subscriber, the backup used for the restore process must not be older than 14 days. If you do not have a backup within the 14 day retention period, you must delete the subscriber s workgroup in the ADMS Console on the publisher and recreate it. If you are restoring the publisher, the backup used for the restore process must not be older than 14 days from the last synchronization date of all subscribers. 13
Alert Notifications Subscribing to Alert Notifications The System Center Data Protection Manager can be configured to notify a user by e-mail of critical, warning, or informational alerts, and the status of recoveries. To subscribe to notifications: 1. In the DPM Administrator Console, select Options on the Action menu. 2. In the Options dialog box, select the Notifications tab. 3. In the Notifications tab, select the type of alerts about which you want to be notified. 4. Under the Recipients, type the e-mail address of each recipient to whom you want DPM to send copies of the notifications. Use commas to separate the e-mail addresses. 5. To test the notification settings, click the Send Test Notifications, and then click OK. Autodesk [and other products] are either registered trademarks or trademarks of Autodesk, Inc., in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product offerings and specifications at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. 2011 Autodesk, Inc. All rights reserved. 14