Release Notes. LiveVault. Contents. Version Revision 0

(1)

R E L E A S E N O T E S

LiveVault

Version 7.65

Release Notes

Revision 0

This document describes new features and resolved issues for LiveVault 7.65.

You can retrieve the latest available product documentation from Autonomy’s Knowledge Base on the Customer Support site.

https://customers.autonomy.com

New in this Release

This section lists the enhancements to LiveVault version 7.65.

Feature Overview

Support for Windows Server 2012

With the LiveVault 7.65 release, customers gain the support and application awareness for Windows Server 2012. The LiveVault software enables you to protect the Microsoft Windows Server file system to the LiveVault Cloud and to integrate with the latest Windows Server platform release.

Support includes integration with Microsoft Volume Shadow Copy service (VSS), Microsoft's enhancements to its file system design, specifically support for Resilient File System (ReFS), which enables customers to have considerable larger file systems (upwards of 16 Exabytes in size).

In addition, LiveVault supports Microsoft's data deduplication technology and by doing so supports the storage efficiency mechanisms built within Windows Server 2012.

Support for SQL Server 2012

With the LiveVault 7.65 release, customers gain support and application awareness for Microsoft's SQL Server 2012. With this enhancement LiveVault extends its application awareness to the latest Microsoft database server platform release. Customers gain the advantage of protecting their existing and supported Microsoft SQL Server versions (SQL 2005, 2008, 2008 R2) along with Windows Server 2012 to the LiveVault Cloud. Support includes integration with Microsoft Volume Shadow Copy service (VSS) to provide application consistent protection.

In addition, LiveVault now supports Microsoft SQL Server 2012 Enterprise edition’s Always On Availability Group feature which promotes a higher level of availability from the database application perspective.

Resolved Issues

This section lists the resolved issues in LiveVault version 7.65.

 An issue with the software being unable to determine sqlcmd location for truncation on 32-bit sql installed on 64-bit windows has been resolved.

(3)

Requirements

 An issue existed with the LiveVault Agent software that occurred when there was a case change to a file name within a backup policy.

This issue impacted the software’s ability to replicate backup files between the vault pairs as well as from a Turbo Restore Appliance (TRA’s) to the vaults. It also impacted history reduction which manages versions and space on the TRAs. This issue has been resolved.

 In the LiveVault Web Management Portal, the disable/enable option on the TurboRestore® Appliance Properties page has been enabled.

 An issue in the Offline Restore Wizard Help with versioning of Microsoft Exchange has been resolved.

 An issue with the display of the Configuration Wizard dialogs for a CIFS Collector Agent on a Japanese language computer has been resolved.

 In the LiveVault Web Management Portal, an issue with a screen text note referencing help on the DPM Restore wizard page has been resolved.

Requirements

This section describes the system requirements, supported platforms, and software dependencies for LiveVault 7.65.

The documented platforms are the recommended and most fully-tested platforms for LiveVault. Other platforms may be supported and Autonomy can provide support for other platforms on request.

(4)

For information about supported platforms, refer to the System Requirements in the LiveVault Web Management Portal Help system.

Windows System Requirements.

Component Compatibility

Operating System Microsoft Windows Server 2012

Microsoft® Windows® Server 2008, 32-bit and 64-bit

Microsoft Windows Server 2008 R2

Microsoft Windows Server 2003 32-bit and 64-bit (Service Pack 1 or higher)

Microsoft Windows Small Business Server 2003 Premium 32-bit and 64-bit (Service Pack 1 or higher)

VMware ESX 2.5.3, 3.0, 3.5, 4.1 and 5 Supported operating systems above running as Guest operating systems.

HyperV Supported operating systems above running as Guest operating systems.

Clustered agents 2-node Windows clusters only, on the following operating systems:

Windows Server 2008 32-bit and 64-bit

Windows Server 2008 R2

Windows Server 2003 32-bit and 64-bit R2

NOTE Disaster Recovery of cluster nodes is not supported.

File System NTFS on Windows 2003, Windows 2008, Windows 2008 R2 and Windows 2012.

Resilient File System (ReFS) on Windows 2012.

Volumes optimized for data deduplication on Windows 2012.

For more information on Windows 2012 with ReFS and data deduplication, refer to your Windows documentation.

