1 HP D2D Backup Systems Best practices for VTL, NAS and Replication implementations Table of contents Abstract ...
10 The following graph illustrates only the relationship between the number of active data streams and performance. It is not based on real data.
100 The final total source and target configuration is shown below. Example NAS and VTL configurations Map out the interaction of backup, house
101 Overlapping backups to minimize housekeeping interference Source 1 – Bad scheduling Source 2 – Good scheduling As backup DIR 1 finishes it trig
102 Tune the solution using replication windows and housekeeping windows The objective of this section is to allow the solution architect to design
103 Worked example – backup, replication and housekeeping overlaps Because we have sized D2D2502 for the sources - there is a limit of 4 concurrent
104 Initial configuration with replication blackout window set There is improvement in some backup job performance e.g. Share 1 DIR2 & Share 2 S
105 Target initial configuration Some effort is required to map all the activity at the target, but it is clear that, between 20:00 and 02:00, the
106 Offload to Tape requirement In this example the customer wants to know: “What is the best practice to make monthly copies to physical tape from
107 Avoiding bad practices The worked example describes the best practices. Typical bad practices are:- Bad Practice Results Not using the Sizing to
108 Appendix C HP Data Protector Tape Offload – Worked Examples HP Data Protector has an extensive range of Copy processes. Here we will look at ho
109 In this example the following storage devices are configured on HP Data Protector Cell Manager “zen”: HP D2DMSL: is a Virtual Tape emulation on
11 Network configuration All D2D appliances have two 1GBit Ethernet ports, the D2D4312 and D2D4324 appliances also have two 10GBit Ethernet ports. T
110 HP Data Protector has a context window for controlling Object operations as can be seen below. To perform a simple media copy 1. Right click o
111 2. Select the default parameters for the copy. It is important for base media copies that both the primary copy and the secondary copy media are
112 2. Click Next and, depending on what backup objects have been selected, HP Data Protector will check that all the necessary source devices (tha
113 5. Select one or more media depending on the objects that are to be copied. Select Next to display the Summary screen and click Finish to start
114 To perform an interactive object copy, D2D NAS share 1. Select Objects in the left-hand navigation pane and locate the D1D NAS share. 2. Cl
115 4. This shows the full path of the HP Data Protector File library and the file that represents the backup. 5. In this case the File Library
116 Appendix D Making use of improved D2D performance in 2.1.01 and 1.1.01 software Overview HP StoreOnce D2D software released in February 2011 in
117 Replication for Virtual Device Migration This method involves using two D2D Backup Systems and has the benefit that it does not require additiona
118 Step 3 – Recover Data to new VTL /Share 1. Run the replication recovery wizard on the original D2D appliance, this will reverse replicate the da
119 Self Replication for Virtual Device Migration Self replication is the process of replicating data between two devices on the same D2D Backup Syst
12 Single Port mode 1Gbit ports: use this mode only if no other ports are available on the switch network or if the appliance is being used to transf
120 Step 1 – Self replicate data for migration 1. Create a new VTL or Share on the D2D Backup System; this will be the new location for the migrated
121 Replication device self replication migration HPProLiantDL320sUID12Original File ShareOriginal VTLD2D ANew VTLNew File ShareHPProLiantDL320sUID12
122 5. Remove the replication mappings on both D2D Backup Systems. 6. Remove the appliance addresses from the list of replication target appliances
123 Configuring Self Migration from the D2D Web Management Interface The HP StoreOnce Backup System user guide provides step by step instructions on
124 2. The new share has now been created and after a few seconds is online. At this point there is no user data stored in that share. 3. The ne
125 5. Upon successful completion the local appliance will be added to the Target Appliances list. 6. Go to the Replication – NAS Mappings page
126 7. There are two main steps in the Wizard, the first is to select the target appliance from a list. This list will only contain the information
127 9. After completing the wizard, replication will begin synchronizing the data between the two shares. Synchronization will take some time to
128 11. Now reconfigure the backup application to use the new D2D share as a backup target device. For example the backup application will need to re
129 Index 10Gbit Ethernet, 15 A Active Directory, 15 active-to-active replication, 50 active-to-passive replication, 50 activity graph, 44 AD authen
13 Dual Port mode Use this mode if: Servers to be backed up are split across two physical networks which need independent access to the D2D applian
130 O open files, 31 out of sync notifications, 68 P performance activity graph, 44 deduplication, 7 libraries per appliance, 27 maximum concurrent
For more information To read more about the HP D2D Backup System, go to www.hp.com/go/D2D Share with colleagues
14 High availability port mode (Port failover) In this mode, no special switch configuration is required other than to ensure that both Ethernet port
15 10Gbit Ethernet ports on the 4312/4324 appliances 10Gbit Ethernet is provided as a viable alternative to the Fibre Channel interface for providing
16 Broadly there are two possible configurations which allow both: Access to the Active Directory server for AD authentication and Separation of
17 Option 2: HP D2D Backup System on Network SAN only with Gateway In this option the D2D has connections only to the Network SAN, but there is a net
18 Backup server networking It is important to consider the whole network when considering backup performance, any server acting as a backup server s
19 Fibre Channel configuration Fibre Channel topologies The D2D appliances support both switched fabric and direct attach (private loop) topologies.
2 Fibre Channel configuration... 19 Fibre Channel topologies ...
20 Direct Attach (Private Loop) A direct attach (private loop) topology is implemented by connecting the D2D appliance ports directly to a Host Bus A
21 Zoning may not always be required for configurations that are already small or simple. Typically the larger the SAN, the more zoning is needed. Us
22 Another page on the Configuration – Fibre Channel page of the Web Management interface shows the status for all the FC devices that are configured
23 A mixture of iSCSI and FC port virtual libraries and NAS shares can be configured on the same D2D appliance to balance performance needs. Sizi
24 The use of this tool enables accurate capacity sizing, retention period decisions and replication link sizing and performance for the most complex
25 VTL best practices Summary of best practices Tape drive emulation types have no effect on performance or functionality. Configuring multiple
26 cartridges that can be configured per library has also increased compared to G1 products. The table below lists the key parameters for both G1 and
27 A similar limitation exists for Fibre Channel. Although there is a theoretical limit of 255 devices per FC port on a host or switch, the actual
28 Some minor setting changes to upstream infrastructure might be required to allow backups with greater than 256 KB block size to be performed. For
29 Overwrite versus append of media Overwriting and appending to cartridges is also a concept where virtual tape has a benefit. With physical media i
3 Seeding and why it is required ... 55 Seeding
30 D2D NAS best practices Introduction to D2D NAS backup targets The HP StorageWorks D2D Backup System now supports the ability to create a NAS (CIF
31 Shares and deduplication stores Each NAS share created on the D2D system has its own deduplication “store”; any data backed up to a share will be
32 The number of concurrently open files in the table above do not guarantee that the D2D will perform optimally with this number of concurrent backu
33 If a write-in-place operation does occur, the D2D will create a new backup item that is not deduplicated, a pointer to this new item is then creat
34 Backup job time, assuming no housekeeping or replication windows are set Disk space pre-allocation Some backup applications allow the user to c
35 below ensures that multiple backups or streams can run concurrently whilst remaining within the concurrent file limits for each D2D share. Multipl
36 If backing up using application agents (e.g. Exchange, SQL, Oracle) it is recommended that only one backup per share is run concurrently because t
37 Verify By default most backup applications will perform a verify pass on each back job, in which they read the backup data from the D2D and check
38 operations. Housekeeping remains an important part of the data deduplication solution and enough time must be allowed for it to complete in order
39 A local user with the same username and password must be created on the media server that will be using the D2D CIFS share. The backup applica
4 Abstract The HP StorageWorks D2D Backup System products with Dynamic Data Deduplication are Virtual Tape library and NAS appliances designed to
40 1. Create a new Host(A) record in the forward lookup zone for the domain to which the D2D belongs with the hostname and IP address of the D2D. Cl
41 Now that the D2D is a member of the domain its shares can be managed from any computer on the domain by configuring a customized Microsoft Managem
42 3. Now click Add > In the dialog box choose the computer to be managed and select Shares from the View options. 4. Finally select Finish a
43 6. Double click a share name in the right-hand pane and select the Permissions tab. Add a user or group of users from the domain. Specify the le
44 VTL and NAS – Data source performance bottleneck identification In a lot of cases backup and restore performance using the HP D2D Backup System i
45 The activity graph below shows the start of a Virtual Tape Write and the current throughput being achieved. The activity graph below shows the
46 The activity graph below shows the end of a Virtual Tape Read. How to use the D2D storage and deduplication ratio reporting metrics D2D applia
47 This example is from the Storage Reporting GUI page and shows the Disk Storage Capacity Growth for both User Data and Physical Data for the curr
48 D2D Replication The HP StorageWorks D2D products provide deduplication-enabled, low bandwidth replication for both VTL and NAS devices. Replicatio
49 Replication usage models There are four main usage models for replication using D2D devices. Active/Passive – A D2D system at an alternate site
5 Executive summary This document contains detailed information on best practices to get good performance from an HP D2D Backup System with HP Store
50 Many to One configuration
51 N-way configuration In most cases D2D VTL and D2D NAS replication is the same, the only significant configuration difference being that VTL re
52 Replication overview What to replicate D2D VTL replication allows for a subset of the cartridges within a library to be mapped for replication
53 Appliance, library and share replication fan in/out Each D2D model has a different level of support for the number of other D2D appliances that ca
54 Concurrent replication jobs Each D2D model has a different maximum number of concurrently running replication jobs when it is acting as a source o
55 Amount of data in each backup Data change per backup (deduplication ratio) Number of D2D systems replicating Number of concurrent replicat
56 Summary of possible seeding methods and likely usage models Technique Best for Concerns Comments Seed over the WAN link Active -- Passive and Many
57 Seeding methods in more detail Seeding over a WAN link With this seeding method the final replication set-up (mappings) can be established immedi
58 Many to One WAN seeding over the first backup is, in fact, the first wholesale replication from the many remote sites to the Target site. Care mu
59 Co-location (seed over LAN) With this seeding method it is important to define the replication set-up (mappings) in advance so that in say the Ma
6 NAS best practices at a glance Configure multiple shares and separate data types into their own shares. Adhere to the suggested maximum number
60 Many to One Co-location seeding at Source (remote) sites; transport target D2D between remote sites. 1. Initial backup at each remote site 2.
61 Floating D2D method of seeding Many to Once Seeding with Floating D2D target – for large fan-in scenarios Co-location seeding at Source (remote)
62 2. At each remote site perform a full system backup to the source D2D and then configure a 1:1 mapping relationship with the floating D2D device”
63 Seeding using physical tape or portable disk drive and ISV copy utilities Many-to-one seeding using Physical Tape or portable disk drives Physica
64 2. Use the backup application software to perform a full media copy of the contents of the D2D to a physical tape or removable disk target for ba
65 Replication and other D2D operations In order to either optimize the performance of replication or minimize the impact of replication on other D2D
66 A bandwidth limit calculator is supplied to assist with defining suitable limits. Source Appliance Permissions It is a good practice to use the S
67 Replication Monitoring It It The aim of replication is to ensure that data is “moved” offsite as quickly as possible after a backup job completes.
68 Replication Throughput totals Whilst replication jobs are running the Status - Source/Target Active Jobs pages show some detailed performance info
69 Replication share/library details Replication share/library details show the synchronization status, throughput and disk usage for each replicate
7 HP StoreOnce Technology A basic understanding of the way that HP StoreOnce Technology works is necessary in order to understand fa
70 This is very useful to identify: Differences in bandwidth saving and therefore deduplication ratio for an individual cartridge or file. These ca
71 Housekeeping monitoring and control Terminology Housekeeping: If data is deleted from the D2D system (e.g. a virtual cartridge is overwritten or
72 By setting a housekeeping blackout window appropriately from 12:00 to 00:00 we can ensure the backups and replication run at maximum speed as can
73 Overall section This section shows the combined information from both the Libraries and Shares sections. The key features within this section are:
74 c) Restructure the backup regime to remove appends – as the bigger the tapes, files are allowed to grow (through appends,) the more housekeeping
75 Tape Offload Terminology Direct Tape Offload This is when a physical tape library device is connected directly to the rear of the D2D Generation
76 Tape Offload/Copy from D2D versus Mirrored Backup from Data Source A summary of the supported methods is shown below. For easiest integration For
77 Note: Target Offload can vary from one backup application to another in terms of import functionality. Please check with your vendor. Backup app
78 Key performance factors in Tape Offload performance Note in the diagram below how the read performance from a D2D4312 (red line) increases with th
79 2. For “Media Copies” it is always best to try and match the D2D VTL cartridge size with the physical media cartridge size to avoid wastage. For
8 Appended backups need to “clone” the cartridge on the target side, so performance of appended tape replication will not be significantly faster t
80 Appendix A Key reference information
81 D2D Generation 2 products, software 2.1.00 D2D Gen2 Products, Software 2.1.00 D2D2502i D2D2504i D2D4106i/fc D2D4112fc D2D4312fc D2D4324fc De
82 D2D Generation 1 products, software 1.1.00 D2D Generation 1 Products, Software 1.1.00 D2D2502i D2D2503i D2D2504i D2D4004i/fc D2D4009i/fc D2D
83 Appendix B – Fully Worked Example In this section we will work through a complete multi-site, multi-region D2D design, configuration and deployme
84 Backup requirements specification Remote Sites A/D NAS emulations required Server 1 – Filesystem 1, 100 GB, spread across 3 mount points Server 2
85 Using the HP StorageWorks Backup sizing tool Configure replication environment Click on Backup calculators and then Design D2D/VLS replication ov
86 IT IS VERY IMPORTANT that when you are creating the backup specifications in the Sizer tool you pay particular attention to the Field “Number of
87 In the case of sites A and D, when we enter all the backup jobs, we will have seven backup jobs running in parallel which will give us best throu
88 4. As you specify each job in turn click Add job and the job will be loaded to the summary table (see below).
89 5. Add all backup jobs for Sites A and D Please note in line with customer request, at sites A and D the D2D emulation has been selected as NAS E
9 hold-off to prevent impacting the performance of other operations. It is, however, important to note that the hold-off is not binary, (i.e. on or o
90 6. Repeat for Sites B and C.
91 7. Input backup job entries for Site E, which requires full backups every day for 29 days and is also required to have FC attach, so click FC i
92 We will retain 29 days of Fulls.
93 8. Press the Solve/Submit button and the Sizer will do the rest.
94 Sizer output The Sizer creates two outputs. It creates an excel spreadsheet with all the parts required for the solution including Service and S
95 The Sizer has also established that each source needs a 4.6 or 4.47 Mbit/sec link for the sources, whilst the target needs a link size of just
96 Refining the configuration In this worked example it is crucial that we have as many jobs replicating to the target simultaneously as possible.
97 2. Click Solve/Submit again. 3. A new parts list is generated with HP D2D4106 as the target, along with an HP D2D4106 replication license f
98 Note how because the replication is now more efficient we only need just over 2 Mbit/sec WAN links on each of the sources. Configure D2D s
99 On sites A and D the D2D units would be configured with four NAS shares (one for each server), the filesystem servers would be configured with sub
Commentaires sur ces manuels