Home

DataFRAME Remote Data Protection Pack User Manual

1. Primary Start At 12 09 2004 04 23 02 PM setup Z Recur Every 1 Days v Remote setup Primary Setup Remote Setup 2al Management Group Transaction_Data Volume Name CreditData Snapshot Name Schedule Name Number Thresholds for Primary Snapshots 9 0 Size GB Hard Threshold 3 0 Soft Threshold 3 0 Retention for Primary Snapshots Retain Maximum Of 2 Snapshots Retain Snapshots For Figure 2 15 Creating a new remote snapshot schedule Remote Snapshot The time zone displayed in the Remote Snapshot Schedule Schedule area is the time zone set on the DataFRAME through which you are logged in to the management group Best Practice Set all DataFRAMEs in the management group to the same time zone Reset the management group time before creating a remote snapshot schedule For detailed information see Resetting the Man agement Group Time in the chapter Working with Management Groups in the DataFRAME SAN Software Manual 1 Select a start date and time for the schedule 2 Optional Select a recurrence interval for the schedule Using Remote Data Protection Pack 33 Scheduling Remote Snapshots Configuring the Primary Volume and Snapshots Configuring the Remote Volume and Snapshots On the Primary Setup tab specify the hard threshold and the soft threshold for the primary snapshots Specify the retention polic
2. 52 Using Remote Data Protection Pack Sample Remote Data Protection Pack Configurations Overview Because of the flexibility provided by Remote Data Protection Pack you can use the functionality ina variety of configurations that are most suitable for your requirements The sample configurations described in this chapter are only a few possible ways to use Remote Data Protection Pack for business continuance backup and recovery data migration and data mining Usi ng Remote Business continuance comprises both disaster Data recovery and high availability of data Using Remote Data Protection Pack for business continu Protection ance data is stored off site and is continuously Pack for available in the event of a site or system failure Business Continuance Achieving High Creating remote snapshots in remote locations Availabilit with application based scripting can ensure that a y database applications such as SQL Server Oracle and Exchange have continual access to data volumes if production application servers or data volumes fail Sample Remote Data Protection Pack Configurations 53 Using Remote Data Protection Pack for Business Continuance Configuration for High Availability Using off site remote snapshots of your production volumes you can configure a backup application server to access those remote snapshots Off site remote snapshots particularly when supple mented with synchronous volum
3. Figure 2 7 Viewing the remote snapshot Viewing a List of You can view a list of remote snapshots associated Remote with management groups clusters volumes or snapshots Snapshots 1 Click the item for which you want to view the list of remote snapshots 2 Click the Remote Snapshot tab The tab view opens shown in Figure 2 8 The report on the tab lists both management groups and all the snapshots The other columns report status information about the remote snapshots as described in detail in Monitoring Remote Snapshots on page 27 Details Managers Clusters Authentication Groups Volume Lists Register Times Remote Snapshot Primary Man Primary Sna Remote Man JRemote Sna Complete Elapsed Time Data Cop Rate State Transaction CredDataRS1 TransData_ May05RemSS 100 3m 14s 61 5 MB 2 596 Kbisec COMPLETE PriSS_0601 TransData_ Bkup0601 100 imis 61 5 MB 8 259 Kbisec COMPLETE Figure 2 8 Viewing the list of remote snapshots Using Remote Data Protection Pack 23 Working with Remote Snapshots Setting the Remote Bandwidth The remote bandwidth sets the maximum rate for data transfer between management groups The remote bandwidth setting is the upper limit of the range of data transfer that is the copy rate will be equal to or less than the rate set The remote bandwidth specifies the speed at which data is received from an
4. Remote Snapshot An identical copy of a primary snapshot The remote snapshot is located on the same cluster as the remote volume Remote Copy Pair The primary volume and its associated remote volume Failover The process by which the user transfers operation of the application server over to the remote volume This can be a manual operation or it can be scripted Acting Primary Volume Failback The remote volume when it assumes the role of the primary volume in a failover scenario After failover the process by which the user restores the primary volume and turns the acting primary back into a remote volume Failover Recovery After failover the process by which the user chooses to fail back to the primary volume or to make the acting primary into a permanent primary volume Synchronize The process of copying the most recent snapshot from the primary volume to a new remote snapshot On failback synchronization is the process of copying the most recent remote snapshot back to the primary volume The Console displays the progress of this synchronization Split Mirror A split mirror is a remote snapshot whose relationship to the primary volume has been severed Split mirrors are usually created for one time use and then discarded 2 Understanding Remote Data Protection Pack Remote Data Protection Pack Overview How Remote Data Replicating data using Remote Data Protecti
5. mpc DataFRAME Remote Data Protection Pack User Manual Copyright Limited Warranty This manual is the confidential and proprietary product of LeftHand Networks Inc Any unauthorized use reproduction or transfer of this manual without the express written consent of LeftHand Networks Inc is strictly prohibited This manual is designed to provide accurate and authoritative information in regard to the use of the Network Storage Module the SAN iQ Centralized Management Console and the SAN iQ software proprietary products of LeftHand Networks Inc Information in this document is subject to change without notice and does not represent a commitment on the part of LeftHand Networks Inc The software described in the document is furnished under a license agreement The software may be used or copied only in accordance with the terms of the agreement It is against the law to copy the software on any medium except as specifically allowed in the license or nondisclosure agreement The software distributed to you by LeftHand Networks Inc includes certain software packages indicated to be subject to one of the following open source software licenses GNU General Public License GPL the GNU Lesser General Public License LGPL or the BSD License each an OSS Package Please refer to the license_readme file included with the software for additional information regarding the application of these licen
6. Remote Remote Snapshot 1 Snapshot 2 Snapshot Backup Site Production Site 2 Figure 3 8 Off site backup and recovery example configuration How This Configuration Works for Off site Tape Backup Best Practices Retain the most recent primary snapshots in the primary cluster Depending on how long you retain the copies of the remote snapshots you can retrieve data directly from recent remote snapshots rather than going to tape backups Otherwise retrieve data as you normally would from the tape backup By keeping snapshots on your primary volume you can quickly roll back a volume to a previous snapshot without accessing off site backups m When you create a schedule for Remote Data Protection Pack you specify a number of primary and remote snapshots that you want to retain You can retain primary snapshots to facilitate easy rollback of the primary volume Retention of snapshots will affect the amount 66 Sample Remote Data Protection Pack Configurations Using Remote Data Protection Pack for Off site Backup and Recovery Example configuration Achieving Non Destructive Rollback of space that is used in the cluster of DataFRAMEs so balance the number of snapshots to retain with the amount of space you are willing to use To roll back to a snapshot that you did not retain you can still access remote snapshots or tape backups a Retain remote snapshots in the backup location to facilitate fast reco
7. Retention Retain either Maximum number of snapshots Set period of time minutes hours days or weeks Remote Setup Management Group The management group to contain the remote snapshot Volume The remote volume for the remote snapshots Retention Retain either Maximum number of snapshots This number equals completed snapshots only In progress snapshots take additional space on the cluster while they are being copied Also the system will not delete the last fully synchronized snapshot For space calculations figure N 2 with N maximum number of snapshots Set period of time minutes hours days or weeks Understanding Remote Data Protection Pack 13 Using Schedules for Remote Data Protection Pack 14 Understanding Remote Data Protection Pack Using Remote Data Protection Pack Remote Data Protection Pack Overview Registering Remote Data Protection Pack Working with Remote Snapshots Creating a Remote Snapshot This chapter provides instructions for registering configuring and using Remote Data Protection Pack for business continuance backup and recovery and failover For information about how Remote Data Protec tion Pack works and how to plan capacity for Remote Data Protection Pack see Chapter 1 Understanding Remote Data Protection Pack Remote Data Protection Pack is an add on module You must purchase a Remote IP Copy license to use Remo
8. and designate a different backup site The steps are similar to those for initially configuring Remote Data Protection Pack 1 Create a remote snapshot or a remote snapshot schedule on the acting primary volume 2 Make anew remote volume on the new backup site as part of creating that remote snapshot or remote snapshot schedule 3 Reconfigure scripts for failover on the application servers Rolling back a volume from a snapshot is the method for reverting to an earlier copy of the data on a volume Rolling back destroys any snapshots that were created after the snapshot that is rolled back to Using Remote Data Protection Pack 47 Rolling Back Primary and Remote Volumes Rolling Back a Rolling back a primary volume to a primary Primary Volume snapshot replaces the original primary volume with a read write copy of the selected primary snapshot The new volume has a different name than the original and the original volume is deleted Prerequisites Stop applications from accessing the volume Delete all snapshots that are newer than the snapshot you are rolling back from Warning After rolling back a volume to a snapshot you lose all data that was stored since the rolled back snapshot was created Warning Any uncompleted remote copy snapshot that is newer than the snapshot that you are rolling back to will be cancelled 1 Loginto the management group that contains the primary volume that you want
9. Original Production Site 2 Synchronize the Data Synchronize the snapshots OrigPrimarySS 0 and ActPrimarySS 0 created in Steps 2 and 3 of Table 2 3 as appropriate for the application If the original primary volume is not available designate a new primary volume synchronize the data from the acting primary volume and configure the remote snapshot schedule on the new primary volume 1 Stop the application that is accessing the acting primary volume 2 Create a remote snapshot of the acting primary volume and make a new primary volume on the original production site as part of creating that remote snapshot 3 Convert the remote volume into a primary volume 46 Using Remote Data Protection Pack Rolling Back Primary and Remote Volumes Setting Up a New Production Site Making the Backup Site into the New Production Site Rolling Back Primary and Remote Volumes 4 Make the acting primary volume into the remote volume This creates a snapshot of that volume 5 Configure a new snapshot schedule on the new primary volume 6 Reconfigure scripts for failover on the application servers Setting up a new production site involves creating a new primary volume and syncing up the acting primary volume before returning it to its original state as a remote volume The steps are the same as those for creating a new primary volume at the original production site Turn the backup site into the new production site
10. a new primary snapshot of the primary volume and a remote snapshot of the remote volume It then copies the data from the primary snapshot to the remote snapshot This process will recur according to the schedule When editing a remote snapshot schedule you can change the following items Schedule description start date and time recurrence policy a Primary Setup primary snapshot thresholds retention policy Remote Setup retention policy Note Be certain to plan threshold changes carefully See the chapter on snapshots in the DataFRAME SAN Software Manual for detailed information about threshold requirements 1 Select the primary volume that has the schedule you want to edit 2 Click the Remote Snapshot Schedules tab Using Remote Data Protection Pack 35 Scheduling Remote Snapshots 3 Select from the list the schedule to edit From the Tasks menu select Edit Schedule The Edit Remote Snapshot Schedule window opens shown in Figure 2 17 5 Change the desired information 6 Click OK Edit Remote Snapshot Schedule E Edit Remote Snapshot Schedule Name Description Remote Snapshot Schedule Time Zone Mountain Standard Time Start At 12 09 2004 04 45 02 PM V Recur Every 30 Primary Setup Remote Setup Management Group Transaction_Data Volume Name CreditData Snapshot Name Schedule Name Number Thresholds for Primary Snapshots Size 9 0 GB Hard Thr
11. disaster recovery Remote and provide a consistent predictable update of Sna psh ots data for remote backup and recovery Using Remote Data Protection Pack 31 Scheduling Remote Snapshots Creating the Schedule The first step in scheduling remote snapshots is planning for creating and deleting primary and remote snapshots Issues that require planning include m Recurrence frequency Snapshot thresholds a Retention policies For detailed information about these issues see Planning for Remote Data Protection Pack on page 7 Once you have defined your plan you are ready to create the remote snapshot schedule a First create the schedule m Second configure the primary volume and snapshot and a Third create the remote volume and configure remote snapshots 1 Right click the volume for which you want to create the remote snapshot schedule and then select Remote Data Protection Pack gt New Remote Snapshot Schedule The New Remote Snapshot Schedule window opens shown in Figure 2 15 2 Type a name for the schedule 3 Optional Type a description for the schedule 32 Using Remote Data Protection Pack Scheduling Remote Snapshots New Remote Snapshot Schedule New Remote Snapshot Schedule Remote RC_Sch_0 snapshot Description schedu le Remote Snapshot Schedule Name Time Zone Mountain Standard Time
12. g3 Primary i 3 Volume Storage Subnet Primary Snapshot Snapshot 3 00 PAS Remote Primary Snapshot Snapshot 4 00 Pat 1 00 PM Remote Primary Snapshot Snapshot Snapshot 77 00 AM 11 00 AM 14 00 AM Figure 3 11 Non destructive rollback from the remote snapshot Best Practices Roll back the primary To ensure that Remote Data Protection Pack snapshot and keep continues to operate roll back the primary the remote snapshots Volume as follows as a backup 1 Preserve the current state of the primary volume that you want to roll back by creating a one time manual remote snapshot of it 2 Roll back the volume Remote snapshots remain intact 3 After the primary volume is rolled back scheduled creation of remote IP copies will continue Sample Remote Data Protection Pack Configurations 71 Using Remote Data Protection Pack for Data Migration Using Remote Data Protection Pack for Data Migration Achieving Data Migration Configuration for Data Migration Remote Data Protection Pack allows a one time migration of data from one application server to another without interrupting the production appli cation server This capability supports a number of uses such as data mining or content distribution You can use Remote Data Protection Pack to make a complete copy of one or more volumes without interrupting access to the original volumes This type of data migration allows you to copy an entire data set f
13. or remote snapshot schedules When you have management groups that no longer share remote snapshots or remote snapshot schedules you can disassociate those management groups Disassociating management groups destroys all the shared knowledge between those groups 1 Log in to both management groups that you want to disassociate Right click the remote management group and select Edit Management Group The Edit Management Groups window opens shown in Figure 2 24 Edit Management Group Edit Management Group Group Name Local Bandwidth 32763 Kb Sec Remote Management Groups ManagementGr LoggedIn__ Remote Bandwi Connected Transaction_D Yes 32768 Kbisec Yes Disassociate Edit Bandwidth Cancel Figure 2 24 Editing a management group 3 Select the management group or groups you want to disassociate Click Disassociate A confirmation message opens describing the results of disassociating the management groups Using Remote Data Protection Pack 51 Disassociate Remote Management Groups Warning Disassociating the management groups cancels any in progress remote snapshots and deletes all snapshot schedules that are shared between the selected management groups 5 Click OK The Edit Management Group window opens and the remote management group you disas sociated from is gone from the list 6 Click OK to return to the Network view
14. process with a moving graphic of pages from the primary to the remote snapshot as illustrated in Figure 1 2 The pages move in the direction of the data flow from primary to remote snapshot a Transaction_Data a a TransData_Remote amp a TransData04 amp a TransData_BkUp04 z Boulder 1 pa Boulder 2 ae Denver 1 Denver 2 RemYolCDO04 Q 4 k Copying from the Remote snapshot Primary snapshot to Primary snapshot the remote snapshot Figure 1 2 Icons depicting the primary snapshot copying to the remote snapshot Graphical Legend for Remote Data Protection Pack Icons The graphical legend available from the Help menu depicts the icons associated with Remote Data Protection Pack Figure 1 3 displays the Remote Data Protection Pack states icons from the graphical legend 4 Understanding Remote Data Protection Pack Remote Data Protection Pack Overview Snapshot is primary Remote Data Protec Snapshot is remote tion Pack graphics from the Graphical pemote snapsnotpal Legend in the Figure 1 3 Icons for Remote Data Protection Pack as displayed in the Graphical Legends window Remote Data Remote Data Protection Pack is asynchronous Protection Pack replication of data Volume replication is synchronous replication Volume replication is and Volume described in detail in the DataFRAME SAN Software Replication Manual in the chapter Working
15. remote volume a Create a new remote volume during creation of a remote snapshot Create anew volume from the cluster Details panel and then select the Remote option on the New Volume window For more information about the three methods of creating remote volumes see Creating a Remote Volume on page 18 Usi Ng Scheduled remote snapshots provide high Sc hed u es for availability for business continuance disaster recovery and provide a consistent predictable Remote Data update of data for remote backup and recovery Protection Pack 8 Understanding Remote Data Protection Pack Using Schedules for Remote Data Protection Pack Planning the Remote Copy Schedule Recurrence When creating a remote snapshot schedule a number of considerations are important to plan All of these issues impact the amount of storage available in the system How often do you want the snapshots created The recurrence frequency must account for the amount of time it takes to complete a remote snapshot For example if your recurrence schedule is set for a new snapshot every 4 hours you should ensure that the time to copy that snapshot to the remote location is less than 4 hours a Test the Time Required for Copying a Snapshot One way to check the time required to copy a snapshot is to run a test of the actual process In the test you take two remote snapshots of the primary volume Since the first remote snapshot copies the
16. via the remote volume m The remote volume is a pointer to the remote snapshot The remote volume has a size of 0 Snapshots Once data is copied from the primary snapshot to the remote snapshot the remote snapshot behaves as a regular snapshot DataFRAME m Active monitoring of each DataFRAME notifies you when copies complete or fail Active monitoring also notifies you if a remote volume or snapshot is made primary or if the status of the connection between man agement groups containing primary and remote volumes changes Planning the In order to create a remote snapshot Remote Snapshot you must be logged in to both the manage ment group that contains the primary volume and the management group containing the Understanding Remote Data Protection Pack 7 Using Schedules for Remote Data Protection Pack target cluster where the remote snapshot will be created you must designate or create a remote volume in that remote management group m you must have enough space on the target cluster for the remote snapshot Logging in to the Log in to both management groups before you Management Group begin If you are creating the remote volume and remote snapshot in the same management group as the primary volume then you only need to log in to that management group Designating or You can create a remote volume by any of the Creating the Remote following methods Volume a Make an existing volume into a
17. Split Mirror Centralized Management Console E xj Rolling the volume back to this snapshot will delete the volume Before proceeding you must manually delete all snapshots of the volume that are newer than this snapshot To preserve the volume and snapshots that you need to delete create a copy of the volume and snapshots before rolling the volume back Are you sure you want to roll the volume back to this snapshct o Cancel Figure 2 23 Verifying the primary volume roll back 7 Click OK The primary snapshot version of the primary volume is restored as a read write volume 8 Reconfigure application servers to access the new volume A remote volume cannot be rolled back In order to roll back a remote volume you must make the remote volume into a primary volume Use remote snapshots to create split mirrors for data mining and data migration A split mirror isa one time remote snapshot created from the volume containing the data you want to use or move Split mirrors are usually created for one time use and then discarded To create a split mirror create a remote snapshot a create a volume list for that snapshot a create an authentication group for client access configure client to access the remote snapshot 50 Using Remote Data Protection Pack Disassociate Remote Management Groups Disassociate Remote Management Groups Management groups become associated when linked by remote snapshots
18. To cancel a remote snapshot that is in progress 1 Click the primary or remote snapshot The snapshot tab view opens 2 Click the Remote Snapshot tab 3 Select from the list the remote snapshot you want to cancel 4 Click Cancel Remote Snapshot A confirmation message opens 5 Click OK Editing a Remote You can edit the description of a remote snapshot Snapshot You can also change the hard and soft thresholds but it is not recommended 1 Loginto the management group that contains the remote snapshot Using Remote Data Protection Pack 25 Working with Remote Snapshots 2 Right click the remote snapshot and select Edit Snapshot from the menu The Edit Snapshot window opens shown in Figure 2 11 Edit Snapshot Edit Snapshot Snapshot Name Description Created Cluster Replication Level Replication Priority Size Hard Threshold Soft Threshold Auto Grow Checksum Data Figure 2 11 Editing a remote snapshot 3 Change the desired information and click OK Deleting a Remote 1 Loginto the management group that contains Snapshot the remote snapshot 2 Right click the remote snapshot and select Delete Snapshot from the menu A confirmation message opens 3 Click OK 26 Using Remote Data Protection Pack Monitoring Remote Snapshots Monitoring Remote Snapshots Configuring Active Monitoring Alerts for Remote Data Protection Pack M
19. Yolume Remote Make Volume Remote WARNING Changing this primary volume to a remote volume can result in data loss if any hosts are accessing this volume Disconnect any hosts before completing this change Volume CashData in management group Transaction_Data is currently a primary volume When it is changed to a remote volume a snapshot will be created with the name below to save any data currently on the volume Do you want to make this volume a remote volume Snapshot Snapshot Description Snapshot_O Figure 2 19 Creating a snapshot before making a primary volume into a remote volume 5 Type a name for the snapshot that will be created This snapshot preserves any existing data on the volume Optional Type a description for the snapshot Click OK The snapshot is created and the volume becomes a remote volume The Edit Remote Volume window opens again with the editable fields enabled as shown in Figure 2 20 Using Remote Data Protection Pack 39 Scheduling Remote Snapshots Making a Remote Volume Into a Primary Volume y Edit Remote Yolume Edit Remote Volume Type Primary Remote Volume Name Description Created Cluster TransData_BkUp Replication Level None Replication Priority Size Hard Threshold Soft Threshold Auto Grow Off Auto Manual Checksum Data No Figure 2 20 Final
20. able Create a new primary volume synchronize the data with the acting primary volume and then return the acting primary volume to a remote volume Synchronizing the 1 Create Snapshots of Data Data Between the First you create snapshots that contain the data Acting Primary that you need to synchronize The steps to create Volume and the those snapshots are described in Table 2 3 Original Primary Volume Volumes and Volumes and Snapshots on Snapshots on Primary Manage Remote Manage What This Step Action Activity ment Group ment Group Accomplishes 1 Stop applications that are accessing the volumes Table 2 3 Creating snapshots of data to synchronize Using Remote Data Protection Pack 45 Resuming Production After Failover primary volume into the remote volume This auto matically creates a snapshot of the acting primary volume Volumes and Volumes and Snapshots on Snapshots on Primary Manage Remote Manage What This Step Action Activity ment Group ment Group Accomplishes 2 Make a snapshot OrigPrimaryVol_0 Creates a snapshot of the original OrigPrimarySS 0 of the original volume primary volume that includes the data from 1 00 1 30 p m 3 Make the acting RemoteVol_0 Returns the remote ActPrimarySS 0 management group to its original con figuration Table 2 3 Creating snapshots of data to synchronize Creating a New Primary Volume at the
21. an primary snapshots when setting your retention policies Note If you retain more remote snapshots than primary T snapshots the remote snapshots become regular snapshots when their corresponding primary snapshots are deleted You can identify them as remote snapshots by their names since the naming convention is estab lished as part of creating the remote snapshot schedule Best Practices Retain at least two primary snapshots to ensure that only incremental copying is required for primary snapshots m Review your remote copy schedule to ensure that the frequency of the remote copies cor relates to the amount of time required to complete a copy Use the checklist in Table 1 5 to help plan scheduled remote snapshots 12 Understanding Remote Data Protection Pack Using Schedules for Remote Data Protection Pack Scheduled Remote Data Protection Pack Planning Checklist Table 1 5 Scheduled Remote Data Protection Pack Planning Checklist Configuration Category Parameters Snapshot Schedule Start Time Start date mm dd yyyy and Start time mm hh ss for the schedule to begin Recurrence m Recurrence v Recurrence is a yes no choice You can schedule a remote snapshot to occur one time in the future and not have it recur m Frequency minutes hours days or weeks Primary Setup Hard Threshold Set the hard threshold and soft threshold for the Soft Threshold primary snapshot
22. ant tab views 3 Optional Type in a description of the snapshot 4 Optional Change the hard and soft thresholds for the snapshot Using Remote Data Protection Pack 17 Working with Remote Snapshots 5 Click OK to return to the New Remote Snapshot window The information for the primary snapshot is filled in as shown in Figure 2 3 At this point the primary snapshot has been created New Remote Snapshot xi New Remote Snapshot a Primary Management Group Transaction_Data Volume Name CreditData Snapshot Name Snap1CredData New Snapshot Remote Management Group TransData_Remote Y Volume Name v New Volume Snapshot Name Snapshot_O Snapshot Description Figure 2 3 New primary snapshot created Creating a Remote If you have already created the remote volume Volume select the management group and existing remote volume in the Remote section of the New Remote Snapshot window Then go to Completing the Remote Snapshot on page 21 You can create a remote volume by any of the following methods a Make an existing volume into a remote volume a Create a new remote volume during creation of a remote snapshot a Create a new volume from the cluster Details panel and then select the Remote option on the New Volume window 18 Using Remote Data Protection Pack Working with Remote Snapshots Making an existing volume into a remote volume Selecting an existing vo
23. apshot the status says Read only not enough space in cluster to start copy How long do you want to retain the primary snapshots The remote snapshots You can set different retention policies for the primary and remote snapshots For example you can choose to retain 2 primary snapshots and 5 remote snapshots The number of snapshots retained refers to completed snapshots The system will never delete the last fully syn chronized remote snapshot Under some circumstances such as unpredictable network speeds or varying snapshot size a remote snapshot schedule may create primary snapshots more frequently than the remote copy process can keep up with The retention policies for scheduled remote copies ensure that such factors do not cause primary and remote snapshots to become unsynchronized Regardless of the retention policy defined for scheduled remote copies up to 2 10 Understanding Remote Data Protection Pack Using Schedules for Remote Data Protection Pack additional snapshots may be retained by the system at any given time These two additional snapshots include the snapshot that is in the process of being copied and the last fully synchronized snapshot A fully synchronized snapshot is one that has completed copying so that the remote snapshot is a complete mirror of its corresponding primary snapshot Up to two additional snapshots may be retained by the system at any given time Because the system will
24. as shown in Figure 2 21 Using Remote Data Protection Pack 41 Scheduling Remote Snapshots Edit Remote Yolume Edit Remote Volume Type Primary Remote Volume Name Description Created Cluster TransData_BkUp Replication Level None Replication Priority Size Hard Threshold Soft Threshold Auto Grow Off Auto Manual Checksum Data No Edit Volume Type Volume Name Description Created Cluster Replication Level Replication Priority Size Hard Threshold Soft Threshold Auto Grow Checksum Data Remote volume with editable fields enabled Selecting Primary changes the volume to a primary volume with all fields greyed out Figure 2 21 Making a remote volume into a primary volume 4 Click OK The Edit Volume window displays the editable fields enabled You can edit everything but the name and created date and time 5 Make any required changes i e to the size and hard and soft thresholds 6 Click OK The volume becomes a primary volume 42 Using Remote Data Protection Pack Configuring Failover Configuring Failover Planning Failover Using Scripting for Failover Resuming Production After Failover Configuring Remote Data Protection Pack for failover provides for business continuance and high availability When configuring failover you take into consideration both the failover path and the recover
25. can be off line and your primary volume will remain intact At the backup location you can also use synchro nous replication to protect your remote volume against DataFRAME failure a Inthe production location create a cluster of 3 DataFRAMEs all with managers a Create volumes on the cluster and set the replication level to 2 a Create a schedule for making remote snapshots of the primary volume Set the recurrence to every 4 hours and retention of remote snapshots to 2 days Note You can use the same volume replication configuration on the remote volume as well However this replication is configured independently of the volume replication configured on the primary volume If one of the DataFRAMEs in the primary location fails the primary volume will still be available If all of the DataFRAMEs fail or if the application server fails then you can recover data from the remote snapshots or tape backups in the off site location 64 Sample Remote Data Protection Pack Configurations Using Remote Data Protection Pack for Off site Backup and Recovery Using Remote Data Protection Pack for Off site Backup and Recovery Achieving Off site Tape Backup Configuration for Off site Backup and Recovery For backup and recovery systems Remote Data Protection Pack can eliminate the backup window on an application server Using scripting configure the DataFRAME EBSD Driver for Linux driver to mount remote snapsh
26. completed N A for in progress copies Data Data Copied MB GB or TB Amount of data copied so far in smallest unit size Using Remote Data Protection Pack Scheduling Remote Snapshots Table 2 1 Values for Remote Data Protection Pack Details window Statistic Values Data Remaining MB GB or TB Amount of data remaining to be copied in smallest unit size Current Rate Kb sec Current rate of data being copied in Kb second This rate is recalculated regularly throughout the remote copy process N A If not yet available or completed Avg Rate Kb sec Average rate of copy progress You can leave the Details window open and monitor the progress of the remote copy An example of a Details window with a remote copy in progress is shown in Figure 2 14 Remote IP Copy Details Source Info Time Primary Mgmt Group Transaction_Data Start Time 6 2 05 5 53 PM Primary Snapshot Snapshot_0 Elapsed Time 30m 22s Remote Mgmt Group TransData_Remote Est Time Remaining 59m 56s Remote Snapshot Bkup_0602 Completion Time NIA Status Data Manual Scheduled MANUAL Data Copied 291 MB State COPYING Data Remaining 1 15 GB Complete 37 6 Current Rate 1 445 Kb sec Avg Rate 1 308 Kb sec or Figure 2 14 Viewing remote snapshot details for a remote copy in progress Schedull Ng Scheduled remote snapshots provide high avail ability for business continuance
27. e Data Protection Pack Configurations Using Remote Data Protection Pack for Business Continuance Failback to the production configuration Merging data for failback primary volume operation of backup application server begins The application continues to operate after the failover to the backup application servers When the production server and volumes become available again you have two failback options a Resume operations using the original produc tion server and return the backup volumes to their original remote status as illustrated in Figure 3 3 This will require migration back onto the production volumes of data that was written to the backup volumes since the failure a Continue operating on the backup application server When the production server and volumes become available configure the pro duction server to be the backup server role reversal In the failover scenarios described above there are probably two snapshots with different data As part of failback users must make a decision whether to merge the data from the two snapshots and the most effective method for doing so See Synchronizing the Data Between the Acting Primary Volume and the Original Primary Volume on page 45 Sample Remote Data Protection Pack Configurations 57 Using Remote Data Protection Pack for Business Continuance Application Workstations Clustered Application Servers Storage Subnet Prod
28. e replication within a cluster ensures high availability of critical data volumes To use remote snapshots for high availability configure a backup application server to access remote snapshots in the event of a primary system failure Figure 3 1 illustrates this simple high availability configuration Configure clustered application servers in both the primary and backup locations During normal operation the production application server read writes to the primary volume m Set up a schedule for copying remote snapshots to the backup location If your application server uses multiple volumes that must be in sync use a script to quiesce the application before creating remote snapshots 54 Sample Remote Data Protection Pack Configurations Using Remote Data Protection Pack for Business Continuance Configuration Diagram Application Workstations Clustered i Production Application my Application Application Servers Server Read Only Primary ig Remote i Volume Storage a Primary Remote Snapshot Snapshot Figure 3 1 High availability example configuration How This If the production application server or volumes Configuration become unavailable application processing fails 7 over to the backup application server As shown in Works for High Figure 3 2 the remote volume and remote Availability snapshots become primary and the backup appli cation server becomes the production application server acc
29. entire volume it will take longer to copy The second remote snapshot copies only changes made to the volume since the first remote snapshot Since you create the second remote snapshot after the time interval you intend to schedule the copy time for the second remote snapshot is more repre sentative of the actual time required for copying subsequent remote snapshots 1 Create a remote snapshot of the primary volume 2 Wait for the copy to finish 3 Create another remote snapshot of the primary volume 4 Track the time required to complete the second remote snapshot This is the minimum amount of time that you should allow between scheduled copies Understanding Remote Data Protection Pack 9 Using Schedules for Remote Data Protection Pack Thresholds Retention Policies Parameters for Remote Snapshot Schedule Retention Policies Be sure to check the remote bandwidth setting for the management group containing the remote volume since that setting affects the time required to copy a remote snapshot Does the cluster that contains the remote snapshots have sufficient space to accommodate scheduled snapshots See the chapter on snapshots in the DataFRAME SAN Software Manual for information about managing capacity using volume and snapshot thresholds If the cluster does not have sufficient space available the remote snapshot will appear in the Console and it will flash red On the Details tab of the remote sn
30. er However this scenario can use any number of DataFRAMEs Information about creating clusters and volumes can be found in the DataFRAME SAN Software Manual a Inthe production location create a manage ment group and a cluster of 3 DataFRAMEs a Create volumes on the cluster and set the replication level to 2 a Configure the production application server to access the primary volume See the DataFRAME EBSD Driver for Linux User Manual for instructions about configuring DataFRAME EBSD Driver for Linux clients a Create a second management group and cluster of 3 DataFRAMEs in the backup location a Create a schedule for making remote snapshots of the primary volume See Sched uling Remote Snapshots on page 31 Note Volume replication levels are set independently for primary and remote volumes How It Works If one of the DataFRAMEs in the primary location fails the primary volume will still be available If all of the DataFRAMEs fail or if the application server fails then failover to the backup application server occurs and the remote snapshot becomes available Sample Remote Data Protection Pack Configurations 59 Using Remote Data Protection Pack for Business Continuance Application Workstations Clustered Application Servers Storage Subnet Production Application Server Primary Volume Primary Snapshot Backup 3 Application Server Read Only Remote Volume Make Pr
31. eshold 1 0 BY Soft Threshold 1 0 BY Retention for Primary Snapshots Retain Maximum of 10 Snapshots Retain Snapshots For Cancel Figure 2 17 Editing a remote snapshot schedule Deletinga Remote 1 Select the volume for which you want to Snapshot delete the remote snapshot schedule The volume tab view opens Schedule p 2 Click the Remote Snapshot Schedule tab to bring it to the front 3 Select the schedule you want to delete 36 Using Remote Data Protection Pack Scheduling Remote Snapshots Changing the Roles of Primary and Remote Volumes Making a Primary Volume Into a Remote Volume 4 From the Tasks menu select Delete Schedule A confirmation message opens 5 Click OK Changing the roles of primary and remote volumes comes into play during failover recovery You use these procedures when you are resynchronizing data between the acting primary volume and the recovered or newly configured production site primary volume You can make any primary volume into a remote volume First the system takes a snapshot of the volume to preserve the existing data that is on the volume The data can then be accessed on that snapshot Next the volume is converted to a remote volume The remote volume is a placeholder for the remote snapshots and does not contain data itself So the size hard threshold and soft threshold change to 0 length 1 Login to the management group containing
32. essing data from the acting primary volume Sample Remote Data Protection Pack Configurations 55 Using Remote Data Protection Pack for Business Continuance Application Workstations Clustered Application Servers Storage Subnet Production Backup Production Application Application Application V Serer Serer Server Read Only Read Write Primary Remote pla m Primary Remote Primary Snapshot Snapshot Snapshot Figure 3 2 High availability configuration during failover Data availability if the primary volume or production application server fails Failover to the backup application server If either the primary volume or production appli cation server in your production site fails only that data written to the volume since the last remote snapshot was created will be unavailable until the volume or production application server is restored To maintain availability of the application and the remaining data the following process occurs 1 A script or other application monitoring the production application server discovers that primary volume is not available A script executes to fail over to the backup application server 2 The backup application server executes a script to convert the remote volume into a primary volume so that the volume can be accessed by the backup application server 3 Because the backup application server was configured to access the remote now 56 Sample Remot
33. i Remote Snapshot Production Application Server Read Write Primary ary Volume Primary Snapshot Figure 3 4 High Availability During Failover Example Configuration Achieving Affordable Disaster Recovery Even if you do not have clustered application servers or network bandwidth required for config uring hot backup sites you can still use Remote Data Protection Pack to protect your data during an emergency Using remote snapshots you can maintain copies of your volumes in remote sites Set up a schedule for creating remote copies and if your primary storage site becomes unavailable you can easily access the most recent remote copy of your data volumes You can also use remote snapshots to transfer data to a backup location where tape backups are then created This eliminates the backup window on your primary volumes and ensures that you have copies of your data in the remote site on DataFRAMEs as well as on tape 60 Sample Remote Data Protection Pack Configurations Using Remote Data Protection Pack for Business Continuance Configuration for To configure affordable disaster recovery create Affordable remote snapshots of your volumes in an off site location In addition you can create tape backups Disaster Recovery from the remote snapshots in the off site location Configuration Diagram Application Workstations Designate one or more off site locations to be the destination for remote
34. ication and stores the resulting data The designated backup site is in Des Moines Nightly at 11 00 p m accounting updates are replicated to the Des Moines backup facility using Remote Data Protection Pack Remote Data Protection Pack is an add on module You must purchase a license to use Remote Data Protection Pack beyond the 30 day evaluation period You must purchase a license for each DataFRAME in a cluster that will contain a primary volume or a remote volume The following terminology is used in describing the components and processes involved in Remote Data Protection Pack Understanding Remote Data Protection Pack 1 Remote Data Protection Pack Overview Table 1 1 Remote Data Protection Pack Glossary Term Definition Primary Volume The volume which is being accessed by the application server The primary volume is the volume that is backed up with Remote Data Protection Pack Primary Snapshot A snapshot of the primary volume which is created in the process of creating a remote snapshot The primary snapshot is located on the same cluster as the primary volume Remote Volume The volume that resides in the Remote Data Protection Pack location where the remote snapshots are created The remote volume contains no data It acts as a pointer to tell the system where to make the copy of the primary snapshot It can be stored on the same cluster or a different cluster than the primary volume
35. izing the new remote volume 8 Optional Make any necessary changes to the new remote volume You can make a remote volume into a primary volume Changing the remote volume into a primary volume allows the backup application server to read and write to the volume This is useful in failover recovery if you want to use the failover site as the acting primary site Note You cannot make a remote volume into a primary volume while a remote snapshot is in progress Wait until the remote snapshot copy is complete before making the remote volume into a primary volume 40 Using Remote Data Protection Pack Scheduling Remote Snapshots Designating Size and If the remote volume was originally created as Threshold Values for a remote volume the Converted you will need to designate a volume size and Volume hard and soft thresholds If the remote volume was originally created as a primary volume that was then changed to remote a returning that volume to its primary state will automatically return the original size and threshold values You can change these values before completing the conversion 1 Login to the management group containing the remote volume that you want to convert 2 Right click the volume in the network view and select Edit Volume The Edit Remote Volume window opens 3 Change the Type from Remote to Primary Notice that the window changes to the Edit Volume window and all the fields are greyed out
36. lume to become a remote volume will cause 1 a snapshot of all existing data to be created for that volume and then 2 all the data in that volume will be deleted so that the remote volume will have zero length and zero hard and soft thresholds Creating a new remote volume When you create the remote snapshot use the Remote Snapshot window shown in Figure 2 1 to create the volume Alternately you can create a new volume from the cluster details panel and select the Remote option in the New Volume Window S Tip The fastest way to create a remote volume is to create it as part of creating the remote snapshot using the Remote Snapshot window at A N To create the remote volume from the New Remote Snapshot window 1 Inthe Remote section select the Management Group to contain the remote snapshot You must be logged into the management group to continue 2 To create a new remote volume click New Volume The Cluster List window opens shown in Figure 2 4 Using Remote Data Protection Pack 19 Working with Remote Snapshots Cluster List Select a cluster to contain the volume Clusters from management groups that you are logged in to Clu ster Figure 2 4 Selecting a cluster for the remote volume 3 Select a cluster for the remote volume and click OK The New Volume window opens shown in Figure 2 5 See the chapter on volumes in the DataFRAME SAN Software Manual f
37. m to access recovered data To resume operations using the most recent set of remote snapshots 1 Application Workstations Application Servers Read Only Storage Subnet In the backup location make the remote volume into a primary volume Configure application servers to access this volume or if network connections are not fast enough to facilitate reading and writing to the off site location copy this volume to a location where application servers can access it more efficiently Production Application Read Write Primary Primary Snapshot Backup Site Production Site Figure 3 6 Restoring from a remote volume 62 Sample Remote Data Protection Pack Configurations Using Remote Data Protection Pack for Business Continuance Application Workstations Production Application Serer Application Servers Primary Volume Storage Subnet Primary Snapshot Production Site 1 Production Application Server Read Only pa Remote f a4 Remote i Primary i Volume 1 i i Volume 2 Volume Remote Remote Primary Snapshot 1 Snapshot 2 Snapshot Backup Site Production Site 2 Figure 3 7 Restoring from tape backup Best Practices Select a recurrence schedule for remote snapshots that minimizes the potential for data loss Any data written to the primary volume since the most recent remote snapshot was created will be unavailable if the primary volume is unavailable Co
38. move the snapshots to the remote cluster at your conve nience 3 On the cluster in the new location make the remote volume into a primary volume Sample Remote Data Protection Pack Configurations 73 Using Remote Data Protection Pack for Data Migration 4 Configure the application server in the new location to access the new primary volume Figure 3 13 shows migration of data by making a remote volume into a primary volume Application Workstations Design F i Design Team 2 Team 1 Design 5 Application CAD Server Team 2 CAD Server for Servers Next Generation for Current Product Product Read Write Ea Primary 3 _ Primary Volume H ey Volume 2 Storage Subnet Primary N Primary Snapshot pa Snapshot 2 Production Site 1 Production Site 2 Figure 3 13 Configuration after data migration 74 Sample Remote Data Protection Pack Configurations Index A Adding a remote snapshot schedule 3 35 a remote volume 78 remote snapshots 75 22 Affordable Disaster Recovery best practices 63 configuration 67 configuration diagram 67 B Backup and Recovery using Remote Data Protection Pack 65 71 Benefits of Remote Data Protection Pack 6 Best Practices for affordable disaster recovery 63 for high availability 5S for non destructive rollback 77 for off site backup and recovery 66 remote snapshot schedules 33 remote snapshots schedules 2 Business Co
39. mplete the incremental progress of the remote copy operation a Elapsed Time incremental time of the copy operation 28 Using Remote Data Protection Pack Monitoring Remote Snapshots Viewing Status in the Remote Data Protection Pack a Data Copied incremental quantity of data copied a Rate rate at which data is being copied or when the remote snapshot is complete the average rate for the total operation m State status of the operation The Remote Data Protection Pack Details window displays additional details about a remote snapshot Details Window 1 From the Remote Snapshot tab select the remote snapshot for which you want to view details 2 Right click and select View Remote Snapshot Details or double click the snapshot The Remote Data Protection Pack Details window opens as shown in Figure 2 13 Remote IP Copy Details Source Info Time Primary Mgmt Group Transaction_Data Start Time 5 27 05 2 12 PM Primary Snapshot CredDataRS1 Elapsed Time 3m 14s Remote Mgmt Group TransData_Remote Est Time Remaining N A Remote Snapshot May05RemSS Completion Time 5 27105 2 16 PM Status Data Manual Scheduled MANUAL Data Copied 61 5 MB State COMPLETE Data Remaining N A Complete 100 Current Rate NIA Avg Rate 2 596 Kb sec Co Figure 2 13 Viewing remote snapshot details for a completed remote copy During the remote copy process the Details window report
40. never delete the last fully synchronized primary snapshot a remote copy schedule may retain N 2 copies for a retention policy of N the currently copying remote snapshot plus the last fully synchronized snapshot Using the example above if you have a retention policy for your remote copy schedule of 2 primary and 5 remote snapshots the system may retain up to 4 primary and 7 remote snapshots for a period of time Table 1 4 Snapshot retention policy and maximum number of snapshots retained in system Remote Schedule Maximum Number of Retention Policy Snapshots Retained n of primary snapshots n 2 primary snapshots x of remote snapshots x 2 remote snapshots n of hours for primary snapshots n 2 primary snapshots older than n x of hours for remote snapshots x 2 remote snapshots older than xx n of days for primary snapshots n 2 primary snapshots older than n x of days for remote snapshots xX 2 remote snapshots older than xx n of weeks for primary snapshots n 2 primary snapshots older than n x of weeks for remote snapshots x 2 remote snapshots older than xx Understanding Remote Data Protection Pack 11 Using Schedules for Remote Data Protection Pack Remote snapshots will only be deleted after their corresponding primary snapshot is deleted Additionally a remote snapshot will only be deleted after its counterpart primary snapshot Therefore you can not retain fewer scheduled remote snapshots th
41. nizing such data depends on multiple factors including the application involved Example Scenario The following example illustrates only one process for synchronizing data Remember that such syn chronization is optional Table 2 2 Timetable of failover Time Event What Happens 1 00 p m Regular hourly scheduled remote RemoteSS_0 created in snapshot Remote Management Group 1 10 p m Remote copy finishes Copying is complete 1 30 p m Primary volume goes offline OrigPrimaryVol_0 offline 1 33 p m Scripted failover causes remote ActPrimaryVol_0 active in volume to become the acting Remote Management Group primary volume 2 00 p m Original primary volume comes OrigPrimaryVol_0 online back online Data that now needs to be synchronized a Original volume which contains data from 1 00 to 1 30 p m a Acting primary volume which contains data from 1 33 to 2 00 p m 44 Using Remote Data Protection Pack Resuming Production After Failover Retu rning Once the original primary site is operational again f restore operations to that site The steps to Operations to restore operations depend upon the state of the Original Primary original primary volume Site m If the primary volume is working Synchronize the data between the acting primary volume and the restored primary volume before returning the acting primary volume to its remote volume state m If the primary volume is not avail
42. nsider how much data you are willing to lose in the event of an emergency and set the recurrence for creating remote snapshots accordingly If you do not want a large number of remote snapshots to accumulate on your remote volume you can use more than one remote snapshot schedule each with different retention policies For example suppose you want to create remote snapshots every 4 hours to ensure that no more than 4 hours worth of data is lost in an emergency In addition you want to retain 1 week s worth of remote snapshots Retaining 4 hour snapshots for 1 week can result in the accumulation of over 40 remote snapshots Another approach would be to create 2 remote snapshot schedules for the volume Sample Remote Data Protection Pack Configurations 63 Using Remote Data Protection Pack for Business Continuance Use remote snapshots in conjunction with local synchronous volume replication Example configuration f m One schedule to create remote snapshots every 4 hours but only retain the most recent 3 remote snapshots This will ensure that you do not lose more than 4 hours worth of data in an emergency a A second schedule to create remote snapshots every 24 hours and retain 7 remote snapshots To prevent data loss reinforce Remote Data Pro tection Pack with synchronous replication of the volume within the cluster of DataFRAMEs at the primary geographic site With synchronous replica tion a single DataFRAME
43. ntinuance Using Remote Data Protection Pack 53 64 C Canceling a Remote Snapshot 25 Changing backup site into new production site 47 remote volume into primary volume 40 roles of primary and remote volumes 37 volume into remote volume 37 Configuration for affordable disaster recovery 67 for data migration 72 for high availability 54 for non destructive rollback 68 for off site backup and recovery 65 Configuring failover 43 primary volume and snapshots 34 Remote Data Protection Pack 7 remote volume and snapshots 34 Copy Bandwidth setting 8 Copying using Remote Data Protection Pack 15 Creating split mirrors 50 Customer Support registering Remote Data Protec tion Pack 75 D Data availability during failover 56 merging for failback 57 synchronizing 44 transfer rate bandwidth setting 24 Data Migration and Remote Data Protection Pack 72 74 configuration diagram 73 75 configuration for 72 using Remote Data Protection Pack for 72 Deleting remote snapshot schedules 36 remote snapshots 26 Designating or Creating the Remote Volume amp Disaster Recovery affordable using Remote Data Protection Pack 60 64 E Editing remote snapshot schedules 35 36 remote snapshots 25 F Failback merging data for 57 to production configuration 57 Failover data availability during 56 to backup application server 56 with Remote Data Protection Pack 55 59 Feature Registration 75 G Glossary for Remote Data P
44. oint Type a name for the remote snapshot Optional Type a description for the snapshot The completed window is shown in Figure 2 6 Click OK Using Remote Data Protection Pack 21 Working with Remote Snapshots New Remote Snapshot New Remote Snapshot Primary Management Group Transaction_Data Volume Name CreditData Snapshot Name Snap1CredData Remote Management Group TransData_Remote Y Volume Name RemvVolCD04 bs New Volume Snapshot Name RemsscbD04 Snapshot Description Credit Data 04 RemSnah Cancel Figure 2 6 Completing the New Remote Snapshot dialog What the System The system creates the remote snapshot in the Does cluster that contains the remote volume The system then copies the primary snapshot onto the remote snapshot The process of copying the data may take some time The remote snapshot appears below the remote volume as shown in Figure 2 7 Note If you create a remote snapshot of a volume with a T remote snapshot still in progress the second remote snapshot will not begin copying until the first remote snapshot is complete 22 Using Remote Data Protection Pack Working with Remote Snapshots a a Transaction_Data a TransData_Remote a a TransData04 TransData_BkUp04 a 5h b Boulder 1 Boulder 2 Denyer 1 Denver 2 RemvVolCD04 4 l f Pad RemsscbD04 Primary Volume Remote Volume and Primary Snapshot and Remote Snapshot
45. on Protection Pack Pack follows a three step process Works 1 At the production location you create a snapshot of the primary volume this is called the primary snapshot 2 You create a remote volume at the remote location and then create a remote snapshot The remote snapshot is a snapshot of the empty remote volume and it is linked to the primary snapshot 3 The system copies data from the primary snapshot to the remote snapshot 1 System takes a snapshot 2 System creates an empty snapshot of the primary volume of the remote volume Primary Volume gna Remote Volume R e Primary Location Remote Location 3 System copies data from the primary snapshot to the remote snapshot Figure 1 1 Basic flow of Remote Data Protection Pack Note Both primary and completed remote snapshots are the same as regular snapshots See the chapter Working with Snapshots in the DataFRAME SAN Software Manual a Note Remote Data Protection Pack can be used on the same site even in the same management group and cluster a Understanding Remote Data Protection Pack 3 Remote Data Protection Pack Overview Graphical The Centralized Management Console displays Representations special graphical representations of Remote Data Protection Pack of Remote Data Protection Pack Copying the Primary Snapshot to the Remote Snapshot When the primary snapshot is copying to the remote snapshot the Console depicts the
46. onitoring Remote Snapshot Details from the Console Tab View Information for monitoring remote snapshots is available from multiple sources Active monitoring features provide you the capability to configure alerts that you view in the Console as well as receiving alerts as emails and through SNMP traps The Console tab view also provides monitoring information for remote snapshots There are four variables for remote snapshots for which you can configure alerts Notification for these variables automatically come as alert messages in the Console You can also configure Active Monitoring to receive email notification or for SNMP traps The Remote Data Protection Pack variables that are monitored include Remote Data Protection Pack status an alert is generated if the copy fails a Remote Data Protection Pack complete an alert is generated when the remote copy is complete a Remote Data Protection Pack failovers an alert is generated when a remote volume is made primary a Remote management group status an alert is generated if the connection to a remote man agement group changes disconnects and or reconnects For detailed information about configuring Active Monitoring see the Reporting chapter of the DataFRAME SAN Software Manual View information about each remote snapshot in both the Remote Snapshot tab and in the Remote Data Protection Pack Details panel Using Remote Data Protection Pack 27 Monitoring Rem
47. or detailed information about creating volumes New Remote Yolume xj New Remote Volume Type Volume Name Volume_O Description Cluster TransData_BkUp04 Replication Level 2 Way Replication Priority Availability Redundancy Size Hard Threshold Soft Threshold Auto Grow Off Auto Manual Checksum Data Yes No Figure 2 5 Creating a new remote volume 20 Using Remote Data Protection Pack Working with Remote Snapshots Completing the Remote Snapshot 4 Type a name for the volume A volume name must be from 1 to 127 charac ters and is case sensitive Optional Type a description of the volume Select the replication level You can set different replication levels for the remote volume and the primary volume Note You cannot set the size or thresholds for the remote volume Those values are 0 since the remote volume is a placeholder for data 7 10 2 3 Select a replication priority If you select a replication level of None you cannot set a replication priority See the chapter on volumes in the DataFRAME SAN Software Manual for detailed information about creating volumes Select the Target Type for the volume Optional If the volume is an iSCSI target and you want to use 1 way or 2 way CHAP type a target secret Click OK to return to the New Remote Snapshot window The new remote volume has been created at this p
48. or use by a new application or workgroup To copy data from one location to another simply create a one time remote snapshot of the volume To make the remote snapshot a read write volume make it into a primary volume To make a copy of a volume in a remote location configure a cluster of DataFRAMEs in the remote location with enough space to accommodate the volume See the example illustrated in Figure 3 12 72 Sample Remote Data Protection Pack Configurations Using Remote Data Protection Pack for Data Migration Configuration Diagram How This Configuration Works for Data Migration Application Workstations Lod Design Spe Team 4 Design Team 2 Application CAD Server CAD Server for Servers forCurent Next Generation Product Product Read Write Read Only froesacant Remote i Volume Storage 4 Production Site 1 Production Site 2 Figure 3 12 Data migration example configura tion Suppose you want to create a complete copy of a volume for an application to use in different location 1 Configure a cluster of DataFRAMEs in the new location to contain the copied volume 2 Create either a one time remote snapshot of the volume onto the cluster in the new location If your application server uses multiple volumes that must be in sync use a script to quiesce the application before creating remote snapshots Optional You can create regular one time snapshots and use remote copy to
49. ote Snapshots Viewing Information The Remote Snapshot tab displays a list of remote in the Remote snapshots connected with a selected item in the Snapshot Tab Network view For example if you select a man agement group the Remote Snapshot tab displays the list of remote snapshots associated with that management group You can view lists of remote snapshots by management group cluster volume and snapshot levels 1 Select the appropriate item in the Network view 2 Click the Remote Snapshot tab to bring it to the front shown in Figure 2 13 Details Managers Clusters Authentication Groups Volume Lists Register Times Remote Snapshot Primary Man Primary Sna Remote Man Remote Sna Complete Elapsed Time Data Copied Rate State Transaction CredDataRS1 TransData_ MayO5RemSS 100 3m 14s 61 5 MB 2 596 Kb sec COMPLETE Transacton PriSS_0601 TransData_ Bkup0601 38 3 49s 60 5 MB 10 114 Kb see COPYING Figure 2 12 Viewing remote snapshot details in the Remote Snapshot tab The remote snapshot details displayed include a Primary Management Group containing the primary volume from which remote snapshots are created m Primary Snapshot from which the remote snapshot is copied a Remote Management Group containing the remote volume to which the remote snapshot is attached Remote Snapshot target for the copied primary snapshot Co
50. other management group This means that to control the maximum rate of data transfer to a remote snapshot set the remote bandwidth on the management group that contains the remote snapshot 1 Right click the remote management group and select Edit Management Group The Edit Management Group window opens shown in Figure 2 9 Edit Management Group Edit Management Group Group Name Local Bandwidth 32768 Kb Sec Remote Management Groups Management Gr Loggedin _ Remote Bandwi Connected Transaction_D Yes 32768 Kb sec Yes Disassociate Edit Bandwidth Cancel Figure 2 9 Editing a remote management group 2 Inthe Remote Management Groups section click Edit Bandwidth The Edit Remote Bandwidth window opens 24 Using Remote Data Protection Pack Working with Remote Snapshots Edit Remote Bandwidth x Remote Bandwidth 32768 KbiSec Cancel Figure 2 10 Editing the remote bandwidth 3 Change the bandwidth setting as desired For example change the value to 93 KB to use no more than about one half the capacity of a T1 line Note Both bandwidth settings are configured in kilobytes Be careful when configuring this parameter as you may be used to using bits for networking settings Canceling a When you cancel a remote snapshot that is in Remote Snapshot progress the remote snapshot is deleted and the primary snapshot remains
51. ots 006068 31 Configuring Failover ceccceseeeeeeeeeeeeeeees 43 Resuming Production After Failover 43 Rolling Back Primary and Remote Volumes 47 Using Remote Snapshots for Data Migration and Data MINING ra e a aa a estes 50 Disassociate Remote Management Groups 51 Chapter 3 Sample Remote Data Protection Pack Configurations OVET VIEW nan o oa aa dead a oa aE 53 Using Remote Data Protection Pack for Business CONLINUANCE sakar Aa Raa ein a 53 Using Remote Data Protection Pack for Off site Backup and Recovery 65 Using Remote Data Protection Pack for Data Migration Asenna aAa a AA aA 72 Index 75 vi Understanding Remote Data Protection Pack Remote Data Protection Pack Overview Purchase Remote Data Protection Pack Glossary for Remote Data Protection Pack Remote Data Protection Pack provides a powerful and flexible method for replicating data and keeping that replicated data available for business continuance backup and recovery data migration and data mining Remote Data Protection Pack uses the existing volume and snapshot features along with replication across geographic distances to create remote snapshots The geographic distance can be local in the same data center or on the same campus metro in the same city or long distance For example the accounting department in the corporate headquarters in Chicago runs the corporate accounting appl
52. ots on a backup server either local or remote and then back up the remote snapshot from the backup server The remote snapshot is available if the primary volume fails Rather than creating tape backups and then trans porting them to a secure off site location you can use Remote Data Protection Pack to create remote snapshots in an off site location and then create tape backups at the off site location To use remote snapshots for off site tape backup create remote snapshots for access by your tape backup application a Create remote volumes in your backup location Configure your backup application to access the remote snapshots Configure schedules to create remote snapshots in the designated off site locations If your application server uses multiple volumes that must be in sync use a script to quiesce the application before creating remote snapshots a Create routine tape backups of the remote snapshots See the example configuration illustrated in Figure 3 8 Sample Remote Data Protection Pack Configurations 65 Using Remote Data Protection Pack for Off site Backup and Recovery Configuration Diagram Application Workstations Application Servers Storage Subnet Production Application Server Primary Volume Primary Snapshot Production Site 1 J Tape CES Library Production Application Read Only Read Only Remote F R Primary i Volume 1 Volume 2 Volume
53. ring 27 31 planning 7 planning for scheduled 9 13 Rolling Back a Volume Remote Data Protection Pack and primary volumes 48 50 Remote Data Protection Pack and remote volumes 50 S Scheduling remote snapshots 31 35 Setting Bandwidth amp Snapshots See also Primary Snapshots Remote Snapshots Split mirrors creating 50 Sync Bandwidth setting 8 Synchronizing Data after failover 44 between acting primary volumes and original primary volumes T Thresholds requirements rolled back primary volumes 49 Timetable of failover 44 U Uses for Remote Data Protection Pack 6 Using schedules for Remote Data Pro tection Pack 24 scripting for failover 43 Using Data Protection Pack for Data Migration 72 Using Remote Data Protection Pack for Business Continuance 53 for Off Site Backup and Recovery 65 V Viewing a List of Remote Snapshots 23 Volumes making remote 37 Volumes See also Primary Volumes Remote Volumes 77 78
54. rotection Pack 7 Graphical Representations of Remote Data Protection Pack 4 H High Availability and failover 55 59 and Remote Data Protection Pack 53 59 best practices 58 configuration diagram 55 configuration for 54 configuration of Remote Data Pro tection Pack 54 59 I Icons for Remote Data Protection Pack L License Keys 75 M Management Groups disassociating 57 52 Merging data for failback 57 Monitoring Remote Snapshots 27 31 N Non Destructive Rollback best practices 77 configuration diagram 68 configuration for 68 0 Off Site Backup and Recovery best practices 66 configuration diagram 66 configuration for 65 using Remote Data Protection Pack for 65 P Planning failover 43 remote snapshot schedules 9 13 remote snapshots 7 Primary Volumes making remote 37 prerequisites for rolling back 48 rolling back 48 50 name requirements for 49 threshold requirements 49 76 R Remote Data Protection Pack and data migration 72 74 and volume replication 5 business continuance 53 64 creating 4 disassociating management groups 51 52 glossary high availability 53 59 high availability and failover 55 59 high availability configuration 54 59 icons for 4 overview registering 75 routine backup and recovery 65 29 Remote IP Copy routine backup and recovery 71 Remote Snapshots canceling 25 creating 75 22 creating schedule 37 35 editing schedules 35 36 monito
55. rotection Pack operates at the block level moving large amounts of data much more quickly than file system copying Snapshots are incremental that is snapshots save only those changes in the volume since the last snapshot was created Hence failover recovery may need to resynchronize only the latest changes rather than the entire volume Remote Data Protection Pack is robust If the network link goes down during the process copying resumes where it left off when the link is restored 6 Understanding Remote Data Protection Pack Planning for Remote Data Protection Pack P a nni Ng for Remote Data Protection Pack works at the Remote Data management group cluster volume snapshot f and DataFRAME level Protection Pack Table 1 3 Remote Data Protection Pack SAN iQ and DataFRAMEs Storage System Level Remote Data Protection Pack Configuration Management Groups Remote snapshots can be created in the same man agement group or in a different management group than the primary volume m f using different management groups the remote bandwidth setting of the management group containing the remote volume determines the maximum rate of data transfer to the remote snapshot Clusters Remote snapshots can be created in the same cluster or in a different cluster than the primary volume Volumes m Primary volumes contain the data to be copied to the remote snapshot m Data is copied to the remote snapshot
56. s current data for the statistics When the copy is completed the statistics show summary data Figure 2 13 shows a completed remote copy Table 2 1 lists the values for the sta tistics reported in the Details window Using Remote Data Protection Pack 29 Monitoring Remote Snapshots Table 2 1 Values for Remote Data Protection Pack Details window Statistic Values Source Info Section Primary Mgmt Group Name of the management group containing the primary volume and snapshot Primary Snapshot Name of the primary snapshot Remote Mgmt Group Name of the management group containing the remote snapshot Remote Snapshot Name of the remote snapshot Status Manual Scheduled Whether the snapshot was created using a snapshot schedule or manually State Started Copying Stalled Complete Current state of the copy process Complete 0 100 Percent of the copy process that is completed Time Start Time MM DD YY HH MM AM PM Date and time copy started Elapsed Time Xd Xh Xm Xs X a number and the days hours minutes and seconds the copy has been processing N A if not yet available Est Time Remaining Xd Xh Xm Xs X a number and the days hours minutes and seconds estimated to remain in the copy process N A for completed copies or in progress copies not yet calculated Completion Time MM DD YY HH MM AM PM Date and time copy
57. ses to the OSS Packages and your rights and responsibilities under these licenses Copyright Limited Warranty The software described in the document includes software developed by the Apache Software Foun dation The Legion of the Bouncy Castle and Free Software Foundation Inc Copyright 2001 2005 LeftHand Networks Inc All rights reserved LeftHand Networks the LeftHand Networks logo SAN iQ and AEBS are iii registered trademarks of LeftHand Networks Distributed Stor age Matrix and Remote IP Copy are trademarks of LeftHand Networks Copyright 1999 The Apache Software Foundation All rights reserved Copyright 2000 The Legion of the Bouncy Castle All rights reserved Copyright 1991 1999 Free Software Foundation Inc All rights reserved Used under license by MPC Computers LLC EMA001078 00 KDA 11 01 2005 Copyright Limited Warranty Table Of Contents Copyright Limited Warranty ecceeeeeeees ii Chapter 1 Understanding Remote Data Protection Pack Remote Data Protection Pack Overview 1 Planning for Remote Data Protection Pack 7 Using Schedules for Remote Data Protection Pack 8 Chapter 2 Using Remote Data Protection Pack Remote Data Protection Pack Overview 15 Registering Remote Data Protection Pack 15 Working with Remote Snapshots 645 15 Monitoring Remote Snapshots 6068 27 Scheduling Remote Snapsh
58. snapshots Set up a schedule for creating remote snapshots in the designated off site locations If your application server uses multiple volumes that must be in sync use a script to quiesce the application before creating remote snapshots Create routine tape backups of the remote snapshots in the off site locations Production Application Server Application Servers Primary Volume Storage Subnet Primary Snapshot Production Site 1 Ethernet Corporate LAN 2 E Tape ES Library Production Application Read Only pe sdana 3 Remote Primary i Volume 1 i i Volume 2 Volume Remote Remote Snapshot 1 Snapshot 2 Snapshot Backup Site Production Site 2 Figure 3 5 Affordable disaster recovery example configuration How this Works If the DataFRAMEs in your primary location fail or for Affordable volumes become unavailable the off site location contains the most recent remote snapshots Disaster Recovery Sample Remote Data Protection Pack Configurations 61 Using Remote Data Protection Pack for Business Continuance Use the remote snapshots to resume opera tions as shown in Figure 3 6 If you created tape backups you can recover data from tape backups as shown in Figure 3 7 Only data written to the primary volumes since the last remote snapshot was created will be unavailable Application servers that were accessing the down volumes will not be available until you reconfigure the
59. t New Remote Snapshot The New Remote Snapshot window opens shown in Figure 2 1 New Remote Snapshot y New Remote Snapshot Primary Management Group Transaction_Data Volume Name CreditData Snapshot Name Create Primary Snapshot gt New Snapshot Remote Management Group TransData_Remote v Volume Name New Volume Snapshot Name Snapshot_O Snapshot Description Figure 2 1 Creating a new remote snapshot 16 Using Remote Data Protection Pack Working with Remote Snapshots Creating the Primary 1 Inthe Primary section of the New Remote Snapshot Snapshot window click New Snapshot The New Snapshot window opens shown in Figure 2 2 New Snapshot New Snapshot Snapshot Name Snapshot_O Description Cluster Replication Level Replication Priority Size Hard Threshold Soft Threshold Auto Grow Checksum Data Cancel Figure 2 2 Creating a new primary snapshot 2 Type a name for the primary snapshot Names are case sensitive They cannot be changed after the snapshot is created _ ly Tip Make the beginning of volume and snapshot names Gy meaningful for example Snap1Exchg_03 The Console displays volume and snapshot names under i the icons If a name is longer than the width of the icon the end of the name is cut off however the full name does show on the corresponding Details tab and on other relev
60. te Data Protection Pack beyond the 30 day evaluation period For information about register ing Remote Data Protection Pack licenses see Chapter 16 Feature Registration in the DataFRAME SAN Software Manual Remote snapshots are the core of Remote Data Protection Pack You use the existing volume and snapshot capabilities along with replication across geographic distances to create remote snapshots Creating a remote snapshot is the main task in Remote Data Protection Pack You can create a one time remote snapshot or set up a schedule for recurring remote snapshots Many of the parame ters for either case are the same Creating a remote snapshot involves four main steps Using Remote Data Protection Pack 15 Working with Remote Snapshots a First login to the management groups that will contain primary and remote volumes m Second create a primary snapshot on the primary volume a Third create a remote volume or select an existing remote volume Fourth specify the settings for the remote snapshot Getting There 1 Loginto the management group that contains the primary volume for which you are creating the remote snapshot 2 Login to the management group that will contain the remote volume and remote snapshot You can create remote volumes and snapshots within the same management group In that case you only log in to the one management group 3 Right click the primary volume and select Remote Copy g
61. the volume that you want to convert 2 Right click the volume in the network view and select Edit Volume The Edit Volume window opens 3 Change the Type from Primary to Remote Notice that the window changes to the Edit Remote Volume window and all the fields are greyed out as shown in Figure 2 18 Addition ally the values in the size hard threshold and soft threshold fields are set to 0 Using Remote Data Protection Pack 37 Scheduling Remote Snapshots Edit Remote Yolume Edit Volume f Edit Remote Volume Type Primary Remote Type Primary Remote Volume Name Volume Name Description Description Created Created Cluster TransData05 Cluster Replication Level 2 Way Replication Level Replication Priority Availability Redundancy Replication Priority Size 8 0 GB v Size Hard Threshold 3 0 GB Hard Threshold Soft Threshold GB v Soft Threshold Auto Grow Off Auto Manual Auto Grow Checksum Data No Checksum Data Primary volume with size hard and Selecting Remote changes the volume to soft thresholds defined a remote volume with the size hard and soft thresholds set to 0 Figure 2 18 Changes to a volume when changed from Primary to Remote 4 Click OK The Make Volume Remote window opens shown in Figure 2 19 38 Using Remote Data Protection Pack Scheduling Remote Snapshots Make
62. tion policy for the primary and remote snapshots This ensures that you have copies of the same number of snapshots in your primary and remote locations Any snapshots destroyed during rollback of one volume will remain intact on the other volume See Figure 3 9 for an illustration of this configura tion Configuration Diagram Application Workstations Clustered Application Restore Application Serer Serer Servers Read Write Read Only Primary oe Volume i 5 Volume Storage 5 00 PMS Subnet Primary Remote Snapshot Snapshot 3 00 PME 3 00 PM Primary Remote Snapshot Snapshot 7 00 PME 1 00 PM Primary Remote Snapshot Snapshot 77 00 AM 77 00 AM Figure 3 9 Non destructive rollback example 68 Sample Remote Data Protection Pack Configurations Using Remote Data Protection Pack for Off site Backup and Recovery How This You can choose to roll back either the primary Configuration snapshot or the remote snapshot Rolling back one of the snapshots will cause all the more recent Works for Non snapshots of that volume to be deleted The other Destructive volume retains the full set of snapshots You can Rollback continue to make snapshots even though one side was rolled back and the other side was not When deciding whether to roll back the primary or remote volume consider the following a When you roll back the primary snapshot to a primary volume any applications accessing the primary volume
63. to roll back 2 Select the snapshot that you want to roll back to 3 Review the snapshot Details tab to ensure you have selected the correct snapshot 4 From the Tasks menu select Roll Back Volume The Roll Back Volume window opens shown in Figure 2 22 48 Using Remote Data Protection Pack Rolling Back Primary and Remote Volumes Roll Back Yolume Roll Back Volume New Volume Name Volume_0 Description Cluster Replication Level Replication Priority Size Hard Threshold Soft Threshold Auto Grow Checksum Data Figure 2 22 Rolling back a primary volume 5 Type anew name for the rolled back primary volume You can also change the hard threshold and soft threshold if necessary Table 2 4 Requirements for rolling back a primary volume Item Requirements for Changing New Primary Volume Name Must be from 1 to 127 characters Names are case sensi tive Hard Threshold Hard threshold size must be equal to or less than the size of the volume Soft Threshold Soft threshold size must be equal to or less than the hard threshold size 6 Click OK The Roll Back Volume confirmation message opens Using Remote Data Protection Pack 49 Using Remote Snapshots for Data Migration and Data Mining Rolling Back a Remote Volume Using Remote Snapshots for Data Migration and Data Mining Creating a
64. uction Backup Production Application mal Application Application Server Server Read Only Read Write Primary Remote Volume Volume Primary lak Volume Primary Remote Primary Snapshot Snapshot Snapshot Figure 3 3 High availability configuration during failoack Best Practices Use remote snapshots in conjunction with local synchronous volume replication Using remote snapshots alone any data written to the primary volume since the most recent remote snapshot was created will be unavailable if the primary volume is unavailable However you can lessen the impact of primary volume failure by using synchronous volume repli cation Volume replication allows you to create up to 3 copies of a volume on the same cluster of DataFRAMEs as the primary volume The only limi tation is that the cluster must contain at least as many DataFRAMEs as replicas of the volume Rep licating the volume within the cluster ensures that if a DataFRAME in the cluster goes down replicas of the volume elsewhere in the cluster will still be available For 3 way replication up to 2 DataFRAMEs can fail For detailed information about volume replication see the chapter on 58 Sample Remote Data Protection Pack Configurations Using Remote Data Protection Pack for Business Continuance Example configuration volumes in the DataFRAME SAN Software Manual for details This example illustrated in Figure 3 4 uses 3 DataFRAMEs per clust
65. very of backed up data If you retain a number of remote snapshots after a tape backup is created you can access this data without going to the backup tape a Retain 3 primary snapshots This enables you to roll the primary volume back yet it requires a relatively small amount of space on the primary cluster a Retain up to a week s worth of remote snapshots on the backup cluster a For snapshots older than 1 week go to the backup tape As discussed in Rolling Back a Primary Volume on page 48 rolling a snapshot back to a volume deletes any snapshots that were created since the snapshot that you roll back to For example suppose you created snapshots of a volume on Monday Tuesday and Wednesday On Thursday if you roll the volume back to Monday s snapshot then the snapshots from Tuesday and Wednesday will be deleted You can use Remote Data Protection Pack to roll a volume back to an old snapshot without losing the interim snapshots Because Remote Data Protec tion Pack creates two sets of snapshots primary snapshots and remote copies you can roll a volume back to a snapshot and still retain the other set of snapshots Sample Remote Data Protection Pack Configurations 67 Using Remote Data Protection Pack for Off site Backup and Recovery Configuration for To use remote snapshots for non destructive Non Destructive rola Rollback a Create a remote snapshot schedule m Inthe schedule specify the same reten
66. will no longer have access to the most current data as the primary volume has been rolled back to a previous state If the primary volume must be synchro nized with other volumes accessed by the same application consider rolling back the remote volume instead Figure 3 10 shows rollback of the primary snapshot while leaving the remote snapshots intact Sample Remote Data Protection Pack Configurations 69 Using Remote Data Protection Pack for Off site Backup and Recovery Application Workstations Ethernet Corporate LAN Clustered Application Restore Application Serer Serer Servers Read Write Read Only Primary f Volume i Volume Storage 3 00 PMS 5 00 PM Subnet Remote Snapshot 3 00 PM Primary Remote Snapshot Snapshot 4 00 PME 1 00 PAS Primary Remote Snapshot Snapshot 14 00 AM 74 00 AM Figure 3 10 Non destructive rollback from the primary snapshot a To roll back the remote snapshot you must first make the remote volume into a primary volume This will stop scheduled creation of remote snapshots which may jeopardize your high availability disaster recovery or routine backup strategies Figure 3 11 shows rollback of the remote snapshot 70 Sample Remote Data Protection Pack Configurations Using Remote Data Protection Pack for Off site Backup and Recovery Application Workstations Clustered g Application Application Serer Serwers Read Write Read Only Read Write Primary
67. with Volumes Using synchronous volume replication on multiple DataFRAMEs within a cluster in combination with asynchronous Remote Data Protection Pack ona different cluster of DataFRAMEs creates a robust high availability configuration Understanding Remote Data Protection Pack 5 Remote Data Protection Pack Overview Uses for Remote Data Protection Pack Table 1 2 Uses for Remote Data Protection Pack Use Remote Data Protection Pack for How It Works Business continuance disaster recovery Using Remote Data Protection Pack store remote snapshots off site The remote snapshots remain con tinuously available in the event of a site or system failure Off site backup and recovery Remote Data Protection Pack eliminates the backup window on an application server by creating remote snapshots on a backup server either local or remote and backing up from that server m Split mirror data migration content distribution Using Remote Data Protection Pack make a complete copy of one or more volumes without interrupting access to the original volumes Move the copy of the volume to the location where it is needed Benefits of Remote Data Protection Pack Remote Data Protection Pack maintains the primary volume s availability to application servers Snapshots on the primary volume are taken instantaneously and are then copied to remote snapshots in the off site location Remote Data P
68. y for the primary snapshots Click the Remote Setup tab to bring it to the front Primary Setup Remote Setup Management Group TransData_Remote vY Volume Name RV_RCDaily v New volume Snapshot Name Schedule Name Number Retention for Remote Snapshots Retain Maximum of 5 Snapshots Retain Snapshots For Cancel Figure 2 16 The Remote Setup tab 2 5 Select the management group to contain the remote volume and remote snapshots Select an existing volume or click New Volume to create the remote volume See Making a Primary Volume Into a Remote Volume on page 37 Specify a retention policy for the remote snapshots Click OK 34 Using Remote Data Protection Pack Scheduling Remote Snapshots What the System Does Editing a Remote Snapshot Schedule z7 If you created a new volume for the remote volume the system creates a new primary snapshot of the primary volume and a remote snapshot of the remote volume If you selected an existing volume to become the remote volume the system alerts you that all the data on the existing volume will be deleted but that a snapshot of all the existing data will be created first The snapshot that is then created retains all the volume s data 1 Type a name for that snapshot in the alert 2 Click Yes to continue The new snapshot is created and the volume becomes a remote volume The system creates
69. y from failover To achieve failover you plan the following parame ters a the location and structure of management groups and clusters configuration of primary and remote volumes and snapshots and scheduling snapshots configuration of application servers and backup application servers m task flow for failover recovery resuming pro duction after failover Application based scripting provides the capability for creating mounting and deleting snapshots using scripts Remote Data Protection Pack can be scripted as well Remote snapshots and snapshot schedules can be created and managed using scripts Detailed information about snapshot scripting can be found in the Working with Script ing chapter in the DataFRAME SAN Software Manual After failover occurs three scenarios exist for resuming production a Failback Recovery return operations to the original primary site once it is restored m Make the backup site into the new primary site m Set up a new primary site and resume opera tions at that site Using Remote Data Protection Pack 43 Resuming Production After Failover Synchronizing Data After Failover Timetable of failover The task flow for restoring or recovering data and resuming the original Remote Data Protection Pack configuration are different for each scenario After a failover there will usually be two snapshots or volumes that have conflicting data Recovering and synchro

DataFRAME Remote Data Protection Pack User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents