emc® appsync™ 2.2.2 installation and … setup ... emc appsync 2.2.2 installation and...

EMC® AppSync™Version 2.2.2

Installation and Configuration Guide302-002-308

01

Copyright © 2012-2015 EMC Corporation. All rights reserved. Published in USA.

Published September , 2015

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for aparticular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and othercountries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

EMC CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC AppSync 2.2.2 Installation and Configuration Guide

Prerequisites 5

AppSync server prerequisites.......................................................................... 6Application host plug-in prerequisites.............................................................6AppSync console prerequisites .......................................................................7

Display requirements ........................................................................ 7Checklist for AppSync deployment.................................................................. 8VNX Block setup ............................................................................................. 9

Service plan considerations for applications on VNX Block storage........................................................................................................ 10Dynamic mounts ............................................................................. 10Microsoft Cluster Server mounts for SQL Server................................10SAN policy on Windows Server Standard Edition ............................. 11

VNX file setup................................................................................................11Service plan considerations for an application on VNX File storage........................................................................................................ 13VNX file mount................................................................................. 13

VNXe setup................................................................................................... 13Service plan considerations with VNXe.............................................14Mount and unmount copy considerations for VNXe.......................... 14Mount/unmount VNXe NFS datastore considerations....................... 15VNXe NFS datastore restore considerations......................................15

VMAX setup...................................................................................................15Service plan considerations for applications on VMAX storage......... 15Mount and unmount VMAX copies................................................... 17Microsoft Cluster Server mounts for SQL Server................................17VMAX restore................................................................................... 17

VMAX 3 setup................................................................................................18Mount/unmount VMAX 3 copies.......................................................18Service plan considerations for applications on VMAX 3 storage...... 18

ViPR Controller setup.....................................................................................19Service plan considerations with ViPR Controller..............................20Mount and unmount ViPR Controller copies......................................20ViPR Controller copy restore............................................................. 20

XtremIO setup .............................................................................................. 21Summary of service plan features for XtremIO.................................. 22Restore options with XtremIO storage...............................................22

RecoverPoint setup .......................................................................................23Service plan considerations for applications with RecoverPointprotection........................................................................................ 23RecoverPoint prerequisites...............................................................23Dynamic or static mounts.................................................................24

Installation 27

Fresh installation of AppSync overview..........................................................28Installing the server..........................................................................28Installing the host plug-in manually - Windows servers only............. 28Adding servers................................................................................. 30

Upgrade overview..........................................................................................32Upgrading the AppSync server......................................................... 32

Chapter 1

Chapter 2

CONTENTS

EMC AppSync 2.2.2 Installation and Configuration Guide 3

Upgrading the AppSync agent plug-in ..............................................33Service pack installation overview.................................................................34

Installing the AppSync 2.2 Service Pack 2 server.............................. 34Upgrading the AppSync agent plug-in on a server for 2.2 SP2...........35

Uninstalling the server ..................................................................................36Rolling back the AppSync server software ........................................36

Removing a server from AppSync ..................................................................37Uninstalling the AppSync server plug-in........................................................ 37

Configuration and resource management 39

Backup and restore AppSync using the Backup Assistant tool....................... 40AppSync Backup Assistant arguments and actions...........................40Restore an automated backup..........................................................40

Migrating the AppSync server........................................................................ 41Resource management ................................................................................. 41

Adding a RecoverPoint site ..............................................................42Adding VMAX and VMAX 3 storage................................................... 43Add a VNX, VNXe array, or a RecoverPoint site to AppSync................45Adding and registering ViPR Controller storage to AppSync ..............46Add an XtremIO array to AppSync .................................................... 48Viewing EMC storage........................................................................49Removing an EMC storage system ................................................... 49Rediscovering an EMC storage system .............................................49Adding a VMware vCenter Server ..................................................... 49Repurpose copies on VMAX..............................................................50Repurpose RecoverPoint Bookmark copies of Oracle or SQL Serverdatabases........................................................................................51

Chapter 3

CONTENTS


CHAPTER 1

Prerequisites

This chapter includes the following topics:

l AppSync server prerequisites.................................................................................. 6l Application host plug-in prerequisites.....................................................................6l AppSync console prerequisites ...............................................................................7l Checklist for AppSync deployment.......................................................................... 8l VNX Block setup ..................................................................................................... 9l VNX file setup........................................................................................................11l VNXe setup........................................................................................................... 13l VMAX setup...........................................................................................................15l VMAX 3 setup........................................................................................................18l ViPR Controller setup.............................................................................................19l XtremIO setup ...................................................................................................... 21l RecoverPoint setup ...............................................................................................23

Prerequisites 5

AppSync server prerequisitesThe AppSyncserver must meet specific prerequisites.

The AppSync Support Matrix on https://elabnavigator.emc.com/eln/extendedSupport isthe authoritative source of information on supported software and platforms.

For all AppSync and array license information, refer to the EMC AppSync SecurityConfiguration Guide.

Table 1 AppSync server prerequisites

Item Value

Operating system Windows Server 2008 SP2 (x64), Windows Server 2008 R2(x64), Windows Server 2008 R2 SP1 (x64), Windows Server2012, Windows Server 2012 R2

Disk space 775 MB minimum. Exact value appears in the installationwizard.

Memory 6 GB minimum, 8 GB recommended

CPU 2 CPU minimum, 4 CPU recommended

Virtual environments VMware virtual machine. Memory and disk spacerequirements are the same as on physical host.

Additional informationThe AppSync server can now co-exist on the same server with any other EMC product thatuses the RSA Common Security Toolkit, for example NetWorker Server, Unisphere CLI, andNavisphere CLI.

Application host plug-in prerequisitesReview this information for specific requirements before you install the AppSync agent(host plug-in). The AppSync Support Matrix on https://elabnavigator.emc.com/eln/extendedSupport is the authoritative source of information on supported software andplatforms.

Table 2 Application host plug-in prerequisites

Item Value as of GA (refer to support matrix for latestversions)

Operating system l Windows Server

l Linux

l AIX

Disk space 150 MB minimum. Exact value is displayed in theinstallation wizard.

Memory 2 GB minimum

CPU 2 CPUs

Prerequisites


https://elabnavigator.emc.com/eln/extendedSupport



Table 2 Application host plug-in prerequisites (continued)

Item Value as of GA (refer to support matrix for latestversions)

Virtual environments l VMware virtual machine. Memory and disk spacerequirements are the same as on physical host.

l HyperV

Windows ports 8085, 10004, pushing the host plugin to a Windows hostrequires CIFS access (TCP port 139 and TCP port 445).

UNIX ports: Source IP is AppSync server:

l Destination IP = Production or mount host running UNIXAppSync Host plug-in

l Destination port = 22 (SSH port), Protocol: TCP

Source IP = Production or mount host running UNIX AppSynchost plug-in

l Destination IP = AppSync server

l Destination Port = 22 (SSH Port). Protocol: TCP

AppSync console prerequisitesThe AppSync console runs on a variety of web browsers.

Supported browsers follow, for version support : The AppSync Support Matrix on https://elabnavigator.emc.com/eln/extendedSupport is the authoritative source of informationon supported software and platforms.

l Internet Explorer

l Firefox

l Chrome

Flash is required regardless of the browser type, minimum version 10.2.

The console requires 1 GB of RAM when loaded and working at capacity.

Display requirementsAppSync requires a display resolution of 1280x1024.

Prerequisites

AppSync console prerequisites 7



Checklist for AppSync deploymentLearn about initial AppSync deployment steps and how to use the checklist as a map forinstallation and security concerns.

Table 3 Deployment checklist

Basic step Details Notes Done?

Identify a system running a supportedversion of Windows to act as theAppSync server.

Refer to a recent support matrix for AppSync for exactWindows versions for the AppSync server. Refer to the list ofserver prerequisites in this guide for other details.

Verify that you have a supported webbrowser to run the AppSync console.

Refer to the Console prerequisites topic for the list ofsupported browsers.

Verify that the application host (forexample, Microsoft Exchange mailboxserver) meets requirements.

Refer to EMC AppSync User and Administration Guide and thelatest EMC AppSync Support Matrix .

Install the AppSync server executableon the designated server system.

Obtain server installation executable from support.EMC.com.

From a web browser, open the AppSyncconsole.

http://<appsync_server>:8085/appsync

From the desktop shortcut ortheAppSync console, add the storagewhere application data resides.

l To add any of the following storage arrays, go to Settings> Storage Infrastructure

n VNX, VNXe

n VMAX

n XtremIO

n RecoverPoint site

n ViPR Controller

l If mounting copies to a virtual machine that uses RDM

disks, browse to Copy Protection > VMwareDatacenters and click Discover Datacenters > AddvCenter Servers.

From the AppSync console, install theAppSync host plug-in on the applicationhost.

Settings > Servers and click Add. When security preventspush-install, manually install by running AppSync-Host-Plug-in-2.2.2-win-x64.exe on the host.

From the AppSync console, discoverapplication objects on the respectiveservers.

Copy Management > Microsoft Exchange / SQL Server /Oracle / VMware Datacenters / FileSystem.

From the AppSync console, subscribeapplication objects to a service plan tobegin data protection.

Copy Management > Microsoft Exchange / SQL Server /Oracle / VMware Datacenters / FileSystem.

l Protect immediately with Subscribe to Plan and Run,which subscribes the application object to a service planand runs the protection immediately for the selectedobject only.

Prerequisites


Table 3 Deployment checklist (continued)

Basic step Details Notes Done?

l Subscribe to Plan, which subscribes the applicationobject to a service plan, but does not run the plan.Protection occurs according to the service plan'sschedule.

From the AppSync console, you canrepurpose application database copiesfor SQL Server and Oracle for use in test-dev, break-fix, data mining, andreporting. Use the Repurpose wizard toschedule or immediately create first orsecond generation copies as needed.

Copy Management > Oracle or SQL Server to display thelist of available applications.

l Select the database instance that you want to Repurpose,

and then select Repurposeto launch the wizard.

l Follow wizard steps.

l Select Run now or Run later. Complete details appear inthe online help and user guide.

VNX Block setupAppSync supports the creation and management of application copies using VNX Snapcopy technology. Consider best practices for VNX array setup before deploying AppSync.

ConnectivityConsider the following information for VNX connectivity with AppSync.

l AppSync supports Fibre, iSCSI, and FCoE connectivity between the host running theAppSync software and the VNX array. Network connectivity is required between thearray and the AppSync server.

l Storage control occurs only on the AppSync server. No zoning is necessary from theVNX array to the AppSync server. It is not necessary to pre-expose any LUNs.

l Configurations with multiple AppSync servers per VNX array are supported.

VNX LUN supportConsider the following information for VNX LUN support.

