If you have Writable Volumes from another App Volumes deployment, you can import them to your current deployment.
If you have Writable Volumes (2.x) created by using App Volumes Manager 2.x, you cannot import such Writable Volumes when using the latest version of App Volumes Manager.
To import Writable Volumes (2.x), see Import Writable Volumes (2.x)
Ensure that you have access to the Writable Volumes that you want to import. You can verify access in one of the following ways:
- Verify that your vCenter Server instance has access to the datastore where the Writable Volumes that you want to import reside.
- Copy the VMDK files of the Writable Volumes to a different folder on the datastore that you already use for Writable Volumes on your current App Volumes deployment.
- From the App Volumes Manager, click .
- On the Writable Volumes page, click Import.
- Select the datastore from the drop-down list.
- Provide the path from where you want to import the Writable Volumes.
- Click Import.
- On the Confirm Import Writable Volumes window, choose when you want to import the selected volume:
- Import volumes in the background - App Volumes Manager dispatches a background job to import the volume and the display goes back to the manager console immediately.
- Import volumes immediately - App Volumes Manager waits for the import to be completed and the console is not responsive until either the process is complete or 10 minutes have elapsed.
What to do next
Click Rescan to update the list of Writable Volumes in the App Volumes Manager.