AppSync 3.0 For SQL, Oracle and Windows File Systems

APPSYNC 3.
0 FOR SQL,
ORACLE AND WINDOWS FILE
SYSTEMS
AppSync 3.0 for SQL, Oracle and Windows File Systems

Table of Contents
Introduction.................................................................................................................................................. 4
About this lab ..................................................................................................................................................5
Lab Overview ................................................................................................................................................ 6

Lab Environment .............................................................................................................................................7
Lab Credentials ................................................................................................................................................8
Lab Scenario ....................................................................................................................................................9
Labs...............................................................................................................................................................10
Lab 1: Browsing the AppSync Console ........................................................................................................ 11

Browsing the AppSync Console ......................................................................................................................12
Lab 2: Adding Resources to AppSync (must complete before remaining labs) ............................................. 22
Adding Storage, vCenter, and Host Resources ................................................................................................23
Lab 3: Managing SQL.................................................................................................................................. 37

Create and Restore SQL Copies ......................................................................................................................38
Repurposing SQL Copies ................................................................................................................................75
Lab 4: Managing Oracle .............................................................................................................................. 94

Create Oracle Copies......................................................................................................................................95
Validating Oracle (optional) .........................................................................................................................112
Repurposing Oracle Copies ..........................................................................................................................119
Lab 5: Managing File System Replication .................................................................................................. 134

Create and Restore Windows File System Copies ..........................................................................................135
Lab 6: AppSync 3.0 Installation (Optional)................................................................................................ 152

Installing AppSync 3.0 .................................................................................................................................153
Registering Unity storage array .....................................................................................................................164
What's next? ................................................................................................................................................167
Conclusion ............................................................................................................................................... 168

Conclusion...................................................................................................................................................169
Additional Solution Information................................................................................................................ 170

Business Challenge......................................................................................................................................171
Solution .......................................................................................................................................................172
AppSync ......................................................................................................................................................173
Troubleshooting & Tips ................................................................................................................................174

Introduction
AppSync 3.0 for SQL, Oracle and Windows File Systems Page 4
About this lab
AppSync is an EMC software that enables Integrated Copy Data Management (iCDM) with EMCs Primary Storage.
AppSync simplifies and automates the process of generating and consuming copies of production data. In this lab,
you will learn how to create copies of Windows File Systems, Oracle and SQL databases. You will also learn how to
install AppSync 3.0 and register an EMC Unity and EMC VNX storage array.
Lab Overview
Lab Environment
Appsync Lab Environment
The environment for this lab includes the following:
1 x Microsoft Windows 2012 R2 Domain Controller

1 x Microsoft Windows 2012 R2 AppSync server running AppSync 3.0
1 x Microsoft Windows 2012 R2 with the AppSync 3.0 binaries
1 x Microsoft Windows 2012 R2 with Microsoft SQL 2012 production server
1 x Microsoft Windows 2012 R2 with Microsoft SQL 2012 mount host server
2 x Linux Red Hat 6.5 with Oracle 12c RAC clustered database servers
1 x Linux Red Hat 6.5 with Oracle 12c standalone mount host server
1 x vCenter Server (VMware vSphere AppSync Management lab)
1 x ESX host (VMware vSphere AppSync Management lab)
1 x Unified VNX5400 with 5.33.000.5.033 (Unified rockies VSA)
1 x Unity Virtual Storage Appliance (VSA)
Lab Credentials
Environment Details
Note 1: This table is for reference purposes, you may not access everything when completing the use cases in the lab
guide.
Note 2: The VMs are listed in the recommended shutdown order so for example rhel03.vlab.local should be shutdown
first.
Lab Scenario
Stephany is an IT Manager at RainPole. One of Stephany's tasks is to provide the ability to offer copy management
solutions. The objective is to reduce the number of storage copy requests storage administrators get on a daily basis,
as well as to reduce the manual work server and application owners need to perform upon each refresh.
Stephany has recently overseen the installation of a VNX in one of RainPole's Data Centers, as well as is managing the
installation of AppSync. Stephany, as the IT Manager, has been tasked with the following:
Appoint an administrator the lead Administrator role in AppSync to oversee and manage the AppSync product
Ensure the lead AppSync Administrator adds the storage and hosts within AppSync
Ensure the lead AppSync Administrator creates Service Plans to subscribe the application objects to
Ensure the lead AppSync Administrator manages the replication processes
The following Labs will guide the AppSync administrator through each step.
Labs
Please note that Lab 2 must be completed before the remaining labs can be completed. Labs 3-6 can be individually
chosen, or done in any order.
This vLab includes the following:
Lab 1: Browsing the AppSync Console
Lab 2: Adding Resources to AppSync (this lab must be completed before undertaking any other lab)
Adding the VNX storage array

Adding the host resources
Two Windows SQL database servers

Three Linux Oracle database servers
Lab 3: Managing SQL
Creating a Service Plan for automated daily copies for backup purposes on an alternate host
Utilizing Data Repurpose for testing and development purposes on an alternate host
Lab 4: Managing Oracle
Creating a Service Plan for automated daily copies for backup purposes on an alternate host
Utilizing Data Repurpose for testing and development purposes on an alternate host
Lab 5: Managing File System Replication
Creating a Service Plan for on-demand copy testing on an alternate host
Lab 6: Deploying a new AppSync 3.0 server and registering a UnityVSA storage array
Installing AppSync 3.0

Adding a UnityVSA storage resource
Lab 1: Browsing the AppSync
Console
Browsing the AppSync Console
Before you can protect your systems with AppSync you need to become familiar with using the console.
In this lab you will browse and see where to configure options for database copies, service plans, monitoring and
alerting. Once you have completed this you will be able to continue with the remaining labs, where you will add the
array, severs, and configure the environment for automated copy management.
Connecting to the environment
On the desktop, double-click mRemoteNG

mRemoteNG.
Open the AppSync Server
In the Connections pane, double-click AppSync

AppSync.
Launch the AppSync User Interface
On the desktop, double-click AppSync

AppSync.
Privacy error
Click ADVANCED
ADVANCED.
Proceed
Click Proceed to appsync.vlab.local (unsafe)
Log into AppSync
Use the following credentials
admin
Password123!
Click Login
Login.
Console Overview
When you log into AppSync for the first time, a No Storage dialog box is displayed.
Clear Add storage now and click OK