l AppSync only supports LUNs that are in a pool. If you run VNX Snapshot replicationyou must use pool LUNs, not RAID LUNs. For RecoverPoint, use RAID storage.

l AppSync cannot create snapshots on LUNs with compression enabled.

l For VNX Snapshots, AppSync supports primary LUNs of any size.

VNX consistency groupsConsider the following information when using VNX consistency groups:

l All limitations that apply to VNX consistency groups also apply to AppSync.

l You can have multiple consistency groups within a single service plan.

l If you are using VNX consistency groups, all file systems that are related to anapplication in the snapshot set should reside in the same service plan. If not, you canencounter problems with mount and restore.

VNX mountThe following considerations apply:

Prerequisites

VNX Block setup 9

l Mount hosts require SAN visibility to the VNX array.

l Changes made to a VNX Snapshot while it is mounted are persistent.

l If you accidentally delete hardware copies on the array, you cannot mount thosecopies with AppSync.

Avoiding inadvertent overwritesWhen you use AppSync to create a copy of one set of data that shares a LUN with otherdata, the copy contains all the data on that LUN. During restore, you may unintentionallywrite older data over newer data. The entities that are overwritten are called affectedentities. Always configure data so that affected entities are reduced or eliminated.

Each LUN should contain a single file system or database file. If you are certain that thefile system and/or database table residing on that LUN is always be backed up orrestored as a unit, exceptions apply.

Service plan considerations for applications on VNX Block storageAfter you register VNX storage, you can subscribe the application to a service plan tocreate and manage copies.

Bronze plans are supported. AppSync supports VNX Snapshot as the copy technology.Subscribe to the Bronze service plan to create and manage local copies for operationrecovery, backup acceleration, or repurposing (create copies for test/dev). AppSyncsupports pooled LUNs (TLU/DLU) if the Snapshot technology supports these LUNs.

The maximum number of copies that AppSync can create and manage for VNX Block isdictated by the limits of the VNX Snap technology. The maximum number of VNX snapsper source is 256. This allows a maximum AppSync service plan rotation of 255.

Dynamic mountsWith proper zoning, AppSync automatically presents storage to the host when a copy ismounted.

Physical hostWhen AppSync mounts a copy, it dynamically assigns a snapshot to the host. Thephysical host must be zoned to the VNX array.

Virtual machineDynamic mounts happen as raw device mapping (RDM) or through native iSCSI onthe virtual machine.

l For RDM, the ESX server where the virtual machine resides must be zoned to the VNXarray.

l For RDM and virtual disks, virtual center (which manages the ESX server that thevirtual machine mount host resides on) must be registered with the AppSync server.

l For native iSCSI, the virtual machine must be zoned to the VNX array.

l For virtual disks, virtual center of ESXi server (where mount host resides) must beregistered with AppSync. Register the virtual machine with disk.EnableUUID flagenabled. AppSync installs the host plug-in on the virtual machine during registrationfor virtual disk and application level protection.

Microsoft Cluster Server mounts for SQL ServerMicrosoft Cluster Server (MSCS) mounts for SQL Server can be done on production oralternate clusters.

When you mount to a cluster node using VNX storage:

Prerequisites


l The storage group configuration applies only to physical hosts or virtual machineswith NPIV or iSCSI that are directly connected to the VNX. For clusters configuredusing virtual machines with RDM or virtual disk, the copy that is mounted is onlyvisible to the selected node (usually passive node).

l When you mount to a cluster node for backup purposes, create a dedicated storagegroup for one of the nodes of the cluster, preferably the passive node.

l AppSync does not support mount to a cluster as a clustered resource. To mount to acluster as a clustered resource (in a physical/iSCSI environment), clear the selectionof the default setting, and select Use dedicated storage group in the AppSync mountdialog box. During mount, AppSync makes the copy visible to multiple nodes in thecluster by using a Storage Group with multiple assigned nodes. AppSync also mountsthe file systems to the selected mount host. After the completion of AppSync mount,manually add the mounted devices under cluster management to avoid thepossibility of any data corruption.

l If PowerPath 5.7 is installed, the host IP in the VNX storage group changes to the IPthat corresponds to Microsoft failover cluster virtual adapter. PowerPath 5.7 has anauto-host registration feature that intercepts host agent operation and overwrites theIP with its own selection. This feature cannot be turned off. Upgrade to PowerPath5.7.2 and above to correct this issue.

SAN policy on Windows Server Standard EditionOn Windows Server, the SAN policy determines whether a disk comes in online or offlinewhen it is surfaced on the system. For Enterprise Edition systems, the default policy isoffline. On Standard Edition the default policy is online. You need to set the policy toofflineshared to prevent mount failures.

To set the SAN policy to offline on a Windows Server 2008 Standard Edition host, open acommand line window and run the following commands:

C:\>diskpart Microsoft DiskPart version 6.0.6001Copyright (C) 1999-2007 MicrosoftCorporation.On computer: abcxyzDISKPART> san policy=offlinesharedDiskPart successfully changed the SAN policyfor the current operating system.

VNX file setupAppSync supports the creation and management of application copies using VNX FileSnapSure copy technology. AppSync-managed copies can be local, remote (off the VNXReplicator target) or identical point-in-time local and remote copies.

Consider best practices for VNX file setup before deploying AppSync.

VNX SnapSureVNX SnapSure creates a point-in-time copy of all the data on the network file system(NFS). For the initial snapshot, this method creates a full copy of the original file system,therefore requiring the same amount of space on the file system. Subsequent snapshotsspace usage depends on how much the data has changed since the last snapshot wastaken.

SnapSure has the following characteristics:

l Storage Service — VNX File Server

l Source — VNX LUN

Prerequisites

SAN policy on Windows Server Standard Edition 11

l Target — VNX SnapSure local snapshot

l Storage Requirements — The following storage requirements apply:

n The source data must reside on VNX file systems.

n Storage must include enough space for the snapshots on the VNX.

n Storage pools cannot be defined for VNX jobs.

l Mount and Recovery — You can mount the replica on a target host and/or performdirect recovery from target to source.

VNX ReplicatorVNX Replicator creates a point-in-time copy of all the data on the network file system(NFS). VNX Replicator maintains consistency between the source and target file systemsthat are based on the Time Out of Sync policy settings.

VNX Replicator has the following characteristics:

l Storage Service — VNX File Server

l Source — VNX NFS

l Target — Replicator remote snapshot

l Storage Requirements — The source data must reside on network file systems.

l Mount and Recovery — Can mount the copy on a target host and perform recoveryfrom the copy if required.

VNX remote protectionProtection occurs between a local Data Mover and a Data Mover on a remote VNX system.

Both VNX for file cabinets must be configured to communicate with one another by usinga common pass phrase, and both Data Movers must be configured to communicate withone another by using a Data Mover interconnect. After communication is established, aremote session can be set up to create and periodically update a source object at aremote destination site. The initial copy of the source file system can either be done overan IP network or by using the tape transport method.

Some recommendations for the session include:

l The session must be created with the Time Out of Sync update policy instead of amanual refresh.

l The Time Out of Sync value should be set to lowest value possible for the networkconfiguration.

After the initial copy, changes made to the local source object are transferred to a remotedestination object over the IP network. These transfers are automatic and are based ondefinable protection session properties and update policy.

One-to-many replication configurations are not supported in AppSync.

Protecting data on VNX network file systemsFor service plans configured for remote protection, the NFS copy is created as a SnapSureSnapshot on the local and/or remote file system. Copies of NFS data stores can becreated from service plans configured for local, remote, and local and remote protection.

During restore of an NFS copy, AppSync creates a roll back snapshot for every file systemthat has been restored. The name of each roll back snapshot can be found in the restoredetails.

You can manually delete the roll back snapshot after verifying the contents of the restore.Retaining these snapshots beyond their useful life can fill the VNX snap cache and causeresource issues.

Prerequisites


Service plan considerations for an application on VNX File storageOnce you register VNX storage, you can subscribe the application to a service plan tocreate and manage copies.

Bronze, Silver, and Gold plans are supported for copies of applications (NFS data store,Oracle NFS) residing on VNX File.

The limits of VNX SnapSure technology determine the maximum number of copies thatAppSync can create and manage for VNX File.

For Local SnapSure copies you can have a maximum of 96 RO (read-only) snaps. AppSyncservice plan rotation for VNX NFS file system is a maximum of 95.

For Remote SnapSure copies (across Remote Replicator), you can have a maximum of 95RO snaps. AppSync service plan rotation for VNX NFS file system is a maximum of 94.

For RW (read/write) mounts, SnapSure allows for up to 16 RW snaps off existing ROsnaps. A maximum of 16 snapshots for a given source can be mounted RW at anyspecified time. The service plans, by default, unmount the provision copy beforemounting the new copy so this limit has no consequences. However, if theimplementation requires simultaneously mounting multiple copies for the same sourceRW, the limit of 16 must be considered.

VNX file mountYou can mount any VNX File Snapshot copy created in the service plan at any time,independent of other copies created on the same service plan.

The following considerations apply:

l ESX mount hosts must belong to a vCenter server.

l ESX mount hosts require visibility on the network.

l NFS.MaxVolumes, an advanced setting on the ESX server, should be set to thenumber of NFS datastores that will be mounted to each ESX on the network.

l When mounting to an ESX server, AppSync uses the lowest number interface that hasconnectivity.

VNXe setupLearn about VNXe and AppSync copy management, application support, and allowedstorage and replication types.

VNXe arrays support all applications within AppSync. VNXe does not support thefollowing configuration with AppSync:

l NFS file systems on UNIX platforms

l Repurposing copies on VNXe arrays

VNXe copy managementThis section describes a typical AppSync workflow where you can create and manageapplication-consistent copies on VNXe storage. AppSync manages VNXe arrays with theManagement Interface instead of the Service Processor interface.

Perform resource registration for VNXe when you start AppSync after installation. Registerhosts as well as vCenter and storage systems so that AppSync can perform variousoperations that are required to create and manage copies of applications. Typically,registration of an entity includes identifying the system using name/IP address and

Prerequisites

Service plan considerations for an application on VNX File storage 13

providing the necessary credentials (username/password) for AppSync to discover andoperate on the registered system.

Storage and replication typeAppSync supports Unified Snapshot replication technology to create and manage localcopies of applications that reside on VNXe block or file storage.

Source block storage LUNs can be pool LUNs that are either thick or thin. You canprovision the required source block devices using the VNXe LUN or VMware data storewizards within the Unisphere UI. When creating basic LUNs using the LUN wizard selectone of the following options:

l Create a LUN – Creates an individual LUN from a desired storage pool.

l Create a LUN group – Creates a grouping of LUNs from a desired storage pool. Theadvantage of using a LUN group is that all LUNs within the group are snappedtogether guaranteeing consistency on the array.