Additional RAM 128 MB of free memory under normal load.

Available Disk Space 5% or 300 MB free disk space (whichever is greater; typically 5%) on each partition with backed up data, for the snapshot cache.

Data Directory Disk Space Autonomy recommends you to select a location other than your system volume for the backup database files during installation of the agent software.

The backup database files can grow to consume a lot of space, depending on the number of backup policies you create and the amount of data you are backing up. The volume for the LiveVault data directory should optimally have at least 5 GB free disk space.

(5)

Requirements

Data Directory on Windows Server 2012

Autonomy recommends you install the data directory toa NTFS or ReFS formatted volume on Windows Server 2012.

Applications

Microsoft SQL-awareness Microsoft SQL Server 2012 Standalone on all operating systems supported by Microsoft.

Microsoft SQL Server 2012 Enterprise edition’s AlwaysOn Availability Groups on all operating systems supported by Microsoft. Primary and secondary replicas.

Microsoft SQL Server 2005 32-bit and 64-bit on Microsoft Windows 2003, Microsoft Windows 2008 and Microsoft Windows 2008 R2.

Microsoft SQL Server 2008 32-bit and 64-bit on Microsoft Windows 2003, Microsoft Windows 2008 and Microsoft Windows 2008 R2.

Microsoft SQL Server 2008 R2 32-bit and 64-bit on Microsoft Windows 2003, Microsoft Windows 2008 and Microsoft Windows 2008 R2.

NOTE Disaster recovery of SQL Server 2012 AlwaysOn Availability Groups nodes is not supported.

Microsoft

Exchange-awareness

Microsoft Exchange 2010 SP1 Standalone on all operating systems supported by Microsoft.

Microsoft Exchange 2010 SP1 DAG on all operating systems supported by Microsoft.

Microsoft Exchange 2007 SP2/SP3 Standalone on Microsoft Windows 2003 SP1 or higher or Windows 2008 64-bit.

Microsoft Exchange 2007 SP2/SP3 CCR on Microsoft Windows 2003 SP1 or higher or Windows 2008 64-bit.

Microsoft Exchange 2003 SP2 on Microsoft Windows 2003 SP1 or higher

Microsoft Exchange 2003 SP2 on Windows Small Business Server 2003 SP1 or higher.

Refer to the LiveVault Web Management Portal help system for additional information on application support.

Microsoft DPM-awareness Microsoft Data Protection Manager (DPM) 2010 (English-only)

Microsoft Data Protection Manager (DPM) 2007 SP1 (English-only)

(6)

CIFS Collector Agent A CIFS Collector Agent computer must meet all of the following requirements to protect NAS devices and CIFS share data:

Windows 2008 R2 operating system.

Windows Server 2012 operating system.

Dedicated, single use, server.

NOTE Clustered servers are not supported as CIFS collector agents.

4 GB RAM or higher.

Data Directory Disk Space. The CIFS backup database files can grow to consume a lot of space, depending on the number of CIFS backup policies you create and the amount of data you are backing up. The volume for the LiveVault data directory should optimally have the larger of 1 percent of the CIFS data under protection or 10 GB free disk space.

For example:

1 TB or less protected data requires 10 GB of free space on the volume containing the data directory.

2 TB protected data requires 20 GB of free space on the volume containing the data directory

 Domain member of the same domain as the NAS devices to be protected.

NOTE The CIFS Collector Agent can be a virtual machine as long the virtual hardware and storage meet all of the system requirements above.

 User account to meet the following criteria:

Administrator role on the Collector Agent computer.

Administrative Privileges to access the volumes on the CIFS shares.

NOTE Administrative privileges are required in order to back up ACLs on the CIFS shares and to restore files to the CIFS shares properly. If the user account does not have administrative privileges to the CIFS shares, files may be backed up without the ACLs, and restores to the CIFS shares will fail.

(7)

Requirements

Firewall settings Create two outbound packet filters for LiveVault as follows:

Protocol: TCP Direction: Outbound Local port: Dynamic Remote port: 2144

Protocol: TCP Direction: Outbound Local port: Dynamic Remote port: 2145

It is only necessary to create outbound filters, because no inbound connections come from the LiveVault service that would require an inbound packet filter.