OK.
Introduction
You will see the console is arranged in sections for management, reporting, and administration.
Dashboard: A customizable view of reports and alerts. The default dashboard shows recovery point objective
(RPO) status of protected applications, service plan completion status, most recent alerts, and activity in
progress.
Copy Management: Lists the discovered applications such as Microsoft SQL and Oracle databases, and
provides the application-oriented entry point for protection, mount, restore, service plan subscription, and
other operations such as enabling Access Controls.
Service Plans: Lets you view and modify service plan settings, view lists of objects that are subscribed to a
service plan, the copies that were made of those objects, and the events that were generated when the
service plan was run.
Monitoring: Displays alerts, recovery point compliance reports, and service plan completion reports.
Settings: Is for adding servers, VMware vCenter servers, and storage resources to AppSync. License
management, user administration, and server settings are also found under Settings.
Support: Provides access to how-to videos and the AppSync support page at support.EMC.com
Note: The accompanying screen shot may differ from your lab.
Copy Management
AppSync currently supports creating array based copies of Microsoft Exchange, Microsoft SQL, Oracle, VMware data
centers and file systems. Selecting the type of application will display the servers that have those particular
applications, and display those particular application objects, such as the databases, datastores, or file systems. In
labs 2-5,you will walk through these details. Always refer to the AppSync User and Administration Guide for more
details on Copy Management.
Service Plans
Service Plans comes with templates that can be used as is, customized, or used to create other more defined Service
Plans. These Service Plans determine how to manage the copies, such as creating a schedule, number of copies to
maintain, type of technology, snaps, clones or RecoverPoint bookmarks, mount options, as well as many other
options. You will be walking through some of these settings in later labs. Always refer to the AppSync User and
Administration Guide for more details on Service Plans.
Monitoring
In the Monitoring menu, you can review past alerts, review an overview of all Service Plans that have completed and
which environments are compliant with the recovery point objective, as well as review the repurpose monitor.
Settings
In the Settings menu, you can add storage, VMware vCenter Servers, host application servers, add users, license
arrays, and configure other AppSync Server settings such as the SMTP server for alerting.
Support
The Support menu offers links for gaining support on support.emc.com as well as how-to videos.
Lab 2: Adding Resources to
AppSync (must complete before
remaining labs)
Adding Storage, vCenter, and Host Resources
Ensure you are logged into AppSync as admin
admin, and perform the following steps to register the VNX storage array and
hosts.
Log into AppSync as admin if not already logged in
Refer to Browsing the AppSync Console lab, if you need help launching the AppSync log-in dialog box.
Use the following credentials:
admin
Password123!
Click Login
Login.
Add Storage Now
The first time you log in, a dialog box will be displayed, requesting that you add storage. Click OK to Add storage now.
Note: If the No Storage dialog box is not displayed, navigate to Settings > Storage Infrastructure
Add the VNX storage array
Click Add
Add, and then select VNX
VNX credentials
In the Add VNX area, specify the following:
In the SPA field, type 192.168.1.30
In the SPB field, type 192.168.1.31
In the Global user name field, type sysadmin
In the Password field, type sysadmin
Click OK
OK.
Adding the vCenter Server
In order to mount to virtual hosts, you must add the vCenter server. Hover over Settings, and then select VMware
vCenter Servers
Servers.
Add
Click Add
Add.
Enter vCenter credentials
In the Add vCenter Server area, specify the following:
In the Name field, type lp01.vlab.local
In the Username field, type administrator@vlab.local
In the Password field, type Password123!
Click OK
OK.
Adding Hosts
Hover over Settings, and then select Servers

Servers.
Add the Windows hosts
Click Add
Add, and then select Windows Servers
Servers.
Push the plug-in onto both Windows hosts running SQL
In order for AppSync to manage the applications that reside on the servers, AppSync pushes a plug-in that enables
host and application communication. Windows host administrator rights are required for this task.
Select Auto-fill in the user name and password fields after initial entry to alleviate repetitive input.
In the Add Windows Servers area, specify the following. You can use Tab to progress through the fields.
Server Names/IP Address: sqlsource.vlab.local and sqltarget.vlab.local
Domain\User Name: vlab\administrator
Password: Password123!
Click Start to begin pushing the plug-in onto the Windows servers.
When the deployment is complete, click Close

Close.
Add the Linux hosts
Click Add
Add, and then select Unix Servers
Servers.
Push the plug-in onto the Linux host
Similar to the Windows hosts, AppSync pushes a plug-in on each host, in order to manage the application. This plug-in
does not run a service on Unix hosts, other than when requested by the AppSync server, such as when running a copy
job.
Next you will add the rhel03.vlab.local host. The rhel01.vlab.local and rhel02.vlab.local hosts have already been
added to save time.
In the Add Unix Servers area, specify the following. You can use Tab to progress through the fields.
Server Names/IP Address: rhel03.vlab.local
Domain\User Name: root
Password: Password123!
Click Start to begin pushing the plug-in onto the Linux servers.
When the deployment is complete, click Cancel

Cancel.
Summary
After adding the two Windows SQL servers and the third Linux Oracle server, you will see the following under Settings >
Servers
Servers.
Note
Note: If a warning icon is visible on one of the Red Hat Oracle servers, indicating a database may be offline you can
ignore this warning.
Lab 3: Managing SQL
Create and Restore SQL Copies
In this lab you will create a Service Plan for automating daily copies for backup, and perform a restore operation.
The purpose of this lab is to familiarize yourself with Service Plan options, as well as using the Service Plan by
subscribing SQL databases so that the copy can be used to restore a simulated corrupt database.
You will create a Service Plan to automate a daily copy and present it to the mount host for backup purposes. This
copy will also be used for restore purposes. You will simulate this by deleting a production database, restoring the
copy, and then validating the database is recovered correctly.
The copy is not recovered on the mount host, it is left in a read only/pristine state thus preserving it for
restore purposes
The copy is created, a source database is deleted, then the copy is restored and validated
Launching AppSync
admin
Password123!
Click Login
Login.
Creating a Service Plan
Service Plans determine how to manage the application objects that are subscribed, such as the copy schedule,
number of copies to keep, mounting options, among others. In this scenario, you will create a new Service Plan, based
on the Bronze template, and configure the appropriate options.
Hover over Service Plans
Plans, and then select Microsoft SQL Server
Server.
Create a new Service Plan
At the bottom of the screen, click Create.
In the Select an existing plan as a template list box select Bronze to serve as the template.
In the Plan Name field, type SQL_DB_Snap_Backup
Click OK
OK.
Select Service Plan
The new SQL_DB_Snap_Backup Service Plan is created in the Microsoft SQL Server pane.
To modify a Service Plan, click the name of the Service Plan, SQL_DB_Snap_Backup
SQL_DB_Snap_Backup.
Modify the Service Plan
This takes you to the Settings options within the Service Plan. The Plan Startup is highlighted to begin with. This is
where you can change the Recurrence Type frequency, as well as modify the Recovery Point Objective (RPO) - an
alerting mechanism to ensure copies are created in an adequate amount of time.
Leave these settings at their default, so the schedule is set to take a copy every 24 hours with a 24 hour RPO.
After determining the frequency and RPO alerting options, the next step is to configure the Create local copy options.
Click Create local copy