Best practice states that in Microsoft environments you should use LUN groups in theirstorage layout to help the application consistent creation of VNXe snapshots within theMicrosoft VSS Service time window.

You can provision the required source file devices using the VNXe file system or VMwaredata stores wizard. When provisioning from the file system wizard, only NFS share filesystems are supported.

Service plan considerations with VNXeBefore you add a service plan to create VNXe copies, review these considerations.

After you register VNXe storage, subscribe to the Bronze service plan to create andmanage local copies for operation recovery and backup acceleration. After you registerVNXe storage, AppSync selects snap for Bronze plans by default.

For copies across RecoverPoint Continuous Remote Replication or CLR, subscribe to Silveror Gold service plan respectively. You can change snap to Bookmark for RecoverPointcopies.

Mount and unmount copy considerations for VNXeMount/unmount operations on VNXe arrays involve attaching/detaching snapshots toSMPs, and granting/removing (masking/unmasking) snapshot access to SMP LUNs or aset of SMPs to a host.

VNXe only allows one snapshot at a time of a set of LUNs or LUN group for attachment toSMP LUNs. LUNs contained in a LUN group are attached and detached together, there isno partial attach/detach.

Before performing a mount and unmount, zone the mount host to the VNXe array, andregister the host name with its initiators.

The first step AppSync performs when mounting a snapshot on VNXe, is host initiatordiscovery for the mount host. Based on the snapshot information, AppSync maps to theappropriate source LUN/LUN group(s) to determine host access for the mount host.AppSync verifies that no other snapshots are attached to the SMP LUNs. Next AppSyncmodifies host access to either grant snapshot access to perform a mount, or remove hostaccess to unmount.

For RDM or vDISK mount/unmount, AppSync identifies host access based on the hostinitiator for the ESX server.

LUN Groups have an all or nothing approach towards mounts. On Microsoft products, alldevices within or outside of a LUN group need to be initially exposed to the mount host

Prerequisites


so that a VSS import can be performed correctly. Some devices can remain visible but notconnected to a mount point on the mount host.

Mount/unmount VNXe NFS datastore considerationsReview the following information for NFS datastore mount/unmount.

AppSync creates a share based on the VNXe file snap that you want to mount. The sharewill be visible to the mount host. During unmount, the share created during the mountwill be deleted. Share name appears in the following format:

AS-Share-lastFourDigitOfVNXeSerialNum-ProductionFilesystemId-TimeOfShareCreatedRegarding export IPs, AppSync creates a list of export IP interfaces from the VNXe array.Production export IP is a priority.

VNXe NFS datastore restore considerationsBefore the restore, AppSync automatically creates a restore point snapshot of the currentproduction storage resource on the VNXe array.

This restore point snapshot has the following naming convention: AppSync-ROLLBACK-NXeSerialNumber_ProductionFilesystemId_TimeOfSnapCreation.TimeofRestore.The snap AppSync-ROLLBACK-VNXeSerialNumber_xxxxx is not deleted after therestore.

VMAX setupTo create and manage copies of your applications, AppSync supports TimeFinder Cloneand TimeFinder VP Snap replication technology. AppSync also supports remote copymanagement off of an R2 in a SRDF/S or SRDF/A configuration.

Review the following sections before adding your VMAX storage.

Service plan considerations for applications on VMAX storageOnce you register VMAX storage you can subscribe your application to a service plan tocreate and manage copies.

Bronze and Silver plans are supported. TimeFinder VP Snap is the default replicationtechnology used for service plans. You can change your preference to clone if TimeFinderClone copies are desired.

The recommended maximum number of copies to keep before expiration is 6 forTimefinder Clones and up to 31 for VP Snap. The number of Timefinder Clone and VPSnap copies that can be created and managed is influenced by other copy and replicationtechnologies used on the source LUNs. Refer to section on Copy Session Limits" for yourplanning. Refer to VMAX copy session limits. on page 16

Bronze planYou can subscribe to the Bronze service plan to create and manage local copies foroperation recovery, backup acceleration or repurposing (create copies for test/dev).

Prerequisites

Mount/unmount VNXe NFS datastore considerations 15

For RAID LUNs AppSync chooses TimeFinder Clones for the Bronze plan. If the source is aRAID LUN or a mix of RAID and thin LUNs, then AppSync defaults to clone even if youselect TimeFinder VP Snap as your preference.

Silver planFor copies across SRDF/S or SRDF/A subscribe applications to the Silver service plan.

Note

Creation of remote copies in an SRDF/A configuration is not supported with Microsoftapplications.

SRDF/A caveats: Creating a TimeFinder VP Snap or TimeFinder Clone of the R2 device isnot allowed if either of the following is true:

l SRDF/A device-level write pacing is not activated and supported on the SRDF/Asession.

l The SRDF pair is the R21-> R2 of a cascaded configuration, and any of the followingapply:

n The R21 Symmetrix array is running an Enginuity level lower than 5876.159.102

n The R2 Symmetrix array is running an Enginuity level lower than 5875.

n The R21 device is not pace-capable.

l Restore from SRDF/A is not supported

Source storage LUNs can be traditional RAID LUNs or thin LUNs (TDEVs). TimeFinder VPSnap support is only for thin LUNs. Consider the following recommendations:

l R1 > R2 should be in Synchronized state (for SRDF/S) and Consistent state (forSRDF/A)

l For Silver plan Create copy: Affinitizer splits the applications based on the RDF Group(RA Group) to which the source devices belong.

l Put all application LUNs in the same RDF group.

Copy session limitsSymmetrix VMAX series arrays support up to 16 differential sessions per source device,which can be used for TimeFinder/Clone, TimeFinder/Snap, TimeFinder VP Snap, SRDF/Star, Solutions Enabler Open Replicator (ORS), or Symmetrix Differential Data Facility(SDDF) operations.

This limits the number of available copies that can be created.

TimeFinder VP Snap allows an additional 32 sessions per Symmetrix device whichincludes availability of one session of the traditional 16 sessions available. If you want toperform a restore, an additional session is required from the 16.

For example, if you use VP Snap for a source LUN and then desire a restore operation, thisaction leaves 14 sessions available for other copy technologies (TF Clone, ORS,Timefinder/Snap, SRDF/Star, on so on).

Additionally, if you want to create and manage TF Clone copies for the same source, youcan create no more than 7 TF Clone copies using AppSync. (AppSync creates differentialTimeFinder Clone copies which take up 2 differential sessions per copy 14/2 = 7.) SinceAppSync does not delete or expire a copy prior to creating a new one, the source of theAppSync rotation for the TimeFinder Clone copies can be no more than 6. This allows foran additional copy to be created prior to delete/expire of the oldest copy.

Prerequisites


Note

For additional TimeFinder session limits refer to EMC Solutions Enabler SymmetrixTimeFinder Family CLI Product Guide.

Mount and unmount VMAX copiesMount/unmount operations on VMAX involve masking/unmasking LUNs or set of LUNs toa host.

AppSync relies on the VMAX Auto-Provisioning capability. AppSync requires the mounthost to be zoned to the VMAX array. You should create a masking view with theappropriate initiator group, port group and storage group.

When AppSync performs a mount operation on VMAX, it discovers the host initiator forthe mount host first. Based on the host initiator, it maps to the appropriate masking viewto determine the Storage Group to or from which the target LUNs are masked/unmaskedto perform a mount/unmount operation.

For RDM or Vdisk mount/unmounts, AppSync identifies the Masking view based on thehost initiator for the ESX server.

Microsoft Cluster Server mounts for SQL ServerMicrosoft Cluster Server (MSCS) mounts for SQL Server can be done on production oralternate clusters.

When you mount to a cluster node using VMAX storage:

l The storage group configuration applies only to physical hosts or virtual machineswith iSCSI that are directly connected to the VMAX. For clusters configured usingvirtual machines with RDM or virtual disk, the copy mounted is only visible to theselected node (usually the passive node).

l When you mount to a cluster node for backup purposes, create a dedicated storagegroup for one of the nodes of the cluster, preferably the passive node.

l AppSync does not support mount to a cluster as a clustered resource. To mount to acluster as a clustered resource (in a physical/iSCSI environment), deselect thedefault setting Use dedicated storage group on the AppSync mount dialog . Duringmount AppSync will make the copy visible to multiple nodes in the cluster by using aStorage Group with multiple assigned nodes. AppSync also mounts the filesystems tothe selected mount host. After the completion of AppSync mount, manually add themounted devices under cluster management to avoid the possibility of any datacorruption.

VMAX restoreVMAX restricts the maximum number of hops in cascading to two.

If source A has the following sessions such as A > D and A > B > C (when created by aservice plan or using Repurposing workflow), then during the restore from D the numberof hops changes to 3 as the restore session leads to D > A > B > C. Therefore, Appsyncprovides an option to terminate the session B > C if it is a clone.

During consecutive runs if AppSync chooses C as a target for B, then it will be a full syncinstead of a resync since the session B > C will be terminated during restore.

For example:

A > B > C

A > D > E

Prerequisites

Mount and unmount VMAX copies 17

Restore from B will terminate D > E. Restore from D will terminate B > C. Necessarysessions will be terminated only if the you select the option.

If the second generation copy is a TimeFinder VP Snap, you must expire secondgeneration snaps manually. The restore fails if a snap of clone exists for source anddisplays all the copies that need to be expired in the progress window.

Note

Refer to the AppSync VMAX Array Support Guide on the EMC Support website for additionalinformation.

VMAX 3 setupVMAX 3 arrays are supported with AppSync. This section describes supported features,and service plan considerations including mount/unmount and restore of VMAX 3 copies.

To create and manage copies of applications, AppSync supports SnapVX snapshotreplication technology in VMAX 3 arrays.

Mount/unmount VMAX 3 copiesMount/unmount operations on VMAX 3 include masking/unmasking LUNs or a set ofLUNs to a host. AppSync relies on the VMAX 3 Auto-Provisioning capability.

The mount host must be zoned to the VMAX 3 array. Next, you can create a masking viewwith the initiator group, port group, and storage group.

When AppSync performs a mount operation on VMAX 3, it discovers the host initiator forthe mount host first, then based on this host initiator, AppSync maps to (or from) themasking view. This operation determines the storage group where the target LUNs aremasked/unmasked . For RDM or Vdisk mount/unmount, AppSync identifies the maskingview that is based on the host initiator for the ESX server.

You can select the wanted Service Level Objective (SLO) for the target LUN in the mountphase of the service plan. If there is a storage group for the mount host with the wantedSLO, AppSync adds the LUN to the storage group. If this storage group does not exist,AppSync adds the LUN to any storage group that is masked to the host.

If a storage group is configured to pick target devices, AppSync removes the devices fromthe storage group at the time of mount and adds them to the storage group for the mounthost. The devices are added to the original storage group when the copy is expired.

