Data Protection

default snapshot name case in SCS vs ONTAP

JS75
811 Views

Hello

 

Does anyone know the reason for default snapshot names in SnapCenter begin uppercase like 'Daily', 'Weekly', while ONTAP defaults to all lower 'daily', 'weekly' etc. Since snapshot names are case sensitive it's causing confusion and complexity with protection policies.

 

thanks,

Jacek

1 ACCEPTED SOLUTION

PravinKumar
450 Views

Hi Jacek,

 

Thank you for the clarification.

 

Snapshot label is case sensitive, you shall edit the resource group on Snapcenter /SCV and update the custom snapshot label matching your ONTAP snapshot label.

 

Refer below documents:

 

SCV: https://docs.netapp.com/us-en/sc-plugin-vmware-vsphere/scpivs44_create_backup_policies_for_vms_and_datastores.html

Snapcenter: https://docs.netapp.com/us-en/snapcenter/protect-mysql/create-backup-policies-for-mysql.html

 

Thanks and Regards,

Pravin Kumar

View solution in original post

4 REPLIES 4

PravinKumar
486 Views

Hi Jacek,

 

Snapshots created by Snapcenter will start with the Resource group name. For example, in the output provided below, the snapshot names under the volume 'nfs1' beginning with 'RG1' were created by Snapcenter, whereas the rest were created by ONTAP.

 

To customize your snapshot names, For more detailed information, please refer to the following documents:

- [Create resource groups for VMs and datastores on Snapcenter plugin for VMware vSphere(SCV)](https://docs.netapp.com/us-en/sc-plugin-vmware-vsphere/scpivs44_create_resource_groups_for_vms_and_datastores.html)

- [Create resource groups and attach policies on SnapCenter](https://docs.netapp.com/us-en/snapcenter/protect-mysql/create-resource-groups-and-attach-policies.html)

 

Here is the output for your reference:

 

cluster1::> volume snapshot show

                                                                 ---Blocks---

Vserver  Volume   Snapshot                                  Size Total% Used%

-------- -------- ------------------------------------- -------- ------ -----

cluster1-01

         vol0

                  hourly.2                               503.1MB     6%   10%

                  hourly.1                               272.0MB     3%    6%

                  hourly.0                               285.5MB     3%    6%

                  nightly.0                              307.9MB     3%    7%

svm1_cluster1

         nfs1

                  RG1_04-29-2025_02.01.30.0564            1.13MB     0%    0%

                  snapmirror.2e8aaaf9-a887-11ed-a505-005056b098c9_2149176056.2025-04-29_020500

                                                           896KB     0%    0%

                  RG1_04-29-2025_02.06.01.0578            1.02MB     0%    0%

                  RG1_04-29-2025_02.11.13.0867             392KB     0%    0%

 

If my understanding is not correct, could you please share the sample output with me? I'll be more than happy to check and get back to you.

 

Thanks and Regards,

Pravin Kumar

JS75
453 Views

Hello Pravin,

 

I made a mistake - what I meant was the SnapMirror Label case mismatch. The default SnapMirror labels for ONTAP created snapshots are 'daily' and 'weekly' while the same for SCS and SCV are 'Daily' and 'Weekly'.

 

PravinKumar
451 Views

Hi Jacek,

 

Thank you for the clarification.

 

Snapshot label is case sensitive, you shall edit the resource group on Snapcenter /SCV and update the custom snapshot label matching your ONTAP snapshot label.

 

Refer below documents:

 

SCV: https://docs.netapp.com/us-en/sc-plugin-vmware-vsphere/scpivs44_create_backup_policies_for_vms_and_datastores.html

Snapcenter: https://docs.netapp.com/us-en/snapcenter/protect-mysql/create-backup-policies-for-mysql.html

 

Thanks and Regards,

Pravin Kumar

JS75
448 Views

Sure, I can do that. My concern was on why it's created this way that one NetApp product (ONTAP) uses lowercase while the other (SCS/SCV) use first-upper. It's quite confusing and I either have to create separate snapmirror policies for 'daily' and 'Daily' or combine two labels in one policy. Is there any specific reason NetApp did that this way?

 

Thanks

Jacek

Public