PHD Virtual Backup for VMware vSphere

PHDVB User Guide > PHD Virtual Backup Overview > Best Practices

Best Practices

To help ensure optimal performance when running PHD Virtual Backup in your environment, review the best practices included in this section.

Tip:    The PHD Virtual web site includes white papers and other information and suggestions for implementing your data protection solution with PHD Virtual Backup.


When using a CIFS share as backup storage, the CIFS service account must have full permissions (read/write/delete) for the share used as the backup target. Also, antivirus software should not be configured to analyze or scan the PHD VBA CIFS storage repository.

NFS Shares

When using an NFS share as backup storage, the PHD VBA requires direct write access to the NFS export. During backup, the PHD VBA will directly mount and copy files to the NFS share. It is important to configure the export to allow this behavior.

Antivirus software

Running antivirus software on a backup target can result in file locking or deletions and may cause additional issues with writing and deleting backups. PHD Virtual recommends excluding backup targets from antivirus software scans, including the network shares and directories used for backup targets.

In addition, antivirus programs may prevent the PHD Exporter from exporting files to your staging location. If you are running antivirus software on your staging computer, make sure an exclusion is added to your antivirus software to allow the PHD Exporter to save any exported files.

Disk Defragmenter

Defragmenting virtual disks can impede the overall performance of PHD Virtual Backup, resulting in lower deduplication rates, which in turn produces larger backup files written to storage and longer backup durations. To ensure consistent backup performance, PHD recommends running disk defragmentation programs only when necessary.

Running defragmentation on any disks used as backup storage is not recommended.

PHD Exporter

Though the PHD Exporter can be installed to a physical or virtual machine running a Windows Server operating system (see the System Requirements for additional details), for performance reasons, a physical machine is recommended.

Backing up the vCenter Server Virtual Machine

If your vCenter Server is running on a virtual Windows machine, to avoid interruptions and other issues, do not include the vCenter Server virtual machine within your main backup job. Instead, to back up this VM you can create a backup job with a PHD VBA that is connected directly to the host on which the vCenter Server virtual machine exists. vCenter Server VMs should be backed up only during periods of downtime when the risk of interruption is minimized.

Copyright © 2010-2013 PHD Virtual Technologies | Support | Knowledge Base | Videos v6.5.0