Service plan considerations for applications on VMAX 3 storageReview these considerations for service plan support with VMAX v3.

OverviewAfter you register (add) VMAX 3 storage, subscribe an application to a service plan tocreate and manage copies.

For this release of AppSync, Bronze and Silver service plans are supported with VMAX 3.Snap in a service plan with VMAX 3 is equivalent to a SnapVX snapshot linked in nocopy mode. Clone in a service plan is equivalent to SnapVX snapshot linked in copymode. The default preference for a service plan is Snap.

Mount/unmount VMAX 3 copiesMount/unmount operations on VMAX 3 include masking/unmasking LUNs or a set ofLUNs to a host. AppSync relies on the VMAX 3 Auto-Provisioning capability. The mount

Prerequisites


host must be zoned to the VMAX 3 array. Create a masking view with the initiator group,port group, and storage group.

When AppSync performs a mount operation on VMAX 3, it discovers the host initiator forthe mount host first, then based on this host initiator, AppSync maps to (or from) themasking view. This action determines the storage group where the target LUNs aremasked/unmasked . For RDM or Vdisk mount/unmount, AppSync identifies the maskingview that is based on the host initiator for the ESX server.

You can select the wanted Service Level Objective (SLO) for the target LUN in the mountphase of the service plan. If there is a storage group for the mount host with the wantedSLO, AppSync adds the LUN to the storage group. If this storage group does not exist,AppSync adds the LUN to any storage group that is masked to the host.

If a storage group is configured to pick target devices, AppSync removes the devices fromthe storage group at the time of mount and adds them to the storage group for the mounthost. The devices are added to the original storage group when expired.

ViPR Controller setupLearn about support for ViPR Controller with AppSync, including configurationconsiderations, supported service plans and applications.

With this release of AppSync, ViPR Controller operates as another storage system. Thismeans that, ViPR Controller needs to be registered and discovered into AppSync. Refer tothe section on adding ViPR Controller to AppSync.

AppSync supports ViPR Controller snapshots as copy technology for applicationsprovisioned using ViPR Controller. .

Note

An application with a mix of LUNs for protection is not supported. For example, AppSyncdoes not support a mix of native (AppSync-based) LUNs on VMAX and ViPR ControllerLUNs.

AppSync only supports applications that are provisioned by ViPR Controller with blockvirtual pools backed by VMAX/VPLEX with VMAX and XtremIO storage. AppSync does notsupport applications provisioned on file and object virtual pools.

Note

AppSync does not support ISCSI with AIX for either XtremIO native storage or XtremIO onViPR Controller.

Migration from native array to ViPR controllerAppSync supports ViPR Controller copy management functionality such that migration ofapplications from native to ViPR platform occurs without any disruption to existing copiesand service plans and without manual intervention. For example:

1. Assume you have an Oracle database running on a VMAX, and you are using AppSyncto protect this database using a Bronze service plan for local protection.

2. AppSync creates a daily snapshot of the database by directly interacting with VMAXstorage natively using an SMI-S provider.

3. At some time in the future, you decide to use a ViPR Controller platform to automateyour storage infrastructure. As part of this automation, you move all existing volumesinto ViPR Controller. ViPR Controller requires all storage management tasks such asvolume provisioning for snapshot creation, deletion and so on to be performed usingViPR Controller.

Prerequisites

ViPR Controller setup 19

4. You still need local protection of your Oracle database on VMAX storage but you wantto migrate to ViPR Controller for all snapshot operations.

5. With AppSync you can seamlessly migrate to the ViPR Controller platform without anymanual intervention or modification to your existing plans.

Service plan considerations with ViPR ControllerBefore you add a service plan for ViPR Controller copies, review these considerations.

Copy management functionality for ViPR Controller follows the same workflow asAppSync for native storage array support. For example, you must configure a host, a ViPRController resource inside AppSync, and then perform discovery of the application. Oncediscovered, you can subscribe the application to an existing service plan within AppSync.For this release, Bronze service plans are supported.

Mount and unmount ViPR Controller copiesReview this information regarding mounting and unmounting ViPR Controller copies withAppSync.

AppSync allows mounting of application copies created using ViPR snapshot to hostsregistered with ViPR Controller. AppSync makes use of ViPR export groups while mountingcopies of an application.

As part of mount, AppSync determines if a mount host already has a provisioned exportgroup in the project and ViPR array where snapshots are stored. If AppSync finds anexisting export group, it updates the export group by adding snapshots to the exportgroup. If AppSync cannot find an export group for the mount host and ViPR array wherethe snapshot is stored, AppSync makes use of ViPR APIs to provision a new export groupfor the host in the required project for the ViPR arrays where the snapshots are located.

Automatic zoning troubleshooting tip: When a Fabric Manager account has read-onlyaccess and a ViPR array has SAN zoning set to Automatic > Create Export Group, thisaction fails if the host is not zoned to the array. Automatic zoning cannot be performedsince the Fabric Manager account has read-only access to fabric. To work around thisissue, set SAN Zoning to Manual and then manually create a zone between the host andphysical array.

ViPR Controller copy restoreReview these scenarios when considering a restore of a ViPR Controllercopy.

AppSync does not support restore from application copies which are created using ViPRController where the volume was provisioned by ViPR Controller on an XtremIO back-endarray (either natively or by using VPLEX in front-end).

LUN level restore from ViPR snapshotWhile restoring from a ViPR Controller snapshot, AppSync checks for an affected entity incase of consistency groups and warns you about other applications which may becomeimpacted due to the restore.

Granular RestoreAppSync supports granular restore for virtual machines and file with ViPR Controller asstorage platform. Since ViPR Controller does not have capability to create a copy of acopy, granular restore for virtual machines always uses cloning of virtual machines torecover the virtual machines from a replica.

Instant restore functionality is disabled while using ViPR Controller.

Prerequisites


XtremIO setupReview the supported applications, replication technology, configuration requirements,and restrictions for XtremIO arrays with AppSync before you begin the installation.

Application supportAppSync creates write-consistent snapshots on the XtremIO array for each applicationyou add to a service plan. XtremIO supports the following applications:

l Oracles databases

l SQL Server databases

l Exchange databases and DAG

l File systems

l VMware data stores

l RecoverPoint (4.1.2 minimum version) is supported with XtremIO 4.0 and later andAppSync 2.2.2 and later.

Replication technologyAppSync creates XtremIO Snapshots of the application data and places the snapshots inthe following common folder: /AppSyncSnapshots/APPSYNCSERVERNAME/PRODUCTIONHOSTNAME/. Move XtremIO Snapshots from the common folder only if youuse the AppSync copy Remove feature, which removes a copy from AppSync, but doesnot remove the XtremIO snapshots.

AppSync names snapshots by using the following naming convention:TIMESTAMP.snap.ORIGINALVOLNAME. Due to the XtremIO limit of 64 characters in asnapshot name, the ORIGINALVOLNAME should be 40 characters or less.

Review XtremIO limits regarding the number of LUNs that can be snapped at one time. Donot let Oracle database configurations exceed the number of volumes limited bymaximum XtremIO snapshot capabilities.

Note

To familiarize yourself with XtremIO limits, particularly limits regarding XtremIOSnapshots and folders, review the EMC XtremIO Release Notes These notes are availableon the EMC Support website.

RestrictionsConsider the following restrictions for XtremIO with AppSync:

l XtremIO does not support restore of XtremIO Snapshots back to the original volume.However semi-manual recovery procedures using AppSync copies exist for eachsupported application.

l XtremIO Initiator Groups must be defined in XtremIO for all mount hosts to whichAppSync mounts XtremIO copies.

l For this release, AppSync does not support XtremIO with ISCSI connectivity for AIXhosts.

Configuration considerations

l The XtremIO Management Server (XMS) should be configured on a SAN with oneXtremIO array.

l Zone XtremIO arrays to production and mount hosts (physical) or ESX servers(virtual).

Prerequisites

XtremIO setup 21

l For mount and unmount of copies:

n Ensure that you configure Oracle or SQL Server databases on XtremIO arrays fordata and logs.

n Fibre Channel and iSCSI are supported.

Considerations before adding an array:To add and configure an XtremIO array to work with AppSync, you need an XtremIOManagement Server (XMS) configured on a SAN with at least one XtremIO array. One XMSmanages each XtremIO array. Review the following considerations before adding anarray: a

l Administrator privileges are required to add the XtremIO array.

l Ensure XtremIO storage is zoned to production hosts (physical) or ESX servers(virtual). RDM and virtual disk are supported on VMware virtual machines. iSCSI issupported for Windows and Linux hosts, allowing you to see XtremIO storage over aniSCSI LAN. iSCSI is supported for physical or virtual hosts, and also ESX servers.

l Oracle, file systems and VMFS data stores on Linux/AIX are supported. File systemsand virtual disks are supported on Windows.

l You need the XMS name/IP address and credentials.

For steps to add an XtremIO array, go to Add an XtremIO array to AppSync on page 48.

Summary of service plan features for XtremIOTo create application consistent copies of data, service plans are enabled for XtremIO.Review these considerations when you add a service plan for an XtremIO array.

AppSync 2.2.2 and later with XtremIO 4.0 and later support Bronze, Silver, and Goldservice plans. AppSync supports only Bronze service plans on XtremIO 3.x using AppSync2.1.x.x through 2.2.1.x.

AppSync selects XtremIO Snapshot as the default replication technology for storage-ordered copies when a service plan runs.

XtremIO service plans allow you to place application items from multiple XtremIO storagesystems in the same service plan. Service plan scripting is enabled when you configuremount and unmount script actions. Also you can configure expiration rotation count andrun a service plan on a schedule or on demand.

Restore options with XtremIO storageLearn about restore options for application copies on XtremIO arrays when planning theinstallation.

AppSync 2.2.2 and later supports automated restore of XtremIO 4.0 and later copies. Thefollowing applications are supported:


l Exchange standalone databases and Exchange Data Availability Groups (DAG)


l File systems

l RecoverPoint

AppSync uses the Restore wizard for automated restore on XtremIO storage. The Restorebutton is no longer disabled for XtremIO copies. Click the Restore button to launchRestore wizard for respective applications. During restore, AppSync creates anotherXtremIO-generated snapshot, stored under the tag /volumes/AppSyncSnapshots/RestoredSnapshots. An Administrator must clean up these snapshots manually.

Prerequisites


Note

If you have two coopies for restore, one for XtremIO 3.x and another for XtremIO 4.0,AppSync allows restore only for the 4.0 copy. A warning appears for the 3.x copy.

AppSync 2.1.x through 2.2.1.x with XtremIO 3.0.x supports semi-manual restore for thefollowing applications:


