Troubleshooting SMVI Single File Restore

by Frequent Contributor on ‎2010-05-27 09:05 AM

Here is information to troubleshoot SFR issues:

  • SFR only works with backups performed by SMVI 2.0 or later.
  • You must have flex-clone license to restore files from VMs stored on NFS datastore.
    • Since the SMVI server uses a custom SSL certificate, you may see a warning in your browser while downloading the Restore Agent installer.
    • ESX 3.5 supports only eight NFS datastores by default. Refer to KB Article 2239, TR 3428 or TR 3749 for details on how to increase that number to 32.
    • SFR is not supported for IDE disks. If the VM has SCSI and IDE disks, you can use SFR for SCSI disks only. SFR is also not supported on dynamic disks
    • This is the checklist for Restore Agent installer issues:

-       On Windows 2008 R2, .NET framework is a feature of the Operating System and must be enabled before Restore Agent can be installed.

-       You must run the RA installer as a user who is a member of the administrators group.

  • This is the checklist for disk mounting issues:

-       RA only supports the first partition on a virtual disk. For other partitions, you have to manually use the Disk Management or diskpart tool.

-       RA only supports NTFS/FAT-formatted partitions on a disk.

-       SMVI can't add new SCSI controllers to power on a destination VM. Therefore the number of disks that can be attached to a VM are restricted by the available free slots on existing SCSI controllers. A VM can have a maximum of 60 disks (15 slots on 4 SCSI controllers).

-       The automount feature is by default enabled for Windows XP and Vista. Therefore on VMs running these operating systems, you may see that drive letters are preassigned to all the disks (and partitions).

  • There needs to be network connectivity between the target VM and vCenter for a Self Service SFR
  • This is the checklist for VM startup issues:

-       In some VMware operation failures, SMVI may not be able to detach all disks from a VM after the SFR session is expired or deleted. In such cases, the VM startup issues could be due to the stale disks that are left attached to the VM. In most cases, such stale disks can be removed by powering off the VM and then editing the VM settings. Double-check the VMDK path before you remove these disks from a VM.

-       If you are unable to power on the destination VM after using it for SFR, make sure that there are no stale disks left on the destination VM. Typically this would happen for the following conditions:

  • A hosted process on an ESX server crashes while attaching a disk
  • An attach operation fails to complete due to VMware error

For SFR NetApp recommends that the source and destination VMs have the latest VMware Tools running.You should also configure global notification settings before you can successfully use the SFR feature, since the workflow uses e-mail to send out details like the Restore Agent installer link and a configuration file. A VM that has a network assigned on a distributed vSwitch cannot be selected from the SFR wizard; then you would have to manually enter the VM name while creating the SFR session. NetApp recommends that port 8043 be open on the SMVI server if there are firewalls on vCenter or the guest(s) involved in SFR if it is a Self Service SFR

Warning!

This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.

In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information
  • Copyrighted materials without the permission of the copyright owner

Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.