> CommCell Console > Backup and Restore Agents > Snapshot Management > Supported Agents > Microsoft Hyper-V > Troubleshooting

Troubleshooting - Known Issues for IntelliSnap Operations with Windows Server 2016 and Windows Server 2019

For various IntelliSnap backup operation and backup copy operation scenarios, the following limitations apply:

  • The proxy host designated cannot be a member of the cluster nodes where the source VM resides.

  • There is a Microsoft limitation for Disk Signature changes.

For more information about these limitations and the backup operations they apply to, refer to the following table:

Scenario

Applicable Limitations

When granular metadata collection is enabled for IntelliSnap backup operations

  • The proxy host designated for the IntelliSnap backup operations cannot be a member of the cluster nodes where the source VM resides.

    To correctly designate the proxy host (MediaAgent) for this scenario, follow these steps:

    1. From the CommCell Browser, expand Client Computers > virtualization_client > Virtual Server > instance > DefaultBackupSet.

    2. Right-click the default subclient, and then click Properties.

    3. In the Subclient Properties dialog box, click the IntelliSnap Operations tab.

    4. From the Use Proxy drop-down list box, select the MediaAgent accordingly.

  • There is a Microsoft limitation for Disk Signature changes.

    You cannot implement Disk Signature changes at this time

When granular metadata collection is enabled for snapshot mount operations during IntelliSnap backup operations, a File Level Restore or Full VM restore from IntelliSnap backup operations and backup copy operations.

  • The proxy host designated for the IntelliSnap backup operations cannot be a member of the cluster nodes where the source VM resides.

    For for snapshot mount operations, rather than designate a different host, you can spawn up a VM and use it as a node.

    1. Enable the Hyper-V role on the Hyper-V VM.

    2. Install VSA and MediaAgent packages on the VM.

    3. If LUNs are iSCSI-connected, enable iSCSI and add this Hyper-V VM node on the iSCSI array.

    4. If LUNs are FC-connected, attach the virtual fibre channel adapter to the VM, and then zone the WWPN with the array WWPN for connectivity.

  • There is a Microsoft limitation for Disk Signature changes.

    You cannot implement Disk Signature changes at this time

For File Level Restore or Full VM restore from IntelliSnap backup operations

  • The proxy host designated for the restore operations cannot be a member of the cluster nodes where the source VM resides.

    To designate the proxy host (MediaAgent) for this scenario, follow these steps:

    1. From the CommCell Browser, expand Client Computers > virtualization_client > Virtual Server > instance > DefaultBackupSet.

    2. Right-click the subclient, and then select Browse and Restore.

    3. From the Browse and Restore Options dialog box, select the Advanced Options tab.

    4. From the Use MediaAgent drop-down list box, select the MediaAgent accordingly.

  • There is a Microsoft limitation for Disk Signature changes.

    You cannot implement Disk Signature changes at this time.

For backup copy operations

This includes Cluster Shared Volume (CSV) storage snapshots.

  • The proxy host designated for backup copy operations cannot be a member of the cluster nodes where the source VM resides.

    To designate the proxy host (MediaAgent) for this scenario, follow these steps:

    1. From the CommCell Browser, expand Client Computers > virtualization_client > Virtual Server > instance > DefaultBackupSet.

    2. Right-click the default subclient, and then click Properties.

    3. In the Subclient Properties dialog box, click the IntelliSnap Operations tab.

    4. From the Use Proxy drop-down list box, select the MediaAgent accordingly.

  • There is a Microsoft limitation for Disk Signature changes.

    You cannot implement Disk Signature changes at this time.
×

Loading...