l Exchange standalone databases and Exchange Data Availability Groups (DAG)


l File systems

The AppSync User and Administration Guide discusses the procedures for each type ofsemi-manual restore.

RecoverPoint setupConsider best practices for RecoverPoint setup before deploying AppSync. For example,be sure to observe RecoverPoint consistency group granularity best practices.

Service plan considerations for applications with RecoverPoint protectionAppSync supports different RecoverPoint replication options.

Three types of replication options:

Continuous Data ProtectionIn Continuous Data Protection (CDP), RecoverPoint replicates to a storage array atthe same site. In a RecoverPoint installation that is used exclusively for CDP, youinstall RPAs at only one site and do not specify a WAN interface. The Bronze serviceplan protects application replication.

Continuous Remote ReplicationIn Continuous Remote Replication (CRR), RecoverPoint replicates over a WAN to aremote site. There is no limit to the replication distance. The Silver service planprotects application replication.

Concurrent Local and RemoteIn Concurrent Local and Remote Replication (CLR), RecoverPoint protects productionLUNs locally using CDP and remotely using CRR. Both copies have differentprotection windows and RPO policies. The Gold service plan protects applicationreplication. RecoverPoint multi-site (multiple remote sites) is not supported at thistime.

RecoverPoint prerequisitesVerify that the RecoverPoint configuration meets the prerequisites necessary for use withAppSync.

l Install and configure RecoverPoint according to the RecoverPoint documentation.

l Use RecoverPoint to create consistency groups.

l Ensure that the splitters for all mount hosts are attached to the RecoverPoint targetvolumes they are going to use.

l Synchronize time on all systems. Follow the steps in the operating systemdocumentation to configure the AppSync server and all production and mount hosts

Prerequisites

RecoverPoint setup 23

to be synchronized with a time server. This includes all hosts, VNX storage, andRecoverPoint appliances.

l For failover preparation, keep in mind that AppSync requires that RecoverPointConcurrent Local and Remote (CLR) consistency groups have both local and remotecopies, even in a failover situation. This may require RecoverPoint administratorconfiguration steps after failover to configure a local copy on the remote site.

l During AppSync configuration, the RecoverPoint site is added as a resource. In a CLRconfiguration, AppSync discovers all sites in the RecoverPoint system configuration.Credentials for an account that has RecoverPoint admin privileges is required whenadding the site.

Dynamic or static mountsRecoverPoint copies can be mounted in two ways, statically or dynamically.

AppSync supported static mounts of RecoverPoint targets. Using static mounts, theRecoverPoint target LUNs (CDP or CRR) had to be pre-exposed (masked) to the mounthost before you could mount the RecoverPoint copies. If you are using static mounts in avirtual machine environment, the RecoverPoint target LUNs must be masked to the ESXserver, and added as RDMs to the virtual machines prior to mounting the copy.

RecoverPoint targets may also be dynamically mounted. RecoverPoint target LUNs aremapped at mount time to identify the LUNs, and the LUNs are masked (moved to themount host storage group) and surfaced prior to mounting. When the target LUNs fordynamic mount are on VNX storage, the VNX must be registered with AppSync.

For VMAX dynamic mounts, follow the VMAX auto provisioning instructions so thatmasking succeeds.

If you are using dynamic mounts in a virtual environment, do not mask the target LUNs tothe ESX server. AppSync will mask the LUN to the ESX server, and then add the LUN as anRDM to the mount host. Refer to Mount and unmount VMAX copies on page 17.

When unmounting:

l LUNs which were dynamically mounted are dynamically unmounted, that is, the LUNsare removed from the storage group.

l LUNs which were statically mounted remain in the storage group after the unmountcompletes.

l For application copies with LUNs that are mixed (both statically and dynamicallymounted), the LUNs will be dynamically unmounted. All mounted LUNs are removedfrom the storage group.

Given proper zoning, AppSync presents storage to the host automatically when a copy ismounted.

Physical hostAppSync dynamically assigns a snapshot to the host when the copy is mounted. Thephysical host must be zoned to the VNX array of the RecoverPoint target LUNs (CDPor CRR).

Virtual machineDynamic mounts happen as a raw device mapping (RDM) or through native iSCSI onthe VM.

l For RDM, the ESX server where the VM resides must be zoned to the VNX array of theRecoverPoint target LUNs (CDP or CRR).

l For RDM and virtual disks, virtual center (which manages the ESX server where the VMmount host resides) must be registered with the AppSync server.

Prerequisites


l For native iSCSI, the virtual machine must be logged into the VNX initiators of theRecoverPoint target LUNs (CDP or CRR). The VNX must have a storage group definedfor the host.

Prerequisites

Dynamic or static mounts 25

Prerequisites


CHAPTER 2

Installation

This chapter includes information on how to install your AppSync software. Forinformation on how to install arrays, see the chapter on Configuration, section onResource Management.

Topics in this chapter include:

l Fresh installation of AppSync overview..................................................................28l Upgrade overview..................................................................................................32l Service pack installation overview.........................................................................34l Uninstalling the server ..........................................................................................36l Removing a server from AppSync ..........................................................................37l Uninstalling the AppSync server plug-in................................................................ 37

Installation 27

Fresh installation of AppSync overviewReview this section before you perform a new installation of AppSync. This means youhave no previous versions of AppSync on your system.

To install AppSync you must perform the following operations which are discussedfurther in this section:

l Install the AppSync server.

l Install the AppSync agent plugin.

l Add your servers to AppSync.

If you want to upgrade an existing AppSync installation to the current full version (not aservice pack) refer to Upgrade your AppSync installation on page 32.

To install an AppSync Service Pack, refer to Install a service pack.

Installing the serverThe first step to install your AppSync software is to install the AppSync server by runningthe installation executable on the AppSync server host.

Before you begin

Obtain the installation executable from the AppSync distribution or from the AppSyncdownload page on the EMC Support website.

Procedure

1. Run the executable installation file.

2. Follow the wizard steps:

a. Accept the license agreement.

b. Enter a username for default administrator account.

c. Enter a password for default administrator account.

The password for the default administrator account must be a minimum of eightcharacters, must be mixed case, and it must contain at least one number and onespecial character from the following list: !@#$%^&()_-+={}[]<>?/`:;',.|\"

d. If you want an installation location other than the default, enter a location.

The installation location path cannot contain a space.

Location of installation log for serverThe installation log for the AppSync server, appsync_setup.log, is located in thefolder defined by the installing user's TEMP environment variable.

Installing the host plug-in manually - Windows servers onlyInstall the host plug-in manually when a firewall or other security measure prevents pushinstallation from the server to the application host.

Before you begin

You need to obtain the AppSync host plug-in installation executable from the AppSyncdistribution or from the AppSync support page on https://support.emc.com

Installation


http://support.emc.com/

Procedure

1. Run the plug-in executable installation file.

2. Follow the wizard steps.

Accept the license agreement. You can specify an installation location and port otherthan the default. If you use a non-default port setting, keep a record of it. You need tospecify it when you add the host in AppSync.

After you finish

Manually installed hosts must also be added to AppSync. Use the AppSync console,under Settings > Servers.

Note

A reboot of Exchange may be required after installation of the host plug-in.

UNIX host plugin push install with sudo userThis section demonstrates how to perform a push install of the AppSync host plugin on aUNIX host from the AppSync server. Manual configuration is required. This example usessudo user on Linux.

Before you begin

l Create a user on the host where you plan to run the AppSync agent.

l Edit the sudousers file using visudo. (You must edit this file as root.) Make sure youhave permissions to write to the directory. Add the following lines at the end of thefile:

n n Defaults: user !requirettyn n Defaults: user !env_resetn n {user} ALL = (root) NOPASSWD: /{install path}/acp, where {user}

is the user name you created, {install path} is the location where you want toinstall AppSync. For example:appsync ALL = (root) NOPASSWD: /opt/emc/appsync/acp

Go to the AppSync console as the user you created in pre-requisites, then go to the installpath you set for your AppSync installation.

This example (specific to AIX) shows the configuration required for running a successfuldeployment using sudo user appsync in the following deploymentlocation: /opt/emc/appsync.

Procedure

1. Install SUDO RPM package, sudo-1.7.10p7-1 on AIX 6.1.

2. Install zlib if not previously installed.

3. Install openssh for AIX 6.1.

4. Run SFTP server as root.

5. Create user appsync using smit.

6. Run visudo command as root to open the sudoers file, then edit the sudousersfile to include the following lines for sudo user appsync as root:

l n Defaults: {user} !requirettyl n Defaults: {user} !env_reset

Installation

Installing the host plug-in manually - Windows servers only 29

l n user} ALL = (root) NOPASSWD: /{install path}/acp

Where {user} is the user name you created, and {install path} is the location where youwant to install AppSync.

Note

The acp folder must be used specifically with the NOPASSWD option.

7. Create a folder, /appsync under /opt/emc, with read, write and executepermissions for sudo user appsync.

8. Start SFTP server service for the appsync user.

Rediscovering the serverRediscovering a server retrieves the server information on the AppSync host plug-in. Forexample, if you added Exchange to the host, using Rediscover would refresh the serverwith the new associated application.

Before you begin

This operation requires the Resource Administrator role in AppSync.Procedure

1. Select Settings > Servers.

2. Select the server you want to refresh.

3. Select Rediscover.

4. Select Yes to confirm.

Adding serversLearn how to add your servers to your AppSync configuration.

Before you begin

Review this information before you begin. When you add a server, AppSync registers theserver in its database and discovers the protectable objects on that server. If the hostplug-in software is not already present, AppSync attempts to install it. If the host plug-insoftware is present, AppSync attempts to register it. An error occurs if the host plug-insoftware is already registered to another AppSync server.

l The servers must be accessible over IP to the AppSync server.

l You need to supply credentials for an account that has local administrator privilegeson the server.

l For Windows servers: if the server is not part of a domain, disable the following useraccess control: User Access Control: Run all administrators inAdmin Approval Mode .

l On Windows, AIX/Linux, AppSync can push install the host plugin software. OnWindows, you have the option to manually install the software on the applicationservers.



2. Click Add. You can select to add Windows or UNIX/Linux servers.

Installation


3. For each server, enter the host name or IP address, domain\username, and password.

Optionally, you can automatically repeat the credentials from the first entry for thesubsequent entries. For a local account, use the server name as the domain. If you areprotecting databases in an Exchange DAG, add the DAG member servers that host thedatabase copies that you want to protect.

If you want to protect the virtual disk in the host, register the Virtual Center beforehost registration.

If you want to protect SQL Server databases in availability groups on a WindowsAlwaysOn failover cluster, add each node of the cluster. If you are protecting SQLServer databases in a clustered instance of SQL Server, add the SQL Server virtualserver. Before you add the SQL Server virtual server, you must first install the AppSyncagent host plug-in software on all of the nodes in the cluster using the Add Serverswizard or by manually installing the software.

