PHD Virtual Backup for VMware vSphere
This section contains frequently asked questions about PHD Virtual Backup.
The number of PHD Virtual Backup Appliances you will need is determined by how your virtual machine environment is configured. PHD VBAs must be able to access the storage location where virtual machine disks are located in order to perform the backup. If you have some VMs on local storage and others on shared, you will need to deploy at least one appliance that can access the local storage on the individual host. For more information, refer to the Installation Guide.
The number of backups you can store per appliance depends on the size of the backup storage you are using. Due to deduplication and compression, typically, to store one month of backups per VM, you need to allocate backup storage equal to the total size of your VM data. For example, if you have 500 GB of VMs, allocate 500 GB of space to store one month of backups for each VM. Visit the PHD Virtual web site for additional information, including a whitepaper on planning for deduplicated backup storage.
The appliance is deployed via an OVF. Refer to the Installation Guide for deployment details.
When a deduplicated backup is performed, only new blocks of data are written to the storage location for each backup. Since this ratio is calculated while the backup is in progress, before any new data is written, the deduplication ratio is essentially infinite for the current virtual disk backup and is therefore displayed as a ratio of inf (infinite) to 1. When new data is encountered and written to disk, the deduplication ratio is updated.
The retention policy (how long to keep backups for each virtual machine) is configured using the PHD Virtual Backup Console, Configuration page. For details, see Backup Retention tab.
The running backup job will be canceled
Using the File Recovery feature, you can mount an individual virtual disk where an Exchange mailbox or database was stored then access that data using your existing software. For example, to recover a database, you could create an iSCSI target from the backed up disk that contained the database then mount that target on a machine where SQL Server was installed. Then you could use SQL Server to attach the backed up database by simply browsing the attached disk.
Yes. When using Virtual Full backup mode, you can create backup jobs that run as frequently as every 15 minutes. With Full/Incremental mode, you can create any number of customized jobs to protect your virtual machines. For example, you could create a job that backs up all of your VMs each night, then create another job that runs in the afternoon for specific VMs that have shorter RPO requirements.
Yes, using the PHD Console, you can create Replication Jobs to replicate VMs from a primary site to a DR site or another location.
Using the Backup Data Connector, you can enable an SMB/CIFS share on the appliance to access all of your backup data in uncompressed format. For details, see Connectors tab. Additionally, you can use the PHD Virtual Backup Exporter to export Virtual Full backups from your backup storage locations to a Windows Server. From there you can then sweep backups to tape for archiving purposes using a third-party solution. For more, refer to the PHD Virtual Backup Exporter User Guide.
Using Backup Jobs, you can define a schedule for specific VMs that should run first each night. For example, create a job that backs up critical VMs beginning at 8 PM. You could then create a second backup job that includes the next tier of VMs to begin at 10 PM, and so on. In this way, you can ensure that your most critical machines have priority and are protected each night.
PHD Virtual Backup is licensed per-socket, which means the license you purchase will allow you to perform backups and replication on a number of hosts, based on the total socket count. for example, if you purchased a license for 8 sockets and you have 4, 2-socket hosts, you could backup all of the VMs on two hosts and then replicate those VMs to two additional hosts. If you were not using replication, you could instead run backups on four different 2-socket hosts. Be sure to obtain a license that supports the correct number of socket/host combination you need to protect your environment.
For details on using the PHD Console to configure licensing, see License Manager.
Any time before or after the trial period has expired, you can upload your license file using the License Manager area of the PHD Console (see License Manager, for details). After uploading your license, you will then be able to apply that license to all of your deployed PHD Virtual Backup Appliances and also, select the hosts on which you will be performing backups or replication.
Yes. Using PHD Virtual Backup's application aware options, along with PHD Guest Tools installed on the guest VM, you can instruct PHD Virtual Backup to truncate Microsoft Exchange logs. For additional details, see Application Aware Backups.
Yes. Backups created with version 5.4 can be recovered using the latest version 6.0.
Yes. Using the Backup Archive feature you can create individual copies of your backups or even synchronize entire backup data stores on any other supported storage location, including offsite locations like cloud storage. For details, see Disaster Recovery - Backup Archiving..
|Copyright © 2010-2013 PHD Virtual Technologies | Support | Knowledge Base | Videos||v6.5.0|