Hi Heino,
I have answered your questions below:
1. Do we need to create 3 different configurations for this setup? Or is there any variables we can use in the SnapManager for SQL section where we define the commandline string to be executed by SMSQL ?
You could create 3 configs and this might be the easiest but you can also make it work with one config, here is how:
# SMSQL_BACKUP_OPTIONS=-svr 'SQL' -d 'SQL\SHAREPOINT', '1', 'WSS_Content' -RetainBackups 7 #
# -lb -bksif -RetainSnapofSnapInfo 8 -trlog -gen -mgmt standard
The above parameter tells SCF which SMSQL policy to run. What you could do is set this to %USER_DEFINED
SMSQL_BACKUP_OPTIONS=%USER_DEFINED
Now you could pass in what backup options you want through CLI or GUI as follows:
./snapcreator --user <user> --passwd <passwd> --action backup --policy <policy> --params USER_DEFINED=-svr 'SQL' -d 'SQL\SHAREPOINT', '1', 'WSS_Content' -RetainBackups 7 -lb -bksif -RetainSnapofSnapInfo 8 -trlog -gen -mgmt standard --verbose
I realise this isnt very nice but it is an option. I think you can also specify several parameters if that helps. For example: --params PARAM1=foo PARAM2=bar PARAM3=foobar
Then these can be referenced in config as %PARAM1 %PARAM2 %PARAM3
You need to make sure there is a space before and after %<PARAMETER> otherwise I think the parser assumes it is not a reference.
2. Do we need to specify any of the Snapshot, SnapMirror, SnapVault section in SC ? Doesn't SMSQL control all this?
If you want SC to actually do the mirror or vault update then you would need to do this. It sounds like you are using snapshot labels, in this case SMSQL creates label and ONTAP would do update. There is another option however. You can turn off snapshot label creatin in SMSQL and just create normal snapshots. SCF could then vault or mirror these.
To do this you would need to enable following:
NTAP_USE_EXTERNAL_SNAPSHOT=Y - this allows SC to manage snapshot created from other applications such as SnapManagers. On limitation is SC can only handle one snapshot per volume, if you have everything on one volume SMSQL will create multiple snapshots, we are supporting this in future release.
NTAP_SNAPVAULT_UPDATE=Y
VOLUMES=controller1:volume1,volume2
SNAPVAULT_VOLUMES=controller1:volume1,volume2
You need to create vault or mirror relationships on your own SCF, does not do this. In addition if you are doing vault or mirror through another interface, like a data interface then you need to set following:
SECONDARY_INTERFACES=controller1:controller1-data/controller2-data
This maps the primary controller to its primary data mgmt interface and it secondary data mgmt interface
As for SMSQL case, if you can get labels working this is probably easiest assuming you want controller to do the vault and mirror updates and want to configure these policies on controller.
We are working on greatly improving the integration with SC and our windows SnapManagers and any feedback on what you would like to see, use cases you are solving, and more environment details would really help?
Regards,
Keith