Note

If SQL Server virtual server is added before the latest version of the AppSync agenthost plug-in is installed on all physical nodes of the cluster, Add virtual server canfail.

4. Expand Push Install Settings to install the agent host plug-in software as part of theAdd Servers operation.

Use Push Install Settings when AppSync installs the agent host plug-in software aspart of the Add Servers operation. You can specify the agent host plug-in version toinstall, the port (on Windows servers only), and the location in which to install theagent host plug-in. These values apply to each server that you are adding.

Available plug-in versions depend on what is available on the AppSync server. OnWindows servers, the default port is 10004; valid range is from 1024 to 49151. Thedefault install location is system drive\Program Files\EMC\AppSync HostPlug-in.

Note

For Windows servers: verify that agent host plug-in is no more than one versionbehind the version of the server. Make sure that the server components are at thesame version as the AppSync server. You must upgrade the plug-in to 2.1 from anyearlier version, then upgrade to 2.2 if desired. (Refer to ESA-2015-082.)

5. Click Start.

Temporary location for UNIX hostsYou can configure a temporary location for each UNIX host from AppSync console, Serverspage.

This location will be used by AppSync during Oracle mount operations to storeinformation that was previously located in /tmp/<SID>/.

The default temporary location is /tmp/ unless otherwise specified .

Installation

Adding servers 31

Upgrade overviewReview this information before you perform an upgrade of your AppSync installation. Anupgrade is not the same as a service pack installation.

These upgrade procedures can be performed on major or minor releases of AppSync. Toinstall an AppSync service pack, refer to the Service Pack Installation topics later in thisdocument.

Upgrading the AppSync serverLearn how to upgrade the AppSync sever to 2.2 including upgrade paths, supportedversions, and reference documentation for backing up your existing installation ofAppSync.

If you are upgrading a current AppSync installation, you must upgrade the AppSyncserver.

To upgrade AppSync perform the steps that follow on the server host. This includesrunning the new installation executable obtainable from the AppSync distribution or fromthe AppSync page on the EMC Support website. It is not necessary to uninstall theprevious version of AppSync before installing a new one. AppSync server 2.0 and 2.1 canbe upgraded directly to 2.2.

Note

Before you upgrade, refer to the prerequisites required for the server in the previouschapter.

AppSync can now run a backup (and restore) of the existing server before you upgrade.This process is documented in the configuration section of this document.

To upgrade AppSync, follow these steps:

Procedure

1. Disable all service plans and make sure there is no current activity on the AppSyncserver.

2. On the AppSync console go to Help About > AppSync and note your complete AppSyncversion including CFxx (xx = the cumulative hotfix number). You will need this numberlater.

If there is no CF number in the panel, go to C:\Program Files (x86)\Zero GRegistry\AppSyncIndicator to check for the CF number.If no hotfixes were applied to your installation, you will not have a CF number.

3. Additionally, note any hand-edit procedures to configuration files that CustomerSupport requested you to perform for your AppSync server installation. Forinformation on adding back these edits, refer to the section on rolling back the serversoftware.

4. Go to your \EMC\Appsync\Jboss\datastore\data and click Properties to viewthe size of this directory. During upgrade, AppSync runs a backup of the server thatrequires 40% of the size of this directory, so plan a backup save location with at leastthis amount of free space.


The upgrade process requires free space equal to the size of the directory in Step 4.

Installation


6. Follow the wizard steps and accept the license agreement.


Before you begin






Upgrading the AppSync agent plug-inLearn how to update a server and install a newer version of the AppSync agent (host plug-in).

Before you begin

This operation requires the Resource Administrator role in AppSync. If the server is notpart of a domain, the following user access control must be disabled: "User AccessControl: Run all administrators in Admin Approval Mode".When updating Exchange Mailbox or utility servers, you will also need the credentials forrunning the AppSync Exchange Interface service. This service is reconfigured duringupdate.

For AppSync 2.2, verify that agent host plug-in is no more than one version behind theversion of the AppSync the server. For AppSync 2.1 and lower, upgrade the agent hostplug-in to 2.1 from any earlier version, then upgrade to 2.2 if desired. (Refer toESA-2014-179).

Procedure


2. Select the server and select Update Plug-in from the action button below the Serverstable.

3. Select one or more servers from the Update Server Plug-in list.

If you select multiple servers, they must all have the same credentials.

4. Select Set Username and Password.

5. Specify credentials of an account with local administrator privileges on the serversand click OK.

If an Exchange Mailbox or utility server is in the list, you will be asked to enter thecredentials for running the AppSync Exchange Interface service. Specify thecredentials and click OK.

6. Click Start to update the host plug-in.

After you finish

If you are updating a host plug-in on Exchange servers, refer to the latest user andadministration guide for AppSync.

Installation

Upgrading the AppSync agent plug-in 33


Before you begin






Service pack installation overviewReview this information regarding how to upgrade the AppSync server to the version ofthis service pack. Including is information on upgrade paths, supported versions, andreference documentation for backing up the existing installation of AppSync.

If you are upgrading a current AppSync installation, upgrade the AppSync server. Reviewthe following requirements for 2.2.2:

l The 2.2.2 AppSync server cannot be installed as a standalone product. The AppSyncserver must be at 2.2.0, or 2.2.1 before you can upgrade to the 2.2.2 AppSync server.If it is not, upgrade the current AppSync server version to 2.2.0, then upgrade to2.2.2.

Note

An error message appears if you try to install the 2.2.2 AppSync server directly to apre-2.2.0 version of AppSync.

l Uninstalling the 2.2.2 AppSync server does not perform a roll back to 2.2.0, or 2.2.1.The server is completely removed from the installation if uninstalled. A backup is runautomatically before the AppSync server upgrade. AppSync stores the backup in C:\AppSyncBackup\22xx_BACKUP by default.

l Also install the agent plugin for 2.2.2. Refer to Upgrading the agent plugin for theservice pack on page 35.

Installing the AppSync 2.2 Service Pack 2 serverPerform this procedure to install the 2.2 SP2 AppSync server.

Obtain the installation executable from the AppSync distribution or from the AppSyncpage on the EMC Support website. For example, if you are at version 2.1, upgrade theAppSync server first to 2.2.0, then to 2.2.2, so obtain both executables and perform theupgrade procedure twice.

AppSync server 2.0 and 2.1 can be upgraded directly to 2.2.

Procedure

1. Disable all service plans and ensure that there is no current activity on the AppSyncserver.

Installation


2. On the AppSync console, go to Help About > AppSync and note the complete AppSyncversion including CFxx (xx = the cumulative hotfix number). You need this numberlater.

If there is no CF number in the panel, go to C:\Program Files (x86)\Zero GRegistry\AppSyncIndicator to check for the CF number.If no hotfixes were applied to the installation, no CF number appears.

3. Also, note any hand-edit procedures to configuration files that Customer Supportrequested you to perform for the AppSync server installation. For information onadding back these edits, refer to the section on rolling back the server software (2.2.0servers and lower can be rolled back to previous server versions. You cannot roll backAppSync 2.2.2 servers).

4. Go to \EMC\Appsync\Jboss\datastore\data and click Properties to view thesize of this directory. During upgrade, AppSync runs a backup of the server thatrequires 40% of the size of this directory, so plan a backup save location with at leastthis amount of free space.


The upgrade process requires free space equal to the size of the directory in Step 4.

6. Follow the wizard steps and accept the license agreement.

Upgrading the AppSync agent plug-in on a server for 2.2 SP2Learn how to update a server and install a newer version of the AppSync agent (host plug-in).

The AppSync agent plug-in for 2.2.2 can be installed directly and upgraded from[Windows host plug-in] versions lower than 2.2.0.

For Windows servers: With an AppSync server where a windows host agent is registered,verify that agent host plug-in version is no more than one version behind the version ofthe AppSync server. Upgrade the agent plug-in to a minimum version of 2.1 from anyearlier version and then apply 2.1.0.1 CF06 patch on the agent plug-in. (Refer toESA-2015-082.)

Procedure


2. Select the server and select Update Plug-in from the action button below the Serverstable.

3. Select one or more servers from the Update Server Plug-in list.

If you select multiple servers, they must all have the same credentials.

4. Select Set Username and Password.


If an Exchange Mailbox or utility server is in the list, you are asked to type thecredentials for running the AppSync Exchange Interface service. Specify thecredentials and then click OK.

6. Click Start to update the host plug-in.

Installation

Upgrading the AppSync agent plug-in on a server for 2.2 SP2 35


Before you begin






Uninstalling the serverUninstall the AppSync server by running the native Windows uninstall utility.

Before you begin

l Be sure you are logged in as a user with Windows Administrator privileges.

l Remove hosts in Settings > Servers before uninstalling the server.

l This operation requires the Resource Administrator role in AppSync.

Procedure

1. Run the native Windows uninstall utility.

2. Follow the wizard steps.

Files and folders added after installation are not removed.

Rolling back the AppSync server softwareThis procedure shows you how to roll back to a previously installed version of theAppSync server.

Before you begin

EMC Engineering strongly suggests that you contact EMC Customer Support to resolve theissues with the newer, enhanced version of AppSync you are currently running beforetrying to roll back to an older version.

You need your previous and current AppSync versions that you collected when youinstalled the current version of AppSync. Refer to Upgrading the server on page 32.

Procedure

1. Copy your license files to a safe place from the /EMC/AppSync/license folder.

2. Disable all Service Plans and make sure there is no current activity on the AppSyncserver.

3. Uninstall the AppSync server application from the host.

After the uninstall completes, the /EMC/AppSync folder should not be present onthe machine.

4. Re-install the version of AppSync server that was on the host prior to upgrade that younoted during the server upgrade procedure (Upgrading the server on page 32).

Installation


Make sure you apply the exact version of AppSync that includes the exact cumulativehotfix number, if a hotfix was previously installed.

5. Re-apply any hand-edit procedures to configuration files that a readme or EMCCustomer Support Representative requested that you implement for your previousAppSync server installation.

6. Restore the automated backup refer to: Automated backup restore on page 40.

7. Re-apply your AppSync licenses from within the AppSync application.

Removing a server from AppSyncThe Remove Servers Only operation deletes the server's entry in the AppSync database.

Before you begin

This operation requires the Resource Administrator role in AppSync.

You cannot remove a server if its databases are subscribed to service plans, if it hascopies or has copied mounted, or if it is used in any script phases.

Procedure


2. Select a server or servers (multiselection is allowed) and click the Remove > RemoveServers Only button.

3. Select Yes in the Remove Servers dialog.

If successful, the host is removed from the list under Settings > Servers. If not, an errormessage displays indicating why the removal failed.

