Operational Defect Database
BugZero updated this defect 57 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 97131
Site Recovery Manager Configuration Data import fails - Unable to update protection settings for datastore, datastore not found
Last update date:
3/23/2024
Affected products:
Site Recovery Manager
Affected releases:
8.x
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Importing SRM configuration data fails with the below warnings - Create protection groups. Unable to update protection settings for datastore 'Prod-SQL'. Datastore not found.Create protection groups. Unable to update protection settings for datastore 'DB-Servers'. Datastore not found. Create protection groups. Unable to create VM protection group: 'Prod-SQL'. A specified parameter was not correct: Empty array of datastores not allowed.Create protection groups. Unable to create VM protection group: 'DB-Servers'. A specified parameter was not correct: Empty array of datastores not allowed.
Cause
SRM applies snap-xx prefix to recovered datastore names. Configuration import cannot detect these datastores until they are changed to their original names.
Impact / Risks
Configuration data import through the user interface fails partially.
Resolution
Rename all the snap-xx prefixed datastores back to their original names. Change Datastore Name
Related Information
Renaming a datastore when virtual machines are running on the datastore (1006279) - https://kb.vmware.com/s/article/1006279Change Storage Provider SettingsImport the Site Recovery Manager Configuration Data through the User Interface
