Home

P4000 Remote Copy user guide

1. Data Remaining Amount of data remaining to be copied in smallest unit size Current Rate 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 To monitor the progress of the remote copy leave the Remote Snapshot Details window open P4000 Remote Copy user guide 27 Source Info Time Primary Mgmt Group Exchange Start Time 09 29 2008 03 20 17 PM MDT Primary Snapshot BkupLogs_SCsnap Elapsed Time 1m 51s Remote Mgmt Group RemExchange Est Time Remaining 2m 57s Remote Snapshot RemBkupLogs_RS_1 Completion Time NIA Original Mgmt Group Exchange Original Snapshot BkupLogs_SCsnap Status Data Manual Scheduled Manual Data Copied 345 25 MB Snapshot Scanned E o Data Remaining 1 1 GB State Copying Current Rate 25 480 Kbisec Avg Rate 25 480 Kbisec Figure 7 Viewing remote snapshot details for remote copy in progress Configuring active monitoring alerts for Remote Copy There are four variables for configuring alerts for remote snapshots Notification for these variables automatically displays as default alert messages in the alert window You can also configure Active Monitoring to receive notification by email or SNMP traps Monitored Variables for Remote Copy include e Remote Copy status An alert is generated if the copy fails
2. EY NOTE Do this only if a group no longer exists or if instructed by Customer Support 1 Log in to both management groups that you want to disassociate 2 In the navigation window select the remote management group 3 Click Management Group Tasks and then select Edit Management Group 4 Select the management group or groups you want to disassociate that is the management groups that are remote relative to this management group 5 Click Disassociate A confirmation message opens describing the results of disassociating the management groups A CAUTION Disassociating the management group cancels any in progress remote snapshots and deletes all timetables between the primary and remote management groups 40 Click OK The Edit Management Group window is displayed on top again and the remote management group you disassociated from is gone from the list Click OK to return to the navigation window Using Remote Copy 3 Sample Remote Copy configurations Because of its flexibility Remote Copy is useful in a variety of configurations The sample configurations described in this chapter show only a few ways to use Remote Copy for business continuance backup and recovery data migration and data mining Using Remote Copy for business continuance Business continuance is composed of disaster recovery and high availability of data If using Remote Copy for business continuance data is stored off site a
3. 1 In the backup location make the remote volume into a primary volume 46 Sample Remote Copy configurations 2 Configure application servers to access the primary 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 Application Workstations T Production i cereal Application Servers Serer WAN Read Only Read Write Read Wirite gaes Remote Piina Volume y Vol Volume Storage k tu Subnet Remote Primary Primary Snapshot Snapshot Snapshot Backup Site Production Site Figure 15 Restoring from a remote volume In Figure 15 on page 47 note the volume labeled Primary Snapshot in the gray area on the left It originated as a read only backup but is brought into use as an acting primary Application Workstations O Tape Application Production C Library Production Application Application Servers Server Serer WAN Read wWrite Read Write sie iii Primary f See Remote S Primary Volume Volume Storage j F E E ewer 2 2 o Sees Subnet Primary Remote Primary Snapshot Snapshot 1 Snapshot 2 Snapshot Production Site 41 Backup Site Production Site 2 Figure 16 Restoring from tape backup P4000 Remote Copy user guide 47 Best practices Select an optimum recurrence schedule Select a recurrence schedule for remote s
4. gt Reconfigure scripts for failover on the application servers P4000 Remote Copy user guide As your target create a remote volume which will later be converted into your primary volume Configure a new timetable for the scheduled remote snapshots on the new primary volume 37 Setting up a new production site Setting up a new production site involves creating a new primary volume and synchronizing 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 Making the backup site into the new production site Turn the backup site into the new production site and designate a different backup site The steps are similar to those for initially configuring Remote Copy 1 Create a remote snapshot or a timetable for a scheduled remote snapshot on the acting primary volume 2 Make a new remote volume on the new backup site as part of creating that remote snapshot or timetable for a scheduled remote snapshot 3 Reconfigure scripts for failover on the application servers Rolling back primary and remote volumes Rolling back a volume from a snapshot is one method for reverting to an earlier copy of the data on a volume Rolling back procedures requires that you delete any snapshots that were created after the snapshot that is rolled back to Using SmartClone to clone a volume from a snapshot Consider
5. Primary lI i Remote Volume Volume Storage ge Soorm a 1 5 00 PM Subnet Primary Remote Snapshot Snapshot 3 00 PM 3 00 PM Primary Remote Snapshot Snapshot 4 00 PM 7 00 PM Primary Remote Snapshot Snapshot 17 00 AM 77 00 AM Figure 18 Non destructive rollback example How this configuration works for non destructive rollback You can choose to roll back either the primary snapshot or the remote snapshot Rolling back one of the snapshots requires that you delete more recent snapshots of that volume The other volume retains the full set of snapshots You can 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 e When you roll back the primary snapshot to a primary volume any applications accessing the primary volume will no longer have access to the most current data because the primary volume has been rolled back to a previous state If the primary volume must be synchronized with other volumes accessed by the same application consider rolling back the remote volume instead Figure 19 on page 52 shows rollback of the primary snapshot while leaving the remote snapshots intact P4000 Remote Copy user guide 51 Application Workstations Clustered g pplication Application Server Server Servers WAN Read Write Read Only cy Primary i I Remote Volume Volume Storage 3 00 PM i 1 5
6. Remote Volume Volume Storage Subnet Primary Remote Snapshot Snapshot Figure 10 High availability example configuration How this configuration works for high availability If the production application server or volumes become unavailable application processing fails over to the backup application server The remote volume and remote snapshots become acting primary and the backup application server becomes the acting production application server accessing data from the acting primary volume Application Workstations Clustered Production Backup Production Application Application Application mm Application Servers A Serer Server Server WAN Read Only gt Read Write Se Primary Remote Acting X Volume a Volume Primary Storage EJ i Volume Subnet ane Primary Remote Primary x Snapshot aaa Snapshot Figure 11 High availability configuration during failover 42 Sample Remote Copy configurations Data availability if the primary volume or production application server fails If either the primary volume or production application server in your production site fails only that data written to the volume since the last remote snapshot was created is unavailable until the volume or production application server is restored Failover to the backup application server To maintain availability of the applications and the remaining data the following process occurs 1 A script or other application monit
7. Working with remote snapshots u c accaratnaceunredadedand ceswarongutinentierardenenGhaesasieastnedeaiaitosasharnteatacdiaates 17 New for ie hg Ss sretsdsasiepish ence oh ees greta nr slvden eae eonuihoadniinananeeshesteon oS Oasis Eear en senenn na 17 Creating a remote snapshot ss ncianinsasunxasassannierdarwnddeonaninnndeomiacnnesaanenrbenanniers elvan Siansarnraecenineen 17 BeSt PACH sis caiasiduianwencaststsnesviyoreumeda vis tesla intense siesie WATS An vacaudedeseaes tines tah utataled wakileas 17 Gemingdhere on ence ace pecan mute ace inore conan ce E 17 Creating the primary snapshot ss viceansanaahsrvawsansosanniy doivedaiienhewpsucnieaewuehawnd Anwendouvienumantatednineaile 18 Creating primary snapshots for volume sets ccceeeceeeeeeeeeeeeeeceeeeeeeeseeeeeseeeeeteeeeetaees 19 Creating a remote volume ssc uertssnssenaisie nie accalvsslin Baan timate Sacaan bide eter le bbs wba Siiies werlesin 21 Wak the system GOES 5 25 14 icnneainenichendaneaienioceend mara means aia aamnenaaiem um audeeeanaentuite 22 Creating the first COpy sas sn nniscsas counnonia accspauunenesipnauedoimonbiobneuiracinieabwthdaaisaanibanubonenacbaasesdelei 22 Viewing a list of remote snapshots cccccccceesecceeseeeeeeesceceeseeeceeeeeceeeceseseeeeeaeeeeneeeensaeeees 23 Setting the remote bandwidth yin tno i i ln tLe SSCs avn ts dd Wid eg Sinbad al used 23 Selecting remote bandwidth rate ccccccccccccescceeeeseeecesneeeseneceseneeceeeseeeseneee
8. e Remote Copy complete An alert is generated when the remote copy is complete Remote Copy failovers An alert is generated when a remote volume is made primary Remote management group status An alert is generated if the connection to a remote management group changes disconnects and or reconnects For information about configuring Active Monitoring see the HP LeftHand Storage Solution User Manual Scheduling remote snapshots In addition to taking remote snapshots of a volume manually you can set up a schedule to take snapshots and save them remotely Scheduled remote snapshots provide business continuance and disaster recovery as well as a consistent predictable update of data for remote backup and recovery Planning for scheduled remote snapshots is a crucial initial step in implementing Remote Copy The following items require planning in advance for successful deployment of scheduled remote snapshots e Recurrence frequency e Retention policies e Capacity planning Timing For detailed information about these issues see Planning for Remote Copy on page 12 Best practices for scheduling remote snapshots e Create a new remote volume to use with the scheduled remote snapshots 28 Using Remote Copy e If you are performing daily remote copies schedule the remote snapshots during off peak hours If you are setting scheduled remote snapshots for multiple volumes stagger the schedules with at least an hour be
9. unavailable servers can still access the volume through the other storage nodes in the cluster A virtual storage appliance that provides one or more simultaneous storage environments in which SAN iQ may execute as though they were running on the bare iron A manager that is added to a management group but is not started on a storage node until it is needed to regain quorum A logical entity that is made up of storage on one or more storage nodes It can be used as raw data storage or it can be formatted with a file system and used by a host or file server Two or more volumes used by an application For example you may set up Exchange to use two volumes to support a StorageGroup one for mailbox data and one for logs Those two volumes make a volume set P4000 Remote Copy user guide 67 volume lists For release 7 0 and earlier provide the link between designated volumes and the authentication groups that can access those volumes Not used in release 8 0 and later volume size The size of the virtual device communicated to the operating system and the applications VSS Volume Shadow Copy Service VSS Provider HP LeftHand P4000 VSS Provider is the hardware provider that supports the Volume Shadow Copy Service on the HP LeftHand Storage Solution writable space See temporary space 68 Glossary Index A adding a remote snapshot schedule 28 a remote volume 21 remote snapshots 7 affordable disaster recovery best pract
10. 21 creating on the fly 21 using an existing 2 resuming scheduled snapshots 31 retention policy for remote snapshots 14 Rolling Back a Volume from application managed snapshots 38 39 rolling back a volume Remote Copy and primary volumes 38 Remote Copy and remote volumes 39 S scheduled snapshots 29 pausing or resuming 31 schedules planning Remote Copy 15 scheduling remote snapshots 28 scripting for failover 33 setting remote bandwidth 23 snapshots creating application managed 18 29 30 creating application managed for volume sets 1929 deleting schedules 32 pausing or resuming 31 scheduling 29 split mirrors creating 39 Subscriber s Choice HP 57 synchronizing data after failover 36 after failover between acting primary volumes and original primary volumes 37 T technical support service locator website 58 timeline of failover 36 typographic conventions 58 U uses for Remote Copy 11 using Remote Copy for business continuance 41 for data migration 53 for off site backup and recovery 48 V viewing a list of remote snapshots 23 volume replication and Remote Copy 11 volume sets creating application managed snapshots for 19 29 deleting application managed snapshots for failing over from 33 volume type changing primary into remote 34 volumes cloning 11 cloning and data migration 54 synchronizing data after failover 37 P4000 Remote Copy user guide 71 W webs
11. Application Servers Server Server Server WAN Primary Remote Acting Volum Primary Storage Volume Subnet Acting Remote Primary Snapshot Snapshot Primary Snapshot Figure 13 High availability during failover Example configuration Achieving affordable disaster recovery Even if you do not have clustered application servers or network bandwidth required for configuring hot backup sites you can still use Remote Copy 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 snapshots 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 storage nodes as well as on tape Configuration for affordable disaster recovery To configure affordable disaster recovery create remote snapshots of your volumes in an off site location In addition you can create tape backups from the remote snapshots in the off site location e Designate one or more off site locations to be the destination for remote snapshots P4000 Remote Copy user guide 45 Set up a schedule for creating remote snapshots in the designated off site locati
12. Center website P4000 Remote Copy user guide 57 http www hp com support manuals In the Storage section click Disk Storage Systems and then select P4000 SAN Solutions HP websites For additional information see the following HP websites http www hp com e htto www hp com go storage http www hp com service_ locator htto www hp com support manuals http www hp com support downloads e htto www hp com storage whitepapers Typographic conventions Table 8 Document conventions Convention Element Blue text Table 8 Cross reference links and e mail addresses Blue underlined text hitp www hp com Website addresses Keys that are pressed Text typed into a GUI element such as a box Bold text YP GUI elements that are clicked or selected such as menu and list items buttons tabs and check boxes Italic text Text emphasis File and directory names System output Code Commands their arguments and argument values Monospace text Code variables Monospace italic text nes Command variables Monospace bold text Emphasized monospace text A CAUTION Indicates that failure to follow directions could result in damage to equipment or data IMPORTANT Provides clarifying information or specific instructions 58 Support and other resources EY NOTE Provides additional information 9 TIP Provides helpful hints and short
13. Network RAID 10 10 1 or 10 2 is required to protect data in an HP LeftHand SAN solution network window Graphically depicts the status of each storage node Storage nodes on the network are either available or part of a management group NTP Network Time Protocol parity In RAID5 redundant information is stored as parity distributed across the disks Parity allows the storage node to use more disk capacity for data storage peer site Absence of a primary site designation makes all the sites peer sites primary site A site designation assigned by the administrator in the HP LeftHand Centralized Management Console A primary site is more important than a secondary site In this setup you would run a majority of managers in the primary site In a two site setup this allows the primary site to stay online even if the network link between the primary and secondary sites fails Typically the primary site has maiority all of the application servers In configurations that do not designate a primary site the sites are referred to as peer sites original primary The primary volume that fails and then is returned to service volume overprovisioned An overprovisioned cluster occurs when the total provisioned space of all volumes cluster and snapshots is greater than the physical space available on the cluster This can occur when there are snapshot schedules and or thinly provisioned volumes associated with the cluster point in time Snap
14. OK The system automatically updates the volume set information when you click OK If you want to see the updated information you can click Verify Volume Associations then click OK EY NOTE If you have a schedule to remote snapshot a volume and you add a volume to the volume set using the application the system cannot update the volume set information as described above You must delete the schedule and create a new one to reflect the current volume set The schedule also reflects the volume associations based on the volume you select when you create the schedule That volume becomes the owning volume The Volume Set field of the schedule displays O next to the owning volume You should check that the field displays all of the volumes that you want to snapshot It is possible that the owning volume is not aware of all associated volumes If it is not select a volume that is aware of all associated volumes and create the schedule there The procedure below assumes that you selected a volume that is part of a volume set 1 In the navigation window select the primary volume Click the Schedules tab Click Schedule Tasks and then select New Schedule to Remote Snapshot a Volume Click Edit and then select a Start At time oO gt N Select a recurrence interval You can schedule a snapshot to occur every 30 minutes or more 6 Select a retention interval for the primary snapshot either number of days or number of snaps
15. connected iSCSI session associated with volume HdgtrsLogs To avoid possible data inconsistencies you must stop any applications and log off these sessions from the initiators before proceeding All changes to volume HdatrsLogs since snapshot HdgtrsLogs_SS_2 was created will be lost To continue with the operation click OK To create a new SmartClone volume instead click New SmartClone Volume To exit the operation without making changes click Cancel OK New SmartClone Volume Cancel Figure 8 Rolling back a primary volume if iSCSI sessions are still connected Centralized Management Console X WARNING All changes to volume BkupLogs since snapshot BkupLogs_FoFb_SS_1 was created will be lost To continue with the operation click OK To create a new SmartClone volume instead click New SmartClone Volume To exit the operation without making changes click Cancel oK New smartcione Volume Cancel Figure 9 Rolling back a primary volume if iSCSI sessions are not connected 5 Log off any connected iSCSI sessions 6 Click OK The primary snapshot version of the primary volume is restored as a volume with the same name 7 Reconfigure application servers to access the new volume Rolling back a remote volume A remote volume cannot be rolled back until you convert the remote volume into a primary volume and then perform the steps in Roll
16. failover to remote volume 4 1i 5 5 b oyu orsdentdnrergtnsretaee dienes aieianshoiaamedaanrananneiniaaet 35 Resuming production after failover cc cccecccsesceceeseeeeeneeeeneaeeeesesaeecseseeeceeaeeeeseeeseceseeeesseeeenaes 35 Synchronizing data ofter failover siya cesnavacns cates eer atondaaiedaednntasae eee acanrunoanie nea enieoniauades 36 EXO Cae e E E E 36 Returning operations to original primary site s s 0dceraesseanmsaszoeisnpayaananacreniedinevanaraepenonnaconanrs 36 Synchronizing the data between the acting primary volume and the original primary volume ser ee a E E E eee ac ee 37 Creating a new primary volume at the original production site cccccecceeeseeesteeeeteeeneeeees 37 Setting up a new production SIE 4 5 a2hasnslasanviannapeuaeersaadedead aie anaeeas ae ee nO eas 38 Making the backup site into the new production Site cccccccceesseceeeeeeeeeeeeeeeeteeecseeeeestseeeenses 38 Rolling back primary and remote volumes lt 3 cirisvandscnemetarasdacn rece twnerdiaonirided deaeeaawmbevmataens 38 Using SmartClone to clone a volume from a snapshot ccccecceeeeseeeeeeseeeeeeeeeeeeeeeeseseeeseaees 38 Rolling back a primary volume 23552555 so seianssewoni eieateenecdenasaenecanaadiadonimniuesenaunenaonoiant 38 PRETEQUISITOS sanese as aae eae dre eae e E a ge outs EE e arn r a E aa ieaiai 38 Rolling back a remote volume i2zciceeraruerniadeiereeneseiewinieiad abo ease arenes Boas 39 Using remote snapsh
17. 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 matches its corresponding primary snapshot e Up to two additional snapshots may be retained at any given time Because the SAN iQ software never deletes the last fully synchronized 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 two primary and five remote snapshots the software may retain up to four primary and seven remote snapshots for a period of time Table 3 on page 14 shows the maximum retained snapshots with respect to a specific retention policy Table 3 Snapshot retention policy and maximum number of retained snapshots Scheduled remote snapshot retention policy Maximum number of snapshots retained n of primary snapshotsx of remote snapshots n 2 of primary snapshotsx 2 of remote snapshots n of hours for primary snapshotsx of hours for remote n 2 primary snapshots older than nx 2 remote snapshots snapshots older than x n of days for primary snapshotsx of days for remote n 2 primary snapshots older than nx 2 remote snapshots snapshots older than x n of weeks for primary snapshotsx of weeks for re n 2 primary snapshots older than nx 2
18. sets 1 Select a volume that is part of a volume set for the snapshot 2 Log in to the management group that contains the volume for which you want to create a new snapshot 3 Right click on the volume and then select New Remote Snapshot Click New Snapshot P4000 Remote Copy user guide 19 5 Select the Application Managed Snapshot check box This option requires the use of the VSS Provider For information about the requirements for application managed snapshots see the HP LeftHand Storage Solution User Manual or online help This option quiesces VSS aware applications on the server before SAN iQ creates the snapshot The system fills in the Description field and disables the Servers field automatically You can assign servers after the snapshot is created 6 Enter a name for the snapshot or accept the default 7 Click OK The New Snapshot Associated Volumes window opens with a list of all volumes in the volume set 8 Optional Edit the Snapshot Name for each snapshot EY NOTE Be sure to leave the Application Managed Snapshots check box selected This option quiesces the application before creating the snapshots If you deselect the option the system creates a point in time snapshot of each volume listed 9 Optional Edit the Description for each snapshot 10 Click Create Snapshots to create a snapshot of each volume The Primary Remote window opens with the list of the snapshots you just created The fir
19. snapshots you can retrieve data directly from recent remote snapshots rather than using tape backups Otherwise retrieve data as you normally would from the tape backup P4000 Remote Copy user guide 49 Best practices Retain the most recent primary snapshots in the primary cluster By keeping snapshots on your primary volume you can quickly roll back a volume to a previous snapshot without accessing off site backups e When you create a schedule for Remote Copy specify the number of primary and remote snapshots that you want to retain You can retain primary snapshots to facilitate easy rollback of the primary volume EY NOTE Retention of snapshots affects the amount of space that is used in the cluster of storage nodes Balance the number of snapshots to retain with the amount of space you are willing to use You can still access remote snapshots or tape backups if you want to roll back to a snapshot that you did not retain e Retain remote snapshots in the backup location to facilitate fast recovery of backed up data If you retain a number of remote snapshots after a tape backup is created you can access the data without going to the backup tape Example configuration e Retain three primary snapshots This enables you to roll the primary volume back yet it requires a relatively small amount of space on the primary cluster e Retain up to a week s worth of remote snapshots on the backup cluster e For snapshots older th
20. snapshots fail After the primary volume is rolled back scheduled creation of remote copies will resume correctly Completed remote snapshots remain intact Using Remote Copy for data migration or cloning Remote Copy allows migration of data from one application server to another without interrupting the production application server This capability supports a number of uses such as data mining or content distribution P4000 Remote Copy user guide 53 Achieving data migration You can use Remote Copy to make a complete copy clone 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 for 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 Configuration for data migration To make a copy of a volume in a remote location configure a cluster of storage nodes in the remote location with enough space to accommodate the volume See Figure 21 on page 54 for an example configuration Application Workstations Design s Team 4 Design Team 2 Application CAD Serer for CAD Server 5 Serwers Next Generation for Current Eea Product WAN Read Write Read Only 4 Remote Volume Volume Storage Ba i P Subnet Remote Snapshot Primary Snapshot Production Site 41
21. user guide 17 In the navigation window log in to the management group that contains the primary volume or snapshot for which you are creating the remote snapshot You can create remote volumes and snapshots within the same management group In that case log in to the required management group Log in to the remote management group In the navigation window select the primary volume or snapshot If you want to copy an existing snapshot to a remote management group select that snapshot at this step Click Snapshot Tasks and then select New Remote Snapshot Creating the primary snapshot 1 In the Primary Snapshot Setup box click New Snapshot If you selected a snapshot to start the process you do not need to create a new snapshot 2 If you want to use VSS to quiesce the application before creating the snapshot select the Application Managed Snapshot check box This option requires the use of the VSS Provider For more information see the HP LeftHand Storage Solution User Manual or online help If the VSS Provider is not installed use SAN iQ to create a point in time snapshot not using VSS If the volume you selected is part of a volume set see Creating primary snapshots for volume sets on page 19 This option quiesces VSS aware applications on the server before SAN iQ creates the snapshot The system fills in the Description field and disables the Servers field automatically You can assign servers after the snaps
22. uses both NICs simultaneously for data transfer Log files for the storage node are stored both locally on the storage node and are also written to a remote log server This site is on an isolated network and power connection than the other sites However it can be in the same physical location as one of the real sites Also a site for a Failover Manager A collection of one or more storage nodes which serves as the container within which you cluster storage nodes and create volumes for storage Manager software runs on storage nodes within a management group You start managers on designated storage nodes to govern the activity of all of the storage nodes in the group The Management Information Base provides SNMP read only access to the storage node Variables that report health status of the storage node These variables can be monitored using alerts emails and SNMP traps P4000 Remote Copy user guide 63 Multi Site cluster A cluster of storage that spans multiple sites up to 3 A Multi Site cluster must meet at least one of the following conditions e Contain storage nodes that reside in two or more sites e Contain storage nodes that span subnets e Contain multiple VIPs The cluster can have a single site and the multiple VIPs make it a multi site cluster network RAID Synchronous replication mirroring or parity protection on a volume by volume basis Protecting data for a volume across all storage nodes in the cluster
23. using the SmartClone feature to clone a volume from a snapshot that contains the earlier copy of the data you want to use Creating a SmartClone volume preserves all snapshots while providing an exact copy of the desired data The SmartClone volume consumes no extra space on the SAN Rolling back a primary volume Rolling back a primary volume to a snapshot replaces the original volume with a volume that contains the snapshot s data The new volume has the same name as the original Ifa volume is part of a volume set typically you want to roll back each volume using its corresponding snapshot The system allows you to automatically roll back all associated volumes To see any associated snapshots select a snapshot click the Details tab and then look at the Snapshot Set field For more information about volume sets and snapshot sets see the HP LeftHand Storage Solution User Manual or online help Prerequisites Stop applications from accessing the volume A CAUTION Any remote snapshot that has not completed copying is canceled 1 Log in to the management group that contains the primary volume that you want to roll back 38 Using Remote Copy 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 Click Snapshot Tasks on Details tab and then select Roll Back Volume Centralized Management Console WARNING There is at least one
24. 00 PAS Subnet Remote Snapshot 3 00 PM Primary Remote Snapshot Snapshot 1 00 PME 7 00 PM Primary Remote Snapshot Snapshot 44 00 AM 77 00 AM Figure 19 Non destructive rollback from the primary snapshot e 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 20 on page 53 shows rollback of the remote snapshot 52 Sample Remote Copy configurations Application Workstations Clustered Application Application Server Servers WAN Read Write Read Only Read Write Primary i I Remote Primary Volume i Volume Volume Storage 5 00 Pat 5 00 PAS 3 00 Pat Subnet Primary Remote Snapshot Snapshot r X 3 00 PM 3 00 PM Primary Snapshot 7 00 PMS Remote Primary Snapshot Snapshot 1 00 PM 7 00 PM Primary Snapshot 77 00 AM Remote Primary Snapshot Snapshot 14 00 AM 14 00 AM Figure 20 Non destructive rollback from the remote snapshot Best practices Roll back the primary snapshot and keep the remote snapshots as a backup To ensure that Remote Copy continues to operate roll back the primary volume as follows 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 Before roll back scheduled remote
25. 1 is offline ActPrimaryVol_1 becomes primary Scripted failover causes remote volume to nie 1 33 p m j f and active and usable to application become the acting primary volume server 2 00 p m F primary volume comes back on OrigPrimaryVol_1 is online The following data needs to be synchronized once the primary volume is back online e Original volume which contains data from 1 00 to 1 30 p m e Acting primary volume which contains data from 1 33 to 2 00 p m Returning operations to original primary site After the original primary site is operational again restore operations to that site The steps to restore operations depend upon the state of the original primary volume e Ifthe 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 e Ifthe primary volume is not available Create a new primary volume synchronize the data with the acting primary volume and then return the acting primary volume to a remote volume 36 Using Remote Copy Create snapshots that contain the data that you need to synchronize Table 7 Creating snapshots of data to synchronize Synchronizing the data between the acting primary volume and the original primary volume Action Volumes and snapshots on primary management Volumes and snapshots on remote management What this step accom plishes 1 St
26. Creating a remote snapshot on page 17 Ship the storage nodes to the remote Site B Power them on and discover them in the CMC to display the temporary PrimeSync management group cluster and volume Copy the remote snapshot from the temporary PrimeSync management group to the existing remote Site B management group Disassociate the temporary PrimeSync management group from the remote Site B management group For more information see Disassociating remote management groups on page 40 Delete the temporary PrimeSync management group Set up the desired Remote Copy relationship such as configuring a schedule to create remote snapshots of the volume from the primary Site A to remote Site B management group PrimeSync ensures that the proper relationship is established between the original primary volume and the remote site Subsequent remote snapshots from the primary site to the remote site are incremental EY NOTE Use the initial snapshot that you used for the temporary PrimeSync management group copy to create the second Remote Copy or the schedule to create remote snapshots of the volume You are now setting up the Remote Copy that goes from primary site A directly to remote site B which maintains that relationship going forward For more information on PrimeSync see the Application Note SAN iQ Remote Copy PrimeSync Creating Initial Copy in the Customer Resource Center Viewing a list of remote snaps
27. HP StorageWorks P4000 Remote Copy user guide Abstract This guide provides information about configuring and using asynchronous replication of storage volumes and snapshots across geographic distances Part number AX696 96005 Third edition March 2010 Legal and notice information Copyright 2009 2010 Hewlett Packard Development Company L P Confidential computer software Valid license from HP required for possession use or copying Consistent with FAR 12 211 and 12 212 Commercial Computer Software Computer Software Documentation and Technical Data for Commercial Items are licensed to the U S Government under vendor s standard commercial license The information contained herein is subject to change without notice The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services Nothing herein should be construed as constituting an additional warranty HP shall not be liable for technical or editorial errors or omissions contained herein Contents 1 Understanding and planning Remote Copy seeeeeeeeeeeeeeeeeeeeees 9 How Remote Copy Works gtene rr aur area pte een nr E E tenner nn Cor re tee eee ersten errr TEE ae 9 Graphical representations of Remote Copy ccccsscccsssseecseseeeeeseeeeesseeeeneaeeeeseeeeseeteeeeseaeeeees 10 Copying the primary snapshot to the remote snapshot cscceeeeeeeeeeeeeeeeseenteeeeeesenaeeee
28. Production Site 2 Figure 21 Data migration example configuration How this configuration works for data migration Suppose you want to create a complete copy of a volume for an application to use in a different location 1 Configure a cluster of storage nodes in the new location to contain the copied volume 2 Create 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 move the snapshots to the remote cluster at your convenience 3 On the cluster in the new location make the remote volume into a primary volume 54 Sample Remote Copy configurations 4 Configure the application server in the new location to access the new primary volume Figure 22 on page 55 shows the migration of data after converting a remote volume into a primary volume Application Workstations Design Team 2 Application Team 2 CAD Serer for Servers Next Generation Product WAN Read wWrite Read Only Read Write Primary rece Remote Primary Volume Volume 2 Storage h Subnet Primary Primary Snapshot Snapshot 2 Production Site 1 Production Site 2 Figure 22 Configuration after data migration P4000 Remote Copy user guide 55 56 Sample Remote Copy configurations 4 Support
29. ack ccccececceesceeceseeeeseneeeceeceeeeesseceeseeeeeceseesensseeeenaes 50 How this configuration works for non destructive rollback cecceeeseeeeeeeteeeeeeceseeeeseeeeeeeeaee 51 Best practice Seena a E AE EEE E E EET EE REI E ER 53 Roll back the primary snapshot and keep the remote snapshots as a backup seceeeees 53 Using Remote Copy for data migration or cloning cc lt sc0i cccecsesccseusesieionasvensebsrerteesoneesentsenanceneent 53 Achieving data migration 3 2nd ccadcccaSiberidsocedasaeneete eee eee ae 54 Configuration for data migration 2 caiscsaceaviadecsaqesrmnstianestsncssccnaraninvatensesiavennatscansunestannenants 54 How this configuration works for data migration c ccceeesseeeesceeeeeeeeeeeeeeeeceseeeecseeeeenseeeenaes 54 A Support ond oiher VESOURCCS esos NE 57 Contacting FIP arise cise cibedasieaen Sade eulecssice shitesnitnale ote itsiin dels Sates Wealeng dale ep Oe bac cushseurecuish Sheds ERS 57 Subscript onmSeryiCe Vaaaaneieann cates dguaanov gala nateocandaeacinagnuceoced mansananiaysaneeateinaaemp anata cena 57 New and changed information in this edition c ccccesccccessecceesneceseeneeeeesseeeeeeeeeseneeeeseeeeenneeees 57 Related information 546 hscegn exteauh ts uspnaueneenen ate outa aac beatane ane agee tag eseig eco Rem ak tenant nEaaRNET 57 HP websites eee aa a ee eee ee ee ee ro 58 Typographic conventions c asssecieaaanecseicanaeneraeone ne mamnacienanead cami a La
30. age node levels Review Table 2 on page 12 for common configurations at various levels Table 2 Remote Copy SAN iQ and storage nodes Storage system level Remote Copy configuration Management groups Create remote snapshots in the same management group or in a different manage ment group than the primary volume If using different management groups the remote bandwidth setting of the man agement group containing the remote volume determines the maximum rate of data transfer to the remote snapshot Create remote snapshots in the same cluster or in a cluster different from the Clusters primary volume e Primary volumes contain the data to be copied to the remote snapshot Vol e Data is copied to the remote snapshot via the remote volume olumes e The remote volume is a pointer to the remote snapshot The remote volume has a size of O bytes h e After data is copied from the primary snapshot to the remote snapshot the remote Snapshots snapshot behaves as a regular snapshot Storage nodes Active monitoring of each storage node 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 management groups containing primary and remote volumes changes Planning the remote snapshot Prerequisites for creating a remote snapshot e Log in to both the management group that contains the primary volume and th
31. an one week go to the backup tape Achieving non destructive rollback As discussed in Rolling back primary and remote volumes on page 38 rolling a snapshot back to a volume requires you to delete 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 need to be deleted first You can use Remote Copy to roll a volume back to an old snapshot without losing the interim snapshots Because Remote Copy creates two sets of snapshots primary and remote snapshots you can roll a volume back to a snapshot and still retain the other set of snapshots Configuration for non destructive rollback To use remote snapshots for non destructive rollback e Create a remote snapshot schedule e Inthe schedule specify the same retention 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 an illustration of a non destructive rollback configuration in Figure 18 on page 51 50 Sample Remote Copy configurations Application Workstations Clustered Application Restore Application Serer Server Servers WAN Read Wirite Read Only
32. and other resources Contacting HP For worldwide technical support information see the HP support website http www hp com support Before contacting HP collect the following information e Product model names and numbers e Technical support registration number if applicable e Product serial numbers e Error messages e Operating system type and revision level e Detailed questions Subscription service HP recommends that you register your product at the Subscriber s Choice for Business website http www hp com go e updates After registering you will receive email notification of product enhancements new driver versions firmware updates and other product resources New and changed information in this edition The following additions and changes have been made for this edition The following information has been updated New data protection levels called Network RAID replace volume replication and availability designations e Additional functionality added to application managed snapshots e Anew Support and Other Resources chapter has been added The Preface was removed Related information The following documents and websites provide related information e HP StorageWorks P4000 SAN Solution User Manual HP StorageWorks P4000 Multi Site HA DR Solution Pack User Manual e CLIQ The SAN iQ Command line Interface User Manual You can find these documents from the Manuals page of the HP Business Support
33. asks and then select Cancel Remote Snapshot 5 Click OK Editing a remote snapshot To change the description and change the server assignment of a remote snapshot 1 Log in to the management group that contains the remote snapshot 2 Select the remote snapshot in the navigation window 3 Click Snapshots Tasks and then select Edit Snapshot 4 Change the desired information and then click OK Deleting a remote snapshot A CAUTION Do not delete individual snapshots that are part of a snapshot set To see associated snapshots select a snapshot click the Details tab and then view the Snapshot Set field For information about snapshot sets see the HP LeftHand Storage Solution User Manual or online help HP recommends that you keep or delete all snapshots for a volume set If you need to roll back to a snapshot you want to roll back each volume in the volume set to its corresponding snapshot The system gives you the option to automatically delete or roll back all associated volumes Log in to the management group that contains the remote snapshot Select the remote snapshot in the navigation window Click Snapshot Tasks and then select Delete Snapshot from the menu Click OK Poe P m If the snapshot is not part of a snapshot set If the snapshot is part of a snapshot set A confirmation message opens A warning message opens e Click Delete Snapshot e To delete all snapshots in the snapshot set click Delete All A
34. ata 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 37 for more information P4000 Remote Copy user guide 43 Application Workstations Clustered Production g Backup Production Application Application Application Application Servers Serer Serer Server WAN Primary Remote Acting Volum Primary Storage Volume Subnet iy 3 Acting Remote Primary Snapshot Snapshot Snapshot Figure 12 High availability configuration during failback Best practices Remote snapshots with volume replication 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 replication Volume replication allows you to create up to four copies of a volume on the same cluster of storage nodes as the primary volume The only limitation is that the cluster must contain at least as many storage nodes as replicas of the volume Replicating the volume within the cluster ensures that if a storage node in the cluster goes down replicas of the volum
35. cuts HP product documentation survey Are you the person who installs maintains or uses this HP storage product If so we would like to know more about your experience using the product documentation If not please pass this notice to the person who is responsible for these activities Our goal is to provide you with documentation that makes our storage hardware and software products easy to install operate and maintain Your feedback is invaluable in letting us know how we can improve your experience with HP documentation Please take 10 minutes to visit the following web site and complete our online survey This will provide us with valuable information that we will use to improve your experience in the future http www hp com support storagedocsurvey Thank you for your time and your investment in HP storage products P4000 Remote Copy user guide 59 60 Support and other resources Glossary The following glossary provides definitions of terms used in the SAN iQ software and the HP LeftHand SAN Solution active monitoring acting primary volume Active Passive Adaptive Load Balancing add on application application managed snapshot authentication group Auto Discover BondO bonding boot device CHAP clone point CLI cluster Active monitoring tracks the health of the storage node using notifications such as emails alerts in the CMC and SNMP traps The remote volume when it as
36. e The Status of the operation Viewing the status in the Remote Snapshot Details window The Remote Snapshot Details window displays additional details about a remote snapshot 1 In the tab window select the Remote Snapshots tab 2 Select a remote snapshot from the list of snapshots on the Remote Snapshots tab 3 Click Remote Snapshot Tasks and then select View Remote Snapshot Details X Source Info Time Primary Mgmt Group Exchange Start Time 09 29 2008 02 45 52 PM MDT Primary Snapshot HdatrsLogs_55_1 Elapsed Time 1m 22s Remote Mgmt Group RemExchange Est Time Remaining Os Remote Snapshot RemLogs_RS_1 Completion Time 09 29 2008 02 47 15 PM MDT Original Mgmt Group Exchange Original Snapshot HdetrsLogs_SS_1 Status Data Manual Scheduled Manual Data Copied 247 MB Snapshot Scanned Data Remaining 0 MB State Complete Current Rate NA Avg Rate 24 675 Kbisec Figure 6 Viewing remote snapshot details 26 Using Remote Copy During the remote copy process the Remote Snapshot Details window reports current statistics When the copy is completed the statistics show summary data For field descriptions see Table 5 on page 27 Table 5 Fields for Remote Snapshot Details window Statistic Fields Source Info section Primary Mgmt Group The management group containing the primary volume and snapshot Primary Snapshot Remote Mgmt Group The primary snapshot The management group containing t
37. e on and participating in RAID e Uninitialized or Inactive On but not participating in RAID e Off or Missing Not on e DMA Off disk unavailable due to faulty hardware or improperly seated in the chassis Device Specific Module The HP LeftHand Networks vendor specific DSM that interfaces with the Microsoft MPIO framework After failover the process by which you restore the primary volume and turn the acting primary back into a remote volume The process by which the user transfers operation of the application server over to the remote volume This can be a manual operation a scripted operation or VMware enabled A specialized manager running as a VMware appliance that allows you to place a quorum tie breaker node into a 3rd location in the network to provide for automated failover failback of the Multi Site SAN clusters The Failover Manager is designed to run on VMware ESX Server VMware Server and VMware Player It is installed on hardware separate from the SAN hardware 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 The frame size specifies the size of data packets that are transferred over the network Full provisioning reserves the same amount of space on the SAN as is presented to application servers ghost storage node Graphical Legend hardware reports hostname HP LeftHand Centralized Management Con
38. e VSS to quiesce the application before creating the snapshots Because the application is quiesced the data in the snapshot is consistent with the application s view of the data That is no data was in flight or cached waiting to be written when the application created the snapshot Creating a remote snapshot Creating a remote snapshot is the main task when working with Remote Copy You can either create a one time remote snapshot or set up a schedule for recurring remote snapshots Many of the characteristics for either case are the same Create a remote snapshot by using the following steps Log in to the primary management group Log in to the remote management group Create a primary snapshot of the primary volume manually When setting up a schedule to create a remote snapshot of a volume the software automatically creates a primary snapshot which is then copied to the remote volume Either create a remote volume on a remote management group or select an existing remote volume Create the remote snapshot Best practice The best way to prepare for remote snapshots is to create the management group and volumes that will be remote before taking the snapshot Although the interface allows you to create volumes and snapshots as you go that may be a distraction at the time a crucial snapshot is needed Getting there This procedure takes you to the New Remote Snapshot window where remote copy procedures start P4000 Remote Copy
39. e elsewhere in the cluster will still be available For more information about volume replication see the chapter Provisioning Storage in the HP LeftHand Storage Solution User Manual Example configuration Figure 10 on page 42 uses three storage nodes per cluster However this scenario can use any number of storage nodes For information about creating clusters and volumes see the HP LeftHand Storage Solution User Manual e In the production location create a management group and a cluster of three storage nodes e Create volumes on the cluster and set the replication level to 2 Way e Configure the production application server to access the primary volume via iSCSI e In the backup location create a second management group and a cluster of three storage nodes e Create a schedule for making remote snapshots of the primary volume See Scheduling remote snapshots on page 28 44 Sample Remote Copy configurations EY NOTE Volume replication levels are set independently for primary and remote volumes How it works If one of the storage nodes in the primary location fails the primary volume will still be available If all of the storage nodes fail or if the application server fails then failover to the backup application server occurs and the remote snapshot s becomes available Application Workstations Acting Clustered Production Backup Production Application Application Application dmm
40. e management group that contains the target cluster where the remote snapshot will be created e Designate or create a remote volume in that remote management group Ensure there is enough space on the target cluster for the remote snapshot Logging in to primary and remote management groups Log in to both the primary and the remote management groups before you begin or you must log in to the remote management group while creating a remote copy Designating or creating the remote volume Create a remote volume by using any of the following methods e Make an existing volume into a remote volume e Create a new remote volume while creating a remote snapshot 12 Understanding and planning Remote Copy Create a new volume from the cluster Details tab window and then select the Remote radio button on the Advanced tab of the New Volume window From the menu bar select Tasks gt Volume gt New Volume For more information about these methods of creating remote volumes see Creating a remote volume on page 21 Using schedules for Remote Copy Scheduled remote snapshots provide fault tolerance for business continuance and disaster recovery and a consistent predictable update of data for remote backup and recovery Planning the Remote Copy schedule Planning is critical The following issues impact the amount of storage available in the system e Recurrence e Capacity e Retention Recurrence How often do you wa
41. e same cluster in the same management group e Ina different cluster in a different management group e In a different cluster in the same management group Creates a placeholder in the cluster in the form of a ghost storage node that keeps the cluster intact while you remove the storage node to replace a disk or replace the storage node itself and return it to the cluster In Release 8 5 this changes to data protection level Prior to release 8 5 replication level is the term that designated how many copies of data to keep in the cluster Removed in Release 8 5 Prior to Release 8 5 replication priority allowed you to designate whether data availability or redundancy is more important in your P4000 Remote Copy user guide 65 restripe resync rolling back SAN iQ interface secondary site server shared snapshot site SmartClone volume snapshot snapshot set SNMP traps solution pack 66 Glossary configuration Release 8 5 forward defaults to availability This default can be changed using the Cliq Command Line Interface Striped data is stored across all disks in the cluster You might change the configuration of a volume for example change data protection level add a storage node or remove a storage node Because of your change the pages in the volume must be reorganized across the new configuration The system can keep track of several configuration changes at once This means you can change c
42. eesceeeeeeeeeseeeneeeeneeceseeeeseessneeeenee 44 High availability during failover Example configuration ccscccesceeeseeeeeeeeeeseeeneeenaees 45 Affordable disaster recovery example configuration cccccceeesceeeseeeeeetteeeeeneeeeeees 46 Restoring from a remote volume sszansseiannacdannrdaniaanhaeainndemseaduedeswedsawsdaueddonneasorhonnatcabedst 47 Restoring from tape backup i acess ntseaawate rugs sicondaatrendaneantiahass anion taeugdaaitelaidetenelenaiaises 47 Off site backup and recovery example configuration ccccccceceseceeseeeeenteeeeetteeeeeaes 49 Non destructive rollback example ci0icceiiectasacsseusnndasneateeeesnevesaenaeonctaeedes th eepescanevenseaies 51 Non destructive rollback from the primary snapshot cccccccecceceeseeeeeseeetenteeeeeteeeees 52 Non destructive rollback from the remote snapshot cccccccceeececeeeeteeseeteeeeesteeeesaeees 53 Data migration example configuration i lt sessinsdniaanvscsanesnsincesseertenindianebentonwuarnduasateieseet 54 Configuration ofter data migration dcocacsancrinre inven eiiomnanmeimanemceus 55 Tables 1 Uses for Remote Copy sicancasciqnasannsa cant donaxrnaiaarueieaacbay Pidasaaitabiangohonsagnancnannannganaementcn 11 2 Remote Copy SAN iQ and storage nodes ccccceccecessseeseeteeeseeeeeeeeeeeeeeseeeesseeeens 12 3 Snapshot retention policy and maximum number of retained snapshots ceseeeeees 14 4 Scheduled Remote Cop
43. emote snapshot schedule 33 remote snapshots 25 snapshot schedules 32 disassociating management groups 40 for PrimeSync disaster recovery affordable using Remote Copy 45 document conventions 58 related information 57 documentation HP website 57 providing feedback 59 P4000 Remote Copy user guide 69 E editing remote snapshot schedules 32 remote snapshots 25 F failback merging data for 43 to production configuration 43 Failover with volume sets 33 failover configuring 33 data availability during 43 planning 33 resuming production after 35 scripting for 33 setting up new site 38 synchronizing data after 36 timeline for 36 to backup application server 43 with Remote Copy 45 G Glossary for SAN iQ software and LeftHand SAN 61 graphical representations of Remote Copy 10 H help obtaining 57 high availability and failover 45 and Remote Copy 45 best practices 44 configuration diagram 41 configuration for 41 configuration of Remote Copy 45 HP technical support 57 icons for Remote Copy M management groups disassociating 40 disassociating PrimeSync 23 temporary for PrimeSync 23 merging data for failback 43 70 monitoring progress of remote copy 27 remote copy details 26 remote snapshots 25 N non destructive rollback best practices 53 configuration diagram 50 configuration for 50 O off site backup and recovery best practices 50 configurati
44. esseeeeeseeeees 24 Best Practice assy saicasonidehelwcsuiwadetneeiandtwins decinans O E a N E E A EAS 24 Setting the bandwidth isc cuaecosesapneseernnennbisannnieencaabimidensaasicuts etolabensabagntetentiiantennnmmdentaannned 24 Canceling a remote snapshot aissekensycsicnoinsai van AnisdainSwoeanvilenbiansplaninlindundalsabbenindswdueinsininntiinanes 24 Editing a remote snapshot snititastnctinnnteemanocsanrnamaupenioiabosrdin eben mnad iad amaiametonGaauuice 25 Deleting a remote snapshot a5uncdaucuksieannsecsmonensisena iad saimsonietuendiwlub dundee lomsdinminnianebeawbeawenents 25 Monitoring remote snapshots cha sashcnsnsedeseronnntersaranavorranvernnensdvanredonuntasataanenias tiwnsetnsearnietesmnereraannr 25 Monitoring details from the Remote Snapshots feature ccccccceececceseseceeeeseeeeeeeeeeeeeeeeseeeeeses 26 Viewing information in the Remote Snapshots tab ccccecceeeesceeeeeeeeeeeseeeeeeseeeeeseeeeenaes 26 Viewing the status in the Remote Snapshot Details window ceseeeeeteeeeeeetreeetteeeteees 26 Configuring active monitoring alerts for Remote Copy ccceccceeeeeeeeeeeeeeeeseeeeenseeeeeseeeeesteeee 28 Scheduling remote snapshots cos doicasesensrii lun iwivsetewuats tau ieaneieswdansieaiiecnedindalnihta uelaindaliwmsslostaReteuialety 28 P4000 Remote Copy user guide 3 Best practices for scheduling remote snapshots ccccccecesecceeeeeceeeseecesseeeeeeaeeesseseeeeseeeeenteeeeeses 28 Creating
45. f RAID1 disks e RAIDS data blocks are distributed across all disks in a RAID set Redundant information is stored as parity distributed across the disks e RAID50 mirrored sets of RAIDS disks Number of intact disks required to maintain data integrity in a RAID set The rate at which the RAID configuration rebuilds if a disk is replaced Condition of RAID on the storage node e Normal RAID is synchronized and running No action is required e Rebuild A new disk has been inserted in a drive bay and RAID is currently rebuilding No action is required e Degraded RAID is not functioning properly Either a disk needs to be re placed or a replacement disk has been inserted in a drive e Off Data cannot be stored on the storage node The storage node is offline and flashes red in the network window Register individual storage nodes to use add on applications Registration requires sending in the storage node serial numbers to purchase the license keys which are then applied to the storage node The primary volume and its associated remote volume An identical copy of a primary snapshot The remote snapshot is located on the same cluster as the remote volume The volume that resides in the Remote Copy 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 The remote volume can be stored in these ways e In th
46. ges move in the direction of the data flow from primary to remote snapshot HP LeftHand Networks Centra le Figure 2 Icons depicting the primary snapshot copying to the remote snapshot Graphical legend for Remote Copy icons The graphical legend window available from the Help menu depicts the icons associated with Remote Copy Graphical Legend X tems Hardware me _ Primary Shared Snapshot Remote Shared Snapshot Cluster Management Group item needs attention Virtual Manager Failover Manager Remote Snapshot Pair Shared Snapshot Relationship Figure 3 Icons for Remote Copy in the Graphical Legend window 10 Understanding and planning Remote Copy Remote Copy and volume replication Remote Copy is an asynchronous replication of data Volume replication is a synchronous replication of data Using synchronous volume replication on multiple storage nodes within a cluster in combination with asynchronous Remote Copy on a different cluster of storage nodes creates a robust h Uses for igh availability configuration Remote Copy Table 1 on page 11 shows common applications for the Remote Copy application Table 1 Uses for Remote Copy Use Remote Copy for How it works Business continuance and disaster recovery Remote Copy stores remote snapshots on a machine in a geographically separate location The remote snapshots remain available in the eve
47. gh the wizards The wizard uses the information you entered to fill The New Remote Snapshot window when you exit the wizard P4000 Remote Copy user guide 21 3 Optional Enter a description of the remote snapshot and click OK The system creates remote copy EY NOTE There may be a delay in remote copy time What the system does The system creates the remote snapshot in the cluster that contains the remote volume and 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 in the navigation window when the copy completes EY NOTE If you create a remote snapshot of a volume while a remote snapshot is in progress the second remote snapshot does not begin copying until the first remote snapshot is complete Creating the first copy Creating the first copy of data is the first step when setting up a Remote Copy solution Three methods for creating the first copy are described below Copy data directly to the remote site over the WAN Use this method if you are implementing the Remote Copy solution before you accumulate much data in the primary site and your hardware is already installed in the remote site With this method you create the primary management group and the remote management group in their respective locations and then create the initial copy of the data directly over the WAN using Remote Cop
48. he remote volume and snapshot Remote Snapshot The remote snapshot Original Mgmt Group The original management group that contained the original volume and snapshot This is used with PrimeSync feature Original Snapshot The first version of the snapshot from which the first copy was created This is used with PrimeSync feature Status Manual Scheduled Whether the snapshot was created manually or with a scheduled snapshot Snapshot Scanned The percentage complete of the copy process Values are 0 to 100 The current state of the copy process Valid values are Started Copying State Stalled and Complete Time Start Ti Time Zone date and time copy started The field format is MM DD YYYY ay ne HH MM SS AM PM The number of days hours minutes and seconds since the copy began Elapsed Time processing The field format is Xd Xh Xm Xs X N A signifies completed copies or in progress copies not yet calculated Est Time Remaining The number of days hours minutes and seconds estimated to remain in the copy process The field format is Xd Xh Xm Xs X N A signifies completed copies or in progress copies not yet calculated Completion Time Time Zone date and time copy completed The field format is MM DD YYYY HH MM SS AM PM N A signifies completed copies or in progress copies not yet calculated Data Data Copied Amount of data copied so far in smallest unit size
49. hot is created 3 Enter a name for the snapshot or accept the default EY NOTE Make the beginning of volume and snapshot names meaningful for example Snap 1Exchg_03 4 Optional Enter a description of the snapshot Click OK to return to the New Remote Snapshot window The information for the primary snapshot is pre filled For example the text for the field Snapshot Name has changed from Create Primary Snapshot to HdqtrsLogs_SS_1 6 In the Remote Snapshot Setup box use the drop down lists to select the remote management group and volume If you need to create a new volume click New Remote Volume 7 In the Snapshot Name field enter the name for the remote snapshot 8 Optional Enter a description for the remote snapshot 18 Using Remote Copy 9 Click OK in the New Remote Snapshot window The remote copy of the primary snapshot to the remote volume begins f HP LeftHand Networks Centra File Find Tasks Help mE Getting Started E Configuration Summary Efi Exchange EHE Servers 1 Ha Administration H Stes ESS ExchLogs Pertormance Monitor Storage Nodes 3 B Denver 1 Denver 2 Denver 3 Volumes 2 and Snapshots 2 BD Bkuplogs 1 U amp BkupLogs_SCsnap HagtrsLogs 1 Le EH i RemExchange Servers 0 Ha Administration H stes ESS RemExchLogs E Pertormance Monitor gt Storage Nodes 1 E Volumes 1 and Snapshots 2 RemL
50. hot to save existing data on the volume The snapshot that is then created retains all the volume s data 1 Enter a name for that snapshot in the alert 2 Click OK to continue The new snapshot is created and the volume becomes a remote volume The system creates 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 occurs according to the schedule Pausing and resuming scheduled snapshots At times it may be convenient to prevent a scheduled snapshot from taking place This section describes how to pause and then resume a schedule to snapshot a volume P4000 Remote Copy user guide 31 When you pause a snapshot schedule the snapshot deletions for that schedule are paused as well When you resume the schedule both the snapshots and the snapshot deletions resume according to the schedule Pause a schedule nef YP gt In the navigation window select the volume for which you want to pause the schedule Click the Schedules tab Select the schedule you want Click Schedule Tasks on the Details tab and then select Pause Schedule In the Confirm window click OK In the Next Occurrence column of the Schedules tab window this snapshot schedule is marked as paused Make a note to resume this snapshot schedule at a convenient time Resume a schedule ao PSS In the navigation window select the volume fo
51. hots View a list of remote snapshots associated with management groups clusters volumes or snapshots 1 2 In the navigation window select a cluster to view its list of remote snapshots Click the Remote Snapshot The report in the Remote Snapshot tab lists management groups and all the snapshots The other columns show status information about the remote snapshots For more information see Monitoring remote snapshots on page 25 Setting the remote bandwidth The remote bandwidth sets the maximum rate for data transfer between management groups The copy rate is equal to or less than the rate set P4000 Remote Copy user guide 23 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 the remote management group When setting the remote bandwidth you can choose from a list of common network types or calculate a custom rate based on your particular requirements Selecting remote bandwidth rate You may either select a preset speed from a list of standard network types or calculate a custom speed based on your specific requirements Remember that the speed is the maximum rate at which data copies Defaults setting When setting remote bandwidth selecting Defaults allows you to choose from a list of common network types Custom setting The custom setting for remote bandwidth defaults to 32 768KB or about 4MB Use the ca
52. hots You can retain up to 50 snapshots for a volume 7 If you want to use VSS to quiesce the application before creating the snapshot select the Application Managed Snapshot check box This option requires the use of the VSS Provider For more information see Requirements for application managed snapshots in the HP LeftHand Storage Solution User Manual If the VSS Provider is not installed SAN iQ allows creation of a point in time snapshot not using VSS This option quiesces VSS aware applications on the server before SAN iQ creates the snapshot 8 Select the management group and volume that will hold the remote snapshots 9 Log in if you need to 10 Click New Remote Volume to use the wizard to create a volume if you need to make a new one 11 Set the retention interval for the remote snapshot You can retain up to 50 snapshots for a volume 12 Click OK The Volume Associations Found window opens with a list of all volumes in the volume set 13 Review the information about the volume set and the remote copies the schedule will create 30 Using Remote Copy Timing 14 Click Continue The Primary and Remote Volume Associations window opens with the list of the primary volumes in the volume set The first volume is already set up and the next one in the list is selected 15 In the Remote Volume Setup box use the Volume Name drop down list to select the remote volume to use for the selected volume All remote volume
53. hots for a volume 12 Click OK to close the scheduling window and return to the navigation and tab windows The timetable you just created is now listed in the Schedules tab view Creating the schedule for volume sets The schedule creation process for application managed remote snapshots differs only when an application has associated volumes Associated volumes are two or more volumes used by an application volume set For example you may set up Exchange to use two volumes to support a StorageGroup one for mailbox data and one for logs Those two volumes make a volume set When you create an application managed remote snapshot of a volume in a volume set the CMC recognizes that the volume is part of a volume set SAN iQ then prompts you to create a snapshot and remote copy of each volume in the volume set This creates a snapshot set and remote copy that corresponds to the volume set To see any associated snapshots select a snapshot click the Details tab and then view the Snapshot Set field P4000 Remote Copy user guide 29 For information about the requirements for application managed snapshots see the HP LeftHand Storage Solution User Manual or online help When you first create the schedule the system stores information about the volume set as it exists at that time If you remove volumes from the volume set using the application you must update the SAN iQ schedule To update it you only need to edit the schedule and click
54. ices 48 configuration 45 application managed snapshots creating 18 29 30 creating primary snapshot for volume sets 19 29 deleting 19 deleting remote 25 failing over from 33 promoting remote to primary 35 rolling back from 38 39 B backup and recovery using Remote Copy 48 benefits of Remote Copy 11 best practices for affordable disaster recovery 48 for high availability 44 for non destructive rollback 53 for off site backup and recovery 50 scheduled remote snapshot 17 28 scheduled remote snapshots schedule 15 C canceling remote snapshots 24 changing backup site into new production site 38 primary volume into remote volume 34 clone of volume 11 configuration for affordable disaster recovery 45 for data migration 54 for high availability 41 for non destructive rollback 50 for off site backup and recovery 49 configuring failover 33 Remote Copy 12 contacting HP 57 conventions document 58 copying using Remote Copy 17 creating first remote copy 22 first remote copy using PrimeSync 23 remote snapshots 22 31 split mirrors 39 D data availability during failover 43 merging for failback 43 synchronizing after failover 36 transfer rate bandwidth setting 23 data migration and volume cloning 54 configuration diagram 54 configuration for 54 using Remote Copy for 53 with remote snapshots 39 data mining split mirror 40 with remote snapshots 39 deleting r
55. ing back a primary volume If a volume is part of a volume set typically you want to roll back each volume using its corresponding snapshot The system gives you the option to automatically roll back all associated volumes To see any associated snapshots select a snapshot click the Details tab and look at the Snapshot Set field For more information about volume sets and snapshot sets see the HP LeftHand Storage Solution User Manual or online help Using remote snapshots for data migration and data mining Use remote snapshots to create split mirrors for data mining and data migration A split mirror is a 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 P4000 Remote Copy user guide 39 New for release 8 0 Consider using the SmartClone feature to create a split mirror The SmartClone volume is an exact copy of the volume or snapshot yet consumes no extra space on the SAN Creating a split mirror To create a split mirror Create a remote snapshot Create a server for client access e Configure clients to access the remote snapshot Disassociating remote management groups Management groups become associated when linked by either remote snapshots or scheduled remote snapshots Disassociating management groups destroys all the shared knowledge between those groups Best practice for disassociating management groups
56. innsdanmeabsbianpiianniius 45 Configuration for affordable disaster recovery csccececeeseseeeeteeseseeeneeecseeeseeeeseaeestaeestaeentneeess 45 How this works for affordable disaster recovery cccscccceseseceeseceeeeeeeeeeeeeeseeeeseceseeeessteeeenaes 46 Best Practices orrena e rue init usd TARAN E A Guaacaid E E a E 48 Select an optimum recurrence schedule 2cccnincswiaseaieiehoaWieaattanbbiauniacctebgceiagMeiamncaneaeoees 48 Use remote snapshots in conjunction with local synchronous volume replication 06 48 Using Remote Copy for off site backup and recovery ccccssccceesseeeeeeeeeeeeeeeeeeseeeeenseeeensseeeeeneeeees 48 Achieving off site backup pcs ctalensiceanst acwrneascocaned danas dowstattasaecudwepe anaes dessGaapiaiagsanaacenaionaetal 49 Configuration for off site backup and recovery sid scc0sidansicissvccasedetwrdeswnds veh dnbeniehsandbwnnubenennddennias 49 Configuration I FENG ICIIATFcacssrszodosensp stones wa barestngnredan an aaiandied tartan nenaldmsanolaanmnn adbeasieaaepmannenarenens 49 How this configuration works for offsite backup ecceeeseeeeseeseseeeteeeeseeeeeeeceeaeesnaeeetseeetteeeates 49 Best Pract Ges ssercstoiees hesedeestaees a a dna ceeuoved Setar N a a a a 50 Example configuration esnea ian a ia tt tenes sme EAE NE Ea EE E 50 Achieving non destructive rollback 9 senusepiaasaasaeunnasneoauendacunnunsacunena raedspne Ravan nauiaeeuas 50 Configuration for non destructive rollb
57. ites HP HP Subscriber s Choice for Business 57 product manuals 57 72
58. lculation tool to identify a desired bandwidth setting For example if you have a T1 line and you want to set the remote bandwidth to 12 of that capacity you can use the calculation tool to find the correct value 189KB Calculate Custom Bandwidth Calculate a Custom Bandwidth Speed Select the bandwidth speed and the percentage to calculate a fractional bandwidth T1 1 544 Mb sec v k2 189Kbisec Note This speed will be converted to Kh sec and displayed in the Custom field upon returning to the Edit Remote Bandwidth window Figure 5 Calculating a custom value for setting remote bandwidth Best practice Set the bandwidth speed the same in both directions unless you have an asymmetrical WAN link Setting the bandwidth In the navigation window select either the remote or primary management group Click Management Group Tasks and then select Edit Management Group Select the remote or primary management group Click Edit Remote Bandwidth Change the bandwidth setting as desired oF YS Canceling a remote snapshot When you cancel a remote snapshot that is in progress the remote snapshot is deleted but the primary snapshot remains 1 In the navigation window select the remote snapshot 2 Click the Remote Snapshot tab 24 Using Remote Copy 3 Select the remote snapshot you want to cancel from the list if it is not already selected 4 Click Remote Snapshot T
59. m the clone point will display these older snapshots that they share as well as the clone point A user designated location in which storage nodes are installed Multi Site SAN configurations have multiple sites with storage nodes in each site and each site has its own subnet A site can be a logical configuration such as a subnet within the same data center department or application SmartClone volumes are space efficient copies of existing volumes or snapshots They appear as multiple volumes that share a common snapshot called a clone point They share this snapshot data on the SAN A fixed version of a volume for use with backup and other applications Application managed snapshots created for a volume set Use traps to have an SNMP tool send alerts when a monitoring threshold is reached HP LeftHand P4000 Windows Solution Pack split mirror standard cluster storage server stripe synchronize target secret temporary space thin provisioning Trap Community String unicast VIP virtual IP address virtual machine virtual manager volume volume set 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 Also known as a cluster A standard cluster is one that does not use any of the Multi Site features within the SAN iQ software Standard clusters Cannot contain storage nodes tha
60. me while a remote snapshot is in progress Either wait until the remote snapshot copy completes before making the remote volume into a primary volume or cancel the in progress remote copy Click Finish The snapshot is created and the volume becomes a remote volume The final window of the wizard displays a summary of the actions and a reminder to reconnect your iSCSI sessions Using failover to remote volume If the primary volume is not available you can use the wizard to promote the remote volume to an acting primary volume l 2 3 4 In the navigation view select the volume that you want to convert Right click the volume and then select Failover Failback Volume Click Next Select the reason you are failing over the volume Use the second choice if your primary volume is not available and you want to get an acting primary volume into production Select To failover to the remote volume and click Next The next window reminds you to disconnect any iSCSI sessions connected to the volume The final step is to make the remote volume into an acting primary volume This acting primary volume connects to application servers in order to maintain business continuance or accomplish disaster recovery Click Finish The final window of the wizard displays a summary of the actions and a reminder to reconnect your iSCSI sessions If you promoted a remote application managed snapshot use diskpart exe to change the resulti
61. napshots 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 Consider 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 several timetables for scheduled remote snapshots each with different retention policies For example suppose you want to create remote snapshots every four hours to ensure that no more than four hours worth of data is lost in an emergency In addition you want to retain one week s worth of remote snapshots Retaining four hour snapshots for one week can result in the accumulation of over AO remote snapshots Another approach would be to create two remote snapshot schedules for the volume e One schedule to create remote snapshots every four hours but only retain the most recent six remote snapshots This ensures that you do not lose more than four hours worth of data in an emergency e A second schedule to create remote snapshots every 24 hours and retain 7 remote snapshots Use remote snapshots in conjunction with local synchronous volume replication To prevent data loss reinforce Remote Copy with synchronous replication of the volume within the cluster of storage nodes at the primary geographic site With s
62. nd is readily available in the event of a site or system failure Achieving high availability Creating remote snapshots in remote locations with Remote Copy ensures that applications such as SQL Server Oracle and Exchange have access to backup copies of data volumes if production application servers or data volumes fail Using off site remote snapshots of your production volumes you can configure a backup application server to access those remote snapshots or volumes Off site remote snapshots particularly when supplemented with synchronous volume replication within a cluster ensure high availability of critical data volumes Configuration for high availability To use remote snapshots for high availability configure a backup application server to access remote volumes in the event of a primary system failure Figure 10 on page 42 illustrates this simple high availability configuration e Configure primary and backup application servers During normal operation the production application server reads and writes to the primary volume 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 or VSS to quiesce the application before creating remote snapshots P4000 Remote Copy user guide 41 Application Workstations Clustered Production Backup Application Application Application Serwers Serwer Serer WAN Read Only Pimay S
63. ng volume s attributes For more information see the HP LeftHand Storage Solution User Manual or online help Resuming production after failover After failover occurs three scenarios exist for resuming production Failback returns operations to the original primary site it is restored Convert the backup site to the new primary site Set up a new primary site and resume operations at that site P4000 Remote Copy user guide 35 The task flow for restoring or recovering data and resuming the original Remote Copy configuration is different for each scenario Use these procedures when you are resynchronizing data between the acting primary volume and the recovered or newly configured production site primary volume Synchronizing data after failover After a failover there are usually two snapshots or volumes that have conflicting data Recovering and synchronizing data depends on multiple factors including the application involved For more information about synchronizing see Glossary on page 61 Example scenario The following example illustrates one process for synchronizing data Remember that synchronization is optional Timeline of failover Table 6 Timeline of failover Time Event What happens 1 00 p m Regular hourly scheduled remote snapshot RemoteSS_1 creates in remote manage starts ment group 1 10 p m Remote copy finishes Copying is complete 1 30 p m Primary volume goes offline OrigPrimaryVo1_
64. nonaaeed 58 HP product documentation survey swcianssheneisin sambitininsaniadasiel oni leaselasuwphensehanndvanonblanietnunialelbaiuhbaes 59 NE eE 6 P4000 Remote Copy user guide 5 Figures oOo N OOK UU N 10 11 12 13 14 15 16 17 18 19 20 21 22 Basic flow of Remote OY oxo sisushn durex coeare ned hutiataasedanenhmnehtatextolansnaaca neem mcadienscmesar 9 Icons depicting the primary snapshot copying to the remote snapshot ccceeeeeeeees 10 Icons for Remote Copy in the Graphical Legend window cccceesceceteeeereeeeteeeeneeeees 10 Remote copy iN progress eeeeeceeeeeceeeeeeeeeeeenteeseeeeeeceeeeceeeeeceeeeeeeeeeeeeeeeeaaeaaaaaaaaeeees 19 Calculating a custom value for setting remote bandwidth ccceeesceeeseeeeteeeeeeeeeees 24 Viewing remote snapshot details 1 2 icsam tesacernnmaenanenime metered enapeeriies 26 Viewing remote snapshot details for remote Copy in progress cccccceeeseeseesteeeesteeeees 28 Rolling back a primary volume if iSCSI sessions are still connected cecceeereeeeteeeees 39 Rolling back a primary volume if iSCSI sessions are not connected ccescceeseeeeteeeeeee 39 High availability example configuration ccsistsnaieacedtaanmasnceanseauannipanniyborinmenieaeuabnienrs 42 High availability configuration during failover ceccceeseeeesseseeeeeeteeceeeeeeseeesneeeeneeeees 42 High availability configuration during failback escc
65. nt of a site or system failure at the primary site Off site backup and recovery Remote Copy eliminates the backup window on an application server by creating remote snapshots on a backup server either local or remote and back up from that server Split mirror data migration con tent distribution Volume clone Remote Copy makes a complete copy of one or more volumes without interrupting access to the original volumes You can move the copy of the volume to the location where it is needed Remote Copy creates copies of the original volume for use by other ap plication servers Benefits of Remote Copy Remote Copy 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 Copy 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 Therefore failback may need to resynchronize only the latest changes rather than the entire volume Remote Copy is robust If the network link goes offline during the process copying resumes where it left off when the link is restored P4000 Remote Copy user guide 1 Planning for Remote Copy Remote Copy works at the management group cluster volume snapshot and stor
66. nt 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 four hours you should ensure that the time to copy that snapshot to the remote location is less than four hours Testing the copy time One way to check the time required to copy a snapshot is to run a test of the actual process To test this process take two remote snapshots of the primary volume Because the first remote snapshot copies the entire volume it takes longer to copy The second remote snapshot copies only changes made to the volume since the first remote snapshot was taken You create the second remote snapshot after the time interval you intend to schedule Because of that the copy time for the second remote snapshot is more representative of the actual time required for copying subsequent remote snapshots To test the copy time 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 EY NOTE This is the minimum amount of time that you should allow between scheduled copies 5 Check the remote bandwidth setting for the other management group by using the Edit Management Group command This setting affects the time required to copy a remote snapshot P4000 Remote Cop
67. ociated with it A clone point is created when a SmartClone volume is created from a snapshot or from snapshot temporary space Command line interface for the SAN iQ software A cluster is a grouping of storage nodes that create the storage pool from which you create volumes P4000 Remote Copy user guide 6l CMC communication mode community string Configuration Summary data center disaster recovery site disk status DSM DSM for MPIO failback failover Failover Manager failover recovery frame size full provisioning 62 Glossary Centralized Management Console See HP LeftHand Centralized Management Console The unicast communication among storage nodes and application servers The community string acts as an authentication password It identifies hosts that are allowed read only access to the SNMP data The Configuration Summary displays an overview of the volumes snapshots storage nodes and iSCSI sessions in the HP LeftHand Storage Solution It provides an overview of the storage network broken out by management groups Also known as a Site A data center is a physical location in your environment where application servers SAN storage and network equipment reside In the SAN iQ Multi Site software a data center is typically referred to as a site Similar to a secondary site the disaster recovery site is used to operate the SAN in the event of a disaster Whether the disk is e Activ
68. ogs 2 RemLogs_SS_1 Figure 4 Remote copy in progress Creating primary snapshots for volume sets The primary snapshot creation process for application managed snapshots differs only when an application has associated volumes Associated volumes are two or more volumes used by an application volume set For example you may set up Exchange to use two volumes to support a StorageGroup one for mailbox data and one for logs Those two volumes make a volume set When you create an application managed snapshot of a volume in a volume set the CMC recognizes that the volume is part of a volume set The CMC then prompts you to create a snapshot for each volume in the volume set This creates a snapshot set that corresponds to the volume set To see any associated snapshots select a snapshot click the Details tab and then look at the Snapshot Set field For information about the requirements for application managed snapshots see the HP LeftHand Storage Solution User Manual or online help EY NOTE After you create snapshots for a volume set you do not want to delete individual snapshots from the snapshot set You want to keep or delete all snapshots for the volume set If you need to roll back to a snapshot roll back each volume in the volume set to its corresponding snapshot The system gives you the option to automatically delete or roll back all associated volumes To create a primary snapshots for volume
69. om the volume set are reflected here Click Close to return to the Edit Schedule to a Snapshot Volume window The updated list of volumes is populated in the Volume Set field For more information see the HP LeftHand Storage Solution User Manual The Volume Set field allows you to see the current volume set information Click OK The information is automatically updated Deleting the remote snapshot schedule 1 wR WN In the navigation window select the primary volume that has the schedule you want to delete Click the Schedule tab Select the schedule you want to delete Click Schedule Tasks and then select Delete Schedule Click OK Failover and tailback using Remote Copy Configuring Remote Copy for failover provides for business continuance and disaster recovery When configuring failover consider both the failover and failback paths Planning failover To achieve failover consider the following points The location and structure of management groups and clusters Configuration of primary and remote volumes snapshots and scheduling snapshots Configuration of application servers and backup application servers Task flow for failback resuming production after failover If a volume is part of a volume set typically you want to fail over each volume using its correspond ing snapshot To see associated snapshots select a snapshot click the Details tab and review the Snapshot Set field For more information abo
70. on diagram 49 configuration for 49 using Remote Copy for 48 P pausing scheduled snapshots 3 1 planning failover 33 remote copy schedules 15 remote snapshot schedules 13 remote snapshots 2 prerequisites for rolling back primary volumes 38 primary snapshots 18 primary volumes prerequisites for rolling back 38 rolling back 38 PrimeSync 22 temporary management group and 23 using for first copy 23 production resuming after failover 35 R recurring snapshots 29 related documentation 57 remote bandwidth setting 23 Remote Copy and volume replication 11 creating 10 creating the first copy 22 disassociating management groups 40 disassociating PrimeSync management groups 23 high availability configuration 45 icons for 10 monitoring details window 26 monitoring progress of 27 overview 9 planning checklist for remote copy schedules Is PrimeSync 23 routine backup and recovery 48 remote copy high availability 45 Remote Copy business continuance 48 high availability and failover 45 remote snapshots canceling 24 creating 17 22 31 creating schedule 28 data migration 39 data mining 39 deleting 25 deleting application managed 25 deleting scheduled 33 editing 25 editing schedules 32 monitoring 25 monitoring details window 26 new 17 planning 12 planning for scheduled 13 primary 18 retention policy 14 remote volumes adding 21 creating manually
71. onfigurations even while a volume is in the midst of a different reconfiguration In particular if a reconfiguration was done by accident you don t have to wait until it finishes to change back to the original configuration See Stripe When a storage node goes down and writes continue to a second storage node and the original store comes back up the original storage node needs to recoup the exact data captured by the second storage node Replaces the original volume with a read write copy of a selected snapshot New for release 8 0 The new volume retains the same name When you initially set up a storage node using the Configuration Interface the first interface that you configure becomes the interface used for the SAN iQ software communication A site that is less important than the primary site In this setup a minority of managers runs in the secondary site In a two site setup this allows the secondary site to go offline if the network link between the Primary and secondary sites fails Typically the secondary site has a minority or none of the application servers If the primary site fails customers can manually recover quorum in the secondary site An application server that you set up in a management group and then assign volumes to it to provide access to those volumes Shared snapshots occur when a clone point is created from a newer snapshot that has older snapshots below it in the tree All the volumes created fro
72. ons If your applic ation server uses multiple volumes that must be in sync use a script to quiesce the application before creating remote snapshots e Create routine tape backups of the remote snapshots in the off site locations Figure 14 on page 46 shows an example configuration for disaster recovery Application Workstations Production Production Library Appiloatiorn Application Application Serwers Server Server WAN Read Write Read Write ORAE PAEA onna aola Primary Volume Volume Storage p ff i eee Bani iih Subnet Primary Remote Remote Primary Snapshot Snapshot 1 Snapshot 2 Snapshot Production Site 41 Backup Site Production Site 2 Figure 14 Affordable disaster recovery example configuration How this works for affordable disaster recovery If the storage nodes in your primary location fail or volumes become unavailable the off site location contains the most recent remote snapshots Use the remote snapshots to resume operations as shown in Figure 15 on page 47 If you created tape backups you can recover data from tape backups as shown in Figure 16 on page 47 e Only data written to the primary volumes since the last remote snapshot was created will be un available e Application servers that were accessing the offline volumes will not be available until you recon figure them to access recovered data To resume operations using the most recent set of remote snapshots
73. op applications that are accessing the volumes 2 Make a snapshot of the original volume Creates a snapshot of the original primary volume that includes the data from 1 00 1 30 p m 3 Make the acting primary volume into the remote volume This automatically creates a snapshot of the acting primary volume group group OrigPrimary Vol_l1OrigPrimarySS_1 Remote vol_lActPrimarySSs_1 Returns the remote man agement group to its original configuration In addition you capture the 1 33 to 2 00 p m data Synchronize the data Synchronize the snapshots OrigPrimarySS_1l and ActPrimarySS_1 that were created in Steps 2 and 3 of Table 7 on page 37 In the simplest case to synchronize the snapshots remote copy the remote snapshot back to the original primary volume For more information about synchronizing see Glossary on page 61 Creating a new primary volume at the original production site If the original primary volume is not available designate a new primary volume synchronize the data from the acting primary volume and then configure the timetable for the scheduled remote snapshot schedule on the new primary volume 1 Stop the application that is accessing the acting primary volume wR WN Create a remote snapshot of the acting primary volume Convert the remote volume into a primary volume Make the acting primary volume into the remote volume This creates a snapshot of that volume
74. oring the production application server discovers that the 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 For information about scripting see the CLIQ The SAN iQ Command Line Interface User Manual and the sample scripts available on the HP LeftHand website 3 Because the backup application server was configured to access the remote now primary volume operation of the backup application server begins The application continues to operate after the failover to the backup application server Failback to the production configuration When the production server and volumes become available again you have the following two failback options e Resume operations using the original production server and then return the backup volumes to their original remote status as illustrated in Figure 12 on page 44 This will require migration of data that was written to the backup volumes since the failure back onto the production volumes e Continue operating on the backup application server When the production server and volumes become available configure the production server to be the backup server role reversal Merging data for failback In the failover scenarios described above there are probably two snapshots with different d
75. ots for data migration and data mining cccceececeeeseeceenseeeenseeeeeseeeeesteeeees 39 INE for release 8 0 tp rusriciecnibaneee manent a E R 40 Creating a split mirror sc ccissscey GucrnniepeinteravwessemiadeeaRcinnde natn mene aia 40 Disassociating remote management GrOUPS eseeeeeceeeaeeeeeeeeceeneaeeeeeceeeaecueecesceeeeeaeeeeseeeeeeaeeeetees 40 Best practice for disassociating management groups ssccceeeeceeeeseeeeenseeeceeeeeeestseeeseeeeeetaees 40 3 Sample Remote Copy configurations cccccccccccceceeeesststtseeeeeeeeeeeeeens 41 Using Remote Copy for business continuance cccceeseeeeeseeeeeeeeeeceeeeceeseeecenseeeeeaeeeeeteeeseeteeenes 41 Achieving high availability sssrisssi scheint van lyst a ota St lta 41 Configuration for high availability pscscsss cadsncduinnsasncaotneavineneibansnegnipartenertenenanencanecnnn ceventenist 41 How this configuration works for high availability cccccceeeeceeeeeeeeeeeeeeeeeeeenseeeeeenseeeetaees 42 Best practices 5 nsoiclsiac ne sate dna vba noaandetenaeneas baanndsnsgates dain einlagabanbeb nents A tee ntedeeuiae tie adenine 44 Remote snapshots with volume replication eccccceeeeeeseeceeeeeeeeeeeeeeeeeeneeeeestenieeeeessnees 44 Example configuration ch auass naainee wand saeuaneammnedeadonnaeatawsibeauhasaananen sani aeac one eeaniannameens 44 Achieving affordable disaster recovery sisii caisicavis catngsatiinasoiuasysnudponstbanmrsannesa
76. pshot of the primary volume to preserve the existing data that is on the volume Next the primary volume is converted to a remote volume 1 2 3 4 34 In the navigation view select the volume that you want to convert Right click the volume and then select Failover Failback Volume Click Next Select the reason you are failing over the volume Use the first choice if your primary volume is available and you are planning a preemptive move of the primary volume For the steps to use the second choice see Using failover to remote volume on page 35 Select the first choice To move the primary volume and click Next The next window reminds you to disconnect any iSCSI sessions connected to the volume Disconnect the iSCSI sessions if any are displayed and then click Next The next window begins the process to make the primary volume into a remote volume Enter a name and a description for the snapshot to be taken of the current primary volume This snapshot preserves the existing data on the volume Click Next The next window is where you designate the destination for copying the snapshot to a remote snapshot Using Remote Copy 10 The final step is to make the remote volume into an acting primary volume This acting primary volume connects to application servers in order to maintain business continuance or accomplish disaster recovery EY NOTE 11 You cannot make a remote volume into a primary volu
77. r which you want to resume the snapshot schedule Click the Schedules tab Select the schedule you want Click Schedule Tasks on the Details tab and then select Resume Schedule In the Confirm window click OK In the Next Occurrence column of the tab window this snapshot schedule shows the date and time the next snapshot will be created Editing the schedule to remote snapshot a volume When editing the timetable for a schedule to remote snapshot a volume you can change the following items Schedule Description start date and time recurrence policy Primary Setup Retention policy Remote Setup Retention policy Edit the remote snapshot schedule If the snapshot is part of a snapshot set you can also verify that the volumes included in the schedule are the current volumes in the volume set For more information see the HP LeftHand Storage Solution User Manual 1 2 3 4 32 In the navigation window select the primary volume that has the schedule you want to edit Click the Schedules tab and then select the schedule to edit Click Schedule Tasks and then select Edit Schedule Change the desired information Using Remote Copy Optional If displayed click Verify Volume Associations to see if the volume set included in the snapshot set is up to date The Verify Volume Associations window opens and displays the volumes currently associated with the schedule Any volumes that have been added to or removed fr
78. rd in the Getting Started launch pad See the HP LeftHand Storage Solution User Manual for details on working through the wizards Designating an existing volume as a remote volume When you select an existing volume to become a remote volume the following occurs e A snapshot is created of the volume to preserve the data from the primary volume The volume becomes a 0 byte remote volume Creating a new remote volume manually Create a remote volume as you would any other volume Be sure to select the storage nodes at the remote site Because management groups and clusters are logical entities name them to reflect their remote functionality In this method the primary volume is ready Create a remote volume at the remote site to receive the snapshot and then either take the snapshot and create a remote copy or create the schedule to take remote snapshots Creating a remote volume during creation of a remote snapshot If you are using the New Remote Snapshot window you can create a needed cluster and volume as you work through the window 1 In the Remote Snapshot Setup box select a Management Group to contain the remote snapshot EY NOTE You must be logged in to the management group you select 2 Click New Remote Volume The Management Groups Clusters and Volumes wizard opens For specific help see the Getting Started chapter in the HP LeftHand Storage Solution User Manual for details on working throu
79. re and not have it recur or do you want a remote snapshot R currence to be taken on a regular schedule e Frequency minutes hours days or weeks determines the interval between recurring scheduled remote snapshots Primary setup Select one of the following options Retention e Maximum number of snapshots Set period of time minutes hours days or weeks Remote setup Management group The management group that contains the remote snapshot Volume Retention The remote volume for the remote snapshots Select one of the following options e Maximum number of snapshots This number equals completed snapshots only In progress snapshots take additional space on the cluster while copying Also the system will not delete the last fully synchronized snapshot For space calculations figure n 2 where n maximum number of snapshots Set period of time minutes hours days or weeks P4000 Remote Copy user guide 15 16 Understanding and planning Remote Copy 2 Using Remote Copy For information about how Remote Copy works and how to plan capacity for Remote Copy see Understanding and planning remote copy on page 9 Working with remote snapshots Remote snapshots are a core component of Remote Copy Remote Copy uses the existing volume and snapshot capabilities to replicate or copy the data across geographic distances New for release 8 5 You can create application managed snapshots that us
80. remote mote snapshots snapshots older than x e A remote snapshot is deleted only after its corresponding primary snapshot is deleted Additionally a remote snapshot is deleted only after its counterpart primary snapshot You cannot retain fewer remote snapshots than primary snapshots when setting your retention policies 14 Understanding and planning Remote Copy EY NOTE Over the course of time through deletion of primary snapshots if you accumulate more remote snapshots than primary 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 established as part of creating the remote snapshot schedule Best practices e Retain at least two primary snapshots to ensure that only incremental copying is required for remote snapshots e Review your remote copy schedule to ensure that the frequency of the remote copies correlates to the amount of time required to complete a copy Use the checklist in Table 4 on page 15 to help plan scheduled remote snapshots Table 4 Scheduled Remote Copy planning checklist Configuration category Characteristic Scheduled snapshot ee Start date nm dd yyyy for the schedule to begin tart time e Start time mm hh ss for the schedule to begin e Recurrence is a yes or no choice Do you want to take a remote snapshot one time in the futu
81. s 10 Graphical legend for Remote Copy icons acs iicc acccsacseessseancrensarentesenctsuraniesatinnss setacsevnntenies 10 Remote Copy and volume teplicahoni c ivssrsciubsdesardadasGanvdacandceaednonapnmenanrdietraneoavowatia 11 Uses for Remote Copy carina vuepscieiateecnanepadaxsite tea E aana Aa KOSTEN A ETE EEE ATE AET 11 Benefits of Remote Copy ssssssssnnssoesereesesetsesersrstterotttsstetsrttrssttesssrsrsetsrsrtessrttssttrsstrerensers not 11 Planning for Remote Copy x cciacstswiatstveatecensenenneaeniwads suing staveieard eaves raTa Enri nies ENRE ia anniari n 12 Planning the remote snapshot ssssnnsseeensesssseteessetttesseentsssssrrtssssettrtsseretrsrsserrsssssererssrererts 12 Prerequisites for creating a remote snapshot ccceescecsesseeeeenececseeeeeeeseeeeeseeeeentseeensaes 12 Logging in to primary and remote management groups ccceeeeeeeeeceeeeteeeeeestteeeeeeeeaees 12 Designating or creating the remote volume cceeecccceceeeeeeeeeeeceenceeeeeeseneeeeeeseneseeeeeneee 12 Using schedules for Remote Copy a iaciasaonaasatiensninns nae tne eavan erie leaned 13 Planning the Remote Copy schedule lt 0s cccdiecensscesceesvacvesaviqaseannsnadtareeadvadechetstinrdannindeenvquceirve 13 RECUNSNCE soenen ae E EREE immune cee eames Ree 13 CODGCHY erei ege E E E E E E E T 14 Re ETO policies seort an E T A 14 Best practices ariera a a E A E e ae aE a o e E Adr RS 15 PaE E E E e E O EE I EENE NONI T EAE 17
82. s must be set up to use the same remote management group If you need to create a remote volume click New Remote Volume 16 Click Update Pending Table Below to add this remote volume setup to the list at the bottom of the window The system selects the next volume in the Primary Volume list at the top of the window 17 Select the remote Volume Name for the selected volume 18 Click Update Pending Table Below to add this remote volume setup to the list at the bottom of the window 19 Continue until each volume at the top of the window is set up A green check mark shows the volume is set up 20 Click Create Schedule The timetable you just created is now listed in the Schedules tab view for a scheduled remote snapshot When you set up a schedule for recurring remote snapshots with the previous procedure check the time zone setting first The time zone displayed in the Schedule to Remote Snapshot a Volume window is the time zone of the storage node through which you first logged in to the management group See Best practices for scheduling remote snapshots on page 28 What the system does 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 See Best practices for scheduling remote snapshots on page 28 If you selected an existing volume to become the remote volume the system alerts you that it will create a snaps
83. shots that are taken at a specific point in time but an application writing snapshot to that volume may not be quiesced Thus data may be in flight or cached and the actual data on the volume may not be consistent with the application s view of the data preferred interface A preferred interface is the interface within an active backup bond that is used for data transfer during normal operation 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 primary volume The volume which is being accessed read write by the application server The primary volume is the volume that is backed up with Remote Copy quorum A majority of managers required to be running and communicating with each other in order for the SAN iQ software to function 64 Glossary RAID device RAID levels RAID quorum RAID rebuild rate RAID status register remote copy pair remote snapshot remote volume Repair storage node replication level replication priority RAID originally redundant array of inexpensive disks now redundant array of independent disks refers to a data storage scheme using multiple hard drives to share or replicate data among the drives Type of RAID configuration e RAIDO data striped across disk set e RAID1 data mirrored from one disk onto a second disk e RAID10 mirrored sets o
84. shows the basic flow of Remote Copy Reproducing data using Remote Copy follows a three step process 1 At the production location create a snapshot of the primary volume This is called the primary snapshot 2 Create a remote volume at the remote location and then create a remote copy of the primary snapshot to the remote volume 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 eon Remote Volume Read Write Pointer to remote Accessed by 3 snapshots application serrer o O U Source for primary snapshots Primary Snapshot Remote Snapshot Primary Location Remote Location 3 System copies data from the primary snapshot to the remote snapshot Figure 1 Basic flow of Remote Copy P4000 Remote Copy user guide 9 EY NOTE Both primary and completed remote snapshots are the same as regular snapshots Remote Copy can be used on the same site even in the same management group and cluster Graphical representations of Remote Copy The HP LeftHand Networks Centralized Management Console displays special graphical representations of Remote Copy Copying the primary snapshot to the remote snapshot When the primary snapshot is copying to the remote snapshot the CMC depicts the process with a moving graphic of pages from the primary to the remote snapshot The pa
85. sole ID LED iSCSI iSCSI load balancing license keys Link Aggregation Dynamic Mode log files logical site management group managers MIB monitored variables When using Repair Storage Node a ghost storage node acts as a placeholder in the cluster keeping the cluster intact while you repair or replace the storage node Describes all the icons used in the CMC e Items tab displays the icons used to represent virtual items displayed in the CMC e Hardware tab displays the icons that represent the physical storage units Hardware reports display point in time statistics about the performance and health of the storage node its drives and configuration The hostname on a storage node is the user definable name that displays below the storage node icon in the network window It is also visible when the users browse the network Management interface for the SAN iQ software LED lights on the physical storage node so that you can find that node in a rack NSM 260 only Internet SCSI The iSCSI protocol defines the rules and processes for transporting SCSI block level data over a TCP IP network Improves iSCSI performance and scalability by distributing iSCSI sessions for different volumes evenly across storage nodes in a cluster A license key registers a storage node for add on applications Each storage node requires its own license key A type of network bonding in which the logical interface
86. ssociated Snapshots To delete only the snapshot you selected click Delete Selected Snapshot Only To cancel the deletion click Cancel Monitoring remote snapshots Information for monitoring remote snapshots is available from multiple sources Active monitoring provides the capability to configure alerts that you can view in the alert window You can also receive alerts through email and SNMP traps The Alert window also provides real time monitoring information for remote snapshots when you are logged in to the CMC P4000 Remote Copy user guide 25 Monitoring details from the Remote Snapshots feature You can view information about each remote snapshot in both the Remote Snapshots tab and in the Remote Snapshot Details window Viewing information in the Remote Snapshots tab The Remote Snapshots tab displays a list of remote snapshots for each selected item in the navigation window You can view lists of remote snapshots by management group cluster volume and snapshot levels 1 Select the appropriate item in the navigation window 2 Click the Remote Snapshot tab The following fields appear e Complete The incremental progress of the remote copy operation Elapsed Time The Incremental time of the copy operation e Data Copied The Incremental quantity of data copied e Rate The Rate at which data is being copied or when the remote snapshot is complete the average rate for the total operation Stat
87. st snapshot is already selected 11 In the Remote Snapshot Setup box use the drop down lists to select the remote management group and volume for the selected snapshot EY NOTE If you need to create a new volume select New Remote Volume 12 In the Snapshot Name field enter the name for this remote snapshot or accept the default 13 Optional Enter a description for this remote snapshot 14 Click Update Pending Table Below to add this remote snapshot setup to the list at the bottom of the window The system selects the next volume in the Select Primary Snapshot list at the top of the window 15 Select or enter the Volume Name Snapshot Name and Snapshot Description for this remote snapshot IMPORTANT All remote snapshots must be set up to use the same remote management group 16 Click Update Pending Table Below to add this remote snapshot setup to the list at the bottom of the window 20 Using Remote Copy 17 Continue until each snapshot at the top of the window is set up A green check mark shows the snapshot is set up 18 Click Create Remote Copies The remote copy of the primary snapshots to the remote volumes begins Creating a remote volume You can create a remote volume by using the following methods e Designate an existing primary volume as a remote volume e Create a new remote volume manually e Create a new remote volume during creation of a remote snapshot e Use the Management Groups Clusters and Volumes wiza
88. sumes the role of the primary volume in a failover scenario A type of network bonding which in the event of a NIC failure causes the logical interface to use another NIC in the bond until the preferred NIC resumes operation At that point data transfer resumes on the preferred NIC A type of network bonding in which the logical interface performs load balancing of data transmission An additional feature purchased separately from the SAN iQ software Snapshot of a volume that is taken while the application that is serving that volume is quiesced Because the application is quiesced the data in the snapshot is consistent with the application s view of the data That is no data was in flight or cached waiting to be written For release 7 0 and earlier identifies the client or entity accessing the volume Not used in release 8 0 and later A feature in the CMC that automatically searches for storage nodes on the subnet the CMC is connected to Any storage nodes it discovers appear in the navigation window on the left side of the CMC Interface created for network interface failover and only appears after configuring for failover Combining physical network interfaces into a single logical interface Compact flash cards from which the storage node boots up Also known as diskon modules or DOMs Challenge Handshake Authentication Protocol CHAP is a standard authentication protocol The snapshot that has two or more volumes ass
89. t are designated to reside in a site Cannot contain storage nodes that span subnets Can only have a single VIP Storage server software maintains the customer s data It reads to and writes from disks in response to customer reads and writes of SANiQ volumes Striped data is stored across all disks in the array which increases performance but does not provide fault tolerance 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 CMC displays the progress of this synchronization Also you can manually synchronize if necessary to include data that is on the remote volume but not the primary Target secret is used in both 1 way and 2 way CHAP when the target volume challenges the iSCSI initiator Temporary space is created when a snapshot is mounted for use by applications and operating systems that need to write to the snapshot when they access it Temporary space can be converted to a volume using the SmartClone process Thin provisioning reserves less space on the SAN than is presented to application servers The Trap Community String is used for client side authentication when using SNMP Communication between a single sender and a single receiver over a network virtual IP address A highly available address that ensures that if a storage node in a cluster becomes
90. the schedule sania uoewsed nea eae ae EEE aad oe aren ne ees 29 Creating the schedule for volume sets cccccccceescceeeeeeeeseeeeenseeeenesaeeeseaaeeseeaeeesseeeenseeeeenses 29 Timing tor a scheduled remote snapshot sici 2 36isecsensdsnoassnodepaecss eves nediaphanspoqaiabeagndocsntnanendnanes 31 What the system does icq xu siatenes cqustarardaneail ained cleisdiesnaesnassetegiwedaax winds aa taai besnadakiatanaaan exsaernaunaneesd 31 Pausing and resuming scheduled snapshots arise cues deurnsianacehayarsredouulioacunianadaamier wa lauatemniennieens 31 Pause a sch dule saweadavartaradcorerevetri ra tetitantes taktnatenaneninaceinaseivediavennna manera EE Ee I 32 Resume a schedule anioe a a a E N enna 32 Editing the schedule to remote snapshot a volume ccceeecseeeeeceeeeeeeeeeeeeceeeeeeeeeseeeeceeeseneeeee 32 Edit the remote snapshot schedule lt 5 Gass titwayaianniesaednesaesdndadenieaen ae ees 32 Deleting the remote snapshot schedule ccccecccecesscceeseeeceneeeenesaeeseesaeesseseeeseeeeesseeeeessseeeenses 33 Failover and failback using Remote Copy 62s 0idsnssicarwagn tion nartneriniladumainey unin manne 33 Planning failover esl teresa eis stones ana e a e A aa ia ei 33 Using the Volume Failover Failback Wizard x ccag scviserrSenaveadiansddonntiercnlo te seid lords tate aeedoranaeanenies 34 Converting a primary volume to a remote volume cccceceesseeceeeeeeeeeeeeeeeeeeeeeeeeeettaeeeeeestaaeees 34 Using
91. tween start times e Use NTP to set all storage nodes in the management group to the same time zone Reset the management group time before creating a new schedule to remote snapshot a volume Creating the schedule To create the schedule for continuing remote snapshots 1 In the navigation window select the primary volume Click the Schedules tab Click Schedule Tasks and then select New Schedule to Remote Snapshot a Volume Click Edit and then select a Start At time wR WN Select a recurrence interval You can schedule a snapshot to occur every 30 minutes or more 6 Select a retention interval for the primary snapshot either number of days or number of snapshots You can retain up to 50 snapshots for a volume 7 If you want to use VSS to quiesce the application before creating the snapshot select the Application Managed Snapshot check box This option requires the use of the VSS Provider For more information see the HP P4000 SAN Solution User Manual If the VSS Provider is not installed SAN iQ allows the creation of a point in time snapshot This option quiesces VSS aware applications on the server before SAN iQ creates the snapshot 8 Select the management group and vo lume that will hold the remote snapshots 9 Log in if you need to 10 Click New Remote Volume to use the wizard to create a volume if you need to make a new one 11 Set the retention interval for the remote snapshot You can retain up to 50 snaps
92. ut volume sets and snapshot sets see the HP LeftHand Storage Solution User Manual or online help Using scripting for Failover Application based scripting provides the capability for creating mounting and deleting snapshots using scripts Remote Copy can be scripted as well Remote snapshots and scheduled remote snapshots can be created and managed using scripts For information about scripting see the CLIQ The SAN iQ Command Line Interface User Manual and the sample scripts available on the HP LeftHand website P4000 Remote Copy user guide 33 Using the Volume Failover Failback Wizard Changing the roles of primary and remote volumes may be necessary during failover and failback Move your primary volume either as part of a failover failback scenario or as part of a planned move The Volume Failover Failback Wizard takes you through the necessary steps fo move a primary volume to an existing remote volume and to make the existing remote volume to an acting primary volume Later when failing back or restoring operations in a planned move resynchronize data between the acting primary and the recovered or newly configured production site primary volume EY NOTE When failing over a primary volume the volume must have a remote copy relationship for the wizard to be available Converting a primary volume to a remote volume The system allows you to convert a primary volume into a remote volume First the system takes a sna
93. ver The remote snapshot is available if the primary volume fails Achieving off site backup Rather than creating tape backups and then transporting them to a secure off site location you can use Remote Copy to create remote snapshots in an off site location Then optionally you can create tape backups at the off site location Configuration for off site backup and recovery To use remote snapshots for off site tape backup create remote snapshots for access by your tape backup application e Create remote volumes in your backup location e Configure your backup application to access the remote snapshots e Configure schedules to create remote snapshots in the designated off site locations If your applic ation server uses multiple volumes that must be in sync use a script to quiesce the application before creating remote snapshots Optional Create routine tape backups of the remote snapshots Configuration diagram Application Workstations a Team 4 Design c Design Team 2 Application CADS Team 2 CAD Server for Serwers atte Next Generation for Current Product Product WAN Read Write Read Write Primary Primary Volume Volume 2 Storage Subnet Primary Snapshot Primary Snapshot 2 Production Site 41 Production Site 2 Figure 17 Off site backup and recovery example configuration How this configuration works for off site backup Depending on how long you retain the copies of the remote
94. y Use the storage nodes intended for the remote site to configure the remote management group onsite and copy data locally and then ship the remote storage nodes to the remote site Use this method if you initially have all the storage nodes for the Remote Copy solution at the primary site 1 Configure both the primary and remote management groups 2 Create the first copy of the data locally over the gigabit Ethernet 3 Ship the storage nodes for the remote site and install the remote management group just as you configured it in the primary site 4 Allow adequate time between the arrival of the storage nodes and the first remote copy operation EY NOTE The subsequent snapshots from the primary volume to the remote volume are incremental Use the PrimeSync method of Remote Copy to configure a temporary management group create the first copy locally ship the temporary storage node and then copy locally to the remote target 22 Using Remote Copy Use this method if you have the primary Site A and remote site Site B configured and operational 1 While at the primary Site A use available storage nodes to create a new temporary management group cluster and volume This management group cluster and volume are the PrimeSync that you will set up at the primary Site A Make a remote snapshot of the primary Site A volume and then copy it to the temporary PrimeSync management group over gigabit Ethernet See
95. y planning checklist cccccecesseeeecceeeeeeeeeeeeeeeeeeseeeessseeseaes 15 5 Fields for Remote Snapshot Details window cccescccceeeeseeeeeeeeeeeeeeeesteceesneeseesseees 27 6 Timeline of failover nssnennsesseeseeissesseeeeetssessetrstrsstesttrsstsstistrssessrerstesstesterssesstete 36 7 Creating snapshots of data to synchronize ccccseceeesceceenseeeeeeceeeeeeeeeseeeesaeesenaes 37 8 Document Conventions sssssssssssestittttettt tretet ttrt ttre PEP EEEE EEEEEEEEE EEEE EEE EEEE E EEEE EEEren eent 58 P4000 Remote Copy user guide 7 1 Understanding and planning Remote Copy Remote Copy provides a powertul and flexible method for reproducing data and keeping that replicated data available for disaster recovery business continuance backup and recovery data migration and data mining How Remote Copy works Remote Copy uses the existing volume and snapshot features 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 cross country global For example the accounting department in the corporate headquarters in Chicago runs the corporate accounting application and stores the resulting data The designated backup site is in Detroit Nightly at 11 00 p m accounting updates are copied to the Detroit backup facility using Remote Copy Figure 1 on page 9
96. y user guide 13 Capacity Does the cluster that contains the remote volume have sufficient space to accommodate scheduled snapshots If the cluster does not have sufficient space available the remote snapshot appears in the CMC and flashes red On the Details tab of the remote snapshot the status message displayed is Read only not enough space in cluster to start copy Retention policies 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 two primary snapshots and five remote snapshots The number of snapshots retained refers to completed snapshots Take the following characteristics of scheduled remote snapshots into account when planning retention policies The SAN iQ software never deletes the last fully synchronized remote snapshot Under some circumstances such as unpredictable network speeds or varying snapshot size a scheduled remote snapshot may create primary snapshots so frequently that the remote copy process cannot keep up with them The retention policies for scheduled remote snapshots ensure that such factors do not cause primary and remote snapshots to become unsynchronized Regardless of the retention policy defined for scheduled remote snapshots up to two additional snapshots may be retained by the system at any given time These two additional snapshots include the snapshot that
97. ynchronous replication a single storage node can be off line and your primary volume will remain intact At the backup location you can also use synchronous replication to protect your remote volume against storage node failure Example configuration e In the production location create a cluster of three storage nodes all with managers e Create volumes on the cluster and set the replication level to 2 Way e Create a schedule for making remote snapshots of the primary volume Set the recurrence to every four hours and retention of remote snapshots to two days EY 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 that is configured on the primary volume If one of the storage nodes in the primary location fails the primary volume will still be available If all of the storage nodes fail or if the application server fails then you can recover data from the remote snapshots or tape backups in the off site location Using Remote Copy for off site backup and recovery For backup and recovery systems Remote Copy can eliminate the backup window on an application server Using iSCSI command line interface commands and scripts configure the iSCSI initiator to 48 Sample Remote Copy configurations mount remote snapshots on a local or remote backup server and then back up the remote snapshot from the backup ser

P4000 Remote Copy user guide

Contents

Download Pdf Manuals

Related Search

Related Contents