(8)

UNIX System Requirements

Interoperability

This section describes the third-party software and hardware that works with the LiveVault software. It also describes how LiveVault complies with third-party requirements.

Notes

File System Restore Considerations

Autonomy recommends that you restore data to the same file system that was originally backed up.

Operating System Red Hat Enterprise Linux ES 3 and 4, 32-bit (for x86 architecture only)

 openSUSE Linux 10.0, 32-bit

 Sun Solaris 9 and 10, 32-bit, for Sparc architecture only. (LiveVault version 7.10 and earlier).

File System Red Hat: ext2 and ext3

SUSE Linux ReiserFS

Sun Solaris: UFS

Additional RAM 256 MB of free memory under normal load for Linux

256 MB of free memory under normal load for Solaris Available Disk Space 5% free disk space

Windows Storage Server 2012 Due to differences in the hardware supplied by original equipment manufacturers (OEMs), Autonomy recommends that you configure backup to protect volume and folder data. Do not configure backup to protect the System State and operating system volume.

Disaster recovery of Windows Storage Server is not supported or recommended. To recover a Windows Storage Server computer, rebuild the computer with the assistance of your OEM, and then submit a restore request for the computer's data.

(9)

Notes

For example, if you backed up data from a volume formatted with the Resilient File System (ReFS), restore the data to a ReFS volume. If you restore files to a differently formatted file system volume, such as NTFS, some file system-specific file properties are lost, such as security-extended attributes and alternate data streams. Losing data streams creates a risk of data loss.

For more information on Windows 2012 and its supported file systems, refer to your Windows documentation.

Windows Server 2012 Support

Windows 2012 File System and Backup Policy Considerations

If the server has a mixture of file system types, such as ReFS, NTFS and

deduplicated volumes, Autonomy recommends that you create separate backup policies for each volume. In this way, you can simplify the backup and restore process by protecting similar data types together.

For example, you may create one backup policy for the system volume and system state. Then you may create a separate backup policy to protect a volume that is formatted with ReFS, and a third that protects your volume optimized for data deduplication.

Back Up Windows 2012 Volumes Optimized for Data

Deduplication

Select volumes on Windows Server 2012 that are optimized for data deduplication to back up. Data deduplication is a feature in Windows Server 2012 that performs data reduction on a volume by storing one copy of data where there are duplicate blocks, possibly from several files.

For more information on volumes optimized for data deduplication in Windows Server 2012, refer to your Windows 2012 documentation.

Backup Considerations for Windows 2012 Deduplicated

Volumes

Back Up the Volume Optimized

If you choose to create an optimized backup of the Windows 2012 volume, the LiveVault agent software backs up the reparse points and the entire data deduplication store within the System Volume Information directory.

(10)

Autonomy recommends selecting the whole volume or volumes for optimized backup. Backing up the volume(s) as optimized ensures that the minimum amount of data is transferred in the initial backup, resulting in low bandwidth usage.

To back up the volume contents as optimized, select Create optimized backup for the selected deduplicated volume contents during backup policy creation.

Back Up the Volume Non-Optimized

If you choose to back up the volume or individual files and folders non-optimized, the LiveVault agent software reads the contents of the reparse points in place.

Each deduplicated file is backed up in full in the initial backup. The data deduplication store is not backed up.

Backing up the volume or files/folders as non-optimized is beneficial because the LiveVault software only backs up the selected files in full, and does not back up the dedupe store. This minimizes the total amount of data sent in the initial backup, resulting in low bandwidth usage.

The volume is backed up as non-optimized by default.

Restore Windows Server 2012 Deduplicated Volumes

There are several scenarios when you might restore data backed up from Windows 2012 deduplicated volumes:

 Rebuild a deduplicated volume. In the event of failed disks or recovering an entire computer, you must rebuild the deduplicated volumes.

 Restore individual files or directories. In the event of file deletion, or restoring files to a previous date, select individual files for restore.

For more information on volumes optimized for data deduplication in Windows Server 2012, refer to your Windows 2012 documentation.