copy.
Configure the Create Local Copy Options
In the SQL Server Backup Type area, the default Full is selected, as AppSync is the only software creating the backup,
and the transaction log sequence number (TLN) is maintained by AppSync
Note
Note: Only one backup product should maintain the SQL TLN, so if another product is maintaining SQL full backups,
AppSync should be set to Copy, as will be demonstrated when performing copy repurpose in a future step.
In the Expiration of Database Copies area, change this option to keep only 1 copy, as the same copy is refreshed for
backup purposes, every day.
Configure the Unmount Previous Copy Option
In order for AppSync to only mount one copy at a time, select Unmount previous copy
copy.
Configure the Mount Copy Options
When the frequency, RPO alerting, copy and unmount previous copy settings are configured, the next step is to
configure the Mount copy options. Mounting this copy to an alternate host alleviates any contention performed on the
production host. Since this copy is used for backup purposes, there are no recovery options - the application is not
started on the mount host.
Select Mount copy

copy. Specify the following:
Accept the default, Mount copy

copy. You will use the recover copy option later, when you repurpose the copy
In the Mount on Server list box, select sqltarget.vlab.local as the host the copy will be mounted to, rather than back to
the production/source host which is always listed as default
Mount with access

access, accept the default, Read-only
Mount Path
Path, accept the default, Default Path. Since the application is not recovered, there is no reason to use the
same as original path. The purpose for this mount is to simulate how you can backup the array copy to an alternate
media for archiving.
When ready, click Apply to save the settings.
Subscribing to and Running the SQL Service Plan
In this step, you will subscribe to the Service Plan created previously, and also run it.
Hover over Copy Management

Management, and then select Microsoft SQL Server
Server.
Dismiss tip
Select Do not display this hint again

again, and then click OK
OK.
Connection Settings
Highlight the SQLSOURCE row, and then click Connection Settings

Settings.
SQL Server Connection Settings
In the SQL Server Connection Settings area, specify the following:
In the Username field, type vlab\administrator
Click OK
OK.
Dismiss tip
Select Do not display this hint again

again, and then click OK
OK.
User Databases
Click User Databases

Databases.
DB01, DB02, and DB03
Click Select All

All, which will highlight the three user databases, DB01
DB01, DB02
DB02, and DB03
DB03.
Subscribe to Plan
Click Protect > Subscribe to Plan

Plan, and select SQL_DB_Snap_Backup
SQL_DB_Snap_Backup.
Subscribed
This subscribes to the Service Plan, however, it will only run at the set scheduled time depicted in the Service Plan
settings. In the next step, you will run the Service Plan rather than having to wait till midnight.
Run the Service Plan On-Demand
The Service Plan previously created runs on a 24 hour basis, however, you need to test that the replication process
works immediately. You first need to confirm what other potential databases are subscribed, since you would not want
to accidentally run another database, for example.
Select Microsoft SQL Server

Server.
SQL_DB_Snap_Backup
Click SQL_DB_Snap_Backup
SQL_DB_Snap_Backup.
Subscriptions
Select Subscriptions which shows all the subscribed application objects. You will see the three SQL databases
Move up a level
Click Microsoft SQL Server in the directory path, to move up one level.
Run Service Plan
Highlight the SQL_DB_Snap_Backup row. Do not click the name of the Service Plan.
Click Run at the bottom of the screen.
View Details
The Run Service Plan dialog box appears, click Details to view the progress.
Validating the Copy
When the Service Plan completes, click Close and perform the following steps to validate the copy was created and
mounted successfully.
Connect to the SQL Mount Host
In mRemoteNG
mRemoteNG, double-click SQLTARGET
SQLTARGET.
Open Windows File Explorer
On the taskbar, click File Explorer

Explorer.
Navigate to C:\AppSyncMounts > sqlsource > EDrive to view the three databases that were replicated.
You can see how easy it would be copy these files onto archive storage by using a post-mount script, or to be used for
recovery, which you will perform in the next step. Also notice that you cannot change these files, as you selected Read-
only under the mount options when configuring the Service Plan.
Close File Explorer

Explorer.
Deleting the Database
You have validated that the three SQL databases were successfully replicated to the mount host.
In order to simulate a disaster, you will delete one of the three databases, from within SQL Management Studio on the
production/source host, then restore the copy created earlier.
In mRemoteNG
mRemoteNG, double-click SQLSOURCE
SQLSOURCE.
Open SQL Server Management Studio
Double-click SQL Server Management Studio

Studio.
Connect to the SQL Server Management Studio
Click Connect
Connect.
Delete a Database
Click +
+ to expand Databases
Databases.
You will see the three SQL databases, DB01

DB01, DB02
DB02, and DB03
DB03.
Right-click DB01
DB01, and then select Delete
Delete.
Confirm delete
Click OK
OK.
Restoring the Copy
Since one of the databases has been accidentally deleted, you now need to restore it from the copy previously taken
earlier. In order to do this, you will perform a Restore operation. Restore effects all objects on the same storage array
LUN, and in this lab, all three databases and their corresponding logs, will be overwritten. Always be cautious of the
effected entities when restoring. AppSync offers the ability to backup the log files before being overwritten, allowing
the replay of newer logs, reducing the recovery point objective. More details on this subject can be found in the
AppSync User and Administration guide.
AppSync does not currently allow for restore if the copy is mounted, so you must first unmount the copy.
Switch back to AppSync
In mRemoteNG
mRemoteNG, click AppSync
AppSync.

