DELL Technologies AppSync 4.5 User Guide
- May 15, 2024
- DELL Technologies
Table of Contents
DELL Technologies AppSync 4.5
Product Information
Specifications
- Product Name: AppSync 4.5
- Document: Installation and Configuration Guide
- Release Date: March 2023
Product Usage Instructions
Purpose
This document is part of the AppSync documentation set and includes information on installing and configuring AppSync.
Audience
This guide is intended for use by customers and service providers to install and configure AppSync.
Related Documentation
The following publications provide additional information:
- AppSync User and Administration Guide
- AppSync Release Notes
- AppSync Security and Configuration Guide
Typographical Conventions
Dell uses the following type style conventions in this document:
| Style | Description |
|---|---|
| Bold | Used for names of interface elements, such as windows, buttons, |
etc.
Italic| Used for full titles of publications referenced in text.
Product Usage FAQs
- Q: What should I do if the product does not function properly?
- A: Contact your Dell technical support professional for assistance.
- Q: Where can I find the most up-to-date information on product features?
- A: Refer to the product release notes for the most current information.
- Q: How can I ensure I am using the latest version of the documentation?
- A: Visit support.dell.com to verify that you have the latest version of the document.
AppSync 4.5
Installation and Configuration Guide
March 2023
Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better use of
your product. CAUTION: A CAUTION indicates either potential damage to hardware
or loss of data and tells you how to avoid the problem. WARNING: A WARNING
indicates a potential for property damage, personal injury, or death.
© 2020 – 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell
Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its
subsidiaries. Other trademarks may be trademarks of their respective owners.
Customer notifications
Disclaimer for Dell Technologies content and third-party content that has not changed. See table below for details:
Use case Disclaimer for remaining third-party content that has not changed.
Disclaimer for Dell Technologies content that has not changed.
Information
This product, document, KB, content, and its references may contain language
from third-party content that is not under the control of Dell Technologies,
and is not consistent with the current Dell Technologies guidelines for its
content. When such third-party content is updated by the relevant third
parties, this document is revised accordingly.
This product, document, KB, content, and its references may contain language
that is not consistent with the current Dell Technologies guidelines. Dell
Technologies plans to update the document over subsequent future releases to
revise the language accordingly.
Customer notifications
Preface
As part of an effort to improve its product lines, Dell periodically releases
revisions of its software and hardware. Therefore, some functions described in
this document might not be supported by all versions of the software or
hardware currently in use. The product release notes provide the most up-to-
date information on product features.
Contact your Dell technical support professional if a product does not
function properly or does not function as described in this document.
NOTE: This document was accurate at publication time. Go to support.dell.com
to ensure that you are using the latest version of this document.
Purpose
This document is part of the AppSync documentation set, and includes
information on installing and configuring AppSync.
Audience
This guide is intended for use by customers and service providers to install
and configure AppSync.
Related documentation
The following publications provide additional information: AppSync User and
Administration Guide AppSync Release Notes AppSync Security and Configuration
Guide
Typographical conventions
Dell uses the following type style conventions in this document:
Table 1. Typographical conventions
Bold
Used for names of interface elements, such as names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user specifically selects or clicks)
Italic
Used for full titles of publications referenced in text
Monospace
Used for:
System code System output, such as an error message or script Pathnames,
filenames, prompts, and syntax Commands and options
Monospace italic
Used for variables
Monospace bold
Used for user input
[ ]
Square brackets enclose optional values
|
Vertical bar indicates alternate selections – the bar means “or”
{ }
Braces enclose content that the user must specify, such as x or y or z
…
Ellipses indicate nonessential information omitted from the example
6
Preface
Where to get help
Dell support, product, and licensing information can be obtained as follows:
Product information
For documentation, release notes, software updates, or information about Dell
products, go to support.dell.com.
Technical support
Go to support.dell.com and click Service Center. You will see several options
for contacting DellTechnical Support. Note that to open a service request, you
must have a valid support agreement. Contact your Dellsales representative for
details about obtaining a valid support agreement or with questions about your
account.
Online communities
Visit community.dell.com for peer contacts, conversations, and content on
product support and solutions. Interactively engage online with customers,
partners, and certified professionals for all Dell products.
Your comments
Your suggestions will help us continue to improve the accuracy, organization,
and overall quality of the user publications. Send your opinions of this
document to support.dell.com.
Preface
7
1
Prerequisites
This chapter includes the following topics:
Topics:
· AppSync server prerequisites · Application host plug-in prerequisites ·
AppSync console prerequisites · Checklist for AppSync deployment
AppSync server prerequisites
The AppSync server must meet specific prerequisites.
The AppSync Support Matrix on
https://elabnavigator.emc.com/eln/modernHomeDataProtection is the
authoritative source of information on supported software and platforms.
The AppSync Security Configuration Guide provides more information on port
requirements.
Table 2. AppSync server prerequisites Item Operating system
Disk space Memory CPU Virtual environments
Value
Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows
Server 2019, Windows Server 2022.
2275 MB minimum. Exact value appears in the installation wizard.
6 GB minimum, 8 GB recommended.
2 CPU minimum, 4 CPU recommended.
VMware virtual machine. Memory and disk space requirements are the same as on
physical host.
HyperV.
Application host plug-in prerequisites
Review this information for specific requirements before you install the
AppSync agent (host plug-in).
The AppSync Support Matrix on
https://elabnavigator.dell.com/vault/pdf/Dell_AppSync.pdf is the authoritative
source of information about supported software and platforms.
Table 3. Application host plug-in prerequisites
Item
Value as of GA (See support matrix for latest versions)
Operating system
Windows Server Linux AIX
Disk space
150 MB minimum. Exact value is displayed in the installation wizard.
Memory
2 GB minimum
CPU
2 CPUs
8
Prerequisites
Table 3. Application host plug-in prerequisites (continued)
Item
Value as of GA (See support matrix for latest versions)
Virtual environments
VMware virtual machine. Memory and disk space requirements are the same as on
physical host.
Hyper-V
Windows ports
10004, pushing the host plug-in to a Windows host requires CIFS access (TCP port 135 and TCP port 445).
UNIX ports:
Source IP is AppSync server:
Destination IP = Production or mount host running UNIX AppSync Host plug-in
Destination port = 22 (SSH port), Protocol: TCP Source IP = Production or
mount host running UNIX AppSync host plug-in
Destination IP = AppSync server Destination Port = 22 (SSH Port). Protocol:
TCP
NOTE: You can modify the SSH port value after the UNIX host is registered.
The AppSync Security Configuration Guide provides more information about port requirements.
Supported device configurations
Table 4. Supported device configurations AIX Multipath: Multipathing package
is required for platforms running VNX, Unity, PowerStore, XtremIO, Metro node|
VPLEX, or PowerMax. Native MPIO PowerPath
Device mapping using: Symbolic links (File system only) mknod devices Block
devices
File systems: jfs and jfs2
Volume Manager: Native LVM
LINUX
Multipath: Multipathing package is required for platforms running VNX, Unity,
PowerStore, XtremIO, Metro node| VPLEX, or PowerMax. Native MPIO PowerPath
Veritas DMP
Supported where both production and mount host have DMP installed and DMP
devices do not have a partition.
Supported with non-ASM database on VXDMP devices with or without VXVM Volume
manager
Device mapping using: Linux-ASMLib (ASM only) UDEV bindings Dev-mapper devices
Block devices with O_DIRECT Symbolic links
ext2, 3, 4 XFS (necessary rpms that is needed on production and
mount host). VxFS (When using VxVM)
Volume Manager: Native LVM VxVM Supported device configuration:
Non-ASM database on VXVM Volume Group
Prerequisites
9
AppSync console prerequisites
The AppSync console runs on various web browsers. AppSync supports Chrome,
Mozilla Firefox, and Microsoft Edge browsers. For version support : The
AppSync Support Matrix on
https://elabnavigator.dell.com/vault/pdf/Dell_AppSync.pdfis the authoritative
source of information about supported software and platforms. The console
requires 1 GB of RAM when loaded and working at capacity. The following ports
are required and their uses are listed here: 8085: This port is used as an
HTTP port for log collection at the backend, and to push install windows
agent. 8444: This port is used as an HTTPS port for authentication. 8445: This
port is used as an HTTPS port for both GUI and REST. The AppSync Security
Configuration Guide provides more information about the port requirements.
Display recommendations
AppSync supports the minimum display resolution of 1366×768. However, as a
recommendation, AppSync is best viewed in 1920×1080 and Chrome browser.
10
Prerequisites
Checklist for AppSync deployment
Learn about initial AppSync deployment steps and how to use the checklist as a map for installation and security concerns.
Table 5. Deployment checklist
Basic step
Identify a system running a supported version of Windows to act as the AppSync
server.
Details
Notes
See a recent support matrix for AppSync for exact Windows versions for the
AppSync server. See the list of server prerequisites in this guide for other
details.
NOTE: An IPv6 host is not supported.
Done?
Verify that you have a supported web browser to run the AppSync console.
Verify that the application host (for example, Microsoft Exchange mailbox
server) meets requirements. Install the AppSync server executable on the
designated server system. From a web browser, open the AppSync console. From
the desktop shortcut or theAppSync console, add the storage where application
data resides.
From the AppSync console, install the AppSync host plug-in on the application
host.
See the Console prerequisites topic for the list of supported browsers.
See AppSync User and Administration Guide and the latest AppSync Support
Matrix .
Obtain server installation executable from support.dell.com.
https://
To add any of the following storage arrays, go to Settings > Infrastructure
Resources > ADD SYSTEMS Dell Storage Center VMAX3 /PowerMax RecoverPoint Unity
PowerStore VNX Metro node| VPLEX XtremIO PowerFlex
If mounting copies to a virtual machine, go to Settings > Infrastructure
Resources, click the VCENTER SERVERS tab, then click ADD SERVER.
If mounting copies to a kubernetes cluster, go to Settings > Infrastructure
Resources, click the Kubernetes Cluster tab, then click ADD CLUSTER.
IPv6 address is not supported for any array management server or storage
processor.
Settings > Infrastructure Resources, click the SERVERS / CLUSTERS tab, then
click ADD APPLICATION HOST. When security prevents pushinstall, manually
install by running AppSync-Host-Plugin-4.5-win-x64.exe on the host.
NOTE: This is only applicable for Windows. You cannot register hosts with IPv6
IP address.
From the AppSync console, discover application objects on the respective servers.
Copy Management > Select View > Copies > Select Application > Microsoft Exchange / Microsoft SQL Server / Oracle / VMware Datacenters / File Systems / SAP HANA / Kubernetes Cluster.
Prerequisites
11
Table 5. Deployment checklist (continued)
Basic step
Details
Notes
From the AppSync console, subscribe application objects to a service plan to begin data protection.
Go to Copy Management > Select View > Copies > Select Application > Microsoft
Exchange / Microsoft SQL Server / Oracle / VMware Datacenters / File Systems /
SAP HANA / Kubernetes Cluster to display the list of available applications.
Select the application instance that you want to protect, and then select
Create Copy with Plan to launch the wizard.
Configure the steps in the wizard. The Data Protection option is selected by
default.
Protect immediately with Subscribe to Service Plan and Run, which subscribes
the application object to a service plan and runs the protection immediately
for the selected object only.
Select Subscribe to Service Plan, which subscribes the application object to a
service plan, with option to override schedule, but does not run the plan.
Protection occurs according to the service plan’s schedule.
From the AppSync console, you can create copies of your database and file systems for application testing and validation, test and development, reporting, data masking, and data analytics. Use the Repurpose wizard to schedule or immediately create first or second generation copies, as required. AppSync supports repurposing on File systems, SQL Server, SAP HANA systems, Oracle databases and Kubernetes namespaces.
Go to Copy Management > Select View > Copies > Select Application > Microsoft
SQL Server / Oracle / File Systems / SAP HANA / Kubernetes Cluster to display
the list of available applications.
Select the application instance that you want to protect, and then select
Create Copy with Plan to launch the wizard.
Select Data Repurposing and follow the steps in the wizard.
Select Run now ,Schedule, or Run Only Once At later time. Complete details
appear in the online help and user guide.
From the AppSync console, you can configure AppSync to communicate with Dell SupportAssist and provide system configuration information to Dell Technologies.
Settings > Dell SupportAssist > CONNECT NOW to register.
Done?
12
Prerequisites
2
Installation
This chapter includes information on how to install your AppSync software. For
information on how to install arrays, see the chapter Configuration and
Resource Management. Topics in this chapter include:
Topics:
· Installing AppSync · Upgrading AppSync · Uninstalling AppSync · Deploying
AppSync in VMware HA
Installing AppSync
To install AppSync, you must perform the following operations: Installing the
AppSync server. Adding servers to AppSync. Installing the host plug-in
manually. If you want to upgrade an existing AppSync installation to the
current full version see Upgrade your AppSync installation.
Installing the AppSync server
The first step in the AppSync installation process is to install the AppSync
server.
Prerequisites Obtain the installation executable from the AppSync distribution
or from the AppSync download page on the Dell Support website.
Steps 1. Run the executable installation file.
NOTE: On Windows Server 2022 set the following system variable in the
environment : JAVA_TOOLOPTIONS=”Dos.name=Windows Server 2019″.
2. Accept the license agreement, and click Next. 3. On the Choose Install
folder screen, specify the location where you want to install AppSync.
The default location is C:EMCAppSync. NOTE: Users must ensure that the install
directory is empty, before performing a fresh installation of the AppSync
server. The install location cannot contain space. If you change the default
location, click Restore Default Folder to restore the default location.
4. On the AppSync Administrator screen, enter a user name and password for
the default administrator account. NOTE: The password for the default
administrator account must be a minimum of eight characters and maximum of 40
characters in length, must be mixed case, and it must contain at least one
number and one special character from the following list: ! , @ # $ % * ? ~
5. On the AppSync Ports screen, modify the default https, and Keycloak, port
details, as required.
Installation
13
6. Click Next. The Pre-installation Summary page appears.
7. Review the installation summary, and click Install. After installation is
complete, you can view the installation log. The installation log for the
AppSync server, is located at directory $USER_INSTALL_DIRECTORY$/_Dell EMC
AppSync_installation/Logs with the name
Dell_EMC_AppSync_Install_current_timestamp. For example,
Dell_EMC_AppSync_Install_06_11_2020_07_16_22. NOTE: From 4.2 release and
above, all the install logs are available in the
Dell_EMC_AppSync_Install_current_timestamp file and different types of logs
are being demarcated as Install, ==STDERR ENTRIES==, and STDOUT ENTRIES.
8. Click Done. The AppSync Login screen appears.
9. Log in to the AppSync Server. You can navigate to Settings >
Infrastructure Resources to begin configuring Storage Systems and Servers.
NOTE: If AppSync installation completes with error and a status message:
DellEseService not configured successfully, you must run below command in
command prompt to manually install and configure DellEseService.
%AppSync_INSTALL_DIR% tempEmbeddedServiceEnabler.exe /s /v”/qn
INSTALLDIR=%AppSync_INSTALL_DIR%ese”. For example,
C:EMCAppSynctempEmbeddedServiceEnabler.exe /s /v”/qn INSTALLDIR=C:
EMCAppSyncese”.
Adding hosts to AppSync
Learn how to add your servers to your AppSync configuration.
Add a Windows host to AppSync
This section describes the procedure to add a Windows server to AppSync and
install the host plug-in.
Prerequisites Review this information before you begin. When you add a server,
AppSync registers the server in its database and discovers the supported
applications on that server. If the host plug-in software is not already
present, AppSync attempts to install it. If the host plug-in software is
present, AppSync attempts to register it. An error occurs if the host plug-in
software is already registered to another AppSync server. The servers must be
accessible over IP to the AppSync server. The AppSync server must be
accessible to the application server by hostname. You must supply credentials
for an account that has local administrator privileges on the server. For
Windows servers: If the server is not part of a domain, disable the following
user access control: User Access
Control: Run all administrators in Admin Approval Mode . On Windows, AppSync
can push install the host plugin software. On Windows, you have the option to
manually install the
software on the application servers. For Windows Servers: If the Windows
Server is used for mounting a copy, automount must be disabled. To manually
disable
automount run diskpart at a command prompt then enter automount disable at the
DISKPART> prompt. Register the Virtual Center managing the application server
VM. Adding a VMware vCenter Server provides more
information about adding a VMware vCenter Server to AppSync. This operation
requires the Resource Administrator role in AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
Servers / Clusters. 2. Click Add Application Host. 3. Select Microsoft Windows
in the Operating System Field. 4. Review the following host-plug-in
installation settings:
14
Installation
a. Install Plug-in version:4.5 b. Port:10004. This is the default port. c.
Location: C:Program FilesEMCAppSync Host Plug-inlogs. 5. Click Add Host. 6.
For each server, enter the Server name or IP address, domainusername, and
password.
NOTE: Optionally, if you are adding multiple servers, and prefer to use the
same domainusername and password for each server, select the Use the
credentials of the first hosts for subsequent hosts option for before you add
a new host.
7. Click Deploy. 8. Click Close to exit the Add Application Host page.
Installing the host plug-in manually – Windows servers only
Install the host plug-in manually when a firewall or other security measure
prevents push installation from the server to the application host.
Prerequisites Obtain the AppSync host plug-in installation executable from the
AppSync distribution or from the AppSync support page at support.dell.com
Steps 1. Run the plug-in executable installation file. 2. Follow the
instructions on the wizard to complete the host plug-in installation.
NOTE: If you have used a non-default port setting, keep a record of it. You
must specify it when you add the host in AppSync.
Next steps Manually installed hosts must also be added to AppSync. Use the
AppSync console, under Settings > Infrastructure Resources, click the SERVERS
/ CLUSTERS tab then click ADD APPLICATION HOST.
UNIX host plugin push install with SUDO user
This section describes the prerequisites for adding a UNIX agent host with
SUDO user privileges to the AppSync server. This is useful in secure
environments where you do not want AppSync to use root user privileges.
AIX deployment requirements
OpenSSH and OpenSSL packages. OpenSSL is a pre-requisite for OpenSSH
installation. The following packages are mandatory for AppSync to work with
AIX hosts.
BZip2 package. Zlib package is a prerequisite for Bzip2 installation. SUDO
package (only if you want the SUDO feature), or OpenSSH and OpenSSL. Zlib is a
pre-requisite for enabling the
SUDO feature. Supported Oracle database software that is installed on mount
hosts for database recovery. Supported Oracle database that is created on
production hosts. Valid Oracle database configurations as described previously
in this section. Package locations: OpenSSH and OpenSSL packages are on the
operating system CD. Bzip2, Zlib, and SUDO are on the IBM AIX Toolbox website.
To perform a push install of the AppSync host plugin on an AIX host from the
AppSync server: 1. Install the SUDO RPM package.
Installation
15
2. Install zlib, if it is not already installed. 3. Install OpenSSH. 4. Run
SFTP server as root. 5. Create a user {user}, or group {group}on the AIX host
where you plan to run the AppSync host plug-in. . 6. Grant the {user} or
{group} read, write, and run permissions to the install location directory
(and to all its subdirectories
recursively) that you select in Add Application Host of the AppSync UI. 7.
Edit the sudoers file using visudo. (You must edit this file as root.) 8. Add
the following three lines at the end of the file for {user}:
Defaults:{user} !requiretty Defaults:{user} !env_reset {user} ALL = (root)
NOPASSWD: /{install location}/appsync/acp
Where {user} is the username you created, {install location} is the location
where you want to install AppSync host plug-in. For example, if the {user}
created is appsync and the {install location} is /opt/emc, and you want to
apply it to ALL the agent hosts, the entry looks like the following:
Defaults:appsync !requiretty Defaults:appsync !env_reset appsync ALL = (root)
NOPASSWD: /opt/emc/appsync/acp
If you want to restrict to one agent host such as lrmp333.org.com, change the
last line to the following:
appsync lrmp333.org.com = (root) NOPASSWD: /opt/emc/appsync/acp
For {group}, you must add the following three lines at the end of the file:
Defaults:%{group} !requiretty Defaults:%{group} !env_reset %{group} ALL =
(root) NOPASSWD: /{install location}/appsync/acp
Where {group} is the group you created, {install location} is the location
where you want to install AppSync host plug-in. For example, if the {group}
created is appsyncgroup and the {install location} is /opt/emc, and you want
to apply it to ALL the agent hosts, the entry looks like the following:
Defaults:%appsyncgroup !requiretty Defaults:%appsyncgroup !env_reset
%appsyncgroup ALL = (root) NOPASSWD: /opt/emc/appsync/acp
If you want to restrict to one agent host such as lrmp333.org.com, change the
last line to the following:
%appsyncgroup lrmp333.org.com = (root) NOPASSWD: /opt/emc/appsync/acp
Ensure that the secure_path variable is set to default. This is required for
AppSync to run some basic commands which reside in these directories. Defaults
secure_path = /sbin:/bin:/usr/sbin:/usr/bin
NOTE: If you want to add a user to the group created above, follow the below
two steps:
a. Create a user {user} on the Linux host where you plan to run the AppSync
host plug-in. For example, useradd -m appsync b. Add the user to {group}. For
example, usermod -G appsyncgroup appsync 9. Start SFTP server service for the
created SUDO user. For example, SSH as SUDO user and run the sftp-server&
command. 10. Provide the username and password of the created SUDO {user} in
the Add Application Host dialog of the AppSync console. Ensure that you
specify the {install location} used above for Location Settings, and click
Deploy to proceed.
16
Installation
Linux deployment requirements
For the latest support versions, see the AppSync Support Matrix.
Linux deployment requirements include:
Red Hat Linux BZip2 and net-tools package. Oracle® Linux. CentOS. SuSE Linux.
Compatible Linux sg3_utils package. Supported Linux host with root SSH enabled
or another operating system user with SUDO feature enabled. Supported Oracle
database software that is installed on mount hosts for database recovery.
Supported Oracle database that is created on production hosts. Supported
scale-up and scale-out SAP HANA System. A valid Oracle database configuration.
To perform a push install of the AppSync host plugin to a LINUX host from the
AppSync server:
1. Create a user {user} or group {group} on the Linux host where you plan to
run the AppSync host plug-in. 2. Grant the {user} or {group} read, write, and
run permissions to the install location directory (and to all its
subdirectories
recursively) that you select in Add Application Host of the AppSync UI. 3.
Edit the sudoers file using visudo. (You must edit this file as root.) 4. Add
the following three lines at the end of the file for {user}:
Defaults:{user} !requiretty Defaults:{user} !env_reset {user} ALL = (root)
NOPASSWD: /{install location}/appsync/acp
Where {user} is the username you created, {install location} is the location
where you want to install AppSync host plug-in.
For example, if the {user} created is appsync and the {install location} is
/opt/emc, and you want to apply it to ALL the agent hosts, the entry looks
like the following:
Defaults:appsync !requiretty Defaults:appsync !env_reset appsync ALL = (root)
NOPASSWD: /opt/emc/appsync/acp
If you want to restrict to one agent host such as lrmp333.org.com, change the
last line to the following:
appsync lrmp333.org.com = (root) NOPASSWD: /opt/emc/appsync/acp
For {group}, you must add the following three lines at the end of the file:
Defaults:%{group} !requiretty Defaults:%{group} !env_reset %{group} ALL =
(root) NOPASSWD: /{install location}/appsync/acp
Where {group} is the group you created, {install location} is the location
where you want to install AppSync host plug-in.
For example, if the {group} created is appsyncgroup and the {install location}
is /opt/emc, and you want to apply it to ALL the agent hosts, the entry looks
like the following:
Defaults:%appsyncgroup !requiretty Defaults:%appsyncgroup !env_reset
%appsyncgroup ALL = (root) NOPASSWD: /opt/emc/appsync/acp
If you want to restrict to one agent host such as lrmp333.org.com, change the
last line to the following:
%appsyncgroup lrmp333.org.com = (root) NOPASSWD: /opt/emc/appsync/acp
Ensure that the secure_path variable is set to default. This is required for
AppSync to run some basic commands which reside in these directories.
Installation
17
Defaults secure_path = /sbin:/bin:/usr/sbin:/usr/bin
NOTE: If you want to add a user to the group created above, follow the below
two steps:
a. Create a user {user} on the Linux host where you plan to run the AppSync
host plug-in. For example, useradd -m appsync b. Add the user to {group}. For
example, usermod -G appsyncgroup appsync 5. Provide the username and password
of the created SUDO {user} in the Add Application Host dialog of the AppSync
console. Ensure that you specify the {install location} used above for
Location Settings, and click Deploy to proceed.
Add a UNIX server to AppSync
This section describes the procedure to add a UNIX server to AppSync and
install the host plug-in.
Prerequisites Review this information before you begin. When you add a server,
AppSync registers the server in its database and discovers the supported
applications on that server. The servers must be accessible over IP to the
AppSync server. The AppSync server must be accessible to the application
server by hostname. You need to supply credentials for an account that has
root/sudo privileges on the server. On AIX/Linux, AppSync can push install the
host plugin software. This operation requires the Resource Administrator role
in AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
Servers / Clusters. 2. Click Add Application Host. 3. Select Unix in the
Operating System Field. 4. Review the following host-plug-in installation
settings:
a. Install Plug-in version:4.5 b. Port:22. This is the default port. c.
Location:/opt/emc/appsync.
By default, AppSync extracts the host plug-in to a folder named appsync in
this location. The same rule applies even if you change the install location.
For example, if the location is /opt/emc/user1/agent, the AppSync agent host
plug-in will be under /opt/emc/user1/agent/appsync. These values apply to each
server that you are adding. Available plug-in versions depend on what is
available on the AppSync server.
5. Click Add Host. NOTE: If you are adding the Linux or AIX host using sudo
user, AppSync will perform a pre-deployment check that validates the
following:
Ensures that the install location exists. Verifies if you have read, write,
and execute permission on the install location. Ensures Bzip2 package exists.
Ensures sudoers file is configured correctly. Pre-deployment check on a host
can be skipped by creating an environment variable named IGNORE_HOST_PRECHECK,
and setting the value to “True”. When you create the environment variable, it
must be available through the default shell in non-interactive user mode. For
example, for bash shell, you can configure it in .bashrc or in
/etc/environment.
6. For each server, enter the Server name or IP address, domainusername, and
password. NOTE: Optionally, if you are adding multiple servers, and prefer to
use the same domainusername and password for each server, select the Use the
credentials of the first hosts for subsequent hosts option for before you add
a new host.
7. Click Deploy. 8. Click Close to exit the Add Application Host page.
18
Installation
Configuring UNIX agent parameters
You can configure a temporary location and a command execution timeout value
for each UNIX host from the Settings > Infrastructure Resources > SERVERS /
CLUSTERS page of the AppSync console.
To configure UNIX agent parameters:
1. On the AppSync console, go to Settings > Infrastructure Resources >
SERVERS / CLUSTERS . 2. Click the name of any Unix host. 3. In the right pane,
click the Properties tab. 4. Click EDIT.
The Edit Host Properties page opens.
5. Under the Connectivity section, you can edit values for the following
fields: Port
6. Under the Logging section, you can edit values for the following fields
Log Directory Maximum Directory Size Number of days to retain log files
Logging Level Temporary Location Command Execution Time Out
7. Click APPLY.
Temporary location for UNIX hosts
You can configure a temporary location for each UNIX host from the Settings >
Infrastructure Resources > SERVERS / CLUSTERS page. AppSync uses this location
during Oracle mount operations to store information that was previously
located in /tmp/
Command execution timeout
It is the maximum time given by the server to the agent, to run an operation.
An agent operation is composed of one or more sub-operations.
Following are some of the sub-operations:
Operating system command execution Oracle/SAP HANA SQL query execution
Oracle/SAP HANA SQL command execution Oracle RMAN operation SAP HANA Recovery
Operations
A sub-operation gets a timeout which is a portion of the overall operation
timeout. For example, if the Command Execution Timeout is 3 hours or 180
minutes, SQL query sub-operation timeout is one third of it, meaning 1 hour.
Following is an example for command execution timeout and the respective agent
timeouts.
Timeout Categories
SFTP OS Commands Oracle SQL Query Oracle RMAN Oracle SQL command SAP HANA SQL
Query
Weightage
1 1/2 1/3 2/3 1/6 1/6
Command Execution Time (in minutes)
180
Time (in minutes)
180 90 60 120 30 30
Installation
19
Timeout Categories
Weightage
SAP HANA SQL Command
1/5
SAP HANA Utils Execution
1/4
SAP HANA Recovery
1/6
Command Execution Time (in minutes)
Time (in minutes)
35 45 30
Rediscovering the AppSync agent host
Rediscovering an AppSync agent host updates the agent host information on the
AppSync Server. For example, if you add a new supported application to the
application server, you can use the Rediscover feature to refresh the AppSync
server with the new associated application information.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. Select Settings > Infrastructure Resources. 2. Click the SERVERS /
CLUSTERS tab. 3. Select the server you want to refresh. 4. Select REDISCOVER.
Overview of reset SSH keys for UNIX hosts
AppSync now provides rotation of public and private keys, that are used for
setting up an SSH connection with Unix agents.
Prerequisites This operation requires the Resource Administrator role in
AppSync. This can be run for Linux/AIX Host agents, and you need to maintain a
proper connectivity between AppSync and the agent.
About this task Follow the below steps to reset SSH keys for a Unix host in
AppSync (Linux/AIX host plug-in).
Steps 1. On the AppSync console, select Settings > Infrastructure Resources..
2. Click SERVERS/CLUSTERS tab. 3. Select the server you want to reset, and
click MORE > Reset SSH Keys.
NOTE: Host property displays the “SSH Key Generated Time”.
Upgrading AppSync
Describes on how to upgrade AppSync. To upgrade AppSync, you must perform the
following operations: Upgrade the AppSync server Upgrade the AppSync agent
plugin
20
Installation
Upgrading the AppSync server
Describes the prerequisites, and the steps for upgrade.
Prerequisites Disable all service plans and ensure that there is no current
activity on the AppSync server. On the AppSync console, go to Help > About
Dell AppSync and note your complete AppSync version. Also, note any hand-edit
procedures to configuration files that Customer Support requested you to
perform for your
AppSync server installation. For information about adding back these edits,
see the section, Moving AppSync server back to the previous version after an
upgrade. Go to your EMCAppsyncJbossdatastoredata and click Properties to view
the size of this directory. During upgrade, AppSync runs a backup of the
server that requires 40% of the size of this directory, so plan a backup save
location with the required amount of free space. Verify if the version that
you have installed supports an upgrade. The AppSync Release Notes provides
more information about the upgrade paths and any known issues and limitations.
About this task You do not have to uninstall the previous version of AppSync
before installing a new version.
NOTE: Before you upgrade, see the prerequisites that are required for the
server in the previous chapter.
AppSync runs a backup (and restore) of the existing server before you upgrade.
This process is documented in the configuration section of this document. This
might take some time if EMCAppsyncJbossdatastoredata size is huge. To upgrade
the AppSync server:
Steps 1. Obtain the installation executable file from the AppSync distribution
or from the AppSync page on the Dell Support website. 2. Run the executable
installation file. 3. Follow the instructions on the wizard to upgrade the
server. Ensure that you have 4 GB more disk space than what is
displayed on installation wizard, as space is even required to temporarily
extract contents within the installer. NOTE: During the upgrade, if one or
more AppSync services namely AppSync Datastore service, AppSync Security
server, AppSync Server service, and AppSync Watchdog Service are in a corrupt
state, the preinstallation does not proceed, and an error message appears.
Click Ok to cancel the installation. Check the installation logs and retry
installation after rectifying the services or contact Customer Support for
assistance.
After the precheck, if any of the AppSync services get corrupted, the
postinstallation does not proceed further and an error message appears. Click
Ok, to continue the installation. However, the services remain down. Check the
installation logs and retry installation after rectifying the services or
contact Customer Support for assistance.
NOTE:
In AppSync 4.5 version default values for the following parameters are
upgraded as below.
application-service.conf APPSYNC_INSTALL_LOCATIONjbossexecutiveapplication-
service.conf
wrapper.java.additional.2=-Xms2048m (prior to 4.5 default value 1024m)
wrapper.java.additional.3=-Xmx6144m (prior to 4.5 default value 2048m)
After upgrade/repair to AppSync server 4.5, AppSync will retain or change the
below mentioned configuration parameters:
a. If values to below parameters are modified before upgrade or repair:
If values to below parameters are modified before upgrade or repair, then same
values configured before upgrade or repair will be retained post successful
upgrade/repair.
standalone.xml
APPSYNC_INSTALL_LOCATIONjbossstandaloneconfigurationstandalone.xml
Installation
21
application-service.conf
APPSYNC_INSTALL_LOCATIONjbossexecutiveapplicationservice.conf
wrapper.java.additional.2=-Xms2048m wrapper.java.additional.3=-Xmx6144m
b. If values to below parameters are not modified or were set to default
values before upgrade: If values to below parameters were not modified then
below mentioned parameters will be set to AppSync 4.5 default values post
successful upgrade/repair. standalone.xml
APPSYNC_INSTALL_LOCATIONjbossstandaloneconfigurationstandalone.xml
22
Installation
Removing a server from AppSync
The Remove Servers Only operation deletes the server’s entry in the AppSync
database.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
About this task You cannot remove a server if its databases are subscribed to
service plans, if it has copies or has copied mounted.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources.
2. Click the SERVERS / CLUSTERS tab. 3. Select the server you want to remove
and click Remove. 4. Select one of the following options:
Deinstall plug-in and remove server – Deinstalls the plug-in from the server
and removes the server from AppSync. Specify the values for the DomainUsername
and Password fields.
Remove server forcefully – The option forcefully deletes the server’s entry in
the AppSync database. AppSync will not check for any copy dependency on the
server. This operation deletes all internal meta data related to this server.
You must manually perform all cleanup tasks like unmounting copies from the
server. NOTE: Forcefully removing a host from AppSync only removes copies from
AppSync. You must manually unmount the mounted copies from the mount host,
delete copies from the arrays, and uninstall the plug-in from the host. If you
forcefully remove a mounted host from AppSync, ensure that you manually clean
up the mount host, related ESX (if any), and storage array before reusing the
copy again.
Remove server only – Removes the selected server(s) from AppSync. User shoud
deinstall the plug-in manually. 5. Click Remove Host.
Next steps If the server you removed is one of the members of a DAG, you must
rediscover databases in AppSync.
Uninstalling the AppSync agent plug-in
The Deinstall plug-in and remove operation uninstalls the plug-in software
from the selected servers and then removes the server’s entry in the AppSync
database.
Prerequisites This operation requires the Resource Administrator role in
AppSync. If the server is not part of a domain, the following user access
control must be disabled: “User Access Control: Run all administrators in
Admin Approval Mode”.
Steps 1. Select Settings > Servers. 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
password will be applied to all selections. 4. For each server you wish to
deinstall the plug-in, select Set Username and Password. 5. Specify
credentials of an account with local administrator privileges on the servers
and click OK. 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 there are failures, they display with a red icon.
Installation
23
7. If some of the servers fail deinstallation, you can retry. Select Clear
Successful and then select Start again.
Uninstall the AppSync server
Uninstall the AppSync server by running the native Windows uninstall utility.
Prerequisites Be sure you are logged in as a user with Windows Administrator
privileges. Remove hosts in Settings > Infrastructure Resources > SERVERS /
CLUSTERS before uninstalling the server. This operation requires the Resource
Administrator role in AppSync.
Steps 1. Run the native Windows uninstall utility. 2. Follow the wizard steps.
Files and folders added after installation are not removed.
Moving AppSync server back to the previous version after an upgrade
This procedure shows you how to roll back to a previously installed version of
the AppSync server.
Prerequisites Dell recommends that you contact Customer Support to resolve
issues with the newer, enhanced version of AppSync you are currently running
before trying to roll back to an earlier version.
About this task You need your previous and current AppSync versions that you
collected when you installed the current version of AppSync. Refer to
Upgrading the server.
Steps 1. Disable all Service Plans and make sure there is no current activity
on the AppSync server. 2. Uninstall the AppSync server application from the
host.
After the uninstall completes, the /EMC/AppSync folder should not be present
on the machine. 3. Re-install the version of AppSync server that was on the
host prior to upgrade that you noted during the server upgrade
procedure (Upgrading the server). Make sure you apply the exact version of
AppSync that includes the exact cumulative hotfix number, if a hotfix was
previously installed. 4. Re-apply any hand-edit procedures to configuration
files that a readme or Dell Customer Support Representative requested that you
implement for your previous AppSync server installation. 5. Restore the
automated backup, refer to: Automated backup restore. 6. Re-apply your AppSync
licenses from the AppSync application.
Deploying AppSync in VMware HA
VMware provides two solutions that provide access to your virtual machines at
nearly 100% uptime. High Availability (HA) that can automatically migrate and
restart VMs on a secondary ESXi server if any failures occurred on the primary
one. Although being fully automatic, VMware HA cannot completely meet the
needs of business critical operations that require 100% uptime. Fault
Tolerance (FT) is the solution that keeps a shadow up to date copy of the
original VM on the second ESXi server, that can fully eliminate service
downtime during the switch between the original and secondary VMs.
Prerequisites AppSync server must be installed in VMware virtual machine and
ESXi hosts must be in cluster. HA cluster must have at least two ESXi hosts.
24
Installation
The configuration for each host must have Hardware Virtualization (HV) enabled
in the BIOS. All hosts in a HA cluster must be licensed for vSphere HA and
Fault Tolerance. All hosts should have access to the AppSync installed VM
networks and datastores. All hosts in the HA cluster must have static IP
addresses or keep the same dynamic IP address after reboots. AppSync installed
Virtual machine files (except for the VMDK files) must be stored on shared
storage.
About this task
NOTE: To ensure redundancy and maximum Fault Tolerance protection, you must
have a minimum of three hosts in the cluster. In a failover situation, it
provides a host that can accommodate the new secondary VM that is created. See
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc
/GUID-4A626993A829-495C-9659-F64BA8B560BD.html for details.
Steps
1. To create HA protected VMware cluster, open vSphere Web Client or vSphere
Client, and go to the data center where you want to create the cluster. Click
New Cluster.
2. Enter Cluster name and select Turn On vSphere HA check box, to enable HA
before adding ESXi hosts to the cluster. Select Turn On vSphere DRS. NOTE: If
you enable HA before ESXi hosts are added to the cluster, the cluster is not
fully functional until the hosts join. Also, you can decide if you want to
enable vSphere DRS that is compatible with vSphere HA. Distributed Resource
Scheduler is the one responsible for automated load balancing.
3. To add ESXi host to cluster, go to the cluster you created in the vSphere
Web Client, and select Add Host. You must provide hostname, username, and
password for the hosts. NOTE: For each host added to a vSphere HA cluster, an
HA agent is installed to communicate with other agents in the cluster. Every
host in the cluster serves either as an active host or a passive host. You can
verify this in the Host Summary page. See https://docs.vmware.com/en/VMware-
vSphere/7.0/com.vmware.vsphere.avail.doc/ GUID-5432CA24-14F1-44E3-87FB-
61D937831CF6.html for details.
4. After a HA protected cluster is successfully created, you can protect
business critical VMs with vSphere Fault Tolerance. To set up Fault Tolerance
for an AppSync Server installed Virtual Machine, go to that specific VM, right
click, select Fault Tolerance > Turn on Fault Tolerance. Click Yes. Once FT is
successfully enabled for the AppSync Server installed VM, the status becomes
green and FT information for the host is available in the Summary tab. NOTE:
See https://docs.vmware.com/en/VMware-
vSphere/7.0/com.vmware.vsphere.avail.doc/ GUID-7525F8DD-
9B8F-4089-B020-BAA4AC6509D2.html for details.
Installation
25
Licensing
This chapter discusses the following:
Topics:
· Licensing in AppSync
Licensing in AppSync
AppSync provides a 90-day trial license for all supported arrays. AppSync has
the following two license file type supported: XML License FLX License
NOTE: From 4.2 release onwards, AppSync supports XML based licenses.
Each of these license file types consists of the following license categories,
available for AppSync: Starter Pack (AppSync Basic) license – Allows you to
use unlimited amount of storage on a specific array with some
restrictions on the features supported by AppSync. With the Starter Pack
license, you can add only one storage array per AppSync server. Also, you can
mount only 20 application copies. It can be a snapshot of Oracle, Microsoft
SQL, Microsoft Exchange, File systems, SAP HANA, VMware datastores, or
Kubernetes clusters. For example, if you have 20 volumes in one database, and
that database is part of a service plan that mounts, it constitutes one of the
20. It is not based on the number of volumes. On the contrary, if there are 20
databases on one volume and those copies are mounted, then its considered as
20 copies.
NOTE: If you add additional arrays or mount additional copies, the license is
marked as non-compliant, and alerts are sent to
the configured recipient address specified under Resource Notifications in
AppSync > Alerts > Email Notifications page. If a permanent license for one
array is added with starter pack license for another array, both the licenses
are marked as non-compliant. After the starter pack license is upgraded to a
permanent license, you must reapply the permanent license for the second
array, or wait for the license validation thread to run to clear the non
compliance status for the second array. RecoverPoint, metro node | VPLEX, and
remote copies are not supported. Full license (Advanced License) – Is an
array-based license. NOTE: For Kubernetes Clusters, RecoverPoint and metro
node | VPLEX, no separate license is required. The back-end array licenses are
checked in the case of Kubernetes Clusters | metro node | VPLEX and
RecoverPoint. In case of Kubernetes Clusters, CSI configured back-end array
licenses are checked. You must ensure that the appropriate license files are
installed for replication to proceed. Each XML license can have multiple types
of licenses. For example, one XML license can have a Starter pack license with
priority 3, and Full license with priority 1. In this case, license is used
based on its priority level.
26
Licensing
Obtaining a license online
You can access the license management page through the AppSync console.
Prerequisites This operation requires the Resource Administrator role in
AppSync. You need the License Authorization Code (LAC) that was emailed from
Dell Technologies.
Steps 1. Select Settings > License. 2. Click OBTAIN LICENSE ONLINE.
This brings you to the Manage Licenses page on the Dell Technologies support
site. 3. Enter the required information to acquire and save the license file.
In the License management web page, you are prompted to enter a Machine name
as part of the process. Dell Technologies recommends that you enter AppSync-
arrayserialnumber where arrayserialnumber is the serial number of the array.
Next steps Once you have obtained the license file, you need to upload and
install it to the AppSync server.
Upload and install a license file
You must upload the license file to AppSync.
Prerequisites This operation requires the Resource Administrator role in
AppSync. Obtain the license file –The license file must have a filename
extension of .lic and must reside in a browsable location.
Steps 1. Select Settings > License. 2. Click UPLOAD. 3. In the Upload License
File dialog, click SELECT to browse to the license file and select it. 4.
Click OK.
Licensing
27
Configuration and resource management
This chapter includes the following topics:
Topics:
· Resource management · Backup and restore AppSync using the Backup Assistant
tool · Migrating the AppSync server
Resource management
Describes how to manage the resources. Use Settings > Infrastructure Resources
SERVERS / CLUSTERS to manage hosts. Use Settings > Infrastructure Resources STORAGE SYSTEMS to manage storage systems and RecoverPoint sites. Use Settings > Infrastructure Resources > VCENTER SERVERS to manage vCenter Servers. Use Settings > Infrastructure Resources > KUBERNETES CLUSTER to manage Kubernetes clusters.
Configure RecoverPoint storage
Perform this procedure to add a RecoverPoint site to offer Local protection, Remote replication, and Local and Remote replication protection that is provided by Bronze, Silver, and Gold service plans.
Prerequisites This operation requires the Resource Administrator role in AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2. Click ADD SYSTEMS. 3. In the Select System Type page, select RecoverPoint> Next 4. Type credentials for the array in the following fields:
a. Name – Type the site management IP address or hostname for the RecoverPoint site, or RPA cluster name. In a Local and Remote replication configuration, you must add one site, then the others are discovered automatically.
b. Username – Type an existing username for an account that has a RecoverPoint Admin role to access the site. c. Password- Type the password for the account that has a RecoverPoint Admin role to access the site. 5. Click Next. 6. Review the configurations in the Summary page, and click FINISH.
Next steps If you upgrade a SOAP enabled RecoverPoint version earlier than 4.1.1 to the same or a later REST enabled version, you must add RecoverPoint to AppSync again.
28
Configuration and resource management
Updating the RecoverPoint site management IP address
Update AppSync when a RecoverPoint site’s management IP address changes.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2.
Select the RecoverPoint site and expand the right pane to view details. 3.
Click the EDIT button in Properties to open Edit Management Interface. 4. In
the IP Address field, enter the new site management IP address for the
RecoverPoint site and click Apply.
Rediscovering a RecoverPoint site
The Rediscover operation initiates a discovery of site information. For
example, the Rediscover operation may find additional RPAs or changes in site
name (if invalid login credentials impede connectivity).
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2.
Select a RecoverPoint site or sites. 3. Select REDISCOVER.
Removing a RecoverPoint site
You can remove a configured RecoverPoint site from Appsync using this
procedure.
Prerequisites This operation requires the Resource Administrator role in
AppSync. Removal fails if sites are in use.
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2.
Select a RecoverPoint site or sites. 3. Select REMOVE.
Setting the credentials for a RecoverPoint appliance
Specify RecoverPoint appliance credentials when adding the RPA to AppSync and
when the credentials change on the RPA itself.
Prerequisites Ensure you obtain the credentials for the RecoverPoint
appliance. The account that you specify must have the RecoverPoint Admin role.
About this task Initially, specify the credentials when you add the
RecoverPoint appliance to AppSync. To update the credentials in AppSync later,
follow these steps:
Configuration and resource management
29
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2.
Select the RecoverPoint site. 3. Select RESET CREDENTIALS. 4. Add the current
credentials for the appliance.
Viewing RecoverPoint sites
View RecoverPoint sites under the Settings tab.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2.
Select a RecoverPoint site or sites.
The right pane displays details for the RecoverPoint sites you selected.
Configure VMAX3 and PowerMax storage
Perform this procedure to add the VMAX3 and PowerMax arrays to AppSync.
Prerequisites
NOTE: The AppSync Support Matrix is the authoritative source of information on
supported software and platforms.
This operation requires the Resource Administrator role in AppSync. VMAX REST
API host managing the VMAX3/PowerMAX arrays must be registered. VMAX REST API
is available directly from your Unisphere for PowerMAX(U4P) installation. See
AppSync Support Matrix for details on the minimum version of U4P required.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
Storage Systems. 2. Click ADD SYSTEMS. 3. In the Select System Type page,
select PowerMAX/VMAX3> NEXT 4. Type details of Unisphere for PowerMax managing
the array(s) in the following fields:
a. Name/IP Address: Type the Name or IP Address. b. SSL Port: Type the port
number. c. Username: Type the U4P username. d. Password: Type the U4P
password. 5. Click NEXT. 6. Select the array you want to configure and click
NEXT, in the select VMAX3/POWERMAX Arrays page. 7. Click Select in the Storage
Group column to configure storage groups. 8. Select the Storage Groups you
want to include and click >. 9. Click OK. 10. Click Select in the Storage
resource pools column to configure resource pools. 11. Select the Storage
resource pools you want to include and click >. 12. Click OK. 13. Click NEXT
on the Groups and pools page. 14. Review the configurations in the Summary
page, and click FINISH.
NOTE: Multiple Unisphere for PowerMax can be registered for the same array in
AppSync. In case multiple U4P are registered for the same array, you can set
the preferred U4P. Follow the below steps:
30
Configuration and resource management
a. Click SET PREFERRED option at the bottom of the PROPERTIES tab. b. Select
VMAX3/ PowerMAX. c. Select the preferred U4P from the list of management
servers visible at the bottom of the PROPERTIES tab. d. Click SET PREFERRED.
Registerd U4P is not removed from AppSync if it is the preferred provider for
an array. This preferred provider option is available for PowerMAX, VMAX3,
metro node | VPLEX, and DellSC.
Use the VMAX Manage Copy Storage feature
After adding VMAX arrays, you can add or remove storage groups using Manage
Copy Storage in AppSync.
About this task
NOTE: You can perform this procedure only for VMAX3 systems.
Use Manage Copy Storage to assign, or edit a storage group for a specific VMAX
array.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
Storage Systems. 2. Click any VMAX3 system.
The PROPERTIES tab on the right pane refreshes. 3. Click MANAGE COPY STORAGE.
4. In the Manage copy storage page, to reconfigure the Storage Groups field,
click SELECT.
NOTE: Only storage groups which are not part of any masking view are listed
and available for selection. AppSync removes the devices from the storage
group at the time of mount and adds them to the storage group for the mount
host. The devices are added back to the storage group when the copy is
expired.
5. In the Select Storage groups page, select one or more storage groups and
click > to add them to the selected list. Alternatively, you can click >> to
add all available storage groups to the selected list.
6. Click OK. 7. In the Manage copy storage page, to reconfigure the Storage
resource pools field, click SELECT. 8. In the Select Storage resource pools
page, select one or more storage groups and click > to add them to the
selected list.
Alternatively, you can click >> to add all available storage groups to the
selected list. 9. Click OK. 10. Select Terminate clone session created by
Appsync to terminate AppSync created clone sessions on any device in a
VMAX storage group when unconfiguring storage groups. 11. Select Delete device
created by Appsync in pool to delete AppSync created devices in a pool when
unconfiguring storage
resource pools for a specific PowerMax array. 12. Click OK.
Results AppSync discovers the volumes in storage group for linking.
View VMAX target devices
You can provision the target devices in a storage group and/or configure
storage resource pools to create target devices for VMAX copies.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources.
Configuration and resource management
31
2. From the list of storage, select a VMAX array. The array details appear in
the Details pane on the right side of the page.
3. Expand the right pane to view all VMAX array details and the available
VMAX target devices. NOTE: AppSync tracks and manages all the target devices.
Dell Technologies does not recommend manipulating the target devices. It is
only for troubleshooting and must not be manipulated for normal use cases.
4. Click MANAGE DEVICES. 5. The Manage Devices page displays the following
details:
The USER PROVISIONED tab: Displays the devices provisioned by the user. The
APPSYNC PROVISIONED tab. Displays the devices provisioned by AppSync. 6.
Select the USER PROVISIONED tab. 7. Select a target device to perform one of
the following: a. Click Reset Device In-Use Flag to reset the in-use flag to
false, if AppSync does not have any valid copy associated
with the device. b. Click Remove Device in AppSync to remove the devices from
the AppSync inventory, and from the AppSync
configured storage group. 8. Select the APPSYNC PROVISIONED tab. 9. Select a
target device to perform one of the following:
a. Click Reset Device In-Use Flag to reset the in-use flag to false, if
AppSync does not have any valid copy associated with the device.
b. Click Remove Device in AppSync to remove the devices from the AppSync
inventory, and from the AppSync configured storage group.
c. Click Initiate Device Deletion In Array to remove the device from the
AppSync inventory and to delete the device from the array.
10. Select APPLICATION COPY INFO to fetch details of the copy associated with
the selected device such as service plan name, copy time stamp, and so on.
11. Click CLOSE.
Configure a Unity array
Perform this procedure to add a Unity array to AppSync.
Prerequisites Supply the credentials for an account that has the role of
Administrator or Storage Administrator.
NOTE: This operation requires the Resource Administrator role in AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
STORAGE SYSTEMS. 2. Click ADD SYSTEMS. 3. In the Select System Type page,
select Unity> Next 4. Type credentials for the array in the following fields:
a. Management Interface: Type the Name or IP Address of the Management
Interface. b. Global Username: Type the Admin username. c. Password: Type the
Admin password. 5. Click Next. 6. Review the configurations in the Discover
System Type page, and click Finish.
32
Configuration and resource management
Configure a PowerStore appliance
Perform this procedure to add a PowerStore appliance to AppSync.
Prerequisites Supply the credentials for an account that has the role of
Administrator or Storage Administrator.
NOTE: This operation requires the Resource Administrator role in AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
STORAGE SYSTEMS. 2. Click ADD SYSTEMS. 3. In the Select System Type page,
select PowerStore > Next 4. Type credentials for the appliance in the
following fields:
a. Management Interface: Type the fully qualified Name or IP Address of the
Management Interface. b. Username: Type the username. c. Password: Type the
password.
NOTE: To edit the IP address of the management server, use the Change option.
5. Click Next. 6. Select the PowerStore appliance that you want to add to
AppSync, and then click NEXT. 7. Review the configurations in the Summary
page, and click FINISH.
AppSync discovers and operates on the registered system. NOTE: A single
PowerStore management provider can manage a single or multiple appliances, and
AppSync supports both the configurations. AppSync discovers all the NAS
servers that are configured on PowerStore appliances. PowerStore array should
be rediscovered in AppSync whenever there is a configuration change on the NAS
server.
AppSync manages PowerStore appliances with the Management Interface using REST
APIs.
PowerStore volume import
AppSync treats imported volumes on PowerStore appliances like any other new
PowerStore volume.
PowerStore volume migration
When you migrate PowerStore Volumes or Volume Groups across the appliances
within a given cluster, the entire family structure (snapshots and clones) of
the Volume or Volume Group is migrated. When such migrations are performed on
the Array, you must rediscover the respective PowerStore appliance, to update
the migration information in AppSync persistence. If rediscover operation is
not performed, Mount and Restore operations on the affected snapshots or
clones may fail.
Configure an XtremIO array
To enable the XtremIO array to work with AppSync, add the array to the AppSync
configuration.
Prerequisites Supply the credentials for an account that has the role of
Administrator or Storage Administrator.
About this task With XtremIO 4.0 and later, one XtremIO Management Server
(XMS) can manage multiple XtremIO arrays.
Configuration and resource management
33
To add and configure an XtremIO array to work with AppSync, you need an
XtremIO Management Server (XMS) configured on a SAN with at least one XtremIO
array. Ensure XtremIO is zoned to Production and Mount hosts.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
STORAGE SYSTEMS. 2. Click ADD SYSTEMS. 3. In the Select System Type page,
select XtremIO> NEXT 4. Type credentials for the array in the following
fields:
a. Name / IP Address: Type the Name or IP Address of the Management Interface.
b. Username: Type the Admin username. c. Password: Type the Admin password. 5.
Click NEXT. 6. Select the XtremIO array that you want to add to AppSync, and
then click NEXT. 7. Review the configurations in the Summary page, and click
FINISH.
Results You can view the added the array on the AppSync Infrastructure
Resources page of the AppSync console.
Configure VNX storage
Perform this procedure to add the VNX array to AppSync.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
NOTE: If VNX contains VNX File as well as VNX Block, you must be a Global
user. The AppSync Support Matrix is the authoritative source of information on
supported software and platforms.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
STORAGE SYSTEMS. 2. Click Add Systems. 3. In the Select System Type page,
select VNX> Next
a. For a VNX block storage system, enter one or both of the following: the IP
address of service processor SPA or SPB. NOTE: If the IP does not resolve to a
name, create an entry in the Windows host file with a name. Refer to this
file: C:WindowsSystem32driversetchosts
b. If you want to manage file storage as well, type the IP address of the VNX
File Control Station. This is not mandatory if you are only managing block
storage.
4. Type credentials for the array in the following fields: a. SPA b. SPB c.
Control Station d. Global User Name e. Password
5. Click Next. 6. Review the configurations in the Summary page, and click
Finish.
34
Configuration and resource management
Updating the VNX, Unity, XtremIO, or PowerStore storage system
Update AppSync when VNX, Unity, XtremIO, or PowerStore is not configured or
when you want to add functionality (for example, add VNX block or VNX file).
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2.
Select the storage system that you want to configure. 3. In the right pane,
for VNX, edit the IP address fields for SPA, SPB, and Control Station IP. For
Unity, XtremIO, or
PowerStore, Change the Management Interface IP, then click Apply.
Resetting the credentials for VNX, Unity, or PowerStore storage system
When adding or configuring a storage system on AppSync, you specify
credentials. However, you can reset these credentials later.
Prerequisites This operation requires the Resource Administrator role in
AppSync. You must know the credentials for the storage system.
About this task Initially you specify credentials when adding the storage
system to AppSync. Follow steps in the Add Storage wizards. You can also
update the credentials in AppSync later using these steps.
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2.
Select the VNX, Unity, or PowerStore storage. 3. Select RESET CREDENTIALS. 4.
Enter the new credentials for the storage system and then select OK.
Configure a metro node | VPLEX cluster
To protect applications running on metro node | VPLEX storage, add the metro
node | VPLEX cluster(s) to the AppSync storage infrastructure.
Prerequisites This operation requires the Resource Administrator role in
AppSync. On a metro node | VPLEX, you can add either cluster’s management
server or both management servers. For management server redundancy, it is
recommended that you add both management servers. You must also configure the
backend array on which the metro node | VPLEX virtual volume resides in
AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
STORAGE SYSTEMS. 2. Click ADD SYSTEMS. 3. In the Select System Type page,
select Metro node | VPLEX> Next 4. Type credentials for the array in the
following fields:
a. Name/IP Address: Type the Name or IP Address. b. Username: Type the Admin
username.
Configuration and resource management
35
c. Password: Type the Admin password. 5. Click Next. 6. Review the
configurations in the Summary page, and click FINISH. 7. Metro node | VPLEX
only: To add the second management server, repeat steps 1 through 6.
The metro node | VPLEX cluster is added to AppSync and displays in the storage
list on the Storage Infrastructure page. Note that when you add one management
server in a metro node | VPLEX, AppSync automatically discovers both clusters
and displays them in the list. If you click on either cluster in the list, the
right pane will show the same IP address (the address of the management server
you added). However, when you add the second management server, if you click
on either cluster, the right pane will show both IP addresses in the Metro
node | VPLEX Management Servers section.
Resetting a Metro node | VPLEX cluster credentials
If the credentials for a Metro node | VPLEX cluster change, you can edit the
management server to reset the credentials.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
STORAGE SYSTEMS. 2. Select the Metro node | VPLEX cluster. For Metro node |
VPLEX systems, ensure that you are selecting the correct cluster.
Pay attention to the cluster name in the right pane below when you select a
cluster. 3. Select the management server to edit, and then click Edit in the
right pane. 4. In the Edit Management Server dialog, type the new credentials
in the appropriate field, and then click OK.
Setting a preferred Metro node | VPLEX management server
AppSync uses the preferred management server to communicate with Metro node |
VPLEX.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
About this task In the case of a Metro node | VPLEX, if you add both
management servers to AppSync, by default, the selected cluster’s management
server is shown as the preferred management server. To modify the preference:
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2. From
the list of storage, select the Metro node | VPLEX cluster.
The cluster details appear in the right pane. 3. In the right pane, select a
management server and then click SET PREFERRED.
The preferred management server is modified.
Configure a PowerFlex array
Perform this procedure to add a PowerFlex array to AppSync.
Prerequisites Supply the credentials for an account that has the role of
Administrator or Storage Administrator.
NOTE: This operation requires the Resource Administrator role in AppSync.
36
Configuration and resource management
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
STORAGE SYSTEMS. 2. Click ADD SYSTEMS. 3. In the Select System Type page,
select PowerFlex> Next 4. Type credentials for the array in the following
fields:
a. PowerFlex Gateway: Type the fully qualified name or IP Address of the
PowerFlex gateway. b. Username: Type the gateway admin username. c. Password:
Type the gateway admin password.
NOTE: To edit the IP address of the PowerFlex gateway, use the Change option.
5. Click Next. 6. Select the PowerFlex array that you want to add to AppSync,
and click NEXT. 7. Review the configurations in the Summary page, and click
FINISH.
AppSync discovers and operates on the registered system.
Configure Dell Storage Center storage
To protect applications running on Dell SC storage, add the Dell SC arrays to
the AppSync storage infrastructure.
Prerequisites NOTE: The AppSync Support Matrix is the authoritative source of
information about supported software and platforms.
This operation requires the Resource Administrator role in AppSync. Configure
Dell Storage Manager Data Collector for the Dell SC array and confirm that the
array is accessible through the Dell Storage Manager Data Collector to
communicate with AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
STORAGE SYSTEMS. 2. Click ADD SYSTEMS. 3. In the Select System Type page,
select Dell Storage Center> Next. 4. Type credentials for the array in the
following fields:
a. Name/IP Address: Type the Name or IP Address of the Dell Storage Management
Data Collector. b. SSL Port: Type the port number.
NOTE: The default value is3033 for this field.
c. Username: Type the Admin username. d. Password: Type the Admin password. 5.
Click Next. 6. Select the array that you want to configure, and click Next, in
the Select the Dell SC arrays to configure page. 7. Click Next. 8. Review the
configurations in the Summary page, and click FINISH.
View storage system details
Describes how to view the storage system details.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS.
Configuration and resource management
37
2. Select the storage array that you would like to view. The right pane
displays information for the storage system you selected.
Removing a storage system
Describes how to remove a storage system.
Prerequisites No copies that are generated by AppSync can exist on the storage
system. This operation requires the Resource Administrator role in AppSync.
NOTE: You cannot remove storage until all copies have been expired.
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2.
Select the storage system that you want to remove. For VMAX3/PowerMax arrays,
you must also clear the configured
storage group, or storage resource pool, if applicable. 3. Select REMOVE.
NOTE: Before removing a Metro node | VPLEX storage system, ensure that you
clear the arrays that you selected when configuring Metro node | VPLEX
(Service plan > Create local copy > Configure storage options > Array
preference).
Rediscovering a storage system
Use the REDISCOVER operation to query and update storage system information,
such as, name, model, serial number, storage group, and operating environment
version in AppSync.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. Select Settings > Infrastructure Resources > STORAGE SYSTEMS. 2.
Select a storage system. 3. Select REDISCOVER.
NOTE: If you change the Metro node| VPLEX cluster name, ensure that you
rediscover the Metro node| VPLEX cluster before performing any operation.
Configure SNMP notifications
After upgrade or installation of AppSync, you can configure SNMP Notifications
using the .mib file. You must copy the DELL-EMC-APPSYNC-MIB.mib file from
location
38
Configuration and resource management
Configure a VMware vCenter Server
Add a VMware vCenter Server to AppSync when you want to protect VMWare
datastores or when a virtual machine is used as a mount host.
Prerequisites This operation requires the Resource Administrator role in
AppSync. Ensure that you know the credentials of an account with Administrator
privileges on the vCenter Server.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
VCENTER SERVERS. 2. Click ADD SERVER. 3. Enter the following details in the
Add vCenter Server page:
NOTE: Type the credentials for an account that has Administrator privileges on
the vCenter Server.
a. Name: Enter name or IP address of the vCenter server. b. Username: Enter
the username of the user. c. Password: Enter the password of the user.
NOTE: The Run Discover Now option is selected by default.
NOTE: AppSync allows you to mount a file system or a database (that is, the
underlying storage LUN on which they reside) from a physical Windows or Linux
environment to a VMware virtual environment as an RDM device. Ensure that you
add the vCenter managing that virtual machine to AppSync before performing a
mount.
4. Click OK.
Reset credentials for a VMware vCenter Server
Update AppSync when credentials change for a VMware vCenter Server.
Prerequisites This operation requires the Resource Administrator role in
AppSync. You need to know the new credentials to an account that has
Administrator privileges on the VMware vCenter Server.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
VCENTER SERVERS. 2. Select the server you want to reset the credentials for
and click RESET CREDENTIALS. 3. In the Reset Credentials dialog, specify
values for the following fields:
Username Password 4. Click OK.
Remove a VMware vCenter Server
You can remove a VMware vCenter Server from AppSync.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
VCENTER SERVERS.
Configuration and resource management
39
2. Select the server you want to remove and click REMOVE. 3. In the Remove
vCenter Server dialog, click YES.
Rediscover VMware vCenter Server
Rediscover a VMware vCenter Server in AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
VCENTER SERVERS. 2. Select the server you want to rediscover and click
REDISCOVER. 3. In the Discover virtual center dialog, click DISCOVER.
Configure a Kubernetes Cluster
Add a Kubernetes Cluster to AppSync when you want to protect namespaces or
when a cluster is used as a mount cluster.
Prerequisites Review this information before you begin. When you add a
Kubernetes cluster, AppSync registers the cluster in its database and
discovers the namespaces on that cluster. AppSync uses Velero for creating
backups of Kubernetes resources that are associated with namespaces in the
configured cluster. This operation requires the Resource Administrator and
Security Administrator role in AppSync. Register the Kubernetes cluster in
AppSync by providing the Control Plane node details or by Kubernetes API Load
Balancer
details. AppSync configures Velero while registering the Kubernetes cluster.
Velero configuration requires the cluster to access docker hub for pulling the
required images which include the appsync-
velero plug-in image. The AppSync server must be accessible to the Velero pods
by IP address. Provide token of a service account during cluster registration.
Steps are given below: Creating a namespace for service account
kubectl create namespace appsync-users Creating a service account
kubectl create serviceaccount appsync-service-account -n appsync-users
Creating the cluster roles
cat <<EOF | kubectl apply -f –apiVersion: rbac.authorization.k8s.io/v1 kind:
ClusterRole metadata: name: api-cluster-role namespace: appsync-users rules: –
apiGroups: – “” – apps – rbac.authorization.k8s.io – apiextensions.k8s.io –
velero.io – snapshot.storage.k8s.io
40
Configuration and resource management
Configuration and resource management
41
kind: ClusterRole name: api-cluster-role EOF Obtaining the service token
kubectl describe secret appsync-service-account-token-
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
Kubernetes Cluster. 2. Click ADD CLUSTER. 3. Enter the following details in
the Add Kubernetes Cluster page:
a. Control Panel Node: Enter the name or IP address of the Kubernetes cluster
control plane node or Kubernetes API Load Balancer.
b. Port: Enter the port used by Kubernetes. c. ServiceAccount Token: Enter the
service account token cluster. d. Namespace name: Enter the namespace name
where AppSync can configure Velero plugin. e. Bucket Name: Enter the bucket
name. AppSync uses this bucket name to configure the object storage for Velero
to
save all resource backups. 4. Click OK.
Remove a Kubernetes Cluster
You can remove a Kubernetes Cluster from AppSync.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
Kubernetes Cluster. 2. Select the cluster that you want to remove and click
REMOVE. 3. Select one of the following options in Remove Kubernetes Cluster
window:
Remove cluster – Removes the selected cluster from AppSync. Remove cluster
forcefully – Forcefully deletes the Kubernetes cluster entry in the AppSync
database and removes the
configured Velero namespace. AppSync does not check for any copy dependency on
the cluster. It deletes all internal metadata related to this cluster. User
must take care of cleanup tasks like unmounting copies from the cluster.
Deinstall Velero CRD – Removes Velero Custom Resource Definitions from the
cluster. Ensure that no other application depends on Velero Custom Resource
Definitions before selecting this option. 4. Click YES to remove the selected
cluster and NO to cancel the window.
Rediscover Kubernetes Cluster
Rediscover a Kubernetes Cluster in AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
Kubernetes Cluster. 2. Select the cluster that you want to rediscover and
click REDISCOVER.
42
Configuration and resource management
Renew Service Account Token of Kubernetes Cluster
Renew the service account token of a selected Kubernetes cluster in AppSync.
Steps 1. On the AppSync console, select Settings > Infrastructure Resources >
Kubernetes Clusters. 2. Select the cluster that you want to renew the service
account token for and click MORE> RENEW SERVICE ACCOUNT
TOKEN. 3. In the Renew Service Account Token dialog, specify values for the
following fields:
Control Plane Node Service Account Token 4. Click OK.
Backup and restore AppSync using the Backup Assistant tool
Installed with the AppSync server is a tool that can be leveraged to both
backup and restore the local AppSync database. The tool is called the Backup
Assistant.
NOTE: From AppSync 4.5, AppSync backup assistant tool includes applib folder
also as part of the backup and restore operations. A folder named
“AppSync_applib” will be created in the backup folder.
AppSync Backup Assistant arguments and actions
Learn how to back up and restore the AppSync database by selecting the
appropriate arguments for the AppSync Backup Assistant, appsync-backup.bat,
located in the AppSyncbackup-assistant directory.
Ensure you have a valid backup before attempting a database restore. To create
a backup, run appsync-backup.bat from the administrator command prompt using
the following syntax: appsync-backup.bat[-o, -out “
Table 6. 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 =’$SystemDriveAppSyncBackup
-d, -debug
Enables display of DEBUG messages. NOTE: In the debug mode, you can ignore the error: OUTPUT: pg_basebackup: error: could not stat file “C:AppSyncBackup2021_12_21_22_50_10/base.tar.gz”: Unknown error”
-h, -help -i, -import
Prints the Help message.
Allows you to specify a backup that you want to restore to the current host.
(If this argument is not used a backup will be taken.)
An example of an export command.
C:EMCAppSyncbackup-assistant>appsync-backup.bat -o C:AppSyncBackup -d would
create the backup C:
AppSyncBackup2020_01_23_02_00_52Appsync_2020_01_23_02_00_52_base.tar.gz
Configuration and resource management
43
Schedule automated backup of the AppSync server database
You can use the Windows Task Scheduler to schedule backups of the AppSync
server database at normal intervals.
Prerequisites This operation requires the Resource Administrator role in
AppSync.
Steps 1. Log in to the Windows host. 2. Click Computer Management > System
Tools > Task Scheduler. 3. Right-click Task Scheduler Library, and select
Create Basic Task.
The Create Basic Task wizard appears. 4. Specify a name for the schedule, and
click Next. 5. Select a trigger option, and click Next. 6. Set the frequency
and time for the selected trigger option, and click Next. 7. Select the action
that you want the task to perform, and click Next. 8. Browse to the appsync-
backup.bat file or specify the full path (C:EMCAppSyncbackup-assistantappsync-
backup.bat), and click Next. 9. Review the task summary, and click Finish.
The task is created and added to the Windows schedule.
Restore an automated backup
The Backup Assistant tool allows you to restore a backup created previously
with this tool. Learn about the process and caveats for automated backup. Be
sure to restore a backup at a time of low activity on the server.
Prerequisites To restore a back up from an older version of AppSync be sure
that you install the latest version of AppSync before attempting to use the
automated restore.
NOTE: Restoring an earlier version of the backed-up AppSync database on a new
version of AppSync server is not supported. Make sure the version of the
AppSync server installed on the host is same version as the backup that was
created.
Steps Run the backup assistant tool with the -i, -import argument, for
example: C:EMCAppSyncbackup-assistant>appsync-backup.bat -i C:
AppSyncBackup2020_01_23_02_00_52Appsync_2020_01_23_02_00_52_base.tar.gz When
running this restore, the AppSync services will be stopped and restarted
automatically.
Migrating the AppSync server
You can migrate the AppSync server from one server to another.
About this task For example, to migrate a server from Server A to Server B:
Steps 1. Disable all service plans on Server A. 2. If VMAX/PowerMax has been
added to AppSync:
a. Set the AppSync advanced server setting vmax.disable.internal.sg on Server
A to true
44
Configuration and resource management
b. Run a Rediscover operation on one or more VMAX arrays on Server A. This
removes the AppSync provisioned devices from the internal storage group
AppSync creates, and will also delete the internal storage group, named
{AppSync Server Name}_INTERNAL-AppSync-{Integer}. The devices remain intact,
however, not in any particular storage group. You can optionally validate this
within Unisphere for VMAX.
3. Take a backup of the AppSync server from server A using the AppSync Backup
Assistant utility, for example type: EMCAppSyncbackup-assistant>appsync-
backup.bat -o C:AppSyncBackup
4. In the AppSync user interface, on Server A, go to Help > About Dell
AppSync and note the complete AppSync version (including the hotfix number).
Also, note any hand-edit procedures to configuration files that Customer
Support requested you to perform for the AppSync server installation.
5. Install the AppSync Server software on Server B. Ensure to install in the
same drive as in Server A, to maintain the same folder structure. Apply the
exact version of AppSync that includes the exact hotfix number, if a hotfix
was previously installed. Re-apply any hand-edit procedures to configuration
files that were noted in the previous step.
6. Copy the backup file taken in Step 4, to Server B, and then restore it
using the Backup Assistant utility. For example, type EMCAppSyncbackup-
assistant>appsync-backup.bat -i C:
AppSyncBackup2020_01_23_02_00_52Appsync_2020_01_23_02_00_52_base.tar.gz.
7. Enable all service plans on Server B which were previously disabled.
8. If VMAX/PowerMAX has been added to AppSync:
a. Set the AppSync advanced server setting vmax.disable.internal.sg to the
default value of false on Server B. b. Run a Rediscover on one or more VMAX
arrays on Server B. AppSync creates a new internal storage group with the new
AppSync server name, and move the devices from Step 2b, into it. You can
optionally validate this within Unisphere for VMAX.
9. Once Server B is online, shutdown Server A (to ensure that it is not used
inadvertently) or preferably, remove the AppSync software completely.
10. If Kubernetes Cluster were configured in AppSync, you have to reconfigure
the Backup Storage Locations (BSL) on all the clusters. Follow the below steps
to reconfigure:
a. Connect to the Kubernetes Cluster. b. Get the name of BSLs to be configured
using: kubectl get bsl -n
{“appsyncUrl”:”https://
Results
You can now use the AppSync server on Server B.
Configuration and resource management
45
Troubleshooting
This section provides information on the common problems encountered while
installing AppSync.
Topics:
· Host installation and deployment issue · Push install fails while adding
host to AppSync server · AppSync upgrade fails · AppSync upgrade failure due
to insufficient permissions
Host installation and deployment issue
Problem
When installing the agent plug-in, SUDO user installation might fail.
Resolution
Ensure the following: 1. SSH service is configured on the Unix/Linux systems.
2. BZip2, OpenSSH, and OpenSSL packages are available for AIX. 3. The
sg3_utils package is available for Linux. 4. SSH port 22 is unblocked. 5.
There is sufficient space available at the install location. 6. The
home/install directory of the SUDO user has the “write” privilege. The AppSync
Installation and Configuration Guide provides additional information on
installing the SUDO user.
Push install fails while adding host to AppSync server
Problem
When adding a host to the AppSync server, push install fails with the
following error:
Unable to connect host:10.247.170.168 with user:lrmc168administrator using RPC
irx output: Error (53): The network path was not found.
This is due to connectivity issues between the AppSync server and the host
that is being added to the AppSync server. The AppSync server uses port 445
for initiating connection between the server and the host. If it is not able
to establish connection, push install fails.
Resolution
Configure the network properly to ensure that connectivity exists.
46
Troubleshooting
AppSync upgrade fails
Problem
AppSync upgrade failed from 4.1.0.x to 4.2.0.x, 4.2.0.x to 4.3.0.0, and 4.3 to
4.5 with an error.
Resolution
Following are the steps, to resolve this issue: 1. Go to
Troubleshooting
47
References
- vCenter High Availability
- Creating and Using vSphere HA Clusters
- Providing Fault Tolerance for Virtual Machines
- Submit Form
- Computers, Monitors & Technology Solutions | Dell USA