vmdk file containing the VDP guest OS is corrupted or lost. As an example, this is useful if by chance the. It is also possible to mount an existing VDP backup data partition to a new VDP appliance during deployment. When deploying VDP, separate data stores can be selected for the VDP guest OS and backup data partitions. Of course, backup jobs should still be scheduled during the backup window. For example, Backup Job 1 is scheduled to start at 9:05 PM, Backup Job 2 is scheduled to start at 10:20 PM, and Replication Job 1 is scheduled to start at 1:30 AM. Specific times can be selected to start backup and replication jobs. – Granular scheduling for backup and replication jobs Granted, this capability should have been in the initial release of VDP – all I can say is better late than never. vmdk files when creating/editing a backup job or performing a restore. Speaking of feature requests, this was the most requested: The option to select individual. This was a popular feature request and we are now happy to deliver with VDP 5.5! This capability is especially interesting for those who plan to use VDP to backup vCenter Server. The restore of a virtual machine directly to a host can be accomplished without the need for vCenter Server and the vSphere Web Client. SunGard and Secure-24 are planning to offer a backup data replication target service for VDP and I expect many more service providers will offer this service in the near future. For example, the three most recent backups or backups that occurred within a specific time period (by date). It is even possible to restrict which backup data is replicated, if desired. For example, VDP can have a backup job with a daily schedule and a 60-day retention and then replicate the backup data to a service provider weekly with a retention policy of one year at the service provider location. Replication schedules and retention policies can be customized and are separate from backup job schedules and retention. Since the backup data is de-duplicated at both the source and destination and only changed data segments are sent across the wire, bandwidth utilization is minimized – no need for WAN acceleration technologies. It is possible to replicate backup data for all VMs backed up by the VDP appliance or select individual VMs. The replication engine is very robust, efficient, and flexible. If an organization has an existing Avamar implementation, this can also be used as a target for backup data replicated from VDP. Service providers will be able to offer services for receiving, storing, and archiving backup data replicated from VDP at a customer site to Avamar located in service provider data centers. Replication provides a more efficient, secure means to move backup data offsite for disaster recovery purposes (versus legacy tape solutions). – Replication of backup data to EMC Avamar Here are details on these new capabilities in VDP 5.5… Last week at VMworld, VDP 5.5 was introduced which further extends the capabilities of VDP. Simply put, VDP is backup and recovery for VMware, from VMware. One of the real beauties of VDP is its ease of deployment and management which explains why thousands of VMware customers have already downloaded VDP since it was introduced last year. VDP is fully integrated with VMware vCenter Server and the vSphere Web Client. VDP leverages proven technology from EMC Avamar to provide reliable, space-efficient, disk-based data protection for VMware virtual machines (VMs). VMware vSphere Data Protection (VDP) is a backup and recovery solution that was introduced with vSphere 5.1.
0 kommentar(er)
