What can I do with standard disk storage in vRealize Automation

Standard disks can be persistent or non-persistent.

vRealize Automation supports two categories of storage – standard disk and first class disk. First class disk is only available for vSphere.

• vSphere

  vSphere supports dependent (default), independent persistent, and independent non-persistent standard disks. For related information, see What can I do with persistent disk storage in vRealize Automation.

  When you delete a virtual machine, its dependent and independent non-persistent disks are also deleted.

  When you delete a virtual machine, its independent persistent disks are not deleted.

  You can create a snapshot of dependent and independent non-persistent disks. You cannot create a snapshot of an independent persistent disk.

  vSphere cloud zone storage limits that you defined in each project are evaluated when you deploy a cloud template that includes independent non-persistent or independent persistent disks, or when you run a day relevant day 2 action. A request might fail if the disk requested exceeds the limits.

• Amazon Web Services (AWS) EBS

  You can attach an EBS volume to an AWS compute instance or detach an EBS volume from an AWS compute instance.

  When you delete a virtual machine, its attached EBS volume is detached but not deleted.

• Microsoft Azure VHD

  Attached disks are always persistent.

  When you delete a virtual machine, you specify whether to remove its attached storage disks.

• Google Cloud Platform (GCP)

  Attached disks are always persistent.

  Persistent disks are located independently from your virtual machine instances, so you can detach or move persistent disks to keep your data even after you delete your instances.

  When you delete a virtual machine, its attached disk is detached but not deleted.

For related information, see Learn more about storage profiles in vRealize Automation.