PHD Virtual Backup for Hyper-V

(1)

version 7.0

Release Notes

Document Release Date: December 18, 2013 www.phdvirtual.com

(2)

2 Document Date: December 18, 2013

Legal Notices

PHD Virtual Backup for Hyper-V – Release Notes – version 7.0

Copyright © 2005-2013 PHD Virtual Technologies, Inc. All rights reserved worldwide. PHD Virtual Technologies, Inc. software products are protected by one or more U.S. Patent Numbers 8,135,748; patents pending.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form by any means, without written permission from PHD Virtual Technologies, Inc. (“PHD”). The information contained in this document represents the current view of PHD on the issue discussed as of the date of publication and is subject to change without notice. PHD shall not be liable for technical or editorial errors or omissions contained herein. PHD makes no warranties, express or implied, in this document. PHD may have patents, patent

applications, trademark, copyright, or other intellectual property rights covering the subject matter of this document. All other trademarks mentioned herein are the property of their respective owners. Except as expressly provided in any written license agreement from PHD, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Important! Please read the End User Software License Agreement before using the accompanying software program(s).

Linux is a registered trademark of Linus Torvalds.

Windows and Hyper-V are either trademarks or registered trademarks of Microsoft Corporation.

VMware, VMotion, vCenter, and vSphere are either trademarks or registered trademarks of VMware Corporation. Citrix, Xen, XenServer, XenDesktop, XenMotion, and XenCenter are either trademarks or registered trademarks of Citrix Systems, Inc.

(3)

This document provides an overview of the changes made to PHD Virtual Backup for 7.0 release, along with the system requirements, known issues, and licensing information. This document contains the following sections:

 Updates – Page 4

 Known Issues – Page 5

 System Requirements – Page 8

 PHDVB v7 Licensing – Page 9

 Support, Sales, Renewals, Licensing – Page 10

To get the latest version of PHD Virtual Backup:

 New customers: visit PHD Virtual’s website – www.phdvirtual.com – to register and

download the latest version.

For installation and configuration information refer to the latest documentation included with the installation package or on the PHD Virtual web site.

(4)

Updates

v7.0.0 for Hyper-V – December 18, 2013

 PHD Virtual Backup v7 introduces support for Microsoft Hyper-V™ on Windows Server 2012 (Standard and DataCenter) and Windows Server 2012 R2 (Standard and

DataCenter) as well as Hyper-V Server 2012 and 2012 R2 (free version).

 Powered by all-new v7 architecture! – The latest and greatest purpose-built VM data protection architecture provides a unique approach to scalability and enterprise

management.

 Updated Web-Based Interface - A new web-based user interface replaces the previous Windows-based client, allowing for even more flexibility and ease-of-use. The new interface includes many new features and options for viewing the protection status of your environment, including:

 Dashboard - overview of protection status including graphs that display trending data, storage details, jobs in progress, and alerts.

 Protect page - see all of the VMs in all of your virtual environments, apply VM-level settings, and view details for recent backups for each.

 Reports - create detailed, customizable reports based on specific date ranges.

 Per-job email – receive customized reports by email when a job is completed.

 Delivers global deduplication – Built-in, multi-stage deduplication technology cuts storage to the bone with an average dedupe ratio up to 25:1 typically reducing storage requirements by more than 90%.

 Assures block level verification – Reliable data transfer can detect corrupted data during backup and automatically correct it.

 The v7 architecture provides two virtual disks with the Virtual Backup Appliance (VBA for short). The first disk is the OS disk. The second disk houses important configuration data for the VBA. You will add a third disk for the backup target, after the VBA is deployed. The reason we added the second disk to the VBA, is so that a VBA and its OS disk could be discarded, and a new VBA can connect to the data disk, to preserve all necessary configuration information. If you’d like to change the virtual CPU or memory settings, you can easily do that, after the VBA is imported into the environment.

 v7 has major enhancements with inventory and backup catalog management, to improve performance for those huge environments, by leveraging new database and caching algorithms within the management and UI components of the VBA.

(5)

Known Issues

PHD Hyper-V Services

 After uninstalling the PHD Hyper-V services, you may need to manually stop and remove the Erlang port mapper daemon (epmd.exe). Failure to stop this from running will cause a reinstall of PHD Hyper-V services to fail.

 Entering a PHD User Name that includes unicode characters prevents the PHD Hyper-V services from starting on the host. (PHDVB-1320)

PHD Virtual Backup Appliance

 Attaching virtual disks for use as a backup data store to the appliance virtual machine IDE controllers is not supported. Attached disks must be added to the SCSI controller on each appliance VM.

 If an Engine appliance is turned off or reset shortly after a job was created, the job contents may be lost, resulting in a job that does not run. Editing and resubmitting the job will solve this issue. (PHDVB-1114).

 An appliance that could not be updated via the Auto-Update process (due to a job in progress, for example) must be manually updated by logging in to

the appliance and running the update from the command line. (PHDVB-1296) To manually apply an update:

