Microsoft System Center Data Protection Manager

After you installed DPM agent on the protected server which is not on the same domain as DPM server you have to run: On Protected Server in elevated command prompt navigate to : C:\Program Files\Microsoft Data Protection Manager\DPM\bin and run: SetDpmServer.exe –dpmServerName DPMSERVERNAME(FQDN) -isNonDomainServer -userName dpmaccount -productionserverdnssuffix domainname where dpmaccount – give some name to the new account with password Example: On the DPM Server you can run script Attach-NonDomainServer.ps1 in DPM PowerShell: PS C:\Program Files\Microsoft DPM\DPM\bin\Attach-NonDomainServer.ps1 Enter DPM server name, Protected server FQDN and the same credentials you use for configuration on the protected server: Or you can use … Continue reading Configuration DPM Protection of the servers which are not on the same domain as DPM server

Sometimes Protected Computers are decommissioned and you even didn’t uninstall DPM agent on it. In this case this Computer will be stacked under ‘Unprotected computers’group in the DPM Console. You can remove it using script – remove-productionserver.ps1 Go to the DPM server, open DPM PowerShell and run script: 1. Enter DPM server name (ec-ms-scdpm-01); 2.Enter FQDN of the protected computer (ec-ms-adfs2.vsb.bc.ca) Done.

If you successfully installed DPM agent and was able to configure PG for Drives and System State, but SQL Server Dabase doesn’t show up in DPM configuration console, check ‘SQL server VSS writer services’ on the server you want to protect. If the service is missing you will not be able to View the SQL Server database under protected server in DPM protection tab for backup and configuration: For SQL Server 2012 be sure that ‘sysadmin’ check box was ‘checked’ in the Server Roles (see screenshot):

If you are running Sophos as your Anti Virus software it is possible that the error like this: Affected area:    C:\ Occurred since:    1/20/2014 12:36:02 AM Description:    The replica of Volume C:\ on EC-SYNRV-SRV01.vsb.bc.ca is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent. For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check … Continue reading Troubleshooting error: (ID 112 Details: Cannot create a file when that file already exists (0x800700B7))

All information concerning DPM backup (tape’s barcodes, protection groups, dates and time, schedule, policy etc.) is stored in centralized SQL Server Database DPMDB DPM/SQL Performance DPM is largely depending on its SQL database. All settings, jobs and recovery information is hold in the DPM database. When the DPM database has performance issues then this will also impact the performance of the DPM console. One of the possible performance issue are fragmented Indexes in your database. The Report Index Physical Statistics show the status of the fragmentation Rebuild indexes When the indexes are heavily fragmented then you need to rebuild them. … Continue reading Essential information to work with DPM