Restoring VMware data
\n\n\n\n\nVMware restore jobs support Instant VM Restore and Instant Disk Restore scenarios, which\nare created automatically based on the selected source.
\n\nBefore you begin
- \n
- Ensure that a VMware backup job was run at least once. For instructions, see Backing up VMware data. \n\n
- Ensure that appropriate roles are assigned to IBM Spectrum® Protect\nPlus users so that they can complete backup and\nrestore operations. Grant users access to hypervisors and backup and restore operations through the\nAccounts pane.\nFor\nmore information, see Managing user access and Managing user accounts. \n\n
- Ensure that the destination that you plan to use for the restore job is registered in IBM Spectrum Protect\nPlus. This requirement applies to restore jobs that\nrestore data to original hosts or clusters. \n\n
- When restoring a virtual machine by using clone mode and by using the original IP configuration,\nensure that credentials are established through the Guest OS Username and\nGuest OS Password options within the backup job definition. \n\n
About this task
If a VMDK is selected for restore operation, IBM Spectrum Protect\nPlus automatically presents options for an Instant\nDisk restore job, which provides instant writable access to data and application restore points. An\nIBM Spectrum Protect\nPlus snapshot is mapped to a target server\nwhere it can be accessed or copied as required.
\n\nAll other sources are restored through Instant VM restore jobs, which can be run in the following\nmodes:
\n\n- \n\n\n\n
- Production mode \n\n
- Production mode enables disaster recovery at the local site from primary storage or a remote\ndisaster recovery site, replacing original machine images with recovery images. All configurations\nare carried over as part of the recovery, including names and identifiers, and all copy data jobs\nassociated with the virtual machine continue to run. As part of a production mode restore, you can\nopt to replace the storage in the virtual machine with a virtual disk from a previous virtual\nmachine backup. Select \n\n\n\n
- Test mode \n\n
- Test mode creates temporary virtual machines for development or testing, snapshot verification,\nand disaster recovery verification on a scheduled, repeatable basis without affecting production\nenvironments. Test machines are kept running as long as needed to complete testing and verification\nand are then cleaned up. Through fenced networking, you can establish a safe environment to test\nyour jobs without interfering with virtual machines used for production. Virtual machines that are\ncreated in test mode are also given unique names and identifiers to avoid conflicts within your\nproduction environment. \n\n\n\n
- Clone mode \n\n
- Clone mode creates copies of virtual machines for use cases that require permanent or\nlong-running copies for data mining or duplication of a test environment in a fenced network.\nVirtual machines created in clone mode are also given unique names and identifiers to avoid\nconflicts within your production environment. With clone mode, you must be sensitive to resource\nconsumption because clone mode creates permanent or long-term virtual machines.\n\nNote: Restoring a VM in test mode or clone mode without selecting a fenced network might interfere\nwith production VMs and network services. For instructions for creating a fenced network, see Creating a fenced network through a VMware restore job.\n\n \n\n\n
The size of a virtual machine that is restored from a vSnap copy to an IBM Spectrum\nProtect restore point will be equal to the thick\nprovisioned size of the virtual machine, regardless of source provisioning due to the use of NFS\ndatastores during the copy operation. The full size of the data must be transferred even if it is\nunallocated in the source virtual machine.
\n\nWhen you restore VMware data from an IBM Spectrum\nProtect\narchive, files initially will be migrated from tape to a staging pool. Depending on the size of the\nrestore operation, this process could take several hours.
\n\n\n
\n\nRestriction: Windows file indexing and file\nrestore on volumes residing on dynamic disks is not supported.
\n\nProcedure
To define a VMware restore job, complete the following steps:
- \nIn the navigation panel, click Manage Protection > Virtualized Systems > VMware > Create job, and\nthen select Restore to open the Restore wizard. \n\n\nTips: \n\n\n
- \n
- You can also open the wizard by clicking Jobs and Operations > Create job > Restore > VMware. \n\n
- For a running summary of your selections in the wizard, click Preview\nRestore in the navigation panel in the wizard. \n\n
- The wizard is opened in the default setup mode. To run the wizard in advanced setup mode, select\nAdvanced Setup. With advanced setup mode, you can set more options for your\nrestore job. \n\n
\n - \nOn the Select source page, take the following actions: \n
- \n
- \nReview the available sources, including virtual machines (VMs) and virtual disks (VDisks). Use\nthe View filter to toggle the displayed sources to show hosts and clusters,\nVMs, or tags and categories. You can expand a source by clicking its name. \n\n\n
You can also enter all or part of a name in the Search for box to locate\nVMs that match the search criteria. You can use the wildcard character (*) to represent all or part\nof a name. For example,
\n\nvm2*represents all resources that begin with \"vm2\". \n\n - \nClick the plus icon
![\"Plus](\"spp_images/plus.png\")
next to the item that you want to add to the restore list next to the list of sources. You\ncan add more than one item of the same type (VM or virtual disk). \n\n\nTo remove an item from the restore list, click the minus icon
\n\n![\"Minus](\"spp_images/remove.png\")
next to the item. \n\n - \nClick Next.\n \n\n
\n - \nReview the available sources, including virtual machines (VMs) and virtual disks (VDisks). Use\nthe View filter to toggle the displayed sources to show hosts and clusters,\nVMs, or tags and categories. You can expand a source by clicking its name. \n
- \nOn the Source snapshot page, select the type of restore job that you want\nto create: \n
- \n\n
- On-demand \n\n
- Runs a one-time restore operation. The restore job starts immediately upon the completion of the\nwizard. \n\n\n\n
- Recurring \n\n
- Creates a repeating point-in-time restore job that runs on a schedule. \n\n\n
\n - \nComplete the fields on the Source snapshot page and click\nNext to continue. \nThe fields that are shown depend on the number of items that were selected on the\nSelect source page and on the restore type. Some fields are also not shown\nuntil you select a related field.\n\n\n\n
Fields that are shown for an on-demand, single resource restore
\n\n\n
\n\nOption \nDescription \n \nDate range \n\nSpecify a range of dates to show the available snapshots within that range. \n\n\n \nBackup storage type \n\nAll backups in the selected date range are listed in rows that show the time that the backup\noperation occurred and the service level agreement (SLA) policy for the backup. Select the row that\ncontains the backup time and SLA policy that you want, and then take one of the following\nactions: \n\n- \n
- Click the backup storage type that you want to restore from. The storage types that are shown\ndepend on the types that are available in your environment and are shown in the following order:
- \n\n
- Backup \n\n
- Restores data that is backed up to a vSnap server. \n\n\n\n
- Replication \n\n
- Restores data that is replicated to a vSnap server. \n\n\n\n
- Object Storage \n\n
- Restores data that is copied to a cloud service or to a repository server. \n\n\n\n
- Archive \n\n
- Restores data that is copied to a cloud service archive or to a repository server archive\n(tape). \n\n\n
\n\n - Click anywhere on the row. The first backup type that is shown sequentially from the left of the\nrow is selected by default. For example, if the storage types Backup,\nReplication, and Archive are shown,\nBackup is selected by default. \n\n
\n \nUse alternate vSnap server for the restore job \n\nIf you are restoring data from a cloud service or a repository server, select this box to\nspecify an alternative vSnap server, and then select a server from the Select alternate\nvSnap menu. \n\nWhen you restore data from a restore point that was copied to a cloud\nresource or repository server, a vSnap server is used as a gateway to complete the operation. By\ndefault, the vSnap server that is used to complete the restore operation is the same vSnap server\nthat is used to complete the backup and copy operations. To reduce the load on the vSnap server, you\ncan select an alternative vSnap server to serve as the gateway.
\nFields that are shown for an on-demand snapshot, multiple resource restore or recurring\nrestore\n\n\n
\n\nOption \nDescription \n \nRestore Location Type \n\nSelect a type of location from which to restore data: \n\n- \n\n
- Site \n\n
- The site to which snapshots were backed up. The site is defined in the System Configuration > Site pane. \n\n\n\n
- Cloud service \n\n
- The cloud service to which snapshots were copied. The cloud service is defined in the System Configuration > Backup Storage > Object Storage pane. \n\n\n\n
- Repository server \n\n
- The repository server to which snapshots were copied. The repository server is defined in the System Configuration > Backup Storage > Repository Server pane. \n\n\n\n
- Cloud service archive \n\n
- The cloud archive service to which snapshots were copied. The cloud service is defined in the System Configuration > Backup Storage > Object Storage pane. \n\n\n\n
- Repository server archive \n\n
- The repository server to which snapshots were copied to tape. The repository server is defined\nin the System Configuration > Backup Storage > Repository Server pane. \n\n\n
\n \nSelect a location \n\nIf you are restoring data from a site, select one of the following restore locations: \n\n- \n\n
- Demo \n\n
- The demonstration site from which to restore snapshots. This\nmenu item is available only if you updated the product from IBM Spectrum Protect\nPlus Version 10.1.6 or earlier. \n\n\n\n
- Primary \n\n
- The primary site from which to restore snapshots. \n\n\n\n
- Secondary \n\n
- The secondary site from which to restore snapshots. \n\n\n
If you are restoring data from a cloud or repository server, select a server from the\nSelect a location menu.
\n\n \nDate selector \n\nFor on-demand restore operations, specify a range of dates to show the available snapshots\nwithin that range. \n\n\n \nRestore Point \n\nFor on-demand restore operations, select a snapshot from the list of available snapshots in\nthe selected date range. \n\n\n \nUse alternate vSnap server for the restore job \n\nIf you are restoring data from a cloud service or a repository server, select this box to\nspecify an alternative vSnap server, and then select a server from the Select alternate\nvSnap menu. \n\nWhen you restore data from a restore point that was copied to a cloud\nservice or repository server, a vSnap server is used as a gateway to complete the operation. By\ndefault, the vSnap server that is used to complete the restore operation is the same vSnap server\nthat is used to complete the backup and copy operations. To reduce the load on the vSnap server, you\ncan select an alternative vSnap server to serve as the gateway.
\n \n - Click the backup storage type that you want to restore from. The storage types that are shown\ndepend on the types that are available in your environment and are shown in the following order:
- \nOn the Set destination page, specify the instance that you would like to\nrestore for each chosen source and click Next: \n\n
- \n\n
- Original Host or Cluster \n\n
- Select this option to restore data to the original host or cluster. \n\n\n\n
- Alternate Host or Cluster \n\n
- Select this option to restore data to a local destination that is different from the original\nhost or cluster, and then select the alternate location from the available resources. Test and\nproduction networks can be configured on the alternate location to create a fenced network, which\nkeeps virtual machines used for testing from interfering with virtual machines used for production.\nFrom the vCenters section, select an alternative location. You can filter the\nalternative locations by either hosts or clusters. \n\n\n\n\n\n\n\n
- ESX host if vCenter is down \n\n
- Select this option to bypass vCenter Server and to restore data directly to an ESXi host. In\nother restore scenarios, actions are completed through vCenter Server. If vCenter Server is\nunavailable, this option restores the virtual machine or virtual machines that contain the\ncomponents that vCenter Server is dependent on. \n\n\n\n\n\n\n\n\n
\n - \nOn the Set datastore page, take the following actions: \n
- \n
- If you are restoring data to an alternate ESXi host or cluster, select the destination\ndatastore and click Next. \n\n
- If you are restoring data to the original ESXi host or cluster, this page is not\ndisplayed. \n\n
\n - \nOn the Set network page, specify the network settings to use for each\nchosen source and click Next. \n
- \n
- If you are restoring data to the original ESXi host or cluster, specify the following\nnetwork settings:
- \n\n
- Allow system to define IP configuration \n\n
- Select this option to allow your operating system to define the destination IP address. During a\ntest mode restore operation, the destination virtual machine receives a new MAC address along with\nan associated NIC. Depending on your operating system, a new IP address can be assigned based on the\noriginal NIC of the virtual machine, or assigned through DHCP. During a production mode restore, the\nMAC address does not change; therefore, the IP address should be retained. \n\n\n\n
- Use original IP configuration \n\n
- Select this option to restore data to the original host or cluster using your predefined IP\naddress configuration. During the restore operation, the destination virtual machine receives a new\nMAC address, but the IP address is retained. \n\n\n
\n\n - If you are restoring data to an alternate ESXi host or cluster, complete the following\nsteps:
- \n
- In the Production and Test fields, set virtual\nnetworks for production and test restore job runs. Destination network settings for production and\ntest environments should point to different locations to create a fenced network, which keeps\nvirtual machines used for testing from interfering with virtual machines used for production. The\nnetworks that are associated with test and production modes will be used when the restore job is run\nin the associated mode. \n\n
- Set an IP address or subnet mask for virtual machines to be repurposed for development, testing,\nor disaster recovery use cases. Supported mapping types include IP to IP, IP to DHCP, and subnet to\nsubnet. Virtual machines that contain multiple NICs are supported. Take one of the following\nactions:\n
- \n
- To allow your operating system to define the destination subnets and IP addresses, click\nUse system defined subnets and IP addresses for VM guest OS on\ndestination. \n\n
- To use your predefined subnets and IP addresses, click Use original subnets and IP\naddresses for VM guest OS on destination. \n\n
- To create a new mapping configuration, select Add mappings for subnets and IP\naddresses for VM guest OS on destination, click Add Mapping, and\nenter a subnet or IP address in the Add Source Subnet or IP Address\nfield.Choose one of the following network protocols:\n
- \n
- Select DHCP to automatically select an IP and related configuration\ninformation if DHCP is available on the selected source. \n\n
- Select Static to enter a specific subnet or IP address, subnet mask,\ngateway, and DNS. The Subnet / IP Address, Subnet\nMask, and Gateway are required fields. If a subnet is entered as\na source, a subnet must also be entered as a destination.Note: When a mapping is added, the source\nIP address must be entered into the field by the + button. The destination IP\naddress information should be entered into the Subnet / IP Address, Subnet\nMask, and Gateway fields. Re-addressing can only be performed on\nmachines with VMware Tools installed prior to executing the backup job that is to be\nrestored.\n \n\n
IP reconfiguration is skipped for virtual machines if a static IP is used but no\nsuitable subnet mapping is found, or if the source virtual machine is powered off and there is more\nthan one associated NIC. In a Windows environment, if a\nvirtual machine uses DHCP only, then IP reconfiguration is skipped for that virtual machine. In a\nLinux® environment, all addresses are assumed to be static,\nand only IP mapping will be available.
\n \n\n
\n\n
\n\n
\n - If you are restoring data to the original ESXi host or cluster, specify the following\nnetwork settings:
- \nOn the Restore methods page, select the restore method to be used for\nsource selection. Set the VMware restore job to run in Production,\nTest, or Clone. When you run in production mode, you\nhave the option to select Replace virtual disks only and retain virtual machine\nconfiguration. Enabling this option replaces the storage in the virtual machine with the\nvirtual disks from a previous virtual machine backup. This restore method maintains the virtual\nmachine configuration replacing only the storage. When production restore is selected, the virtual\nmachine to which the disk replace is applied must be powered off and only restoring to the original\nlocation is supported. Additionally, options such as overwriting the virtual machine and restoring\nbased on tags are not available because the virtual machine is not being recreated. After the job is\ncreated, it can be run in production or clone mode through the Job Sessions\npane. \n
- You can also change the name of the restored VM by entering the new VM\nname in the Rename VM (optional) field. The Rename VM\noption is not available when the production mode is used with the replace virtual disks option\nenabled. Click Next to continue.\n \n
- Optional: \nIf you are running the restore job in advanced mode, you can set\nadditional options as follows: \n\n\n\n\n\n
- \n\n
- Power® on after recovery \n\n
- Toggle the power state of a virtual machine after a recovery is run. Virtual machines are\npowered on in the order in which they are recovered, as set in the Source step. If Use\noriginal IP configuration is selected, the Power on after\nrecovery option is not honored.Restriction: Restored virtual machine\ntemplates cannot be powered on after recovery.\n \n\n\n\n
- Overwrite virtual machine \n\n
- Enable this option to allow the restore job to overwrite the selected virtual machine. By\ndefault, this option is disabled. \n\n\n\n
- Continue with restore even if it fails \n\n
- Toggle the recovery of a resource in a series if the previous resource recovery fails. If\ndisabled, the restore job stops if the recovery of a resource fails. \n\n\n\n\n
- Run cleanup immediately on job failure \n\n
- This option enables the automatic cleanup of backup data as part of a restore job if the job\nfails. This option is selected by default. Do not clear this option unless instructed by IBM® Software Support for troubleshooting purposes. \n\n\n\n
- Allow to overwrite and force cleanup of pending old sessions \n\n
- Enable this option to allow a scheduled session of a recovery job to force an existing pending\nsession to clean up associated resources so the new session can run. Disable this option to keep an\nexisting test environment running without being cleaned up. \n\n\n\n
- Restore VM tags \n\n
- Enable this option to restore tags that are applied to virtual machines through vSphere. \n\n\n\n
- Enable Streaming (VADP) restore \n\n
- Parallel streaming for virtual machine restore operations is set by default. You\ncan deselect this option for virtual machine restore operations. VADP proxy selection for streaming\nrestore is based on the site of the source snapshot being restored.Tip: When you are\nrestoring virtual machines managed by a VMware Cloud (VMC) on AWS Software-Defined Data Center\n(SDDC), this option should always be enabled to allow streaming of the data.\n \n\n\n\n
- Append suffix to virtual machine name \n\n
- Enter a suffix to add to the names of restored virtual machines. \n\n\n\n
- Prepend prefix to virtual machine name \n\n
- Enter a prefix to add to the names of restored virtual machines. \n\n\n
\n - Optional: \nOn the Apply scripts page, choose the following script options and click\nNext. \n
- \n
- Select Pre-script to select an uploaded script, and an application or\nscript server where the prescript runs. To select an application server where the script will run,\nclear the Use Script Server check box. Go to the System Configuration > Script page to configure scripts and script servers. \n\n
- Select Post-script to select an uploaded script and an application or\nscript server where the postscript runs. To select an application server where the script runs,\nclear the Use Script Server check box. Navigate to the System Configuration > Script page to configure scripts and script servers. \n\n
- Select Continue job/task on script error to continue running the job\nwhen the script that is associated with the job fails. When this option is enabled and the prescript\ncompletes with a nonzero return code, the backup or restore job continues to run and the prescript\ntask status returns
COMPLETED. If a postscript completes with a nonzero return\ncode, the postscript task status returnsCOMPLETED. When this option is not\nselected, the backup or restore job does not run, and the prescript or postscript task status\nreturns with aFAILEDstatus. \n\n
\n - \nTake one of the following actions on the Schedule page: \n
- \n
- To run an on-demand job, click Next. \n\n
- To set up a recurring job, enter a name for the job schedule, and specify how often and when\nto start the restore job. Click Next. \n\n
\n - \nOn the Review page, review your restore job settings and click\nSubmit to create the job. \n\n\n
On-demand jobs will begin immediately; recurring jobs will begin at the scheduled start time.
\n\n \n
What to do next
After the job is completed, select one of the following options from the\nActions menu on the Jobs Sessions or Active Clones sections in the\nRestore pane:
\n\n- \n\n
- Cleanup \n\n
- \n
Destroys the virtual machine and cleans up all associated resources. Because this is a temporary\nvirtual machine to be used for testing, all data is lost when the virtual machine is destroyed.
\n\n \n\n\n\n - Move to Production (vMotion) \n\n
- Migrates the virtual machine through vMotion to the datastore and the virtual Network defined as\nthe production network. \n\n\n\n
- Clone (vMotion) \n\n
- Migrates the virtual machine through vMotion to the datastore and virtual Network defined as the\ntest network. \n\n\n
![\"image\"](\"/support/pages/system/files/inline-images/0587adbc-8477-431f-8c68-9226adea11ed_JRE131.JPG\")
![\"image\"](\"/support/pages/system/files/inline-images/0587adbc-8477-431f-8c68-9226adea11ed_16641MABLOGHOOTSUITE.png\")
![\"image\"](\"/support/pages/system/files/inline-images/0587adbc-8477-431f-8c68-9226adea11ed_862260SUB_BUTTON_Twitter-Follow-Button.png\")
![\"image\"](\"/support/pages/system/files/inline-images/0587adbc-8477-431f-8c68-9226adea11ed_362380SUB_BUTTON_youtube-subscribe-button-psd-photoshop-july-2013.png\")
![\"Legacy](\"../common/Legacy_tag.svg\")
\n![\"Illustration](\"/content/dam/connectedassets-adobe-cms/worldwide-content/creative-assets/s-migr/ul/g/9b/a1/content-hub-explainers-page-leadspace-short.component.xl.ts=1737477212059.png/content/adobe-cms/us/en/topics/_jcr_content/root/leadspace\")
\n ![\"\"](\"https://dw1.s81c.com/developer-static-pages/default/en/default_images/event.jpg\")
![\"\"](\"https://dw1.s81c.com/developer-static-pages/default/en/default_images/blog.jpg\")
![\"\"](\"https://s3.us.cloud-object-storage.appdomain.cloud/developer/default/tutorials/awb-watsonx-assistant-thumbs-up-down-feedback/card.jpg\")
![\"\"](\"https://s3.us.cloud-object-storage.appdomain.cloud/developer/default/tutorials/awb-build-rag-application-watsonx-ai-flows-engine/card.jpg\")
![\"\"](\"https://s3.us.cloud-object-storage.appdomain.cloud/developer/default/blogs/awb-grow-javascript-skills-professional-certificate/card.jpg\")
![\"\"](\"https://dw1.s81c.com/developer-static-pages/default/en/default_images/openproject.jpg\")
![\"\"](\"https://dw1.s81c.com/developer-static-pages/default/en/default_images/tutorial.jpg\")
![\"\"](\"https://dw1.s81c.com/developer-static-pages/default/en/default_images/article.jpg\")
![\"\"](\"https://s3.us.cloud-object-storage.appdomain.cloud/developer/default/tutorials/awb-dynamic-theming-ibm-carbon/card.png\")
![\"\"](\"https://id.rlcdn.com/464526.gif\")
![\"Widgets](\"icon_widget.jpg\")
icon.![\"Edit](\"icon_carbon_edit.jpg\")
![\"Notebook](\"icon_widget_notebook.jpg\")
icon to the canvas. If you want the widget to fill the next available pane in\nthe template, click the ![\"Timestamp](\"ca_notebook_timestamp_icon.jpg\"){kind=icon}
icon.![\"Properties](\"icon_properties.jpg\")
icon, and then click ![\"Edit](\"ca_icon_edit_drill_through.jpg\"){kind=icon}
icon from the widget toolbar. ![\"image\"](\"/support/pages/system/files/inline-images/69ec672c-dd6b-443d-add8-bb9a9a490eba_noThresholds_StatusGauge_3.jpg\")
![\"image\"](\"/support/pages/system/files/inline-images/69ec672c-dd6b-443d-add8-bb9a9a490eba_RequiredSettings_gauge.jpg\")
![\"White](\"/content/dam/connectedassets-adobe-cms/worldwide-content/stock-assets/getty/image/photography/bf/fa/whitedatablocksurface.component.xl.ts=1735844232109.jpg/content/adobe-cms/us/en/products/_jcr_content/root/leadspace_container/leadspace\")
\n ![\"Person](\"/content/dam/connectedassets-adobe-cms/worldwide-content/stock-assets/getty/image/others/0d/55/0d5559fa-782c-468c-b1ac373923dbdb5b.component.xl.ts=1730381080533.jpg/content/adobe-cms/us/en/cloud/mobile/_jcr_content/root/leadspace_container/leadspace\")
\n