I have a DPM server at Site A that I use to backup systems at Site B and Site C. This has been working fine and I have not had an issue until now. I have added more servers to Site B and some new clients and they are backing up to the Site B DPM server and all is good there. I have tested a restore and all seems fine.

I went to add these new systems to be replicated to my server at Site A. Unfortunately, when I modify the protection group on site A, none of the new servers or clients are showing up in the list s being available on the Site B server.

Steps I have tried:

I have updated all servers to DPM 2012 with update Rollup 7 and they show as being on the latest release. No joy seeing the new servers

I have restarted both servers. No joy seeing the new servers

While modifying the Protection Group I clicked on the refresh button for the Site B DPM server. No joy seeing the new servers

Deleted the protection group and added it back in under a different name. No joy seeing the new servers

Checked the WindowsImageBackup and made sure access existed. No joy seeing the new servers

Lastly, my credentials do not let me in as sysadmin on SQL on the site A server. Hopefully I will not need to do anything there.

Cheers

Dave

Hi Dave,

I've managed to solve this problem before by doing the following:

1. Restart the primary DPM-server and wait for it to completely finish the reboot.
2. Restart the secondary DPM-server.
3. Wait 10-15 minutes after the secondary DPM-server is finished rebooting.
4. On the primary DPM-server: Modify the protection group with the "non-listed" servers and click-through the wizard without making any changes.
5. On the secondary DPM-server: On the management tab, right-click you primary DPM-server and click Refresh. When its status is OK, see if your new servers are listed.

I hope this will resolve your problem!

Kind Regards
Markus

Crud. That did not work. Followed the steps you outlined and I am still not seeing any new servers or new clients listed to be backed up. 

Thanks for the advise. Wish it would have worked.

Cheers

Dave

Worked with Roy at Microsoft on this one. What happened is that in January I had to rebuild the primary server and restore the database. There was some issues but working with Microsoft we got these resolved. All was good.

Then came the roll-ups. It looks like the restore does not set the GUID correctly. So, even though DPM had one GUID as the primary, the old GUID was known throughout the rest of the stored procs and never updated. Luckily, it continues to work until the roll-ups are installed. This is a bug that the DPM team has put in to be fixed, but pretty interesting

To find the GUID in the DPM database do

                                      select propertyname, PropertyValue From tbl_DLS_GlobalSetting where PropertyName like 'DPMCategory'<o:p></o:p>

Stored procs are

prc_AM_PSInfo_GetClusterDetails

prc_AM_PSInfo_GetClusterNodes

prc_AM_PSInfo_GetInstalledAgents

prc_AM_PSInfo_GetRGPossibleOwners

prc_AM_PSInfo_GetRGVNMappings

prc_AM_PSInfo_GetServers

prc_AM_PSInfo_GetServerTimeZone

prc_AM_PSInfo_TempProtectedServersList_Create

prc_AM_PSInfo_TempProtectedServersList_Finalize

prc_AM_PSInfo_TempProtectedServersList_Insert

prc_ARM_FileGen_AddDirOrFile

prc_ARM_FileGen_CreateCumulativeFileListTable

prc_ARM_FileGen_CreateFileListTable

prc_ARM_FileGen_DeleteTempTables

prc_ARM_FileGen_GenerateFile

prc_ARM_FileGen_GetMediaList

prc_ARM_Pruning_CreateDatasetListTable

prc_ARM_Pruning_CreateDataSourceListTable

prc_ARM_Pruning_CreateDependentDatasetListTable

prc_ARM_Pruning_InsertOldestFullDataset

prc_ARM_Pruning_IsDatasetListEmpty

prc_ARM_Pruning_IsDatasourceListEmpty

prc_ARM_Pruning_PopulateAllDependentDatasets

prc_ARM_Pruning_PopulateDataSourceList

prc_ARM_Pruning_PopulateNonExpiredDependentDatasets

prc_ARM_Pruning_PruneDirAndFileTable

prc_ARM_Pruning_PrunePathTable

prc_ARM_Pruning_PruningPolicy_PopulateDatasetList

prc_ARM_Pruning_RemoveDependentDatasets

prc_ARM_Pruning_TruncateDatasetListTable

prc_ARM_Pruning_TruncateDataSourceListTable

prc_ARM_Pruning_TruncateDependentDatasetListTable

Cheers

• Marked as answer by DGRAHAM4 11 hours 15 minutes ago

Worked with Roy at Microsoft on this one. What happened is that in January I had to rebuild the primary server and restore the database. There was some issues but working with Microsoft we got these resolved. All was good.

Then came the roll-ups. It looks like the restore does not set the GUID correctly. So, even though DPM had one GUID as the primary, the old GUID was known throughout the rest of the stored procs and never updated. Luckily, it continues to work until the roll-ups are installed. This is a bug that the DPM team has put in to be fixed, but pretty interesting

To find the GUID in the DPM database do

                                      select propertyname, PropertyValue From tbl_DLS_GlobalSetting where PropertyName like 'DPMCategory'<o:p></o:p>

Stored procs are

prc_AM_PSInfo_GetClusterDetails

prc_AM_PSInfo_GetClusterNodes

prc_AM_PSInfo_GetInstalledAgents

prc_AM_PSInfo_GetRGPossibleOwners

prc_AM_PSInfo_GetRGVNMappings

prc_AM_PSInfo_GetServers

prc_AM_PSInfo_GetServerTimeZone

prc_AM_PSInfo_TempProtectedServersList_Create

prc_AM_PSInfo_TempProtectedServersList_Finalize

prc_AM_PSInfo_TempProtectedServersList_Insert

prc_ARM_FileGen_AddDirOrFile

prc_ARM_FileGen_CreateCumulativeFileListTable

prc_ARM_FileGen_CreateFileListTable

prc_ARM_FileGen_DeleteTempTables

prc_ARM_FileGen_GenerateFile

prc_ARM_FileGen_GetMediaList

prc_ARM_Pruning_CreateDatasetListTable

prc_ARM_Pruning_CreateDataSourceListTable

prc_ARM_Pruning_CreateDependentDatasetListTable

prc_ARM_Pruning_InsertOldestFullDataset

prc_ARM_Pruning_IsDatasetListEmpty

prc_ARM_Pruning_IsDatasourceListEmpty

prc_ARM_Pruning_PopulateAllDependentDatasets

prc_ARM_Pruning_PopulateDataSourceList

prc_ARM_Pruning_PopulateNonExpiredDependentDatasets

prc_ARM_Pruning_PruneDirAndFileTable

prc_ARM_Pruning_PrunePathTable

prc_ARM_Pruning_PruningPolicy_PopulateDatasetList

prc_ARM_Pruning_RemoveDependentDatasets

prc_ARM_Pruning_TruncateDatasetListTable

prc_ARM_Pruning_TruncateDataSourceListTable

prc_ARM_Pruning_TruncateDependentDatasetListTable

Cheers

• Marked as answer by DGRAHAM4 Friday, September 11, 2015 8:25 PM