After you finish

If the server you removed is one of the members of a DAG, you must rediscover databasesin AppSync.

Uninstalling the AppSync server plug-inThe Deinstall plug-in and remove operation uninstalls the plug-in software from theselected servers and then removes the server's entry in the AppSync database.

Before you begin

This operation requires the Resource Administrator role in AppSync. If the server is notpart of a domain, the following user access control must be disabled: "User AccessControl: Run all administrators in Admin Approval Mode".

Procedure


2. Select one or more servers and select Deinstall plug-in and remove.

3. Select servers from the Deinstall Server Plug-in wizard.

The wizard allows multi-selection. In these cases, the same user name and passwordwill be applied to all selections.

4. For each server you wish to deinstall the plug-in, select Set Username and Password.


Installation

Removing a server from AppSync 37

6. Click Start to deinstall the server plug-in and remove the server from AppSync.

The deinstallation progress displays in the progress column for each server. If thereare failures, they display with a red icon.

7. If some of the servers fail deinstallation, you can retry. Select Clear Successful andthen select Start again.

Installation


CHAPTER 3

Configuration and resource management

This chapter includes the following topics:

l Backup and restore AppSync using the Backup Assistant tool............................... 40l Migrating the AppSync server................................................................................ 41l Resource management ......................................................................................... 41

Configuration and resource management 39

Backup and restore AppSync using the Backup Assistant toolInstalled with the AppSync server is a tool that can be leveraged to both backup andrestore the local AppSync database. The tool is called the Backup Assistant.

AppSync Backup Assistant arguments and actionsLearn how to back up and restore the AppSync database by selecting the appropriatearguments for the AppSync Backup Assistant, appsync-backup.bat, located in the\AppSync\backup-assistant directory.

Ensure you have a valid backup before attempting a database restore.To create a backup, run appsync-backup.bat from the administrator commandprompt using the following syntax:

appsync-backup.bat[-o, -out "<path>"] [-d, -debug] [-h, -help]

Table 4 AppSync Backup tool arguments and actions

Argument Action

-o, -out Allows you to specify the base directory in which to save the backup. The backup is placed in a sub-directory referencing the current Date and Time. (Default ='$SystemDrive\AppSyncBackup\<DateTimeStamp>')

-d, -debug Enables display of DEBUG messages.

-h, -help Prints the Help message.

-i, -import Allows you to specify a backup that you want to restore to the current host. (If this argument is not used abackup will be taken.)

An example of an export command.appsync-backup.bat -o C:\AppSyncBackupDir -d

Restore an automated backupThe Backup Assistant tool allows you to restore a backup created previously with thistool. Learn about the process and caveats for automated backup. Be sure to restore abackup at a time of low activity on the server.

Before you begin

To restore a back up from an older version of AppSync be sure that you install the latestversion of AppSync before attempting to use the automated restore.

Automated restore is supported for backups taken with the Backup Assistant tool fromAppSync 2.0 and above.

Note

Automated restore is supported for backups taken with the Backup Assistant tool fromAppSync 2.0 and above. However, restoring an earlier version of the backed-up AppSyncdatabase on a new version of AppSync server is not supported. Make sure the version ofthe AppSync server installed on the host is same version as the backup that was created.



Backups taken from AppSync 1.6 are still supported but you must follow the manualrestore process.

Procedure

1. Run the backup assistant tool with the -i, -import argument, for example: C:\AppSyncBackup\2100_BACKUP\2015_06_17_06_34_32\base.tar.gz

When running this restore, the AppSync services will be stopped.

Migrating the AppSync serverYou can migrate the AppSync server from one server to another.

For example, to migrate a server from Server A to Server B:

Procedure

1. Disable all service plans on Server A.

2. Copy the license files from Server A from /EMC/AppSync/license to a folder onServer B.

3. On the AppSync console on Server A, go to Help About > AppSync and note thecomplete AppSync version including CFxx (xx = the cumulative hotfix number). Also,note any hand-edit procedures to configuration files that Customer Support requestedyou to perform for the AppSync server installation.

4. Install the AppSync server on Server B. Ensure you apply the exact version of AppSyncthat includes the exact cumulative hotfix number, if a hotfix was previously installed.Re-apply any hand-edit procedures to configuration files that you noted in step 3.

5. Take a backup of the AppSync server from server A using the AppSync BackupAssistant utility, for example type: appsync-backup.bat -o C:\AppSyncBackupDir

6. Restore the backup on Server B using the Backup Assistant utility, type: appsync-backup.bat -i C:\AppSyncBackupDir\base.tar.gz

7. Re-apply the AppSync licenses on Server B within the AppSync application.

8. Enable service plans on server B.

9. Stop the AppSync server on Server A.

Results

You can now use the AppSync server on Server B.

Resource managementUse Settings > Servers to manage hosts.

Use Settings > Storage Infrastructure to manage storage systems and RecoverPoint sites.

Use Settings > VMware vCenter Servers to manage vCenter Servers.


Migrating the AppSync server 41

Adding a RecoverPoint siteLearn how to add a RecoverPoint site to offer CLR, RecoverPoint Continuous DataProtection, and RecoverPoint Continuous Remote Replication protection that is providedby Bronze, Silver, and Gold service plans.

Before you begin


Procedure

1. Select Settings > Storage Infrastructure.

2. Select Add > RecoverPoint Sites.

3. Type the site management IP address or hostname for the RecoverPoint site, or RPAcluster name.

In a CLR configuration, you must add one site, then the others are discoveredautomatically.

4. Type an existing username and password for an account that has a RecoverPointAdmin role to access the site.

Updating the RecoverPoint site management IP addressUpdate AppSync when a RecoverPoint site's management IP address changes.

Before you begin


Procedure

1. Select Settings > Storage Infrastucture.

2. Select the RecoverPoint site.

3. In the Details pane, in the IP Address field, enter the new site management IP addressfor the RecoverPoint site and click Apply.

Rediscovering a RecoverPoint siteThe Rediscover operation initiates a discovery of site information. For example, theRediscover operation may find additional RPAs or changes in site name (if invalid logincredentials impede connectivity).

Before you begin


Procedure


2. Select a RecoverPoint site or sites.


Removing a RecoverPoint site

Before you begin

This operation requires the Resource Administrator role in AppSync. Removal fails if sitesare in use.



Procedure



3. Select Remove.

Setting the credentials for a RecoverPoint applianceSpecify RecoverPoint appliance credentials when adding the RPA to AppSync and whenthe credentials change on the RPA itself.

Before you begin

Ensure you obtain the credentials for the RecoverPoint appliance. The account that youspecify must have the RecoverPoint Admin role.

Initially, specify the credentials when you add the RecoverPoint appliance to AppSync. Toupdate the credentials in AppSync later, follow these steps:

Procedure

1. Select Reset Login Credentials from a RecoverPoint site that is listed in Settings >Storage Infrastructurepage of the console.

2. Add the current credentials for the appliance.

Viewing RecoverPoint sitesView RecoverPoint sites under the Settings tab.

Before you begin


Procedure



The Details pane displays information for the RecoverPoint sites you selected.

Adding VMAX and VMAX 3 storageFollow this procedure to add VMAX and VMAX 3 arrays to AppSync.

Before you begin


AppSync requires a minimum of version 8.0.2 for the SMI-S provider to support VMAX 3arrays, and a minimum SMI-S provider version 4.6.2.27 to support VMAX V2 arrays. Donot use the same SMI-S provider to manage both V2 and V3 arrays.

Note

After upgrading to AppSync 2.2.2, or after upgrading the SMI-S provider, rediscover allVMAX arrays in AppSync. This action updates the provider configuration information.

AppSync can manage both V2 and V3 arrays on the same host with an SMI-S providerversion 8.0.3.10 and later.

Procedure

1. On the AppSync console, select Settings > Storage Infrastructure.


Adding VMAX and VMAX 3 storage 43

2. In the lower left corner of the console, click Add in the drop-down list, and then selectVMAX Storage to launch the Add VMAX storage wizard.

3. On the first page of the wizard, type SMI-S provider credentials including Name orIP address, Port number, User Name, and Password.

4. Click Enter to display the Select VMAX page.

A list of VMAX arrays managed by the SMI-S provider appears.

5. Select the wanted array (the array where you want to store the copy, not theproduction array), and then click Next.

The Groups and Pools page appears where you can configure VMAX arrays for storagegroups and/or storage pools. For VMAX 3 arrays, only storage group options appear,for example:Figure 1 Configure VMAX storage group

6. Select a Storage Group and/or Storage Pool from the drop-down list. If you selectStorage Pool, add the threshold for storage pool usage.

For a VMAX 3, if the storage group option is not configured, the storage Resource Poolis used to create target devices.

7. After selecting these options, click Finish.

A pop-up appears with a Successfully Configured VMAX storage message.

Using VMAX Manage Copy Storage featureAfter adding VMAX arrays, you can change or begin assignments of the array to a storagegroup or pool using the Manage Copy Storage feature of the AppSync console.

Before you begin

From the AppSync console browse to the VMAX arrays: Settings > Storage Infrastructure

Use the Manage Copy Storage feature, to assign, or edit a storage group or storage poolfor a specific VMAX array.

Procedure

1. On the Storage Infrastructure array list in the console, highlight the VMAX you want toconfigure, and then click Manage Copy Storage located in the lower menu bar of theStorage Infrastructure screen.

This action launches the Manage Copy Storage dialog box which appears withcurrently configured storage group and pool information for the selected array (ifpreviously configured).



2. Select the wanted storage group for the array from the drop-down Storage Groupmenu in the dialog box.

3. Select the wanted storage pool from the drop-down Storage Pool menu. You can alsoassign the percentage of the array you want to allocate to the pool.

For VMAX V3, Storage Pool displays as Storage Resource Pool, which is pre-selectedand not user selectable.

4. Click OK.

Results

AppSync configures the new data for the VMAX array.

Add a VNX, VNXe array, or a RecoverPoint site to AppSyncThis operation requires the Resource Administrator role in AppSync.

Before you begin

Supply the credentials for an account that has the role of Administrator or StorageAdministrator.

Note

If VNX contains VNX File as well as VNX Block, you must be a Global user.

Procedure


2. Click Add.

3. Select one of the following:

l VNX

l VNXe

l RecoverPoint

4. Add a name or IP address:

a. For a VNX block storage system, enter one or both of the following: the IP addressof service processor SPA or SPB.

Note

If the IP does not resolve to a name, create an entry in the Windows host file with aname. Refer to this file: C:\Windows\System32\drivers\etc\hosts

b. For a VNX, type the IP address of the Control Station.

c. For VNXe, type the Name or IP Address of the Management Interface

