Solved

NAS client configuration for intellisnap for 'generic' volumes

  • 31 August 2023
  • 2 replies
  • 38 views

Userlevel 1
Badge +5

Hello. Will greatly appreciate your feedback/guidance here. 

 I need to enable intellisnap for subclients with the data on a netapp source. It’s vmware, and supposedly volumes that are “just volumes”: not nfs, not cifs or anything specfic to a particular application. The customer “doesn’t want NDMP in the environment”. I see in the NAS client there is, ndmp, nfs and cifs as options.  How can I configure the nas client to snap ‘generic’ or just ‘ad hoc’ volumes for lack of a better way to describe them without using the ndmp or nfs or cifs agents under the CV NAS client ? I am not seeing a way to do this. The storage policy is set up with a snap primary copy for the source and a vault/replica copy to a destination netapp. The customer doesn’t want ndmp used and doesn’t want streaming method used. Is this even possible ?

Thank you!

 

icon

Best answer by Damian Andre 1 September 2023, 03:49

View original

2 replies

Userlevel 7
Badge +23

Hi @mzator,

Generic volume support does not really exist - Commvault’s job is to backup the application and hence there should be an application level attachment to the storage using the correct agent (VSA in this case).

I understand what the customer wants to achieve -  But Commvault is all built around consistency for the app to ensure successful retoration. Backing up a raw volume while applications are writing data is a really poor strategy and bound to cause consistency issues - if anything it may be a good last ditch effort if other recovery methods fail, but I would not trust the data on those volumes protected in this way.

The correct way to do this is an intellisnap enabled VSA backup, which ensures the VM is consistent inside the guest, and the VM disk is made consistent via VMware VADP snapshot.

The customer may be better off scheduling volume level snapshots from within NetApp, as Commvault isn't really adding any value without orchestrating the consistency other than perhaps managing the retention.

Another not-recommended way to do this is to create a single VM with Intellisnap and ensure it has VMDK disks on each volume/datastore the customer wants to backup and replicate. Every volume will be snapped and replicated as without using something like VVOL, you can’t just replicate data for a single VM on a volume - the whole volume must be included.

To restore, you’d mount the VM using the vault copy and then copy the data off those volumes manually. Really dirty way to achieve this outcome and I would not recommend it!

Userlevel 1
Badge +5

Thank you Damien this is really helpful and useful information. 

Reply