HP D2D D2D Best Practices for VTL, NAS and Replication implementations (EH985- - Page 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 subdirectories for each of the mount points. These subdirectories can be created on the D2D NAS CIFS share by using Windows Explorer (e.g. Dir1, Dir2, Dir3) and the backup jobs can be configured separately as shown below, but all run in parallel. For example: Server 1 Mount points C, D, E C:  D2DNASShare/Dir1 D:  D2DNASShare/Dir2 E:  D2DNASShare/Dir3 This has two key advantages - all file system type data goes into a single NAS share which will then yield high deduplication ratios and, because we have created the separate directories, we ensure the three backup streams can run in parallel hence increasing overall throughput. This creation of multiple NAS shares on Sites A and D (4 in total) with different data types allows best potential for good deduplication whilst keeping the stores small enough to provide good performance. This would also mean that a total of 8 NAS replication targets would need to be created at Site E, since NAS shares require a 1:1 source to target mapping. Sites B and C For sites B and C the customer has requested VTL emulations. Server 1 - 200 GB Filesystem, spread across 2 mount points C,D Server 2 - 200GB SQL data Server 3 - Special App data, 200GB In this case we would configure 3 x VTL Libraries with the following drive configurations: Server 1 VTL - 2 drives (to support 2 backup streams) say 12 slots Server 2 VTL - 1 drive (since only one backup stream) say 12 slots Server 3 VTL - 1 drive (since only one backup stream) say 12 slots The monthly backup cycle means a total of 11 cartridges will be used in each cycle, which has guided us to select 12 cartridges per configured library. The fixed emulations in HP D2D like ―MSL2024‖ would mean we would have to use a full set of 24 slots but, if the customer chooses the ―D2DBS‖ emulation, the number of cartridges in the VTL libraries is configurable. Note: the backup software must recognize the ―D2DBS‖ as a supported device. As a general rule of thumb, configure the cartridge size to be the size of the full backup + 25% and, if tape offload via backup application is to be used, less than the cartridge size of the physical tape drive cartridges. So let us create cartridges of 250 GB for these devices (200GB * 1.25)) Site E We will require 8 NAS replication shares for Sites A and D. For sites B and C with VTL emulations we have a choice, because with VTL replication we can use ―slot mappings‖ functionality to map multiple source devices into a single target devices (hence saving precious device allocation). So, we can either create 6 * VTL replication libraries in the D2D at Site E or merge the slots from 3 * VTL on sites B and C into 3 x 24 slot VTLs on Site E. This allows the file system data, SQL data and the Special App data to be replicated to VTLs on Site E with the same data type, -again benefiting from maximum dedupe capability and not creating a single large VTL device on site E which would give lower performance as the dedupe store becomes mature. We also need to provision two VTL devices for daily full Exchange backups that are retained for 1 month - 4 stream backups for Exchange plus a single stream backup for the Special Application data. VTL 1 = 4 drives, at least 31 slots (to hold 1 month retention of daily fulls) VTL 2 = 1 drive, at least 31 slots (to hold 1 month retention of daily fulls) 99