hitachi application protector - hitachi data systems · pdf fileitachi application protector...

MK-91HAP009-05

Hitachi Application Protector

Quick Install and Configuration Guide for Microsoft® Applications

FASTFIND LINKS

Document Organization

Product Version

Getting Help

Contents

ii

Hitachi Application Protector Quick Install and Configuration Guide for Microsoft® Applications

Copyright © 2011-2014 Hitachi, Ltd., Hitachi Data Systems Corporation. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd.

(hereinafter referred to as “Hitachi”) and Hitachi Data Systems Corporation (hereinafter referred to as “Hitachi Data Systems”).

Hitachi Data Systems reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current

information available at the time of publication. When new and/or revised information becomes available, this entire document will be updated and distributed to all registered users.

All of the features described in this document may not be currently available. Refer to the most

recent product announcement or contact your local Hitachi Data Systems sales office for

information about feature and product availability.

Notice: Hitachi Data Systems products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems agreements. The use of Hitachi Data Systems products is governed by the terms of your agreements with Hitachi Data Systems.

Hitachi is a registered trademark of Hitachi, Ltd. in the United States and other countries. Hitachi

Data Systems is a registered trademark and service mark of Hitachi, Ltd. in the United States and other countries.

All other trademarks, service marks, and company names are properties of their respective

owners.

Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

Contents iii


Contents

Preface .................................................................................................... v

Intended Audience................................................................................................... vi Product Version ....................................................................................................... vi Document Revision Level ......................................................................................... vi Documentation related to Application Protector ......................................................... vii Related Documents ................................................................................................. viii Document Conventions ............................................................................................ ix

Convention for Storage Capacity Values ..................................................................... x

Document Organization ............................................................................................. x

Getting Help ............................................................................................................ xi Comments ............................................................................................................... xi

Introduction .......................................................................................... 1-1

Overview ............................................................................................................... 1-2

Supported Operating Systems ................................................................................ 1-3

Prerequisites ......................................................................................................... 1-4

Hardware Prerequisites ....................................................................................... 1-4

Software Prerequisites ........................................................................................ 1-4

Microsoft® Applications Prerequisites .................................................................. 1-5

Application Protector Server Pre-installation Prerequisites ..................................... 1-6

Application Protector Client Pre-installation Prerequisites ...................................... 1-7

Registering SharePoint Server Writer Services ...................................................... 1-8

Reviewing the Application Protector Configuration Flow ........................................... 1-9

Restrictions and Considerations for Operating Application Protector ........................ 1-10

Limitations ....................................................................................................... 1-10

Operation Restrictions and Considerations ......................................................... 1-13

iv Contents


Installing Application Protector ............................................................... 2-1

Application Protector System configuration .............................................................. 2-2

Managing Application Protector Server Installations.................................................. 2-6

Installing the Application Protector Server ............................................................ 2-6

Upgrading the Application Protector Server ........................................................ 2-10

Repairing the Application Protector Server .......................................................... 2-13

Removing the Application Protector Server ......................................................... 2-16

Managing Application Protector Client Installations ................................................. 2-19

Installing the Application Protector Client ........................................................... 2-19

Updating the Application Protector Client ........................................................... 2-23

Changing the Application Protector Client ........................................................... 2-25

Repairing the Application Protector Client ........................................................... 2-28

Removing the Application Protector Client .......................................................... 2-31

Silent Installation of Application Protector Server and Client ................................... 2-34

HAPRO Server and Client Silent Installation ........................................................ 2-35

HAPRO Server and Client Silent Removal ............................................................ 2-35

Configuring Application Protector ............................................................ 3-1

Understanding the Service Account Permissions ....................................................... 3-2

Licensing Application Protector ............................................................................... 3-4

Viewing Licenses ................................................................................................ 3-4

Activating the License ......................................................................................... 3-4

Preface v


Preface

This document provides instructions for installing Hitachi Application Protector (hereinafter referred to as Application Protector or HAPRO).

This section includes the following topics:

Intended Audience

Product Version

Document Revision Level

Documentation Related to Application Protector

Related Documents

Document Organization

Document Conventions

Convention for Storage Capacity Values

Getting Help

Comments

vi Preface


Intended Audience This guide is intended for the customers and Hitachi Ltd. partners who license,

and use the Hitachi Adaptable Modular Storage (AMS), Hitachi Network Attached Storage (HNAS), Hitachi Virtual Storage Platform (VSP), Hitachi

Unified Storage, and Hitachi Unified Storage VM, and Hitachi Virtual Storage Platform G1000 (VSP G1000) administrators as well as application backup administrators involved in installing, configuring, and operating Hitachi

Application Protector.

Readers of this document should be familiar with the following:

Microsoft® Exchange Server® system administration

Microsoft® SQL Server® system administration

Microsoft® SharePoint Server® system administration

System back up and maintenance

Product Version This document revision applies to Hitachi Application Protector Version 2.8 or later.

Document Revision Level

Revision Date Description

MK-91HAP009-00 January 2012 Initial release

MK-91HAP009-01 September 2012 Revision 1, supersedes and replaces MK-91HAP009-00

MK-91HAP009-02 March 2013 Revision 2, supersedes and replaces MK-91HAP009-01

MK-91HAP009-03 August 2013 Revision 3, supersedes and replaces MK-91HAP009-02

MK-91HAP009-04 February 2014 Revision 4, supersedes and replaces

MK-91HAP009-03

MK-91HAP009-05 July 2014 Revision 5, supersedes and replaces MK-91HAP009-04

Preface vii


Documentation Related to Application Protector

In the following table, Hitachi Application Protector is abbreviated to HAPRO.

Manual name (Document number)

Description Installation

Configuration Operation Maintenance

Quick Install and

Configuration Guide for Microsoft® Applications

(MK-91HAP009)

Installation of the HAPRO

client and server

Prerequisites and restrictions common to HAPRO Exchange Server,

SharePoint Server and

SQL Server documents.

◎ ○

User Guide for

Microsoft® Exchange Server

(MK-91HAP005)

The configuration to use

HAPRO after installing the HAPRO Client and HAPRO Server. License setup, setup of a log level, etc.

Uninstalling HAPRO.

Descriptions of the HAPRO Snapshot function and

usage using GUI.

Descriptions of the HAPRO

log management function.

The unique contents of

HAPRO Exchange Server, SharePoint Server and SQL Server are written in each user’s guide.

◎ ◎

User Guide for

Microsoft® SharePoint Server®

(MK-91HAP006)

User Guide for Microsoft® SQL Server®

(MK-91HAP007)

CLI Guide for Microsoft® Applications

(MK-91HAP021)

Description of the HAPRO CLI functions.

◎

viii Preface


Manual name

(Document number) Description

Installation

Configuration Operation Maintenance

Troubleshooting Guide for Microsoft® Applications

(FE-91HAP010)

Reference guide to log output from HAPRO.

Actions when any

problems occurr in HAPRO.

Descriptions of the

messages output by HAPRO (cause and actions).

Descriptions of the log

information when any

problems occurred in HAPRO.

○ ◎

[Legend] ◎:Most relevant manual ○:Relevant manual

Related Documents

Hitachi Application Protector User Guide for Microsoft® Exchange Server®,

MK-91HAP005

Hitachi Application Protector User Guide for Microsoft® SharePoint Server®, MK-91HAP006

Hitachi Application Protector User Guide for Microsoft® SQL Server®, MK-91HAP007

Hitachi Application Protector CLI Guide for Microsoft® Applications, MK-91HAP021

