VSC 6.2.1 with SnapCenter 2.0

nicholsongc — Wed, 04 Jun 2025 14:56:20 GMT

Is there a limitation with mounting a snapshot/backup containing more than one (1) LUN in a volume?

I have a single volume with five (5) LUNs.

/vol/user_data/User_lun_1

/vol/user_data/User_lun_2

/vol/user_data/User_lun_3

/vol/user_data/User_lun_4

/vol/user_data/User_lun_5

Each LUN is presented to an ESX host as a datastore.

Each datastore contains two (2) VMDKs (7TB each)

I have a VM with all 10 VMDKs added to its disk configuration.

It is a Windows 2012 server with all 10 disks spanned to create a single ~70TB volume.

OK - don't ask why it was setup this way... but it preceeds my employment...

I create/run a backup job to backup the VM - including all spanned entities

Backup runs without error and I am able to see the snapshot listed in the volume (user_data)

When I try to MOUNT the backup in VSC to recover files:

Mount operation clones the snapshot.

I am able to see the temp volume and the contained five (5) LUNs within

However, only "User_lun_5" is mapped.

Therefore only "User_lun_5" is listed in the VSC GUI as a datastore to mount to my ESX host

The result is that I do not have ALL VMDKs available to re-create the spanned volume/disk to complete my restore.

When this approach is used WITHOUT SnapCenter 2.0 integrated with VSC 6.2.1P1D1 the process works as designed. Which leads back to my question:

Is there a limitation with mounting a snapshot/backup containing more than one (1) LUN in a volume?

Re: VSC 6.2.1 with SnapCenter 2.0

Jeff_Yao — Wed, 28 Jun 2017 05:24:42 GMT

try this to see if helps

nicholsongc — Wed, 02 Aug 2017 16:03:47 GMT

So the official word from NetApp is that ONE LUN PER VOLUME is the rule... therefore only ONE LUN will be visible for mounting.

My question continues to be: "How does VSC pick the particular LUN out of a choice of five (in my example)?"

Stick to Best Practice (1 LUN per volume) and this will not be an issue.