Server.
SQL_DB_Snap_Backup
Click SQL_DB_Snap_Backup
SQL_DB_Snap_Backup.
Unmount DB01
Select Copies
Copies.
Select the DB01 database row.
Note: All databases will be unmounted as part of this step, since they were all mounted together and are considered
effected entities.
Click Unmount
Unmount.
Confirm
Click OK
OK.
Task Complete
When the Unmount task has completed, click Close

Close.
Mount Status
The Mount Status has changed to Not Mounted

Mounted.
Perform the Restore
After the volumes have been unmounted from SQLTARGET

SQLTARGET, you can perform the Restore. AppSync restores at the LUN
level, so anything on the LUNs you have replicated, will be restored, this means DB02 and DB03, and their
corresponding log files.
Restore
Select the DB01 database row again, but this time click Restore
Restore.
Next
Click Next
Next.
Select Acknowledgment
You will be notified of the effected entities, as mentioned previously, which requires acknowledgment.
Select the acknowledgment, and then click Next

Next.
Transaction Logs
You will not enable transaction log backup prior to restoring. If you wish to take backups of the current transaction
logs, before the restore, you can enable this option. This option is useful if recovering a copy made a significant time
ago, and allows you to put the SQL database in a NORECOVERY state, allowing to replay those saved transaction logs,
thus reducing the recovery point objective (RPO). The method you are choosing is recovery to a specific point-in-time
(PiT), which offers the lowest recovery time objective (RTO).
Click Next
Next.
Accept default
Accept the default Leave databases ready to use [RESTORE WITH RECOVERY] so the SQL databases are usable after the
recovery.
Click Next to view the Summary.
Finish
Click Finish
Finish.
Complete
After the task has completed, click Close
Validate the Restore
After the restore is complete, the DB01 database will be visible in SQL Server Management Studio.
Select SQLSOURCE
In mRemoteNG
mRemoteNG, select SQLSOURCE
SQLSOURCE.
Connect
Close SQL Server Management Studio

Studio, then open and connect again.
Successful restore
Click +
Databases.
DB01 has been successfully restored.
Repurposing SQL Copies
In this lab you will repurpose the a SQL database, meaning, you will create a 1st generation copy which will serve as a
point-in-time (PiT) copy and then a 2nd generation copy which will be created from that 1st generation copy, mounted
and the database recovered on the mount host. This simulates creating a test and development environment, or for
perhaps report generation, alleviating any impact on the production environment.
The purpose of this lab is to familiarize yourself with the repurposing features of AppSync, by creating on-demand
repurposing copies. As a general rule, repurposed copies are not meant for backup and recovery, though 1st
generation copies can be used for such situations. repurposed copies are not automated, or scheduled beyond the
initial 1st generation copy, and so are managed manually through the UI.
Utilize data repurposing for test and development or reporting purposes on an alternate host.
A Generation 1 copy is created to serve as a Gold copy, a copy that is not mounted or changed in any manner
and can be used for recovery purposes if required.
A Generation 2 copy is created from the Generation 1 copy, mounted, and then recovered in SQL, providing
the secondary environment for repurposing use cases
Launching AppSync
admin
Password123!
Click Login
Login.
Create 1st Generation Copy
You will now create the 1st generation copy that serves as a point-in-time (PiT) copy, which is then used to create the
2nd generation copy, mounted and recovered on an alternate host.

Management, and then select Microsoft SQL Server.
SQLSOURCE
Click SQLSOURCE
SQLSOURCE.
User Databases
Click User Databases

Databases.
Create Repurpose Copy
Select the DB01 database row.
Click Repurpose
Repurpose, and then select Create Repurpose Copy
Copy.
Repurpose - Intention
The Repurpose wizard appears with the first step, called Intention.
You will notice that you can create both 1st and 2nd generation copies at the same time, however, you will only create
a 1st generation copy at this time, and create the 2nd generation copy in a future step; showing you how to create
multiple 2nd generation copies if required.
Accept the defaults, and then click Next

Next.
Repurpose - Settings
The next step within the Repurposing wizard is to choose similar settings as you would see when setting up a Service
Plan. Here, you can initiate a pre-copy script, configure copy settings, initiate a post-copy script, provide mount and
unmount options, as well as initiating a post-mount script.
The only setting you will change is the type of SQL backup, as seen in the following diagram. Since a Full copy is being
created with the daily Service Plan, you will choose Copy for the repurposed copy, preserving the SQL transaction log
sequence number (TLN) - please refer to the AppSync User and Administration Guide for more details.
In the SQL-Specific Copy Options area, select Copy

Copy, and click Next
Next.
Repurpose - Schedule
For the purpose of this lab, accept the default selection Run Now and click Next
Next.
Repurpose - Summary
The last step within the Repurpose wizard is to review the settings, and then to initiate the copy. Some settings are
hidden within a scrolling menu.
Confirm the settings, and click Finish to start the process.
Repurpose - Completion
Click Details to expand the process log to view more information on what is occurring in the background. Ignore any
licensing warnings.
Click Close when the process is complete.
Create 2nd Generation Copy
Once the 1st Generation copy is created, any number of 2nd generation copies can be created from that 1st gen copy.
The limit of copies depends on the storage array, and its code level, so please refer to the the array product
documentation for those specifics.
In this section of the lab, you will create a 2nd generation copy, mount it to the SQL mount host, recover the database,
that is, bring the copied database on line for purposing use cases, such as creating a mirrored environment for test
and development, or for running reports so the production host is not subjected to additional load.
Select database
Click DB01 to select the 1st Generation copy created in the previous step.
1st Generation Copy
You will see the copy created in the previous step, with the label description 1st Generation local copy
copy.
Highlight the 1st Generation local copy row, and then click Repurpose
Repurpose.
Similar to creating the 1st gen copy, there is a wizard that helps you perform the 2nd generation copy. Since you are
creating a copy from a 1st generation copy, the only option is to create the 2nd gen copy, the limit for how many
copies removed from the source.
Click Next
Next.
Similar to the 1st generation, and Service Plan settings, there are options to configure pre/post-copy scripts, as well
as mount options. The Create 2nd gen copy is always selected by default, and cannot be changed.
First select Unmount previous copy