Hitachi Application Protector Troubleshooting Guide for Microsoft® Applications, FE-91HAP010

Hitachi Storage Adapter for Microsoft® Volume ShadowCopy Service

V04.11 User's Guide, MK-09DF8197

Hitachi Volume Shadow Copy Services (VSS) Hardware Provider User’s Guide, MK-09DF8197

Hitachi NAS Platform™ and Hitachi High-performance NAS platform™ powered by BlueArc® System Administration Guide, MK-96BA002

Preface ix


Document Conventions This document uses the following typographic conventions.

Convention Description

Bold Indicates the text on a window, other than the window title, including

menus, menu options, buttons, fields, and labels. Example: Click Next.

Italic Indicates a variable, which is a placeholder for actual text provided by

the user or system. Example: copy source-file target-file

NOTE: Angled brackets (< >) are also used to indicate variables.

screen/code Indicates the text that is displayed on screen or entered by the user.

Example: # pairdisplay -g oradb

< > angled

brackets

Indicates a variable, which is a placeholder for actual text provided by

the user or system. Example: # pairdisplay -g <group>

NOTE: Italic font is also used to indicate variables.

[ ] square brackets

Indicates the optional values. Example: [ a | b ] indicates that you can choose a, b, or nothing.

{ } braces Indicates the required or expected values. Example: { a | b } indicates that you must choose either a or b.

| vertical bar Indicates that you have a choice between two or more options or arguments. Examples:

[ a | b ] indicates that you can choose a, b, or nothing.

{ a | b } indicates that you must choose either a or b.

|| double vertical

bar

Indicates that you have a choice between two or more options or

arguments. Examples:

[a || b] indicates that you can choose a, b, or nothing.

{a || b} indicates that you must choose either a or b.

underline Indicates the default value. Example: [ a | b ]

This document uses the following icons to draw attention to information.

Icon Meaning Description

Tip Tips provide helpful information, guidelines, or suggestions for

performing tasks more effectively.

NOTE Calls attention to important and/or additional information.

CAUTION Failure to take or avoid a specified action can result in adverse conditions or consequences (for example, loss of access to

data).

WARNING Failure to take or avoid a specified action can result in severe

conditions or consequences (for example, loss of data).

x Preface


This document uses the following conventions for support matrix.

Conventions Description

Features that are fully functional and available in Hitachi Application

Protector.

x Features that are not functional or not available in Hitachi Application Protector.

Not Supported Features that are not supported by Hitachi Application Protector.

Convention for Storage Capacity Values Storage capacity values for the Hitachi Data Systems storage products are

calculated based on the following values:

Hard Disk Drives (HDDs and SDDs)

Physical Disk Capacity

Logical Units (Block size = 512 B)

(Logical Disk Capacity)

1 KB = 1,000 bytes 1 KB (kilobyte) = 1,024 bytes

1 MB = 1,0002 bytes 1 MB (megabyte) = 1,0242 bytes

1 GB = 1,0003 bytes 1 GB (gigabyte) = 1,0243 bytes

1 TB = 1,0004 bytes 1 TB (terabyte) = 1,0244 bytes

1 PB = 1,0005 bytes 1 PB (petabyte) = 1,0245 bytes

1 EB = 1,0006 bytes 1 EB (exabyte) = 1,0246 bytes

Document Organization The following table provides thumbnail descriptions of the chapters. Click the

chapter name in the first column to go to that chapter. The first page of every chapter contains links to the contents.

Chapters Description

Chapter 1,

Introduction

This chapter provides an introduction of Application

Protector.

Chapter 2, Installing

Application Protector

This chapter provides the details of installing

Application Protector.

Chapter 3,

Configuring Application Protector

This chapter provides information about mandatory

configuration (first time) after installing Application Protector.

Preface xi


Getting Help If you need to call the Hitachi Data Systems Support Center, make sure to

provide the following items:

The circumstances surrounding the error or failure.

Debug information acquired by executing the HAPRO_DUMP command.

For details about the HAPRO_DUMP command, refer to the Hitachi

Application Protector CLI Guide for Microsoft® Applications.

The Hitachi Data Systems customer support staff is available 24 hours a day,

seven days a week. If you need technical support, log on to the Hitachi Data Systems Portal for contact information: https://portal.hds.com.

