SnapCenter and SQL AvailabilityGroup

[sanderbreur]

Hi,

during install of SnapCenter 1.1 youve got the option "install local SQL express DB or use an existing SQL server/instance.

We have an SQL Availability Group (AG) so we chose the second option for a existing host.

Now, if we use the AG name with windows credentials install fails with error 1603 in the log.

If we do the same but use a nodename/instance of the same AG install finishes fine and DB is added to the node.

However, this is nog the way we want it because with a AG host failover DB's become stale.

So, is there a workaround to use the AG name during install?

[Sahana]

Hi,

Try using the cmdlet Add-SmBackupDataset  Refer https://library.netapp.com/ecm/ecm_get_file/ECMLP2440057 

Refer page 8 Resources: For availability group backup @{"Host"="localhost";"Type"="SQL Availability Group";"Names"="AG1"} Valid Type values are: SQL Database, SQL Instance, SQL Availability Group. You can include comma-separated values for Names. 

[neerajd]

hi sanderbreur,

If you want to have SnapCenter Repository (NSM)database on AG, you should install on primary host of AG by giving Hostname\Instance. Once the installtion of SnapCenter is done. you need to migrate the NSM to Netapp lun. using protect-smrepository. Once NSM is on NetApp lun manually create NSM database on AG. 

you need to change the web.config file using C:\inetpub\wwwroot\SnapCenter\Web.config

change <DBServer> value= "AG lister name and port"

example: 
<add key = "DBServer" value="ag-list-nam, 5010"/>

once done same the changes and restart SMCORE "SnapCenter SMCore Service" server in SnapCenter.

Please refer documentation of SnapCenter Plugin for MSSQL under session:

"Prerequisites for protecting snapcenter repository". 

if you need help please reach out to netapp support they should able to help you. 

Thanks

Neeraj