copy. Now select Mount copy to configure the following settings:
Select Mount and recover copy

copy.
In the Recovery Instance list box, select SQLTARGET

SQLTARGET.
In the SQL Server Connection Settings dialog box, specify the following:
In the Username field, type vlab\administrator
Click OK
OK.
In the Mount Path list box, select Same as original path

path.
Click Next to select the Schedule options.
Schedule options
Click Next to review the Summary.
Repurpose - Finish
Click Finish to complete.
Repurpose - Complete
After the task is complete, click Close

Close.
Repurposing Validation
In these next steps you will perform validation.
User databases
Click User Databases to move up one level.
DB01
Click DB01
DB01.
View 2nd gen copy
Click, and expand the arrow next to the 1st generation copy to view the 2nd generation copy. The copy is mounted on
the sqltarget.vlab.local host.
SQL Validation
Now that the copy is mounted on the SQLTARGET host, the database will have been added to the mount host, and is
online. You will validate this in SQL Server Management Studio on the SQLTARGET host.
Connect to SQLTARGET
In mRemoteNG
mRemoteNG, click SQLTARGET
SQLTARGET.
Open SQL Server Management Studio
Double-click SQL Server Management Studio

Studio.
Connect
Click Connect
Connect.
Expand and validate databases
Click +
Databases.
DB01 has been added and is online.
Lab 4: Managing Oracle
Create Oracle Copies
In this lab you will create a Service Plan for automating daily copies for backup, however, unlike in the SQL lab, this
lab does not provide instruction on how to perform a restore operation. Refer to the AppSync User and Administration
Guide, in the section titled Restoring an Oracle copy and also, Restoring a RAC copy to understand what is involved
with restoring in a RAC environment.
The purpose of this lab is to familiarize your with Service Plan options, as well as using the Service Plan by subscribing
an Oracle database so that the copy can be used for backup purposes.
Objective:
You will create a Service Plan to automate a daily copy and present it to the mount host for backup purposes.
The copy is not recovered on the mount host, it is left in a read only/pristine state preserving it for restore
purposes
Optionally validate the replicated database by adding a table entry using script, refreshing the copy, then
running another script on a mount host to validate the changes.
Launching AppSync
admin
Password123!
Click Login
Login.
Plans, and then select Oracle
Oracle.
Click Create
Create. In the Select an existing plan as a template list box, select Bronze
Bronze.
In the Plan Name field, type Oracle_DB_Snap_Backup
Click OK
OK.
The Oracle_DB_Snap_Backup Service Plan is created.
To modify the Service Plan, click Oracle_DB_Snap_Backup

Oracle_DB_Snap_Backup.
Settings
This takes you to the Settings options within the Service Plan. The Plan Startup is highlighted to begin with. This is
where you can change the Recurrence Type frequency, as well as modify the Recovery Point Objective (RPO)(RPO), an
alerting mechanism to ensure copies are created in an adequate amount of time.
Accept the defaults, so the schedule is set to take a copy every 24 hours with a 24 hour RPO.
After determining the frequency and RPO alerting options, the next step is to configure the Create Local Copy options.
Click Create local copy
In the Oracle Options area, accept the default Place the database in hot backup mode
mode. You will not copy the FRA or
BCT, or integrate with RMAN in this lab
In the Expiration field, type 1, as the same copy is refreshed for backup purposes, every day
Click Apply to save the changes.
Configure the Unmount Previous Copy Option
In order for AppSync to mount one copy at a time, select Unmount previous copy
copy.
Configure the Mount Copy Options
Once the frequency, RPO alerting, copy and unmount previous copy settings are configured, the next step is to
configure the Mount copy options. Mounting this copy to an alternate host alleviates any contention performed on the
production host. Since this copy is used for backup purposes, there are no recovery options, the application is not
started on the mount host.
Select Mount copy

copy. Specify the following:
In the Mount operation list box, select Mount on standalone server and recover database
database.
Even though you will select recover database, the database is not altered on the mount host. You must use this option
due to using UDEV devices, rather than file systems. This is the only way a backup can be taken from the mounted
copy, by accessing the correct files.
In the Mount on Server list box, select rhel03.vlab.local as the host the copy will be mounted to, rather than back to
the production/source host which is always listed as default
Mount to Path
Path: Accept the default - this option is irrelevant in this lab, since udev rules are created, rather than file
system mount points.
Open-mode
Open-mode: Accept the default, Read-only
Read-only.
In the Database name list box, select %DB%
In the SID name list box, select %SID%
in the ASM diskgroup name list box, select %DG%
Click Apply to save the settings.
Subscribing to and Running the Oracle Service Plan
In this step, you will subscribe to the Service Plan created previously, and also run it.
Copy Management

Management, and then select Oracle
Oracle.
Highlight orcl1
Highlight the orcl1 database row.
Click Protect > Subscribe to Plan > Oracle_DB_Snap_Backup

Subscribed
This subscribes to the Service Plan, however, it will only run at the set scheduled time depicted in the Service Plan
settings. In the next step, you will run the Service Plan.
Run the Service Plan On-Demand
The Service Plan previously created runs on a 24 hour basis, however, you need to test that the replication process
works immediately.
You first need to confirm what other potential databases are subscribed, since you do not want to accidentally run
another database, as an example.
Select Oracle

Plans, and then select Oracle
Oracle.
Oracle_DB_Snap_Backup
Click Oracle_DB_Snap_Backup
Subscriptions
Select Subscriptions
Subscriptions. This displays all the subscribed application objects, you will see just the one Oracle database,
orcl1
orcl1.
Move up one level
Click Oracle
Oracle, to move up one level.
Run
Highlight the Oracle_DB_Snap_Backup Service Plan row.
Click Run
Run.
View Details
Click Details to view the progress.
Note: This task will take approximately 10 minutes to complete.
Click Close when complete.
Review
Once the Oracle_DB_Snap_Backup Service Plan completes, you can confirm that the copy was created successfully.
Oracle_DB_Snap_Backup
Click Oracle_DB_Snap_Backup
Copies
Select Copies
Copies.
You will see only one copy listed, as you ensured that only one copy is maintained during the configuration of the
Service Plan, under the Create local copy settings.
This view outlines which RAC node had the active copy, what the database name is, the date and time of the copy, if
the database was placed into hotbackup mode, which server the copy is mounted to, and additional information.
Note: Since this is a RAC environment, the database may report on either server rhel01 or rhel02, so the accompanying
screen may differ and display a different server name each time the Service Plan runs.
Validating Oracle (optional)
OPTIONAL - Validating the Copy
The following steps are optional, giving you an idea of how to validate changes made to the source volume are
replicated appropriately to the target volume.
Once the Service Plan completes, from the previous step, you can perform the following steps to validate that an
updated table is refreshed on the target.
To begin, in mRemoteNG double-click RHEL01 and RHEL03