Comments Please send us your comments on this document: [email protected]. Include the document title and number, including the revision level (for

example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems.

Thank you!

https://portal.hds.com/

mailto:[email protected]

1

Introduction 1-1


Introduction

This document describes how to install the Hitachi Application Protector

(hereinafter referred to as Application Protector or HAPRO).

This chapter describes the following topics:

Overview

Prerequisites

Reviewing the Application Protector Configuration Flow

Restrictions and Considerations for Operating Application Protector

1-2 Introduction


Overview Application Protector is application protection software that uses storage

snapshots for backups. It also uses recovery time objective (RTO) and recovery point objective (RPO) for database recovery, based on client-server

architecture.

Application Protector supports Microsoft® Exchange Server®, Microsoft® SQL

Server®, and Microsoft® SharePoint Server® (hereinafter referred to as Exchange Server, SQL Server, and SharePoint Server respectively).

Application Protector Server is installed on the host running the supported

Microsoft® Application. Application Protector Server helps backup and storage administrators to create shadow copies, also known as snapshots, of the

storage logical units (LUNs) hosting the supported Microsoft® Application databases.

Application Protector Client is a graphical user interface (GUI) Microsoft® Management Console (MMC) snap-in that allows the Administrators to manage

Application Protector Servers remotely. MMC provides access to Application Protector functions including snapshot and schedule management as well as recovering the protected databases for the supported Microsoft® Application

installed on the server.

NOTE: You cannot create a combined snapshot of multiple entities that have

storage LUNs coming from dissimilar storage systems (such as VSP, HUS VM, AMS, HNAS, HUS, and VSP G1000 and that are supported by Application

Protector). Application Protector supports creating combined snapshot of application database entities that are mounted on a similar type of storage system LUNs.

In addition, the command line interface (CLI) tool, HAPRO.exe, provides functions that are similar to the MMC-based snap-in GUI. For more details on CLI commands, refer to the manual, Hitachi Application Protector CLI Guide

for Microsoft Applications.

Introduction 1-3


Supported Operating Systems The following table lists the supported Microsoft® Windows Operating System

versions and the supported Microsoft® Applications for Application Protector.

Table ‎1-1 Supported Microsoft® Applications for Application Protector

Microsoft® Application

Version

Microsoft® Windows Operating System

Win2008 R2 SP1 64-bit

Win2012 64-bit

Win2012 R2 64-bit

Microsoft®

Exchange Server

2007 SP1 x x x

2007 SP2 x x x

2007 SP3 x x

2010 x x

2010 SP1 x x

2010 SP2 x x

2010 SP3 x

2013 x

2013 SP1 x x

Microsoft® SQL

Server®**1

2005 SP3 x x

2005 SP4 x x

2008 SP1 x x

2008 SP2 x x

2008 SP3 x x

2008 R2 SP1 x x

2008 R2 SP2 x x

2008 R2 SP1 MSFC **2 x x

2008 R2 SP2 MSFC **2 x x

2012

2012 SP1

Microsoft® SharePoint

Server®

2007 SP1 x x x

2007 SP2 x x

2007 SP3 x x

2010 SP1 x x

**1 Application Protector does not support configurations in which the SQL Servers of different versions are mixed.

**2 In Windows 2008, Microsoft® Cluster service is known as Microsoft Failover Cluster (MSFC). Application Protector supports MSFC in 2 Node Active-Passive configurations. For more details, see the section for configuring and protecting database entities in a Cluster setup, in the Hitachi Application Protector for SQL Server User Guide.

1-4 Introduction


Prerequisites This section describes the hardware, software, and HAPRO client and server

prerequisites.

Hardware Prerequisites

The following table describes the hardware prerequisites for Application

Protector.

Table ‎1-2 Hardware Prerequisites

Item Description

System Processor 64 bit, 1.5 GHz (Dual Core Recommended)

System Memory 2 GB

Install Free Disk Space 20 MB (Minimum)

Networking Gigabit Ethernet Recommended

Software Prerequisites

The following table describes the software prerequisites for Application

Protector.

Table ‎1-3 Application Protector Server Software Prerequisites

Item Description

Supported

Operating Systems

• Microsoft® Windows 2008 R2 SP1

• Microsoft® Windows Server 2012

• Microsoft® Windows Server 2012 R2

Application Software

• Microsoft® Exchange Server 2007 SP1,SP2,SP3

• Microsoft® Exchange Server 2010 Non-SP, SP1, SP2, SP3

• Microsoft® Exchange Server 2013 Non-SP, SP1

• Microsoft® SQL 2005 SP3 and above (x86 & x64)

• Microsoft® SQL 2008 SP1 and above (x86 & x64)

• Microsoft® SQL 2008 R2 SP1 and above (x86 & x64)

• Microsoft® SQL 2012 Non-SP and above (x64)

• Microsoft® SharePoint 2007 SP2 and above

• Microsoft® SharePoint 2010 SP1 and above

Introduction 1-5


Item Description

Hitachi Applications

• Hitachi HNAS VSS Provider v 8.1, 8.2, 10.0, 10.2, 11.0, 11.1

• Hitachi Storage Adapter for Microsoft® Volume Shadow Copy

Service V04.11.0

Other Applications • Microsoft .NET Framework 3.5 SP1

• MMC v3.0

In addition, the service in the following table must be in operation.

Table ‎1-4 Related Service

Service Name Display Name The kind of the startup Remarks

VSS Volume Shadow Copy Manual or Automatic It is a service to make backups, such as Volume

Shadow Copies.

Microsoft® Applications Prerequisites

Microsoft® Applications must have the corresponding writer services installed

and configured on the server machine.

The following table describes the Microsoft Applications writer services.

Table ‎1-5 Microsoft Application Prerequisites

Microsoft® Application

Writer Service Registering Writer Service

Exchange Server® Microsoft® Exchange

Information Store

Registered automatically

SQL Server® SQL Writer Service Registered automatically

SharePoint Server®

2007

Windows® SharePoint

Services VSS Writer

Use the following command:

“stsadm –o registerwsswriter”

For more details, see Registering SharePoint Server Writer Services.

SharePoint Server®

2010

SharePoint 2010 VSS Writer Use the following command:

“stsadm –o registerwsswriter”

For more details, see Registering SharePoint Server Writer Services.

1-6 Introduction


Application Protector Server Pre-installation Prerequisites

You must perform the following tasks prior to installing the Application Protector

Server.

Microsoft® applications and the corresponding Writer services must be installed and registered.

Appropriate VSS Provider must be installed and configured on the application server.

SharePoint Server writer services must be installed and registered. For more information on registering, see Registering SharePoint Server Writer Services

SQL Server writer services must be running for the connected SharePoint Server.

AMS, VSP, HUS VM, HNAS, HUS, or VSP G1000 LUNs must be created and mounted on the target server on which the supported Microsoft®

Application is installed and running.

AMS, VSP, HUS VM, HNAS, HUS, or VSP G1000 LUNs must be formatted using NTFS file system and Application database objects mounted on these

LUNs.

CAUTION! All application instance database object files (database and logs) that

need to be protected using Application Protector must be mounted on either AMS, VSP, HUS VM, HNAS, HUS, or VSP G1000 LUNs. Application Protector does not

support mixed storage LUNs, such as LUNs coming from dissimilar storage systems and its models.

Hitachi Storage Adapter for Microsoft® Volume ShadowCopy Service to

create storage hardware snapshots or Shadow Images on the backend storage system.

NOTE: The hardware provider is configured using VSS provider configuration

utility with the details for accessing the storage system or its other prerequisite configuration software, such as CCI/Raidcom Manager/HORCM.

Hitachi HNAS Controller has VSS access enabled (on SMU Web UI set this by navigating to Home > Server Settings > VSS Access Configuration).

The Hitachi AMS, HUS P-VOLs exposed on the server have pre-created S-VOLs with a resting state as PSUS (a prerequisite for Shadow Image (SI) snapshots) using the VSS Provider UI.

The Hitachi AMS and HUS P-VOLs exposed on the server have pre-created S-VOLs. In addition, configure VSS Provider with the controller IPs for AMS/HUS.

Introduction 1-7


Hitachi VSP, HUS VM, and VSP G1000 has the CCI (HORCM) configured and running. VSS provider must be configured with the serial number of the VSP, HUS VM, and VSP G1000 system. For more details, see Hitachi

Storage Adapter for Microsoft® Volume ShadowCopy Service V04.11 User's Guide.

Hitachi VSP, HUS VM, and VSP G1000 must have the S-VOLs pre-created

having relationship status as PAIR.

Application Protector provides limited support for Cluster Continuous Replication (CCR) environment of Exchange Enterprise Server 2007.

In a cluster environment, you may plan to switch Application Protector to

the other cluster nodes for backup and recovery. It is recommended that you always store the Application Protector metadata on a storage LUN that can be shared and made accessible from the active and the designated

passive cluster node.

Application Protector Server must be set up to handle failover and failback

scenarios in the SQL Server clustered environment. This is a one-time

configuration and is required for the cases where you may want to switch

the backup to a new active cluster node or perform the database

recovery on a different node than the one on which the snapshot was

actually created.

WARNING! You must specify the mount point that is located on a non-clustered

disk. Windows does not support mounting a LUN on a clustered disk when working with MSCS or MSFC cluster.

See the following for more information about setting up Application Protector

in a clustered environment for Exchange Server and SQL Server:

Hitachi Application Protector User Guide for Microsoft® Exchange Server®

Hitachi Application Protector User Guide for Microsoft® SQL Server®

For more information about configuring Hitachi applications, see:

Hitachi Volume Shadow Copy Services (VSS) Hardware Provider User’s Guide

Hitachi NAS Platform™ and Hitachi High-performance NAS platform™ powered by BlueArc® System Administration Guide

Application Protector Client Pre-installation Prerequisites

You must perform the following tasks prior to installing Application Protector Client.

1. Microsoft® .NET Framework 3.5 must be installed on the Client machine.

2. MMC version 3.0 must be installed on the Client machine if it is not there

by default.

1-8 Introduction


Registering SharePoint Server Writer Services

Registering the SharePoint Writer provides the list of available databases to

perform snapshots related activities.

To register SharePoint server writer

1. Go to the command prompt.

2. Change the command path to %ProgramFiles%\Common

Files\Microsoft Shared\Web Server Extensions\12\BIN for SharePoint Server 2007 SP2.

OR

Change the command path to %ProgramFiles%\Common

Files\Microsoft Shared\Web Server Extensions\14\BIN for SharePoint Server 2010 SP1.

3. Type the following command to register the SharePoint Server writer services:

Stsadm –o registerwsswriter

Introduction 1-9


Reviewing the Application Protector Configuration Flow The following figure illustrates the Application Protector environment

configuration flow.

Figure ‎1-1 Application Protector environment configuration flow chart

1

Configuration for prerequisites

Installation and configuration of VSS Provider

(See：Hitachi Storage Adapter for Microsoft® Volume

ShadowCopy Service V04.9 User's Guide)

Storage configuration (assignment of P-VOL and create PAIR)

(See：Users guide for supported storage)

Allocate the data of the target application to the HAPRO

supporting storage, or verify that the data of the target application has been allocated to the HAPRO supporting storage.

Registration of VSS Writer service

(See: "Prerequisites" in this document)

Refer to the "Prerequisites" of each HAPRO User's Guide for

the other prerequisites.

2

Installing HAPRO Server

Install HAPRO Server in the Application server

(See: Installing the Application Protector Server in this manual)

3

Installing HAPRO

Client

Install HAPRO Client in Application Server or host that can be accessible to Application server.

(See: Installing the Application Protector Client in this manual)

Configure the service account

(See: Configuring Service Account Credential in HAPRO

Users Guide)

Register the HAPRO license

(See: Licensing Application Protector in each User’s

Guide for HAPRO)

4

Configuring HAPRO

1-10 Introduction


Restrictions and Considerations for Operating Application Protector

HAPRO has some restrictions and considerations on installation and operation.

This section describes the following:

Restrictions and considerations for the HAPRO environment (environment for operation or installation)

Restriction and considerations for operating HAPRO.

Limitations

The following table describes limitations when installing or operating HAPRO. Items 1 to 3 in the following table are all prerequisites not only for installation

but also for using HAPRO after installation.

Table ‎1-6 Limitation for HAPRO environment

Item Contents

Restricting HAPRO configuration Do not allocate multiple application data on same LUN.

Restricting the number of LUNs

Microsoft Windows gives up to 255 LUNs per host. If the VSS

Provider tries to map the LUN number more than 255 for the backup

target S-VOL, this backup operation will fail as Windows cannot recognize the specified LUN number. Therefore, specify the LUN number 254 or less.

Restricting reverting If user didn't have appropriate privileges, the revert operation may not be performed. Assign “Administrator” privileges to SQL server

roles of “public” and “sysadmin”. Then, you can perform revert operation.

Restricting calling VSS provider

function at reverting operation

If the VSS provider processing has failed at reverting operation,

P-VOL may be offline. In this case, the user must set disk as online manually. For the details, see Hitachi Storage Adapter for Microsoft® Volume ShadowCopy Service V04.9 User's Guide or visit http://support.microsoft.com/kb/2668865.

Restricting volume configuration

for disk

The configuration containing multiple volumes for one disk is not

supported.

Restriction due to the

configuration change

If the user has changed the application configuration, recovery,

or revert using the Snapshot, which was retrieved before changing the configuration, it cannot be used. If the configuration has changed, a Snapshot needs to be obtained again.

Restriction on Snapshot retrieval against the volume mounted on the directory

If a user mounts the directory on the storage which is not supported by HAPRO and locates the entity on the volume, a Snapshot cannot be retrieved.

Source volume and mount point need to be the storages supported by HAPRO.

http://support.microsoft.com/kb/2668865

Introduction 1-11


Item Contents

Precautions on entity configuration when executing Revert Snapshot

Do not store any data other than the Revert Snapshot target entity in the volume in which the Revert Snapshot target entity data is stored.

Restriction when a Snapshot is mounted on another server

1. Snapshot created for the HNAS volume cannot be mounted on another server.

2. A server on which a Snapshot is created and a server on which a snapshot to be mounted should use the same OS version.

System database on the SQL Server

Do not locate the system database on the SQL Server to the backup target volume of HAPRO.

When using the Replace Target Database Files with the Revert

option in Recover

Do not store any data other than the target entity of the Replace Target Database Files with the Revert option in the volume in which

the target entity data of the Replace Target Database Files with

Revert option is stored.

Consistency of a Snapshot

created using HAPRO for SQL

When you plan database backup and recovery using HAPRO for SQL,

follow the procedure supported by the applicable business application (SharePoint, SAP) which uses the database. Note that HAPRO for SQL only guarantees the consistency of the database and not applications using the DBs.

Functions of Exchange Server 2013

The following functions of High Availability and Site Resilience are not supported.

-Support for multiple databases per disk

-Automatic reseed

-Automatic recovery from storage failures

-Lagged copy enhancements

Reference URL: http://technet.microsoft.com/en-us/library/ jj150540(v=exchg.150).aspx

Limitation of the usable

characters for Entity

Do not include “|” (vertical bar) in the name of the backup target

Entity.

Upgrading from HAPRO v2.0 When upgrading HAPRO from v2.0, please upgrade both HAPRO

Server and Client. Also, please configure the Service Account again after upgrading from v2.0. Otherwise, you cannot use fully HAPRO features.

Precautions when using RDM LUs on VMware

1. When configuring RDM LUs, set [Physical Compatibility Mode].

2. When creating and mounting snapshots for RDM LUs, the

mountable server configuration is any of the following.

- A Virtual machine which created the snapshots.

- A different virtual machine on the ESXi Server on which the virtual machine created the snapshots is running.

- A virtual machine on the different ESXi Server from the ESXi Server on which the virtual machine created the snapshots is running.

Restrictions on the number of nodes in SQL Server 2012

AlwaysOn environments.

AlwaysOn Failover cluster instance supports the two nodes cluster configuration.

Also, AlwaysOn Availability Groups supports one Primary Server and up to four Secondary Servers.

1-12 Introduction


Item Contents

Restrictions on the environments when executing Restore Entity and Recover Entity in SQL Server 2012 AlwaysOn environments

(AlwaysOn Availability Groups)

It is needed to configure with the same service account and password on each server.

Note that this restriction is not applicable if the following options are specified.

- CLI

Specifying --disableautorecovery.

- GUI

Checking "Disable auto recovery (AlwaysOn Availability Groups)" in the "Select Recovery Options" window.

Considerations for "SQLBackupFolder" to be set in

SetConfig.

1. The shared folder should be accessible from a secondary node via the UNC path.

2. A name of the shared folder should be the specified folder name.

Example:

Specified folder: C:\temp\AGBackup

Shared folder name: AGBackup

3. There should be some free space in which the full backup data and the log backup data of the primary database can be stored temporarily.

Restrictions on HAPRO remote configuration

Connection between HAPRO Client and HAPRO Server which are belonging to the different domains is not supported.

Introduction 1-13


Operation Restrictions and Considerations

The following table describes the restrictions and considerations for operating HAPRO.

Table ‎1-7 Restrictions and considerations for operating HAPRO

Item Contents

Specifying File and

Directory path

Application Protector does not allow specifying special character

including comma(,), colon(:), and other delimiter characters when the user specifies LUN, directory path, and file name. If specified, the required operation such as creating a Snapshot will fail.

UNC path only supports Granular Recovery (EXG) and RFR archive log

(SQL) functions. Other functions are not supported by UNC path.

Restricting

consecutive creation of snapshot

Snapshot will fail. Snapshot creation is an asynchronous process using

the Microsoft VSS subsystem. A snapshot cannot be created if VSS is in the busy status by doing backup or restore on any other object iSCSI LUN from a third party VSS enabled requestor. When any operations through the VSS subsystem (creating, mounting and reverting Snapshot) are performed, leaving more than one minute interval between the operations is recommended.

Restricting for deleting

Entity

When the Entity is deleted, operations such as displaying, deleting,

mounting, unmounting and reverting Snapshot may not be able to perform. You need to delete an entity, database, or snapshot using HAPRO GUI only

Execution time for deleting Snapshot

Snapshot deletion may take time depending on the environmental conditions such as configurations.

Restricting Snapshot creation

Snapshot creation fails, if the error code “80042314” is included in the error message, the error may be displayed because a high load is put on the system.

In this case, take the following actions:

1. Create a Snapshot when the load on the system is low.

2. Reduce the target entity to create a Snapshot.

When an error has

occurred in the VSS Provider

If error code “80042306”is included in the error code when an error

has occurred during the HAPRO operation, a problem may have occurred in the VSS Provider.

Take the appropriate action according to the VSS Provider manual.

Precautions on

operating Revert

If either the Revert Snapshot or optional Revert operation of Recovery

has failed and the error message “800423fe” has been included, check the following:

Verify that no other disk having the same disk signature as the P-VOL exists.

If the same disk signature as P-VOL exists, change the disk signature.

Maximum number of target volumes to create the Snapshot

The maximum number of volumes that can be included in the Snapshot per Snapshot creation is 64. To create the Snapshot for more than 65 volumes, set the number of volumes included in one Snapshot to less than 64 and create Snapshots over several times.

1-14 Introduction


Item Contents

Precautions to

execution user

Use the administrative user account to access the HAPRO Client.

Error event logs occurred during Recovery or Restore and Revert operations.

Error event logs may be recorded in the OS event log against the target entity. Error event logs to be output:

Log Name: Application

Source: MSExchange Search Indexer

Event ID: 104

Task Category: General

Level: Error

Description:

Exchange Search Indexer failed to enable the Mailbox Database <target entity name> (GUID = <GUID of the target entity>) after <the number of retries> tries. The last failure was: MapiExceptionMdbOffline…

The above event logs may occur when the database is suspended.

If the event logs were output during the database is suspended by the HAPRO operation, no problem even if you ignore the event logs.

Error event logs occurred during the HAPRO operation

If the mailbox database which manages the system mailbox is suspended, or if the mailbox database is the target database to be operated by HAPRO, error event logs may be recorded in the OS event

log.

Log Name: Application

Source: MSExchange Management Application

Event ID: 5000

Task Category: AdminAuditLog

Level: Error

Description:

Failed to save admin audit log for this cmdlet invocation.

To avoid the above error event logs, take the all following actions:

Move the mailbox to a database other than the HAPRO operation target database.

Place the mailbox database which manages the system mailbox,

online.

When a Snapshot

cannot be deleted

If a Snapshot created by HAPRO has been deleted due to the storage

operation or any other reasons, a Snapshot cannot be deleted from HAPRO.

In this case, delete a Snapshot of HAPRO using ”-deletemetadata” in HAPRO_SYNC utility.

For the details of HAPRO_SYNC utility, refer to the manual, Hitachi

Application Protector CLI Guide for Microsoft® Applications.

Introduction 1-15


Item Contents

Precaution when

performing Recover Entity in the Exchange Server environment

HAPRO cannot use the latest transaction log (Enn.log) when mounting

the database.

To perform the recovery including the latest transaction log (Enn.log),

dismount the database before performing recovery.

Error display to users Error notification methods to users are as shown below.

CLI operation: Output to the command prompt

Output to log file

GUI operation: Output to the pop-up window

Output to log file

Execution of schedule: Output to log file

Precaution for recovery

If only S-VOL of a volume has deleted when multiple volumes are included in a Snapshot set, an error occurs and terminated as the required backup does not exist for recovery.

In this case, delete a target Snapshot and create a Snapshot again.

Precaution when

operating a Snapshot

Do not use the access Snapshot with more than one server

simultaneously.

Precaution when

creating a Snapshot

Ensure that a Snapshot is not mounted in HAPRO while also creating a

new snapshot.

Limitation of the characters to be input

Multibyte characters cannot be specified for HAPRO including file names and directory path.

Precaution for the enabled path length

Microsoft Windows gives restrictions that when path length including a file name exceeds 259 characters, this data cannot be deleted. Therefore, do not use a path with more than 259 characters.

When the file and

folder created by HAPRO cannot be deleted

For the deletion method of a file and a folder, visit the following URL:


Precaution for creation

of Snapshot

After completing a “Create snapshot” operation, the to-be-created

snapshot may display in the Snapshots tab before it is completely finished, as shown in the Operations tab.

After expiration date of TrialLicense

expired, the

confirmation screen of the validation of TrialLicense is displayed

Install a valid license after closing the "Do you want to activate trial license?" dialog displayed and start the Activate License Wizard.

Precaution for the descriptions of SnapshotName when importing metadata

When the import of metadata finishes normally, “N.A.” is displayed by SnapshotName in the Operation tab of HAPRO of the server side of the import destination. No problem even if you ignore it.


1-16 Introduction


Item Contents

Instruction at the time

of HAPRO installation.

When HAPRO installation was executed, there is the case that restart

is necessary. In this case, the following messages are displayed.

Click “Yes” when you execute the restart immediately or Click “No”

when you execute the restart later, then click “Finish”.

Output message: You must restart your system for the configuration changes made to Hitachi Application Protector Server 2.8.0 (x64) to take effect. Click Yes to restart now or No if you plan to manually restart later.

Precautions for

executing roll forward recovery of Exchange Server

When a roll forward recovery is executed in the Exchange Server, it is

necessary to meet all of the following terms for the entity which is the target of the roll forward recovery.

All transaction log files which the Exchange Server created exist in the

destination of the recovery after having created the target snapshot

executing the roll forward recovery.

When operating the generation, all snapshots after having created a snapshot to execute the roll forward recovery exist.

Health monitoring of VSS Service

Even if an error occurs in VSS service, there is the case that HAPRO cannot detect it.

Monitor the Windows event log in order to detect the problem early.

Precaution for

schedule that is executed on a switchover date of Standard Time from

Daylight Saving Time.

Create Snapshot which has been scheduled to be executed at the end

of summer and the beginning of winter switchover time may not be executed.

Example: Schedule to be executed at between PST AM1:00 and 1:59

on 2014/11/2.

Set the schedule to execute Create Snapshot while avoiding the end of summer and the beginning of winter switchover time.

To create a Snapshot during the time zone shown above, create a Snapshot manually.

Reference information:

http://support.microsoft.com/kb/325413/en-us

Multiple clients managing the same HAPRO Server

If the following conditions are met, the HAPRO client does not operate.

- Using different user accounts on the same host.

- Operating the HAPRO client simultaneously using the two user accounts.

Use a single client/single user account for simultaneous operation.

Deleting the log

causes errors during GUI operations

When deleting the HAPRO log, ensure that the HAPRO client attached

to the Application server is not operating.

No HAPRO processes are operating on the Application.

Restrictions on creating a Snapshot in SQL Server 2012

AlwaysOn environments (Availability Groups)

Full backup Snapshot cannot be created for the secondary database.

http://support.microsoft.com/kb/325413/en-us

Introduction 1-17


Item Contents

Precautions to execute

Revert Snapshot in SQL Server 2012 AlwaysOn environments (Availability Groups)

If the database included in the corresponding Snapshot has been

added to the availability group, the database must be removed from the availability group before executing Revert Snapshot.

Note that this precaution is not applicable when the Revert option of Recover Entity or Restore Entity is specified.

Precautions to execute

Recover Entity and Restore Entity in SQL Server 2012 AlwaysOn environments (Availability Groups)

1. Since there is an influence on the recovery operation of HAPRO, do

not back up the primary database using HAPRO, or do not retrieve the backup by operating the SQL Server during the recovery operation.

2. Since HAPRO does not detect failover of the availability group,

operations when failover occurs during the HAPRO recovery

operation is not guaranteed. Do not execute a failover of the availability group during the recovery operation.

Precautions to create a Snapshot schedule

If the next backup starting time has come before completing the scheduled backup, the next backup will be skipped and not executed. To avoid this situation, review the Snapshot schedule so as not to skip the scheduled backup.

1-18 Introduction


2

Installing Hitachi Application Protector 2-1


Installing Application Protector

This chapter guides you through the installation wizard for installing the Application Protector Server and Client. A single master installer installs the relevant server and client software on whichever supported system it is

launched.


Application Protector System configuration

Managing Application Protector Server Installations

Managing Application Protector Client Installations

Silent Installation of Application Protector Server and Client

2-2 Installing Hitachi Application Protector


Application Protector System configuration HAPRO consists of the server and client components. The HAPRO client exists

per application corresponding to each Exchange/SQLserver/SharePoint. Two configurations are available as the installation configuration of HAPRO Client and

HAPRO Server:

One configuration is for installing HAPRO Client and HAPRO Server on different hosts (refer to “Figure ‎2-1 HAPRO Client and HAPRO Server

installed on different hosts”).

The other configuration is for installing HAPRO Client and HAPRO server on the same host (refer to “Figure ‎2-2 HAPRO Client and HAPRO Server

installed on the same host”).

You can use both configurations according to the system operation policy.

The Snapshot volumes acquired by HAPRO can be mounted on servers—other

than the business server—according to the user operation, for the purpose of verifying the backup data and acquiring the secondary backup (in addition to

the original purpose as a backup). In this case, installing the HAPRO Server on the server to be mounted is required (refer to “Figure ‎2-3 Configuration when

mounting and using a Snapshot from another server”).



DBserver (SQLserver)

Mail server (Exchange)

Exchange Server

Windows

Exchange DB

ShadowImage / CoW / JetClone

VSP / AMS / HUS /HUS VM / HNAS

Control point

Windows

WMI

HAPRO Server

User system

Backup

Revert

VSS H/W

Provider

MMC HAPRO Client

for SharePoint

Client HAPRO Client

For SQLserver

Client HAPRO Client

For Exchange

RAID Manager

Windows

HAPRO server

Contents server

(SharePoint) Windows

HAPRO server

SQLserver

DB

Backup

Revert

Contents (SQLserverDB)

Backup

Revert

Restore

Restore

Restore

SNM2-API

SQL Server

VSS H/W

Provider

RAID Manager

SNM2-API

SharePoint Server

VSS H/W

Provider

RAID Manager

SNM2-API

SQL Server

IP Network

WMI： Windows Management and Instrumentation MMC： Microsoft Management Console

Figure ‎2-1 HAPRO Client and HAPRO Server installed on different hosts



DBserver (SQLserver)


Exchange Server

Windows

Exchange

DB



HAPRO Server

User system

Backup

Revert

VSS

H/W

Provider

HAPRO Client

For SQLserver

Client

HAPROClient

For Exchange

RAID Manager

Windows

HAPRO server

Contents server

(SharePoint) Windows

HAPRO server

SQLserver

DB

Backup

Revert

Contents (SQLserverDB)

Backup

Revert

Restore

Restore

Restore

SNM2-API

SQL Server

VSS

H/W

Provider

RAID Manager

SNM2-API

SharePoint Server

VSS

H/W

Provider

RAID Manager

SNM2-API

SQL

Server

WMI WMI

HAPRO Client

for SharePoint

Client

WMI

MMC MMC MMC

Control point

IP Network

Installed according to the user system configuration (not necessarily required for HAPRO system configuration)


Figure ‎2-2 HAPRO Client and HAPRO Server installed on the same hosts



Host for secondary use


Exchange Server

Windows

Exchange DB



Control point

Windows

WMI

HAPRO Server

User system

Backup

VSS

H/W Provider

MMC

HAPRO Client For Exchange

RAID Manager

Windows

HAPRO server

SNM2-API

Exchange Server

VSS

H/W Provider

RAID Manager

SNM2-API

IP Network

Mount


Figure ‎2-3 Configuration when mounting and using a Snapshot from another server



Managing Application Protector Server Installations

Installing the Application Protector Server

To install the Application Protector Server:

NOTE: Elevated privileges are required to install the Application Protector

Server.

1. Insert the Application Protector installation media in the applicable drive.

2. The Auto launcher launches the master installer or if you prefer, you can double-click the master installer Setup.exe to launch the Application

Protector master installer.

3. On the Hitachi Application Protector master installer dialog box, click

Install HAPRO Server Software to start the Application Protector Server installation.

Figure ‎2-4 Hitachi Application Protector master installer dialog box



4. In the Hitachi Application Protector Server Setup wizard Welcome dialog box, click Next.

Figure ‎2-5 Welcome dialog box

5. Accept the End User License Agreement to proceed with the installation.

Figure ‎2-6 End-User License Agreement dialog box



6. Use the default path for installation, or click Change to navigate and select a custom path, then click Next.

Figure ‎2-7 Destination Folder dialog box

NOTE:

The length of the installation path must not exceed 60 Characters.

Following are the characters which can be specified for the install path:

A-Z, a-z, 0-9, !, #, $, &, ', (, ), +, -, ., :, =, @, [, \, ], ^, _, `, {, }, ~, space

7. Click Install to start the installation process.

Figure ‎2-8 Ready to Install dialog box



8. Click Finish to complete the installation and exit the Setup wizard.

Figure ‎2-9 Completion dialog box

NOTE: When the HAPRO installation is executed, a system restart might be necessary. In this case, the following messages are displayed:

Click “Yes” when you execute the restart immediately or Click “No” when you execute the restart later, then click “Finish”.

Output message:

You must restart your system for the configuration changes made to Hitachi

Application Protector Server 2.8.0 (x64) to take effect. Click Yes to restart now or No if you plan to manually restart later.



Upgrading the Application Protector Server

This section describes the steps to upgrade the existing Application Protector Server. Currently, Application Protector Server supports upgrade from version

2.0 or 2.1 or 2.6 or 2.7.

NOTE: Perform the following prior to upgrading the Application Protector Server:

1. Stop the Application Protector Server operations.

2. Restart the Windows Management Instrumentation (WMI) winmgmt service or stop the wmiprvse.exe process from the Task Manager.

The procedures described in this Note are not only applicable to the upgrade of the Application Protector Server, but also to the repair installation.

To upgrade the Application Protector Server:

NOTE: Elevated privileges are required to upgrade the Application Protector

Server.


2. The auto-launcher launches the master installer or you can double-click the Setup.exe to launch the Application Protector master installer.

3. Click Install HAPRO Server Software in the Hitachi Application Protector master installer wizard to start the Application Protector Server upgrade.

Figure ‎2-10 Application Protector master installer wizard

4. Click Yes in the confirmation wizard to start the upgrade.



Figure ‎2-11 Upgrade confirmation

5. Click Install in Resuming the Hitachi Application Protector Server Setup Wizard.

Figure ‎2-12 Resuming the Setup Wizard

In case that HAPRO is in progress, the following dialog will be displayed. If the server can be rebooted after upgrading HAPRO, click OK and continue to upgrade. If the

server cannot be rebooted, click Cancel to interrupt the upgrade process.

Figure ‎2-13 Upgrade suspension message



6. Click Finish to complete the upgrade and exit the Setup wizard.

Figure ‎2-14 Completing the Setup Wizard

NOTE:

To upgrade the Application Protector Server, execute the following HAPRO_SYNC utility command to synchronize the HAPRO WMI data: HAPRO_SYNC.exe –u

When the HAPRO upgrade is executed, it might be necessary to restart the

system.



Repairing the Application Protector Server

To repair the installed Application Protector Server:

NOTE: Elevated privileges are required to repair the Application Protector Server.


2. The Auto launcher launches the master installer (or, you can double-click

the master installer Setup.exe to launch the Application Protector master installer).

3. On the Hitachi Application Protector master installer dialog box, click Install HAPRO Server Software.

Figure ‎2-15 Hitachi Application Protector Master Installer dialog box

4. In the Hitachi Application Protector Server Setup wizard Welcome

dialog box, click Next.




5. In the Application Protector Server Setup wizard Change, repair, or remove installation dialog box, click Repair to repair the error in the

installation by fixing the missing and corrupt files, shortcuts, and registry entries.

Figure ‎2-17 Change, repair, or remove installation

6. Click Repair in the Ready to repair Hitachi Application Protector Server

wizard.

Figure ‎2-18 Ready to repair



In case that HAPRO is in progress, the following dialog will be displayed. If the server can be rebooted after the repair installation of HAPRO, click OK

and continue the repair installation. If the server cannot be rebooted, click Cancel to interrupt the repair installation. Re-execute the repair installation after taking the procedure stated in the first note of the section,

Upgrading the Application Protector Server.

Figure ‎2-19 Repair installation message

7. In the Hitachi Application Protector Server Setup wizard, click Finish.


NOTE: When the HAPRO installation is executed, a system restart might be

necessary. In this case, the following messages are displayed:


Output message:





Removing the Application Protector Server

To remove the existing Application Protector Server:

NOTE: Elevated privileges are required to remove the Application Protector

Server.


2. The Auto launcher launches the master installer or you can double-click the

master installer Setup.exe to launch the Application Protector master installer.

3. On the Hitachi Application Protector master installer dialog box, click Install HAPRO Server Software.


4. In the Hitachi Application Protector Server Setup wizard Welcome dialog box, click Next.




5. In the Hitachi Application Protector Server Setup wizard Change, repair, or remove installation dialog box, click Remove to remove

Application Protector Server.

Figure ‎2-23 Change, repair, or remove installation dialog box

6. In the Ready to remove Hitachi Application Protector Server dialog box, click Remove.

Figure ‎2-24 Ready to remove Application Protector Server dialog box



7. In the Hitachi Application Protector Server Setup wizard, click Finish.




Output message:





Managing Application Protector Client Installations

Installing the Application Protector Client

To install the Application Protector Client:

NOTE: Elevated privileges are required to install the Application Protector

Client.


2. The Auto launcher launches the master installer (or, you can double-click the master installer Setup.exe to launch the Application Protector master

installer).

3. In the Hitachi Application Protector master installer dialog box, click

Install HAPRO Client Software.


4. In the Welcome dialog box, Click Next.




5. Accept the End User License Agreement to proceed with the installation, then click Next.

Figure ‎2-28 End-User License Agreement dialog box

6. Select the Application Protector Microsoft® Application snap-in you want to

install and click Next.

NOTE:

You can select three features: SQL, Exchange, SharePoint. Each feature

has three options: ([Will be installed], [Entire feature will be installed], and [Entire feature will be unavailable]). The first and second options have the same meaning in the HAPRO installer. These options enable “feature

available”.

Selecting the HAPRO for SharePoint check box installs the Application

Protector for SQL in addition to Application Protector for SharePoint and creates two separate desktop shortcut icons for managing the Application Protector for SharePoint and SQL respectively.

If you have installed any of the HAPRO for Microsoft® Application component (such as HAPRO for SQL, HAPRO for Exchange or HAPRO for

SharePoint), and want to add another HAPRO component, then you must remove the HAPRO Client and reinstall it. This time you must select the additional required HAPRO components.



Figure ‎2-29 Application Selection dialog box

7. You can select a custom path for installation in the Change Destination

Folder dialog box displayed by clicking a Browse button in Custom Setup dialog box. The Browse button will be activated by clicking the root Application Protector Client feature in the Custom Setup dialog box. Use

the default path for installation or click Browse to navigate and select a custom path, and click OK>Next.

Figure ‎2-30 Destination Folder dialog box

NOTE:

The length of the installation path must not exceed 60 Characters.

Following are the characters which can be specified for the installation

path:

A-Z, a-z, 0-9, !, #, $, &, ', (, ), +, -, ., :, =, @, [, \, ], ^, _, `, {, }, ~,

space



8. Click Install to start the installation.

Figure ‎2-31 Ready to Install dialog box





Output message:





Updating the Application Protector Client

This section describes how to update the Application Protector Client to the latest version.

To update the Application Protector Client:

NOTE: Elevated privileges are required to update the Application Protector Client.


2. The auto-launcher launches the master installer (or, you can double-click

the Setup.exe to launch the Application Protector master installer).

3. Click Install HAPRO Client Software in the Hitachi Application Protector

master installer wizard to start the Application Protector Client update.

Figure ‎2-33 Application Protector Master installer wizard

4. Click Yes in the confirmation dialog box to remove the older version and

install the new version.

Figure ‎2-34 Confirmation dialog box



5. Click Install in the Resuming the Hitachi Application Protector Client Setup Wizard.

Figure ‎2-35 Setup resume wizard





Click “Yes” when you execute the restart immediately or Click “No” when you

execute the restart later, then click “Finish”.

Output message:





Changing the Application Protector Client

You can modify the installed Application Protector Client setup for the supported Microsoft Application features by using the Change option.

To change the Application Protector Client:

NOTE: Elevated privileges are required to change the installed applications on the Application Protector Client.


2. The auto-launcher launches the master installer (or, you can double-click

the Setup.exe to launch the Application Protector master installer).

3. Click Install HAPRO Client Software in the Hitachi Application Protector

master installer wizard.

Figure ‎2-37 Application Protector Master installer wizard

4. Click Next in the Welcome to the Hitachi Application Protector Client Setup

Wizard.




5. Click Change in the Change, repair, or remove installation wizard.

Figure ‎2-39 Change, repair, or remove installation wizard

6. Select the required Microsoft application feature and click Next in the

Custom Setup wizard to change the features.

Figure ‎2-40 Custom Setup wizard



7. Click Change in the Ready to change Hitachi Application Protector.

Figure ‎2-41 Ready to change wizard

8. Click Finish in the Complete the Hitachi Application Protector Client Setup Wizard.

Figure ‎2-42 Setup complete wizard





Output message:





Repairing the Application Protector Client

To repair the installed Application Protector Client:

NOTE: Elevated privileges are required to repair the Application Protector Client.


2. The Auto launcher launches the master installer (or, you can double-click the

master installer Setup.exe to launch the Application Protector master installer).

3. In the Hitachi Application Protector master installer dialog box, click Install

HAPRO Client Software.


4. In the Welcome dialog box, Click Next.




5. In the Change, repair, or remove installation dialog box, click Repair.


6. In the Ready to repair Hitachi Application Protector Client dialog box, click Repair.

Figure ‎2-46 Ready to repair dialog box



7. In the Hitachi Application Protector Client Setup wizard, click Finish.






Output message:

You must restart your system for the configuration changes made to Hitachi Application Protector Server 2.8.0 (x64) to take effect. Click Yes to restart now or

No if you plan to manually restart later.



Removing the Application Protector Client

To remove the installed Application Protector Client:

NOTE: Elevated privileges are required to remove the Application Protector Client.


2. The Auto launcher launches the master installer (or, you can double-click the

master installer Setup.exe to launch the Application Protector master installer).

3. In the Hitachi Application Protector master installer dialog box, click Install HAPRO Client Software.


4. In the Welcome dialog box , click Next.




5. In the Change, repair, or remove installation dialog box, click Remove.


6. In the Ready to remove Hitachi Application Protector Client dialog box, click

Remove.

Figure ‎2-51 Ready to remove client dialog box



7. In the Hitachi Application Protector Client Setup wizard, click Finish.




Output message:





Silent Installation of Application Protector Server and Client

You can perform a Silent installation using the Microsoft® Windows installer

Msiexec tool from the command prompt. For more information about Msiexec, see http://technet.microsoft.com/en-us/library/bb490936.aspx.

Syntax

Msiexec /Option {package/Productcode} [Optional Parameter]

Options

/i App.msi: Name of the Server or Client installation file

/x: uninstall the Client installation

/f: Repair the Client installation

/qn: no GUI

/l: Installation process log file

The following table describes the parameters for silent installation.

Table ‎2-1 Application Protector Silent Install Parameters

Parameter Possible Values Default Value Example Required

INSTALL_DIR Installation path folder

C:\Program Files\Hitachi\Applicat

ion Protector

INSTALL_DIR =”C:\My Folder\Apps”

This is configured during the clean installation only.

No

ADDLOCAL SQL

Exchange

SharePoint

N/A ADDLOCAL=SQL,

Exchange

No

ACCEPT_ LICENSE

yes

no

no

Logs Error about

EULA denial and ends installation

ACCEPT_LICENSE=yes

ACCEPT_LICENSE=no

Yes

CAUTION!

Do not copy and paste the parameters.

Specify at least one of the parameters for ADDLOCAL for the HAPRO

Client installation. You can continue the HAPRO Client installation without specifying any parameters, and later, invoke the HAPRO Client components from the MMC by adding a feature.

The possible values for ADDLOCAL parameter are case sensitive.

NOTE: Characters which can be specified for the install path are as follows:

A-Z, a-z, 0-9, !, #, $, &, ', (, ), +, -, ., :, =, @, [, \, ], ^, _, `, {, }, ~, space

http://technet.microsoft.com/en-us/library/bb490936.aspx



HAPRO Server and Client Silent Installation

Sample Command for installing Application Protector Client

Sample Command for installing Application Protector Server

Sample command for repairing Application Protector Server

Sample command for repairing Application Protector Client

Sample command for upgrading Application Protector Server

NOTE: To upgrade Application Protector Client from 2.0, 2.0.1, 2.6 or 2.7, you

need to use the GUI. Upgrading Application Protector Client from 2.0, 2.0.1, 2.6 or 2.7 is not supported using the CLI.

HAPRO Server and Client Silent Removal

Sample command for removing Application Protector Server

Sample command for removing Application Protector Client

msiexec /i HAPROInstaller_Client_x64.msi /qn /l log.txt

INSTALL_DIR=C:\MyApps ADDLOCAL=SQL,Exchange ACCEPT_LICENSE=yes

msiexec /i HAPROInstaller_Server_x64.msi /qn

INSTALL_DIR="%ProgramFiles%\Hitachi\Application Protector\" ACCEPT_LICENSE=yes

msiexec /f HAPROInstaller_Server_x64.msi /qn /l log.txt INSTALL_DIR=C:\MyApps ACCEPT_LICENSE=yes

msiexec /f HAPROInstaller_Client_x64.msi /qn /l abc.txt

msiexec /i HAPROInstaller_Server_x64.msi /qn reinstall=all reinstallmode=vamus

msiexec /x HAPROInstaller_Server_x64.msi /qn /l abc.txt

msiexec /x HAPROInstaller_Client_x64.msi /qn /l abc.txt

3

Configuring Application Protector 3-1


Configuring Application Protector

This chapter shows you how to set up user credentials and activate the license for the Application Protector.


Understanding the Service Account Permissions

Licensing Application Protector

3-2 Configuring Application Protector


Understanding the Service Account Permissions Service Account permissions are required to perform the operations such as Create

Snapshot, Delete Snapshot, Create Snapshot Schedule, Revert, Restore, or Recover.

The Service Account for Application Protector must have the following local

administration or domain administration privileges in order to perform tasks using Application Protector.

CAUTION! Snapshot-based backup and recovery activity fails if the service account is not configured for the supported Microsoft® Application servers.

Table ‎3-1 Service account user privileges

Operation Local Server

Privileges Domain Privileges Application Role/Group

List Entities Local Administrator

Domain User Role13

Create Snapshot Local Administrator

Domain User Role1

Mount Snapshot Local Administrator

Domain User Role1

Unmount

Snapshot

Local

Administrator

Domain User Role1

Delete Snapshot Local

Administrator

Domain User Role1

Recover

Snapshot

Local

Administrator

Application Administrator

with Domain user privileges

Role24

Revert Snapshot Local Administrator

Application Administrator with Domain user privileges

Role2

3Role1: For Exchange, Role1 is View-only Organization Management and for SQL and SharePoint, database creator.

4Role2: For Exchange, Role2 is Organization Management and for SQL and SharePoint sysadministrator/database creator.

Configuring Application Protector 3-3


To set up a service account:

1. Click Set in the Server tab.

2. Enter User Name and Password in the Set User dialog box.

3. Click OK.

For more details on Application Protector Server configuration, refer to the

following manuals:

Hitachi Application Protector User Guide for Microsoft® Exchange Server

Hitachi Application Protector User Guide for Microsoft® SharePoint Server®


3-4 Configuring Application Protector


Licensing Application Protector Application Protector has license validation at the Application Protector Server

level. Application Protector is available with the trial and full version license. Application Protector supports the following license types:

Trial license

Product license

Viewing Licenses

After you have completed installing Application Protector and configured the user

credentials, you can view the Application Protector license details.

Click View License Information to view the license for the supported Microsoft®

Application licenses. The following table describes the details.

Table ‎3-2 Viewing Application Protector License Information

Item Description

License Displays license per production server based on application type and

the storage platform used to execute and store the snapshots.

Expiry Displays expiry date of license.

Activating the License

To activate the full user license or if the trial license has expired for the supported

Microsoft® Applications perform the following:

To activate the license:

1. Click Activate License in the Actions pane.

2. Enter the mandatory details to generate licensing request in the License

Activation Wizard and click Next.

3. Verify the details for generating the licensing request and click Next, else click

Back to edit the details.

4. Save the Generated Capability Request file.

NOTE: You must send the Generated Capability Request file to HDS support to

receive a license file.

5. To install the license, on the next screen browse the License XML File received from the HDS Support and click Install.

For more details about activating licenses, refer to the following manuals:

Hitachi Application Protector User Guide for Microsoft® Exchange Server

Hitachi Application Protector User Guide for Microsoft® SharePoint Server®


Hitachi Application Protector CLI Guide for Microsoft® Applications

MK-91HAP009-05

Hitachi Data Systems

Corporate Headquarters 2845 Lafayette Street Santa Clara, California 95050-2639

U.S.A. www.hds.com

Regional Contact Information

Americas +1 408 970 1000 [email protected]

Europe, Middle East, and Africa

+44 (0) 1753 618000 [email protected]

Asia Pacific +852 3189 7900 [email protected]

http://www.hds.com/


