You are here: Configuration > Appliance settings > Backup storage > Preparing to add storage

Preparing to add storage

Consider the following recommendations before adding storage:

Warning!     It is strongly recommended that all storage is either direct attached storage (DAS, internal to the hypervisor) or resides on one external storage array. If you configure storage across multiple storage arrays and one becomes unavailable, all backup data is corrupted, resulting in total data loss.

As you add storage, be sure to add resources to the UEB virtual machine, such as CPU and memory.
It is recommended to use direct attached storage (DAS), internal to the host, or leverage SAN or NAS storage by connecting the external array to the host.
You can create VMDK or VHD(X) disks on storage internal to the host (DAS).
You can connect a SAN LUN on the array to the hypervisor and expose it to the UEB VM. You can then add the entire LUN to the UEB VM or create VMDK or VHD(X) virtual disks on the LUN and expose the disks to the UEB VM.
You can connect a NAS share to the host over the NFS protocol to create VHD(X) disks .
You can connect a NAS share to the hypervisor over the NFS protocol as a datastore to create VMDK disks.
Although it is possible to attach external storage directly to the UEB appliance, this is not recommended. If you must connect external storage to the UEB VM directly through network protocols (CIFS, NFS, or iSCSI), make sure to use a supported vendor from the list in KB 3350.
Storage should be dedicated to the UEB VM and not shared by other virtual machines, applications, etc.
If you are using external SAN or NAS storage, the shares or LUNs used by the UEB VM should be dedicated to that UEB VM.
The UEB VM can be deployed on a host in a cluster configuration and can use shared storage. However, in this configuration, the UEB VM should use a dedicated NAS share or SAN LUN.
For best performance with SAN storage, use a thickly provisioned LUN and either a thick provisioned eager zeroed VMDK or a fixed size VHD(X).
For VMware environments, do not use Storage vMotion. Storage must remain in a fixed location.