RHEL03.
Validate the Table on orcl1
In the RHEL01 session, to connect as the oracle user type:
su - oracle
Perform the same task on RHEL03

RHEL03.
View the Existing Table
You will be in the /home/oracle directory. Confirm this by typing:
pwd
Run the validate.sql script:
./validate.sql
Repeat this task on RHEL03 to confirm the tables match on both servers.
Add Table Entry
In the RHEL01 session, which is the source server, you will run the add.sql script that will prompt you for your name,
add it to the table, and output the new table data.
Type the following:
./add.sql
Type your name, and press Enter

Enter.
Do not repeat this step on RHEL03. You will refresh the database using the AppSync Service Plan, which will update
the table on RHEL03.
Re-run the Service Plan
Next, you will run the Oracle_DB_Snap_Backup Service Plan again, to update the entry you added in the previous step.
Switch to AppSync. Log back in as admin

admin/Password123!
Password123! if necessary.
Navigate to Service Plans > Oracle
Highlight the Oracle_DB_Snap_Backup Service Plan row, and click Run

Run.
Run Complete
When the task is complete, click Close

Close.
Re-validate Table on RHEL03
Once the Service Plan completes, switch to the RHEL03 host.
Run the validate.sql script:
./validate.sql
You will see the newly added entry to the table.
Optionally Clean-up
To clean up the environment, you can run the remove.sql script on RHEL01
./remove.sql
As the database mounted on RHEL03 is read-only, you will need to re-run the Service Plan again to ensure the
database changes on RHEL01 are replicated.
Repurposing Oracle Copies
In this lab you will repurpose the Oracle database, meaning, you will create a 1st generation copy which will serve as a
Gold point-in-time (PiT) copy and then a 2nd generation copy which will be created from that 1st gen copy, mounted
and the database recovered on the mount host. This simulates creating a test and development environment, or for
perhaps report generation, thus alleviating any impact on the production environment.
The purpose of this lab is to familiarize yourself with the repurposing features of AppSync, by creating on-demand
repurposing copies. As a general rule, repurposed copies are not meant for backup and recovery, though 1st
generation copies can be used for such situations.
Objective:
Utilize data repurposing for test and development or reporting purposes on an alternate host.
A Generation 1 copy is created to serve as a Gold copy, a copy that is not mounted or changed in any manner
but can be used for recovery purposes if required.
A Generation 2 copy is created from the Gen 1 copy, mounted, and then recovered in Oracle, thus providing
the secondary environment for repurposing use cases.
Launching AppSync
admin
Password123!
Click Login
Login.
Create 1st Generation Copy
You will now create the 1st generation copy, which serves as a point-in-time (PiT) copy, also referred to as a Gold copy,
which is then used to create the 2nd generation copy.
Management, and then select Oracle
Oracle.
Initiate the Create Repurpose Copy
Select the orcl1 database row.
Click Repurpose
Repurpose, and then click Create Repurpose Copy
Copy.
The Repurpose wizard appears with the first step, called Intention. You can create both 1st and 2nd generation copies
at the same time, however, you will only create a 1st generation copy at this time, and create the 2nd generation copy
in a future step; showing you how to create multiple 2nd generation copies if required.
Accept the defaults, and click Next

Next.
The next step within the Repurposing wizard is to choose similar settings as you would see when setting up a Service
Plan. Here, you can initiate a pre-copy script, configure copy settings, initiate a post-copy script, provide mount and
unmount options, as well as initiating a post-mount script.
In the Oracle-Specific Copy Options area, select Place the database in hot backup mode
mode.
Click Next
Next.
Repurpose - Schedule
Accept the default selection Run Now

Now, and click Next
Next.
Repurpose - Summary
The last step within the Repurpose wizard is to review the settings, and then to initiate the copy. Some settings are
hidden by a scrolling menu.
Confirm the settings, and click Finish to start the process.
You can click Details to expand the process log and view more information on what is occurring in the background.
Ignore any licensing warnings.
Click Close when the process is complete.
Create 2nd Generation Copy
Once the 1st Generation copy is created, any number of 2nd generation copies can be created from that 1st gen copy.
The limit of copies depends on the storage array, and its code level, so please refer to the the array product
documentation for those specifics.
In this section of the lab, you will create a 2nd generation copy, mount it to the Oracle mount host, recover the
database, that is, bring the copied database on line for purposing use cases, such as creating a mirrored environment
for test and development, or for running reports so the production host is not subjected to additional IO.
Initiate the 2nd Generation Repurpose Copy
Click orcl1
orcl1.
1st gen local copy
Click the 1st gen local copy row, and then click Repurpose
Repurpose.
Similar to creating the 1st gen copy, there is a wizard that helps you perform the 2nd generation copy. Since you are
creating a copy from a 1st generation copy, the only option is to create the 2nd gen copy,
Click Next
Next.
Similar to the 1st generation, and Service Plan settings, there are options to configure pre/post-copy scripts, as well
as mount options. The Create 2nd gen copy is always selected by default, and cannot be changed.
Select Unmount previous copy

copy.
Select Mount copy

copy.
In the Mount operation list box, select Mount on standalone server and recover database
database.
In the Mount on Server list box, select rhel03.vlab.local

rhel03.vlab.local.
In the Open-mode list box, select Read-write
Read-write.
Click Next
Next.
Scheduling options
Accept the default Run Now

Now, and click Next
Next.
Repurpose - Summary
Click Finish to complete.
Click Close
Close.
Repurposing Confirmation
You will now see an arrow next to the 1st generation copy, and the 2nd gen copy.
The 2nd gen copy is mounted on the rhel03.vlab.local host.
Lab 5: Managing File System
Replication
Create and Restore Windows File System Copies
In this lab you will create a Service Plan for on-demand copies for backup, and perform a restore operation.
The purpose of this lab is to familiarize yourself with Service Plan options, as well as using the Service Plan by
subscribing a Windows File System so that the copy can be used to restore a deleted file.
Objective:
You will create a Service Plan to create an on-demand copy, not scheduled as preformed in the other two labs, and
then restore a file which is accidentally deleted.
The copy is not scheduled, rather it is an on-demand copy