Considerations for Rebuilding Deduplicated Volumes

 You must restore to a Windows Server 2012 computer. Performing a restore of optimized data to another operating system such as Windows 2008 will fail.

 Restore of optimized files to the system volume is not supported.

 Rebuild the deduplicated volume by restoring the data to an empty, formatted volume of sufficient size. To ensure consistency of the dedupe store, do not enable deduplication on the new volume. For more information on volumes

NOTE Because most of the data resides in the deduplication store within the System Volume Information directory, Autonomy recommends that you back up the volume in its entirety and do not configure different backup policies to split a volume's data.

(11)

Notes

optimized for data deduplication in Windows Server 2012, refer to your Windows 2012 documentation.

 To ensure optimized restore, protect the entire deduplicated volume. If only selected files and folders are protected, their restore will not be optimized. If you restore an item using Item-level recovery, it will be restored in an

unoptimized state.

 Redirecting a rebuilt volume to another Windows Server 2012 computer is supported. However, the destination volume must be an empty, formatted volume mapped to the same drive letter as the original volume on the original computer. You cannot redirect the volume rebuild to another location. To ensure consistency of the dedupe store, do not enable deduplication on the new volume.

Considerations for Restoring Individual Files or Directories

 You must restore to a Windows Server 2012 computer. Performing a restore of optimized data to another operating system such as Windows 2008 will fail.

 Restore of optimized files to the system volume is not supported.

 When restoring files, the files are opened exclusively by the LiveVault software. If another process such as a data deduplication job is running, the LiveVault software will fail to open and restore the files.

Autonomy recommends that you temporarily disable any active deduplication on the target volume before starting a restore. For more information on disabling the deduplication jobs, refer to your Windows Server 2012 documentation.

 When you restore individual files or directories with the options to either automatically rename the original or restored files, the copy operation accesses the original stub file, rehydrating it to its original file size.

For example, if you select a deduplicated file for restore, and select

Auto-rename the existing file, the stub file is rehydrated by the operating system as part of the copy to the new .00001 file. The end result is both the renamed file and the newly restored file are fully hydrated.

IMPORTANT If you restore an entire volume as non-optimized, without selecting to rebuild the deduplicated volume, the destination volume must have sufficient disk space to restore all of the files in their entirety. In addition, the volume will now be enabled as a deduplicated volume.

(12)

SQL Server 2012 Support

The LiveVault 7.65 release supports Microsoft SQL Server 2012 in the following configurations:

 Standalone SQL Server 2012 on its supported platforms

 SQL Server 2012 Enterprise edition with AlwaysOn Availability Groups on its supported platforms on the primary and secondary replicas.

Disaster Recovery of SQL Server 2012 with AlwaysOn

Availability Groups

Disaster recovery for cluster nodes participating in a SQL Server 2012 AlwaysOn Availability Group is not supported.

For a AlwaysOn Availability Group node, rebuild the computer, install SQL Server 2012, add the node to the Availability Group, and allow SQL to replicate the databases to the rebuilt node.

If more than one node of the Availability Group has failed or the SQL data cannot be replicated, rebuild the nodes and then submit a restore request for the SQL data. After the SQL data is restored, add the database(s) to the Availability Group and allow SQL to replicate the databases.

For more information, refer to your Windows documentation and SQL Server 2012 documentation.

Backup Considerations for SQL Server 2012 AlwaysOn

Availability Group

If you are running SQL Server 2012 Enterprise edition in a AlwaysOn Availability Group configuration, install the agent software on the Primary or Secondary Availability Replica nodes.

The LiveVault agent software backs up the SQL data on whichever node you install the agent software on. A single system can also act as a primary and secondary for different availability groups at the same time.

(13)

Notes

For optimal protection in the event of failover, install the agent software to all nodes in the Availability Group, perform additional configuration steps, and create separate SQL-aware backup policies to protect the replicas on each node.

Primary Availability Replica Node Backup Considerations

For recommended best practices for protecting your SQL databases in an AlwaysOn Availability Group, refer to your Microsoft documentation.

Consider the following factors when deciding whether to install the agent software on the Primary Availability Replica of your AlwaysOn Availability Group:

 The LiveVault agent can run backups on either the Primary or Secondary Availability Replica nodes, but can only perform SQL-aware restores on the primary node.