d. For a RecoverPoint site, type the site management IP address or hostname for theRecoverPoint site, or RPA cluster name.

In a CLR configuration, you only add one site, then the others are discoveredautomatically.

5. Type additional credentials:

a. For VNX, type the username and password to access the storage system.

b. For VNXe, type the Global Username (Admin username), and Password (Adminpassword.


Add a VNX, VNXe array, or a RecoverPoint site to AppSync 45

c. For RecoverPoint, type an existing username and password to access the site foran account that has the RecoverPoint Admin role.

6. Click OK.

Updating the VNX or VNXe storage systemUpdate AppSync when the VNX is not configured or when you want to add functionality(for example, add VNX block or VNX file).

Before you begin


Procedure


2. Select the VNX storage system that you want to configure.

3. In the Details pane, for VNX, edit the IP address fields for SPA, SPB, and ControlStation IP, or for VNXe, edit the Management Interface credentials, then click Apply.

Setting the credentials for a storage systemYou need to specify credentials when adding or configuring a VNX or VNXe, VMAX, VMAX3, XtremIO or ViPR Controller storage system on AppSync.

Before you begin


You need to know the credentials for the storage system.

Initially you specify credentials when adding the storage system to AppSync. Follow stepsin the Add Storage wizards. You can also update the credentials in AppSync later usingthese steps.

Procedure

1. Select Reset Login Credentials from a storage system listed in Settings > StorageInfrastructure.

2. Enter the new credentials for the storage system and then select OK.

Adding and registering ViPR Controller storage to AppSyncReview pre-requisites and learn the procedure for adding and registering ViPR Controllerstorage to AppSync.

Before you begin

This procedure requires the Storage Administrator role in AppSync and ViPR ControllerProvider Tenant Administrator credentials.ViPR Controller must be registered and discovered into AppSync. AppSync is not multi-tenant aware and allows only one credential to be associated per storage system,therefore configure ViPR Controller with AppSync using ViPR Controller TenantAdministrator credentials. These credentials provide ViPR Controller system rights.

Before adding the ViPR Controller storage, consider the following:

l AppSync uses ViPR Controller Client APIs to communicate with a ViPR Controllersoftware-defined storage system.

l Client APIs makes REST calls to ViPR Controller internally on port 4443 (default).

l As part of ViPR Controller software-defined storage system discovery, AppSyncdiscovers all the controller nodes that are managed by a particular virtual IP.



n By default AppSync uses the IP address that is used to register the ViPR System.EMC recommends that you use the ViPR Controller public virtual IP address(VIP) toregister the array.

n You can change the IP preference and set AppSync to use a particular node IPaddress for all the REST communication.

Procedure

1. On the AppSync console, go to Settings.

2. From the Add drop-down list select ViPR Controller.

Figure 2 Add ViPR to AppSync

The Add ViPR wizard launches.

3. Type the ViPR Virtual Name or IP Address to register ViPR.

4. Type the Global user name.

This name is the username for the ViPR Controller.

5. Enter the ViPR Controller Password.

6. Protocol and Port are pre-configured.

They are set by default.

7. Click OK.

The ViPR Controller details page (Settings Storage Infrastructure) launches where youcan view the added ViPR Controller instance with configuration information.

Results

ViPR Controller details page launches (Settings > Storage Infrastructure) where you canview the added ViPR Controller instance with configuration information.If ViPR Controller credentials are modified in the future, the AppSync StorageAdministrator can reset the ViPR credentials on this settings page.


Adding and registering ViPR Controller storage to AppSync 47

Figure 3 ViPR Controller Settings and Details

Add an XtremIO array to AppSyncTo enable the XtremIO array to work with AppSync, add the array to the AppSyncconfiguration.

With XtremIO 4.0 and later, one XtremIO Management Server (XMS) can manage multipleXtremIO arrays.

To add and configure an XtremIO array to work with AppSync, you need an XtremIOManagement Server (XMS) configured on a SAN with at least one XtremIO array. EnsureXtremIO is zoned to Production and Mount hosts.

Procedure

1. On the AppSync console, go to Settings > Storage Infrastructure.

2. On the left side, center of the Storage Infrastructure page, click Add, and then selectXtremIO.

The Add XtremIO wizard opens.

3. Type the credentials for the XtremIO Management Server, including Name/IP address,Username, and Password, and then click Next.

4. Select the XtremIO array that you want to add to AppSync, and then click Finish.

Results

You can view the added the array on the AppSync Storage Infrastructure page of theAppSync console.



Viewing EMC storageGet steps to view EMC storage on AppSync.

Before you begin

View EMC storage systems under the Settings tab of the AppSync console. This operationrequires the Resource Administrator role in AppSync.

Procedure


2. Select the storage array you would like to view.

The Details pane displays information for the storage system you selected.

Removing an EMC storage systemGet the steps you need to remove an EMC storage system from AppSync.

Before you begin

No copies generated by AppSync can exist on the storage system. This operation requiresthe Resource Administrator role in AppSync.

Note

You cannot remove storage until all copies have been expired.

Procedure


2. Select the storage system you want to remove. For VMAX and VMAX 3 arrays, you mustalso deselect the configured storage pool if applicable.

3. Select Remove.

Rediscovering an EMC storage systemUse the Rediscover operation to query and update VMAX, VMAX v3, VNX, VNXe, XtremIO,ViPR Controller, or RecoverPoint storage system information, such as, name, model, serialnumber, storage group, storage pool, and operating environment version in AppSync.

Before you begin


Procedure


2. Select a storage system.


Adding a VMware vCenter ServerAdd a VMware vCenter Server to AppSync when a virtual machine is used as a mount hostfor a VNX Snapshot copy.

Before you begin

l This operation requires the Resource Administrator role in AppSync.


Viewing EMC storage 49

l Ensure that you know the credentials of an account with Administrator privileges onthe vCenter Server.

Procedure

1. Select Settings > VMware vCenter Servers.

2. Click Add.

3. Type the vCenter Server name.

4. Type the credentials for an account that has Administrator privileges on the vCenterServer.

Resetting the login for a VMware vCenter ServerUpdate AppSync when credentials change for a VMware vCenter Server.

Before you begin

This operation requires the Resource Administrator role in AppSync. You need to knowthe new credentials an account that has Administrator privileges on the VMware vCenterServer.Procedure


2. Select the vCenter server.

3. Select Reset Login Credentials.

4. Enter the credentials of a user account that has Administrator privileges on thevCenter Server.

Removing a VMware vCenter ServerYou can remove a VMware vCenter Server from AppSync.

Before you begin



2. Select one or more vCenter servers to remove.

3. Click Remove.

Repurpose copies on VMAXConsider this information when repurposing Oracle and SQL Server database copiesresiding on a VMAX.

You can repurpose a VMAX source copy where the database resides or the source can bethe target device in an SRDF session.

You can only repurpose a 1st Gen copy from the source, or a 2nd Gen copy (copy of thecopy).

You can repurpose a RecoverPoint bookmark copy of an Oracle or SQL Server database.

When considering repurposing, review the following information:

l VMAX does not support a mix of thick and thin devices in cascading.

l A first generation copy must be a clone. The second generation copy can be a clone ora TimeFinder VP Snap.



l If the source device is thick, then the first and second generation targets are thick. Ifthe source device is thick, AppSync only supports a clone of a clone for the sourcedevice.

l If the source is thin, AppSync supports both a TimeFinder VPSnap of clone and aclone of a clone.

l The first generation copy can be a remote copy or local copy in an SRDF session. Butthe second generation is local only.

l If you have thick source devices, configure the storage group with thick devices,otherwise the first generation copy creation fails.

VMAX 3 repurpose overviewReview VMAX 3 support for Repurposing.

AppSync supports local and remote repurposing of VMAX 3SnapVX copies. Refresh of anexisting copy will create a new snapshot of the source LUN and link it to the originaltarget of the copy in the required mode. The old snapshot is then expired.

Use the Repurpose wizard to create a local or remote repurposed copy with VMAX 3.

Repurpose RecoverPoint Bookmark copies of Oracle or SQL Server databasesAppSync supports the ability to repurpose RecoverPoint Bookmark copies for Oracle orSQL Server databases.

Use AppSync to repurpose a RecoverPoint Bookmark on a VMAX target (VMAX 3 notsupported with this release) and create a first generation (1st Gen) copy, which leveragesTimeFinder Clone or TimeFinder VPSnap replication technology. You can repurpose theclone copy further (not for VPSnap ) to create a 2nd Gen copy that leverages TimeFinderClone or TimeFinder Clone VPSnap.

l Bookmark (hidden) > Clone

l Bookmark (hidden) > Clone > Snap

l Bookmark (hidden) > VPSnap

l Bookmark (hidden) > Clone > Clone

To copy Bookmarks, use the RecoverPoint repurpose wizard. The RecoverPoint Applianceand SMI-S provider or VNX must be registered in AppSync.

Supported configurations include:

l Application: Oracle and SQL Server

l Storage: VNX and VMAX (1st Gen copy is a VMAX copy of

l Bookmark: The 2nd Gen copy is a copy of the 1st Gen copy).

In the repurpose wizard, select Use Bookmark as an intermediate step to performRecoverPoint repurposing. If you do not select this option, AppSync begins nativerepurposing. The drop-down list lists create a 1st Gen copy from site. This optiondetermines if the system uses RecoverPoint Continuous Data Protection or RecoverPointContinuous Remote Replication Bookmark repurposing.

Considerations

l If you refresh the 1st Gen copy, AppSync takes a new copy of the database.

l 1st Gen and 2nd Gen copies are always local.

l Manual expire of 1st Gen the Bookmark copy.

l Refresh a 2nd Gen to create a copy of the 2nd Gen from the 1st Gen.


Repurpose RecoverPoint Bookmark copies of Oracle or SQL Server databases 51

l If the 1st Gen copy is a VMAX clone, the same LUN is used during refresh (instead ofrotation).

Repurpose (create) a 1st Gen copy of a RecoverPoint BookmarkLearn to repurpose a RecoverPoint Bookmark on a VMAX target and create a 1st Gen(clone) copy of an Oracle or SQL Server database, which leverages TimeFinder Clone orTimeFinder VPSnap replication technology. You can repurpose the clone copy further ( notfor VPSnap ) to create a second generation copy that leverages TimeFinder Clone orTimeFinder Clone VPSnap.

Before you begin

The RecoverPoint Appliance and SMI-S provider or VNX must be registered in AppSync.

To copy Bookmarks, use the RecoverPoint repurpose wizard.

Procedure

1. Log in to the AppSync console and select Copy Management.

2. In the repurpose wizard, select Use Bookmark as an intermediate step to performRecoverPoint repurposing.



emc® appsync™ 2.2.2 installation and … setup ... emc appsync 2.2.2 installation and...

Documents