The copy is created, a source file is deleted, then the copy is restored and validated.
Launching AppSync
Before beginning this lab, close the web browser, and open a new AppSync session. This step is to address occasional
cache issues.
admin
Password123!
Click Login
Login.

Plans, and then select FileSystems
FileSystems.
Click Create
Create. In the Select an existing plan as a template list box, select Bronze
Bronze.
In the Plan Name field, type Windows_FS_Backup
Click OK
OK.
Windows_FS_Backup Service Plan
To modify the Service Plan, click Windows_FS_Backup

Windows_FS_Backup.
You will now see the Settings options in the Service Plan. The Plan Startup is highlighted to begin with. This is where
you can change the Recurrence Type frequency, as well as modify the Recovery Point Objective (RPO), an alerting
mechanism to ensure copies are created in an adequate amount of time.
In the Startup Type area, select On demand

demand.
The next step is to configure Create local copy options.
In the Expiration area, type 1. This will keep only one copy, as the same copy is refreshed for backup purposes, every
day
Click Apply
Apply.
Subscribing to and Running the File System Service Plan
In these steps, you will subscribe to the Service Plan created previously, and also run it in the same step unlike
subscribing and then running the Service Plan in a separate step, as preformed in the previous labs.
File Systems

Management, and then select FileSystems
FileSystems.
When prompted, select Do not display this hint again and click OK
OK.
sqlsource.vlab.local
Click sqlsource.vlab.local
When prompted, select Do not display this hint again and click OK
OK.
M:\
Click M:\
Create copy using plan
Click Create copy using plan

plan, and then select Windows_FS_Backup
Windows_FS_Backup.
This subscribes to the Service Plan, and will also run the plan in the same step.
Close
Click Details to monitor the task progress.
When complete, click Close

Close.
Deleting the File on Production
You have created a copy of productions M:\ drive that contains a file called File System Test File
File. You will now delete
this file on the SQLSOURCE server, then restore the copy previously created.
In mRemoteNG
mRemoteNG, click SQLSOURCE
SQLSOURCE.
Open Windows File Explorer

Explorer.
Open the E:\ Drive
Double click FileSystem (M:)
Delete the File System Test File
Right-click File System Test File

File, and then select Delete.
Restoring the Copy
Since the file has been deleted, and this is to simulate a file that is not recoverable form the recycle bin, you now need
to restore it from the copy previously taken. In order to do this, you will perform a Restore operation. Restore effects all
objects on the same storage array LUN, though in this lab, this volume being restored contains nothing else which will
be overwritten. Always be cautious of the effected entities when restoring.
First, switch to AppSync
Windows_FS_Backup
Navigate to Service Plans > FileSystems.
Click Windows_FS_Backup
Windows_FS_Backup.
Copies
Click Copies
Copies, highlight the M:\ row
row, and click Restore
Restore.
Filesystem Restore Wizard
The Filesystem Restore Wizard will appear. Click Next

Next.
Note: If you do not see a copy, close the browser, and open AppSync again.
Summary
Review the Summary, and click Finish to begin the restoration.
Restore complete
After the restore completes, click Close
Validate the Restore
With the restore now complete, File System Test File has been recovered to the M:\ drive location.
Open File Explorer on the SQLSOURCE host.
Open the M:\ drive
Confirm File System Test File has been successfully restored.
Lab 6: AppSync 3.0 Installation
(Optional)
Installing AppSync 3.0
Connecting to the environment
On the Lunchpad desktop, double-click mRemoteNG

mRemoteNG.
Connect to Windows server
Double-click AppSync02
File Explorer

Explorer.
Launch the installation program
Navigate to c:\software > AppSync-3.0.0.0
Double-click AppSync-3.0.0-win-x64, and click Run to start the installation process.
Introduction
When the wizard appears, click Next

Next.
License Agreement
Select I accept the terms of the License Agreement

Agreement, and click Next
Next.
Choose Install Folder
Click Next
Next.
AppSync Administrator
In the Password fields, type Password123!
Click Next
Next.
AppSync Ports
Click Next
Next.
Pre-Installation Summary
Review the summary, and click Install

Install.
Install Complete
When the install is complete, click Next

Next.
Information
Click Done
Done.
Log into AppSync
After the installation is complete, AppSync will launch automatically.
At the Your Connection is not Private message, click Advanced and Proceed to appsync02.vlab.local
appsync02.vlab.local.
admin
Password123!
Click Login
Login.
Registering Unity storage array
Add Storage
The first time you log in, a dialog box will be displayed, requesting that you add storage. Click OK to Add storage now
now.
Add the Unity storage array
Click Add
Add, and then select Unity
Unity.
Enter the appropriate Unity credentials
Specify the following:
In the Management Interface field, type 192.168.1.99
In the Global user name field, type admin
Click OK
OK.
Storage Infrastructure
The Unity array is now registered with AppSync.
What's next?
You have now completed a basic AppSync 3.0 installation and registered your first storage array. Refer to Lab 1,2,3,4
and 5 if you want to explore additional AppSync 3.0 features.
Conclusion
Conclusion
This concludes the AppSync 3.0 for SQL, Oracle, and Windows File Systems vLab. You have learned how to add
resources such as a storage arrays, a vCenter server, Linux and Windows hosts. You have created customized service
plans, subscribed application objects to those service plans, and then run those service plans. In addition, you have
validated copies and restored a Microsoft SQL database. You have learned how to repurpose copies for a variety of
use cases, such as testing and development or reporting.
Additional Solution Information
Business Challenge
RainPole
RainPole is uniquely positioned in the Public Cloud hosting arena as one of the first companies offering cloud services
as their core business model. RainPole is preparing to position itself as the logical option to the largest players by
offering customers more control over their cloud environment. RainPoles entire virtualization platform is based on
VMware technologies.
RainPole needs to provide their customers with a simple, SLA driven solution. Customers are looking for:
Simplified management of multiple replicas for different purposes