Because the Secondary Availability Replicas are read-only, restores of data to the secondary replica will fail. You can, however, perform a redirected restore from the Secondary Availability Replica node to another location and manually synchronize the databases.

 Autonomy recommends you back up data from the primary node when AlwaysOn is configured to be asynchronous.

 Installing the agent software requires a reboot of your server. If you install the software on the Primary Availability Replica node, the reboot causes the secondary Availability Replica node to become the primary.

If you want to back up the SQL data from the Primary replica node, you must return the rebooted server to a Primary role after reboot.

 Upon failover, the Primary replica node becomes the Secondary and backups will begin to fail. To ensure uninterrupted backups in the event of a failover, you must perform additional configuration steps to enable the LiveVault software to take snapshots of the Secondary Availability replicas.

Refer to your SQL 2012 AlwaysOn Availability Group help system for instructions on configuring the secondary replica for backup.

IMPORTANT When installing the LiveVault agent on SQL Server 2012 AlwaysOn nodes, do not install as a cluster setup.

Availability Groups do not use shared cluster storage because each node maintains a copy of the database on local storage. Availability Groups require that SQL is installed on clustered systems, but having shared storage is optional and the databases will not be found on shared storage.

(14)

 You must configure the secondary replica nodes in SQL to allow backup. This is not done by default. Refer to your SQL 2012 AlwaysOn Availability Group help system for instructions on configuring the secondary replica for backup.

 Autonomy recommends you back up data from the secondary node when AlwaysOn is configured to be synchronous.

 If you run backups on the secondary node and replication is not working (for example, it is in an Initializing or Failed state), your data will be unprotected until replication is restored.

 Upon failover, the secondary replica node becomes the primary.

Configure the LiveVault Software on Replica Nodes

If you choose to install the LiveVault agent software onto the Primary replica node of the AlwaysOn Availability Group, no additional software configuration is

required.

If you choose to install the agent software onto a Secondary replica node, or to ensure uninterrupted backups in the event of a failover, you must perform additional configuration steps to enable the software to take snapshots of the Secondary Availability replicas.

Configuration Parameter

The agent software configuration settings reside in a file named LVConfig.xml within the agent installation directory, usually located in the following location:

C:\Program Files\Autonomy\BackupEngine\LVConfig.xml The configuration parameter within the LVConfig.xml to allow the service to back up data on a Secondary Availability replica node is :

<BackupTypeCopy>1</VSSBackupTypeCopy>

Stop the Backup Service

In preparation for editing the configuration settings, you must stop the running LiveVault backup service.

To stop the LiveVault backup service

1. Stop the LiveVault agent backup service by one of the following methods.

 Enter the following command at a command prompt:

NOTE If you install the agent software onto the secondary node without first configuring the Secondary replicas for backup in SQL, LiveVault backups will fail with an inability to access the VSS writer to take a snapshot.

(15)

Notes

net stop lvbackupservice The backup service stops.

 Stop the service from the Services Management panel.

i. Click Start, then select Administrative Tools > Computer Management >Services.

ii. Select LiveVault Backup Service.

iii. Select Stop Service.

The backup service stops.

Add the Configuration Parameter

To add the configuration parameter to enable backup on a Secondary Availability Replica node

1. Open the LVConfig.xml file within the installation directory, usually located in the following location:

C:\Program Files\Autonomy\BackupEngine\LVConfig.xml

2. Add the following setting preceding the </Configuration> tag:

3. Save the changes to the file.

Restart the Backup Service

After adding the configuration parameter, you must restart the backup service in order for the agent software to pick up to the changes.

To restart the backup service

NOTE Editing the LVConfig.xml file requires local administrative rights.

IMPORTANTDo not alter any of the existing settings in the LVConfig.xml file.

Doing so prevents your agent from connecting successfully to the LiveVault service.

(16)

The backup service starts.

 Start the service from the Services Management panel.

i. Click Start, then select Administrative Tools > Computer Management >Services.

ii. Select LiveVault Backup Service.

iii. Select Start Service.

The backup service starts.

Restore Considerations for SQL AlwaysOn

Consider the following factors when preparing to restore databases to an AlwaysOn Availability Group:

 In order to restore a database that participates in an Availability Group, you must remove the database from the Availability Group. If this is not done, the restore will fail while trying to prepare the SQL writer for restore.

To prepare the Availability Group for restore