Log in to the appliance virtual machine console and open a command shell prompt. Enter the following command:

Where [update file] is the name of the current update file found in /var/lib/phdvb/update/packages. For example, phdvb-7.0.0.11600.phd.

 After completing Quick Setup where a second appliance was selected for use as an Engine, the appliance used as Management cannot be used as an Engine - you cannot select an attached disk on the Management appliance for use as Storage via the

Configure page of the web interface. To work around this issue, click Add Appliance and re-enter the IP address of the management appliance. (PHDVB-1053)

 After changing the IP address of the Presentation appliance and re-connecting to the web interface using the new IP may result in an error when viewing the Configure page, "One or more management appliances appears to be down. Please ensure that your management appliances are powered on and reachable on the network.” Rebooting the presentation appliance will resolve this issue. (PHDVB-1340)

(6)

Recovering VMs

 Fibre Channel adapters are not backed up or restored with VMs. They must be manually added back to the VM after the restore is completed. (PHDVB-1011).

 The Recovery Email report displays the value for verify as "None" regardless of the value set within the job. (PHDVB-1267)

 Recovery jobs resulting in warnings generate and send an email report with email settings set to "On Errors Only." (PHDVB-1307)

 VM Target Path in the Recovery dialog includes the original .XML file name. This cannot be modified. A new file is created when the VM is recovered (PHDVB-1306)

 When restoring a VM, if the original backed up VM did not have a MAC address assigned, restore will fail if you select to use the same MAC from the original VM (VMs cannot be created with no MAC address). To work around this issue, use Auto-Generate MAC option when restoring the VM. (PHDVB-1413)

Reporting

 Exported PDF and CSV reports display unicode characters incorrectly. (PHDVB-1217) Scheduled Jobs and GMT

 Backups scheduled for certain weeks of a month (using First, Second, etc) may not run when expected due to the GMT offset. (PHDVB-337)

Because of the GMT offset, the date on an Engine appliance may coincide with the date in the local timezone. For example, when a backup job is scheduled for 20:00EST on the second Tuesday, the engine appliance will receive 00:00 on the second Wednesday. This is acceptable as long as Tuesday and Wednesday are in the same week for that month. But if the month starts on a Wednesday, the second Tuesday is on the 14th, but the second Wednesday is the 8th. When the Engine appliance checks if the job should run on Wednesday the 8th at midnight, it will check if it is the second week. In this case it is, so the job will start. When the appliance checks if the job should run on Wednesday the 15th, it will determine that it is not the second week, and the job will not run.

Windows Server 2012 R2™

 Live exporting a VM during backup:

 Reason for failed backup Job: "Failed to create snapshot: Invalid state ".

 Live resizing a VM disk(Expanding/Shrinking) during backup:

 Reason for failed backup Job: " Failed to create snapshot: System In Use".

(7)

 Reason for failed backup Job: "Failed to create snapshot: Not Supported". Web Interface

 System Job - Delete displays individual deleted VM details Status as "Unknown" (PHDVB-1243)

 Add Environment dialog hangs if any field contains a backslash or other unsupported character. (PHDVB-1324)

 Canceling a queued job will cause that job's status to be reported as 'Unknown' in the jobs history. In addition, this job may remain in the Active Jobs tab for a long time before it is moved to Recent Jobs. (PHDVB-1319)

 Quick Setup wizard cannot be used to configure backup storage using an existing backup data store disk. Only a new backup storage target can be created with a new attached disk using Quick Setup. To use an existing backup data store, exit the Quick Setup wizard use Configure page. (PHDVB-1430)

 After removing an environment, the storage widget on the dashboard will continue to display storage targets associated with the removed environment. (PHDVB-1396)

(8)

System Requirements

The following requirements must be met to run PHD Virtual Backup version 7.

Table 1 – System Requirements

Operating System Windows Server 2012™ or Windows Server 2012 R2™ (Standard and DataCenter editions) with the Hyper-V role enabled

Hyper-V Server 2012™ and Hyper-V Server 2012 R2™ (free versions)

Browsers

(For Web-based interface)

Mozilla Firefox Google Chrome

For optimal performance, the web interface should be accessed from a machine with at least 1 dedicated CPU, 1GHZ or faster Intel or AMD processor, at least 1 GB of available memory, a gigabit or faster network connection, and viewed with a minimum resolution of 1280x1024.

(9)

PHD Virtual Backup Licensing

PHD Virtual Backup for Hyper-V version 7.0 is a free release. If you would like to purchase support for this product, it can be done by contacting PHD Virtual directly.

(10)

Support, Sales, Renewals, and Licensing

For information on new sales, licensing and support renewals you can email

[email protected] or [email protected]

For additional information about PHD Virtual’s products and services, go to phdvirtual.com

To license and register this product, go to phdvirtual.com

For customers and partners with an active support agreement, you can use the support web board or phdvirtual.com for more information about software patches, technical documentation, and support programs.