If you are protecting data that changes frequently throughout the day, you may want to synchronize your data hourly. You can choose between two modes of synchronization: Only before each shadow copy is created or Nearly-continuous (hourly). DPM relies on synchronization to keep replicas synchronized with the protected data on the file servers. Synchronization is the process by which Data Protection Manager (DPM) transfers data changes from a protected file server to a DPM server, and then applies the changes to the replica of the protected data. One of the parameters you setup during Protection Group configuration is synchronization. SET = ‘ALTER INDEX ALL ON ‘ + + ‘ REBUILD WITH (FILLFACTOR = ‘ + + ‘)’ĮXEC NEXT FROM TableCursor INTO TableCursor SELECT OBJECT_SCHEMA_NAME()+’.’+name AS TableName Therefore we use the script below which will rebuild every index existed in database with fillfactor of 80. You can do that by hand, but that’s a ‘hell of a job’. When the indexes are heavily fragmented then you need to rebuild them. The Report Index Physical Statistics show the status of the fragmentation One of the possible performance issue are fragmented Indexes in your database. When the DPM database has performance issues then this will also impact the performance of the DPM console. All settings, jobs and recovery information is hold in the DPM database. All information concerning DPM backup (tape’s barcodes, protection groups, dates and time, schedule, policy etc.) is stored in centralized SQL Server Database DPMDBĭPM is largely depending on its SQL database.