1. In SQL Server Management Studio, remove the database from the Availability Group.

For more information on removing the database from the Availability Group, refer to your SQL Server 2012 documentation.

2. Log into the LiveVault Web Management Portal.

3. Select the agent computer.

4. Perform a SQL aware restore to restore the database(s) to the Primary Availability Replica Node, or perform a file restore to direct it to another node.

The restore completes.

For more information on restore options, refer to the LiveVault Web Management Portal help system.

5. In SQL Server Management Studio, add the database to the Availability Group.

NOTE You cannot add the database to an Availability Group if the database exists in a different state on other nodes.

(17)

Notes

Manual Upgrade of TurboRestore Appliance

You upgrade the Appliance software on manufactured TurboRestore Appliances by one of two methods.

 Automatically update the appliance software via the automatic update feature.

Refer to the LiveVault Web Management Portal Help system for more information on configuring automatic software updates.

 Manually apply software updates through the Appliance Management User Interface, after obtaining the software installation kits from Autonomy

Customer Support.

If you choose to manually apply the software updates through the Appliance Management User Interface, you must update the software installation kits in the following order.

1. Obtain the two appliance installation programs from Autonomy Customer Support.

2. Install the LiveVault Appliance engine installation kit, depending on your platform.

LVBackupAppliance_<build>.exe or

LVBackupEngineX64Appliance_<build>.exe

3. Install the LiveVault Appliance Management User Interface installation kit, depending on your platform.

LVApplianceMgmt_<build>.exe or

LVApplianceMgmtX64_<build>.exe

IMPORTANT The updates must be applied in the order stated above, as components from the engine installation are needed before the

Management User Interface can be installed.

Failure to install these components in the proper will result in an Appliance that cannot connect to the LiveVault system correctly.

(18)

Documentation

The following documentation was updated for this release:

 LiveVault Release Notes

 LiveVault Quick Start Guide

 LiveVault Environment Configuration Guide

 LiveVault Agent Distribution Guide

 LiveVault Disaster Recovery Guide

 LiveVault Appliance Build Guide

 LiveVault Appliance Setup and User Guide

 LiveVault Data Shuttle User’s Guide

 LiveVault Media Restore Server Build Guide

 LiveVault MRS Request Guide for Partners

 LiveVault Web Services Programming Reference

 LiveVault Vault Build Guide: Multiple Volume Vaults

 LiveVault Vault Build Guide: Single Volume Vaults

In addition, the LiveVault Web Management Portal and applications include online Help.

You can retrieve the most current product documentation from Autonomy’s Knowledge Base on the Customer Support Site.

A document in the Knowledge Base displays a version number in its name, such as IDOL Server 7.5 Administration Guide. The version number applies to the product that the document describes. The document may also have a revision number in its name, such as IDOL Server 7.5 Administration Guide Revision 6.

The revision number applies to the document and indicates that there were revisions to the document since its original release.

It is recommended that you periodically check the Knowledge Base for revisions to documents for the products your enterprise is using.

To access Autonomy documentation

1. Go to the Autonomy Customer Support site at https://customers.autonomy.com

2. Click Login.

(19)

Documentation

3. Enter the login credentials that were given to you, and then click Submit.

The Knowledge Base Search page opens.

4. In the Search box, type a search term or phrase. To browse the Knowledge Base using a navigation tree only, leave the Search box empty.

5. Ensure the Documentation check box is selected.

6. Click Search.

Documents that match the query display in a results list.

7. To refine the results list, select one or more of the categories in the Filter By pane. You can restrict results by

 Product Group. Filters the list by product suite or division. For example, you could retrieve documents related to the iManage, IDOL, Virage or KeyView product suites.

 Product. Filters the list by product. For example, you could retrieve documents related to IDOL Server, Virage Videologger, or KeyView Filter.

 Component. Filters the list by a product’s components. For example, you could retrieve documents related to the Content or Category component in IDOL.

 Version. Filters the list by product or component version number.

 Type. Filters the list by document format. For example, you could retrieve documents in PDF or HTML format. Guides are typically provided in both PDF and HTML format.

8. To open a document, click its title in the results list.

To download a PDF version of a guide, open the PDF version, click the Save icon in the PDF reader, and save the PDF to another location.