1 / 41

FlexCopy

FlexCopy. FlexCopy overview. Definition of terms: Hi-Copy external storage copy (Hitachi) FlexCopy external storage copy (HP). Prerequisites. XP disk arrays:. XP128, XP1024 XP12000. minimum Firmware:. XP128/1024: 21.09.01 XP12000: initial release. minimum RAID Mgr:. v01.12.06.

saddam
Télécharger la présentation

FlexCopy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FlexCopy

  2. FlexCopy overview • Definition of terms: • Hi-Copy external storage copy (Hitachi) • FlexCopy external storage copy (HP) HP Confidential

  3. Prerequisites XP disk arrays: XP128, XP1024 XP12000 minimum Firmware: XP128/1024: 21.09.01 XP12000: initial release minimum RAID Mgr: v01.12.06 Command View XP: XP128/1024: v1.8b XP12000: v2.0 external storage: MSA1000 & MSA1500(XPs ?) HP Confidential

  4. FlexCopy - Specifications HP Confidential

  5. introduction HP Confidential

  6. FlexCopy Functionality • FlexCopy is a capability resident on HP StorageWorks XP128/XP1024/XP1024 disk arrays that enables you to copy data in both directions between an XP1024/128/12000 Disk Array and an external disk array. • Flex Copy also lets you easily back up the data in an XP1024 /128/12000 disk array to another disk array and then restore the backed-up data to the XP disk array. • FlexCopy differs from the conventional XP Business Copy functionality in that FlexCopy does not maintain any degree of data concurrency or perform any mirroring operations. Instead, FlexCopy completes one copy from the data source to the copy destination. HP Confidential

  7. FlexCopy Concept HP Confidential

  8. SAN SAN FlexCopy - Usage for Backup MSA1000 Panther X mapped FC S-VOL BC S-VOL P/S-VOL mapped S-VOL P-VOL mapped S-VOL S-VOL S-VOL HP Confidential

  9. Typical FlexCopy Setup XP Business Copy Pair MSA FlexCopy LUNs MSA XP (S-VOL) (P-VOL) 1:01 0:01 XP (S-VOL/ P-VOL) 0:02 MSA (S-VOL) 1:02 arrows show possible relationships only (at different points in time) HP Confidential

  10. Typical FlexCopy Procedure Create an external copy on 1:01 of LDEV 0:01: • pause or stop any application currently using LDEV 0:01 • suspend the BC pair 0:010:02 • split the BC pair 0:010:02 to SMPL state • resume or restart any application effected in step 1 • issue a paircreate on the FC pair 0:02  1:01 and waitfor it to reach the PAIR state • split the FC pair 0:02  1:01 with pairsplit –S • recreate the production BC pair 0:010:02 with a fullinitial copy via paircreate HP Confidential

  11. Typical FlexCopy Procedure Restore form an external copy (1:01) to LDEV 0:01: • split the BC pair 0:010:02 to SMPL mode • stop the application using LDEV 0:01 • issue a paircreate on the FC pair 1:01  0:01 and waitfor it to reach the PAIR state • split the FC pair 1:01  0:01 with pairsplit –S • start the application previously stopped in step 2 • recreate the production BC pair 0:010:02 with a fullinitial copy via paircreate HP Confidential

  12. Limitations • FlexCopy Limitations- • FlexCopy is supported only with XP1024/128/12000. • FlexCopy will not pair from or against any OPEN volumes that are not in SMPL state. • Care must be taken to properly size LUs resident in external storage so that the XP CVS (VLL) function can be used to re-reference the external LU in terms of XP storage dimensions. Failure to match LU sizes will most likely result in data loss. • MSA Limitations- • MSA1000 controller failover is not supported for FlexCopy at this time. • Attempts to configure MSA1000 LUs for FlexCopy using the XP configuration facilities while both controllers are visible to the XP will most likely result in the false/duplicative LUs being reported visible in FlexCopy configuration screens. HP Confidential

  13. MSA1000 Configuration(1 -2) Do not connect the path to the controller on the Standby side of the MSA1000 subsystem The table below shows the port setting status of the XP disk array when you connect the MSA1000 external disk array. HP Confidential

  14. MSA1000 Configuration(2-2) • If you connect an MSA1000 as an external disk array, you need to set the host mode of the port to Windows. Please refer to the following documents for information on how to configure the MSA1000: • 􀁐 HP StorageWorks Modular SAN Array 1000 QuickSpecs • 􀁐 HP StorageWorks Modular SAN Array 1000 User Guide • XP and the MSA1000 LUs used for FlexCopy should be of the same size. When creating LUs resident on the MSA1000 for use with FlexCopy that are to match their counterparts on the XP, is it is necessary to size these LUs slightly larger (2-3MB).This will allow to compensate for the ACU auto-resizing algorithm that is applied to each MSA1000 LU. • These same principles apply when creating LUs on the XP to match FlexCopy LUs already defined on the MSA1000. However, when this direction is taken, it will be necessary to ensure that the XP OPEN-V LUs that are created are geometrically identical (same number of XP OPEN-V cylinders) to the referenced and re-defined MSA1000 LUs. HP Confidential

  15. Adjusting LU capacity when setting Copy pairs HP Confidential

  16. Actual Capacity Available When an external LU is defined with an emulation of OPEV-V, the exact size of the external volume will be available to the HOST (the HOST itself will see the exact same value as expected from the original LU. In the XP display however, the mapped LU may be displayed with a slightly larger size than it actually has. This is due to the slot management method in the XP. Size displayed size to the HOST(s): External Vol Capacity = 30GB 30GB = 31457265[Kbytes] 31457265 Kbytes = 62914530[LBA] 30GB External LU OPEN-V Size displayed in the XP: Adjust Slot Count 62914530[LBA] ÷ 512 = 122879.9 122879.9 (round up) = 122880[SLOT] Convert to HBA again 122880 x 512 = 62914560[LBA] This is the capacity displayed in the Add LU SVP screen. Ext Volume capacity is 62914530 (LBA) Adjusted capacity For internal control is 62914560 (LBA) Notes: 1. For OPEN-V, 1 SLOT has 512 LBA. 2. The volume is controlled by the # of slots used. This is part of the control method. HP Confidential

  17. FlexCopy Operational Notes • Note 1 - If a host uses middleware such as Volume Manager, data in the destination LU (S-VOL) will not match data in the host until the data in the source LU (P-VOL) is exported from the host and applied to the disk array. • Note 2 - If two or more Flex Copy pairs are located in the same parity group, the I/O performance on the host server may suffer. • Note 3 - Flex Copy enables up to 64 concurrent copy operations. If the number of copy requests exceeds 64, the 65th and subsequent requests will not be processed until a copy operation in progress has completed. • Note 4 - The local disk array does not force the external disk array to reserve the mapped external LU. Therefore, do not to write from the external disk array side to a mapped external LU whose IO Suppression mode is set to Disable. HP Confidential

  18. FlexCopy Operational Notes • Note 5 - On the external LU used for Flex Copy operations, you must select IO Suppression mode when you map the external volume to an internal volume. • Note 6 - If you use a mapped external LU as the P-VOL or S-VOL in a Flex Copy pair, then when you map the LU you must: • set the emulation type to OPEN-V • set IO Suppression mode to Enable • Note 7 - An LU set for Auto LUN XP or Business Copy XP cannot be used as the copy pair LU for Flex Copy operations • Note 8 – FlexCopy P-Vol/S-Vol do not need to be mapped to XP hosts • Note 9 – WRITE IO will be impossible for FC volumes in any state HP Confidential

  19. FlexCopy Features A one-time, point-in-time copy of data from the local disk array to or from the external disk array Host access to the external array LU must be by direct connection to the external storage device -- it cannot be via the local disk array All Flex Copy LDEVs on the local disk array imported from external storage must be of OPEN-V emulation type External Storage Features Real-time usage of external storage devices as additional local disk array storage,providing a total capacity of up to 32 peta-bytes and thousands of external LUs Host access to the external storage LU must be via the local disk array – it cannot be by direct connection to the external disk array LU For external array LUs not involved with External Storage XP, direct access from a host is allowed with external XP disk arrays and disallowed with external MSA1000 disk arrays Local disk array LDEVs imported from external storage can be mapped in (from the XP12000's perspective) as any standard XP emulation type (with a few limitations FlexCopy vs. External Storage HP Confidential

  20. usingCommand View XPto addexternal storage HP Confidential

  21. FlexCopy – Preparing External Storage Discover the external subsystem HP Confidential

  22. FlexCopy – Preparing External Storage Discover the external subsystem externalLUN# FlexCopy „virtual disk group“ HP Confidential

  23. FlexCopy – Preparing External Storage „format“ external storage as OPEN-V create smalled OPEN-V volumes later through standard CVS operation panels in Command View XP HP Confidential

  24. usingCommand View XPfor FlexCopyoperations HP Confidential

  25. Using FlexCopy via Command View (1) select one or more potential P-Vols HP Confidential

  26. Using FlexCopy via Command View (2) assign S-Vols to P-Vols HP Confidential

  27. Using FlexCopy via Command View (3) apply changes HP Confidential

  28. Using FlexCopy via Command View (4) No Copy option only assigns the pairing relationshipthe FC pair will get the status NOCOPYRaidmanager is needed to initiate a copy process viapairresync command through Command View only paircreate and pairsplit –S operationscan be performed HP Confidential

  29. Using FlexCopy via Command View (5) • When you operate from the FlexCopy panel, following states are • displayed: • COPY (PD): Copy processing of all the data in the P-VOL To the S-VOL is in progress (COPY Pending) • PAIR: Copy processing has been complete • PAIR (NOCOPY): The copy pair is set by FlexCopy, but the copy processing has not been executed, yet. To start the copy processing, you need to operate the copy pair using Raidmanager HP Confidential

  30. usingRaid Manager XPfor FlexCopyoperations HP Confidential

  31. Limitations • There seems to be functions implemented to be compatible to standardBusiness copy • FlexCopy does not support the -m (noread) option of the paircreate command. • FlexCopy does not support the quick resync mode of the pairresync command. • FlexCopy does not support the quick restore mode of the pairresync -restore command. • Write operations cannot be performed onto a P-Vol when the P-Vol isin any pairing relationship. • Access to the S-Vol from MSA attached host in SMPL state only • FlexCopy does not support the At-Time Split function. HP Confidential

  32. Limitations • When you create a pair using an external volume that is mapped as an internal volume, RAID500 subsystem automatically decides whether to use FlexCopy or Business Copy depending on the attributes of the mapped volume • FlexCopy volumes on MSA are NOT visible on attached hosts xpinfo will not show devices • RAID Manager configuration files have to be created manually usingthe raidscan command HP Confidential

  33. Commands supported paircreate pairdisplay pairsplit pairresync pairevtwait pairmon pairvolchk raidscan HORCM_MON#ip_address service poll(10ms) timeout(10ms)127.0.0.1 52050 1000 3000HORCM_CMD#dev_name dev_name dev_name/dev/rdsk/c1t2d3HORCM_DEV#dev_group dev_name port# TargetID LU# MU#hicp hicpdev1 CL1-A 0 0 0HORCM_INST#dev_group ip_address servicehicp 127.0.0.1 52051 HP Confidential

  34. FlexCopy for XP128/1024 FlexCopy for XP12000 Conclusion  do not over-sell it!  go for E-Lun HP Confidential

  35. module end HP Confidential

  36. FlexCopy findings for RAID Manager usage, all external FC LDEVs needs to be mappedto a FC CHIP port use a dummy host group in order to avoid any problems(host scanning zero size disk LUNs) HP Confidential

  37. FlexCopy findings • # Created by mkconf.sh on Tue Feb 1 13:36:18 MET 2005 • HORCM_MON • #ip_address service poll(10ms) timeout(10ms) • 127.0.0.1 55001 1000 3000 • HORCM_CMD • #dev_name dev_name dev_name • /dev/rdsk/c4t0d0 /dev/rdsk/c7t0d0 • HORCM_DEV • #dev_group dev_name port# TargetID LU# MU# • bc bc_000 CL2-B 12 7 • fc fc_000 CL2-B 12 4 1 • HORCM_INST • #dev_group ip_address service • bc 127.0.0.1 55002 • fc 127.0.0.1 55002 HP Confidential

  38. FlexCopy findings • # Created by mkconf.sh on Tue Feb 1 13:36:18 MET 2005 • HORCM_MON • #ip_address service poll(10ms) timeout(10ms) • 127.0.0.1 55001 1000 3000 • HORCM_CMD • #dev_name dev_name dev_name • /dev/rdsk/c4t0d0 /dev/rdsk/c7t0d0 • HORCM_DEV • #dev_group dev_name port# TargetID LU# MU# • bc bc_000 CL2-B 12 7 • fc fc_000 CL2-B 12 4 1 • HORCM_INST • #dev_group ip_address service • bc 127.0.0.1 55002 • fc 127.0.0.1 55002 HP Confidential

  39. FlexCopy findings # pairdisplay -g bc -fcxe Group PairVol(L/R) (Port#,TID, LU-M) ,Seq#,LDEV#.P/S,Status, % ,P-LDEV# M CTG CM EM E-Seq# E-LDEV# bc bc_000(L) (CL2-B ,12, 7-0 )50411 410.SMPL ----,----- ----- - - - - - - bc bc_000(R) (CL2-B ,12, 4-0 )50411 411.SMPL ----,----- ----- - - - - - - # pairdisplay -g fc -fcxe Group PairVol(L/R) (Port#,TID, LU-M) ,Seq#,LDEV#.P/S,Status, % ,P-LDEV# M CTG CM EM E-Seq# E-LDEV# fc fc_000(L) (CL2-B ,12, 4-1 )50411 411.SMPL ----,----- ----- - - - - - - fc fc_000(R) (CL1-B ,15, 4-0 )50411 2c0.SMPL ----,----- ----- - - - H 6350GX3QI0H1 3 HP Confidential

  40. FlexCopy findings # raidscan -p CL1-B -fxe PORT# /ALPA/C,TID#, LU#..Num(LDEV#....)...P/S, Status, LDEV#, E-Seq#,E-LDEV# CL1-B /e8/ 1,15, 4-0 .1(2c0)...........SMPL ---- -----, 6350GX3QI0H1 3 CL1-B /e8/ 1,15, 4-1 .1(2c0)...........SMPL ---- -----, 6350GX3QI0H1 3 CL1-B /e8/ 1,15, 4-2 .1(2c0)...........SMPL ---- -----, 6350GX3QI0H1 3 CL1-B /e8/ 1,15, 5-0 .1(2c1)...........SMPL ---- -----, 6350GX3QI0H1 4 CL1-B /e8/ 1,15, 5-1 .1(2c1)...........SMPL ---- -----, 6350GX3QI0H1 4 CL1-B /e8/ 1,15, 5-2 .1(2c1)...........SMPL ---- -----, 6350GX3QI0H1 4 CL1-B /e8/ 1,17, 6-0 .1(2c2)...........SMPL ---- -----, 6350GX3QI0H1 5 CL1-B /e8/ 1,17, 6-1 .1(2c2)...........SMPL ---- -----, 6350GX3QI0H1 5 CL1-B /e8/ 1,17, 6-2 .1(2c2)...........SMPL ---- -----, 6350GX3QI0H1 5 pairdisplay -g fc -l -fcxe Group PairVol(L/R) (Port#,TID, LU-M) ,Seq#,LDEV#.P/S,Status, % ,P-LDEV# M CTG CM EM E-Seq# E-LDEV# fc fc_000(L) (CL1-B ,15, 4-0 )50411 2c0.SMPL ----,----- ----- - - - H 6350GX3QI0H1 3 fc fc_001(L) (CL1-B ,15, 5-0 )50411 2c1.SMPL ----,----- ----- - - - H 6350GX3QI0H1 4 fc fc_002(L) (CL1-B ,17, 6-0 )50411 2c2.SMPL ----,----- ----- - - - H 6350GX3QI0H1 5 HP Confidential

  41. FlexCopy findings HP Confidential

More Related