Technology that is aware of, and integrates with, business applications
An easy process for creation, refresh, recovery, expiration and scheduling of disk-based replicas
Automatic discovery of changes and notification of failures
Fast simple recover of data
Solution
Copy Management Solution
RainPole's IT team has selected EMC AppSync as their copy management solution.
This solution provides the following:
Eliminate backup window: By using Microsoft application protection frameworks such as VSS, production can
be backed up without impacting performance, allowing customers to completely eliminate backup windows
by taking snapshots of the production volumes and then backing up the secondary copy.
Instant restore capabilities: Many of EMCs customers have a need to restore data quickly for restore
purposes or for test/development/reporting purposes. You can restore in minutes not hours, and restore on
the SAN not the LAN (no more copying huge files over the LAN).
Tiered application RTO and RPOs: EMCs strategy is not just about protecting applications with just snapshots
for backup acceleration and operational recovery, it leverages advanced features for data repurpose
Automated, RPO-based protection: AppSync allows you to easily assign tiered service plans to an application.
Service plans are a better way to protect your applications because there are only three service plans to
choose from (Gold, Silver, Bronze). The Gold and Silver plans incorporate remote technology, such as
RecoverPoint. You can run them with a schedule (e.g., replicate data every day at 12 p.m.), or define a
recovery point objective (e.g., replicate data so that you have a copy every three hours). Service plans also
can be edited, which allows you to customize and control each step of the copy creation process.
Confident application recovery: AppSync allows you to verify your data before sending it off to disk or tape
and allows you to set RPO alerts so that if your RPO goals were exceeded, you would receive an alert.
AppSync
EMC AppSync offers a simple, self-service application protection, SLA driven approach for protecting a variety of
applications residing on EMC Primary storage.
Application environments are dynamic, and AppSync responds by following the application as it moves within the
virtual infrastructure therefore assuring SLAs are maintained. After defining service plans (e.g. bronze = local array
replication), application owners can protect and make space-efficient copies of production data without involving IT,
and recover data quickly.
Application are protected by subscribing them to a Service Plan. A Service Plan is comprised of multiple phases such
as create copy, mount copy, validate copy and so on. The default service plans offer tiered levels of protection. For
example, the service plans for protection range from on-demain local copies, created as needed, to plans that
automate copies every three hours, seven days a week. Service plans can be changed to match requirements.
AppSync provides an application protection monitoring service that generates alerts when the SLAs are not met. It also
generates reports that tell whether data is protected, recoverable and compliant with service level agreements.
Troubleshooting & Tips
These are basic troubleshooting tips.
Mounting and Restoring
Be sure to close any open file, file browser window, or command prompt before performing any mount, unmount, or
restore operation.
Missing Items
Depending on the size of your viewing screen, some parts of the AppSync UI may not be visible and you may need to
scale the display window in order to see the navigation buttons, or the browser cache may need to be refreshed. It has
been experienced that some users have tried to select a copy for restore, but that copy was not visible in the restore
window. In order to correct this, follow the following steps.
Within the IE browser, open Internet Options

Navigate to Content
Content, and then click Settings under AutoComplete
Click Delete AutoComplete history
Ensure every option is selected, and click Delete
Close the remaining dialog boxes, by clicking OK
Running out of disk space on Oracle server
If the lab environment is run for extended periods of time, such as more than a day or two, Oracle archive log files may
have filled up the disk space. You will need to run a script to clean up old archive logs. Follow these steps to clean the
archive logs.
In mRemoteNG
mRemoteNG, open RHEL01
Type:
su - oracle
Press Enter
Enter.
Type:
./clean.sh
Press Enter
Enter.

AppSync 3.0 For SQL, Oracle and Windows File Systems

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

AppSync 3.0 For SQL, Oracle and Windows File Systems

Diunggah oleh

Hak Cipta:

Format Tersedia

APPSYNC 3.

AppSync 3.0 for SQL, Oracle and Windows File Systems

Lab Overview ................................................................................................................................................ 6

Lab Credentials ................................................................................................................................................8

Lab Scenario ....................................................................................................................................................9

Lab 1: Browsing the AppSync Console ........................................................................................................ 11

Lab 3: Managing SQL.................................................................................................................................. 37

Repurposing SQL Copies ................................................................................................................................75

Lab 4: Managing Oracle .............................................................................................................................. 94

Validating Oracle (optional) .........................................................................................................................112

Repurposing Oracle Copies ..........................................................................................................................119

Lab 5: Managing File System Replication .................................................................................................. 134

Lab 6: AppSync 3.0 Installation (Optional)................................................................................................ 152

What's next? ................................................................................................................................................167

Conclusion ............................................................................................................................................... 168

Additional Solution Information................................................................................................................ 170

Troubleshooting & Tips ................................................................................................................................174

The environment for this lab includes the following:

1 x Microsoft Windows 2012 R2 Domain Controller

This vLab includes the following:

Lab 1: Browsing the AppSync Console

Adding the VNX storage array

Two Windows SQL database servers

Lab 3: Managing SQL

Lab 4: Managing Oracle

Lab 5: Managing File System Replication

Creating a Service Plan for on-demand copy testing on an alternate host

Installing AppSync 3.0

Connecting to the environment

On the desktop, double-click mRemoteNG

Open the AppSync Server

In the Connections pane, double-click AppSync

On the desktop, double-click AppSync

Click Proceed to appsync.vlab.local (unsafe)

Use the following credentials

Clear Add storage now and click OK

Log into AppSync as admin if not already logged in

Use the following credentials:

Add the VNX storage array

In the Add VNX area, specify the following:

In the SPA field, type 192.168.1.30

In the SPB field, type 192.168.1.31

In the Global user name field, type sysadmin

In the Password field, type sysadmin

In the Add vCenter Server area, specify the following:

In the Name field, type lp01.vlab.local

In the Username field, type administrator@vlab.local

In the Password field, type Password123!

Hover over Settings, and then select Servers

Server Names/IP Address: sqlsource.vlab.local and sqltarget.vlab.local

Domain\User Name: vlab\administrator

When the deployment is complete, click Close

Server Names/IP Address: rhel03.vlab.local

Domain\User Name: root

When the deployment is complete, click Cancel

Use the following credentials:

Creating a Service Plan

At the bottom of the screen, click Create.

In the Plan Name field, type SQL_DB_Snap_Backup

Select Service Plan

Click Create local copy

Configure the Mount Copy Options