Professional Documents
Culture Documents
Abstract
Conceptually understanding OpenStorage software and the API-based integration with Symantec NetBackup provides a clear view of the business value and technical merits of the integration. This guide moves past the conceptual stage to solution planning and deployment. Best practice guidelines are covered with the goal of eliminating implementation challenges. Knowledge and experience gained from assisting early adopters is logically presented for the overall benet of those deploying an OpenStorage solution with Data Domain deduplication storage.
DEDUPLICATION STORAGE
Table of Contents
1 2 INTRODUCTiON .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Target AuDIence. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2 EXecutIVe Summary . . . . . . . . . . . . . . . . . . . . . . . . 3 PLANNiNG.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1 NamIng ConVentIons. . . . . . . . . . . . . . . . . . . . . . . 3 2.2 NetWorks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.3 DocumentatIon. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 5 MULTipLE NETBACKUp DOMAiN CONFiGURATiONS .. . 12 6 DiSASTER RECOVERY.. . . . . . . . . . . . . . . . . . . . . . . . . . . 13 6.1 WItHIn tHe Same NetBackup DomaIn. . . . . . . . 14 6.2 To a DIfferent NetBackup DomaIn. . . . . . . . . . 14
7 ADDiTiONAL REFERENCES.. . . . . . . . . . . . . . . . . . . . . . . 14 8 CONCLUSiON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9 AppENDiX MiGRATiON TO OpENSTORAGE .. . . . . . . . 15 9.1 MuLtIpLe ProtocoLs on One Data DomaIn SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9.2 EXIstIng Backups RetaIn or DupLIcate?. . . . . 15 9.3 Are Storage LIfecycLe PoLIcIes ReQuIreD?. . . . 15 9.4 NetBackup PoLIcy MoDIfIcatIon . . . . . . . . . . . . 15 9.5 Legacy RepLIcatIon. . . . . . . . . . . . . . . . . . . . . . . . 15 9.6 DeLetIng Legacy Storage UnIts. . . . . . . . . . . . . 16
3 OpTiMiZED DUpLiCATiON. ......................... 8 3.1 Storage UnIts anD Storage SerVer Access . . . 8 3.2 NetWork ConsIDeratIons . . . . . . . . . . . . . . . . . . . 9
3.3 THrottLIng OptImIZeD DupLIcatIon. . . . . . . . . . . 9 3.4 OptImIZeD DupLIcatIon FaILures. . . . . . . . . . . . . . 9 3.5 SeeDIng Remote Data DomaIn SYSTEMs. . . . . . 10 3.6 DupLIcatIon Job ConfIguratIon OptIons. . . . 10
4 DUpLiCATiON TO TApE.. . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1 HIerarcHIcaL DupLIcatIon . . . . . . . . . . . . . . . . . 11 4.2 Tape CreatIon from tHe PrImary NetBackup Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.3 Tape CreatIon from a Non-PrImary NetBackup Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1 Introduction
Data Domain deduplication storage with Symantec NetBackup OpenStorage software is not difcult to install or congure. Deployment is straightforward in most environments. However, deployments involving multiple sites and a complex environment may experience issues with naming conventions, network infrastructure, or site-generated documentation detailing the installation. Therefore, OpenStorage implementations should be well planned and documented so that they can be deployed more quickly with fewer challenges when compared to the use of ad-hoc techniques. Deployment is often followed by a series of trials or tests to prove that the solution is functioning as planned. In this guide, OpenStorage best practices are examined and discussed to assist in eliminating the bottlenecks associated with deployment and functional testing of the solution.
4 NetBackup media server load balancing, eliminating the need to manually divide client backups across NetBackup media servers utilizing OpenStorage storage units. 4 Tape consolidation Backup images from remote locations and branch ofces can be replicated to a centralized location where they can be duplicated to tape under the control of NetBackup.
2 Planning
Deciding to change naming conventions halfway through a deployment can be painful, more so if production backups were executed to previously-named components that later need to be deleted in order to be renamed. Likewise, reconguring portions of the IP network that connect NetBackup media servers and Data Domain deduplication storage systems halfway through a deployment can be problematic when testing with production backups. Combining name changes with network changes is made worse with poor or nonexistent documentation. While conguration changes are both possible and supported, a production environment may not be the best place to learn these techniques for the rst time. Production environments differ from lab environments in that the severity of a setback is likely to be less pronounced in the lab. Creating a plan and documenting the conguration forms the foundation for a successful deployment and subsequent test phases.
At present, multiple LSUs can be congured on a single Data Domain system. This can create conicts for advanced NetBackup features such as media server load balancing, capacity reporting, etc., and is only a recommended best practice when the Data Domain system is being congured in multiple NetBackup installations.
4 Select the Failover storage unit selection algorithm. 4 Note that there may be cases where a storage unit group has been created for use in conjunction with multiple storage units using disk pools on a common Data Domain system. In this case use of the Media server load balancing storage unit selection algorithm is recommended. Using storage unit groups is optional. Use of the Failover selection algorithm is a best practice as it facilitates sending the same backups to the same Data Domain system which will equate to a higher data deduplication ratio. In the event that the preferred storage unit enters a non-operational state, backups will be sent to an alternate storage unit. This methodology may be of interest for mission critical or otherwise important backup jobs. Alternatively, you may elect not to use storage unit groups for backups that do not require N+1 redundancy.
NetBackup Master Server NetBackup Media Server
LAN
LAN
LAN
WAN
2.2 Networks
Varying degrees of network complexity are associated with a given OpenStorage deployment. At a minimum, a single Data Domain system congured as a storage server is network connected to a NetBackup media server. NetBackup optimized duplication adds additional requirements as does a conguration that leverages media server load balancing.
NetBackup Client
LAN LAN
A NetBackup client that can be backed up through a number of different NetBackup media servers. The OpenStorage storage unit has been congured so that each NetBackup media server can access its resources. This enables NetBackup media server load balancing, where the least loaded media server is used to fulll a backup request. Additionally, this conguration allows NetBackup to bypass an ofine media server when fullling a backup or restore request.
Figure 1: Optimized duplication with a common LAN This is a simple example of a NetBackup master/media server LAN connected to two Data Domain systems. In this use case both backup and optimized duplication trafc use the same NIC (Network Interface Card) on a given Data Domain system.
SYMANTEC NETBACKUP OPENSTORAGE 5
deployments, the use of a dedicated backup network is preferred when compared to mixed use network congurations. When deploying a Data Domain system that can accommodate data transfer rates exceeding the capabilities of 1 GbE networks, using a 10 GbE infrastructure can overcome data transfer rate bottlenecks. Single stream performance that exceeds 125 MB/s dictates the need for a 10 GbE network connection. 4 Network topologies without a 10 GbE infrastructure The network connecting NetBackup media servers to a given Data Domain system can optimally incorporate the use of multiple 1 GbE interfaces so long as there is only one connection per NetBackup media server. (Figure 5) An alternative topology that utilizes multiple 1 GbE network connections on one or more NetBackup media servers is also possible.
1 GbE Private Network 1 GbE Private Network 1 GbE Private Network 1 GbE Private Network
Figure 5: Recommended use of multiple 1 GbE networks In the example shown above, each of four NetBackup media servers connects to a specic NIC on a Data Domain system congured as a single storage server. Each NetBackup media server is congured to use DNS or a local host le such that the storage server name resolves to a specic interface on the Data Domain system. This conguration accommodates NetBackup media server load balancing as it utilizes a single storage server, single disk pool, and a single storage unit. By default the storage unit is dened to allow all four NetBackup media servers to use the shared disk pool resource. This 1 GbE topology imposes limits on maximum single stream as well as aggregate data transfer rates from any single NetBackup media server to the Data Domain system. The combined data transfer rate of all NetBackup media servers can result in an aggregate data transfer rate that seeks to better utilize resources and achieve the maximum throughput possible on the Data Domain system.
Figure 4: Dedicated backup network Dedicated backup networks, as shown in gure 4, provide a number of tangible benets
In many cases there may be no fundamental reason to commingle NetBackup client network trafc with the network that connects NetBackup media servers and storage servers. When possible, the network used for NetBackup media server to Data Domain system communications should be segregated from other production networks. While not always possible based on customer requirements and pre-existing NetBackup media server and network infrastructure
need arise to modify, alter, or enhance the solution, documentation lays the groundwork for moving forward. In the event that technical support or other assistance is required, documentation can assist in rapid problem isolation and resolution. 4 Topology Diagram: This basic diagram consists of a map of physical components labeled using the recommended naming conventions. Also included are the individual networks and IP addresses of the components. This common sense approach makes it possible for others within or outside of the organization to quickly understand the overall view of the deployed solution when needed. 4 Data Collection: Collecting and recording relevant conguration information is consistent with the creation of best practice documentation. On the NetBackup master server and each NetBackup media server used for the OpenStorage solution, the following commands (or their equivalent) should be executed:
Figure 6: Recommended use of multiple 1 GbE networks In the example above, each of four NetBackup media servers connects to a specic NIC on a Data Domain system congured as a single storage server. Each NetBackup media server is congured to use DNS or a local host le such that the storage server name resolves to a specic interface on the Data Domain system.
Multiple 1 GbE connections between a NetBackup media server and Data Domain system should be congured as follows: 4 Congure a single LSU on the Data Domain system. 4 Congure a unique storage server for each network connection. 4 Congure a unique disk pool for each storage server using the single LSU. 4 Congure a storage unit for each unique disk pool. 4 Optionally, create a storage unit group that includes the storage units congured earlier. The storage unit group should use the Media server load balancing storage unit selection algorithm. Backup policies can be congured to use the storage unit group versus specic storage units. Note that the following limitations exist with this conguration: 4 Capacity reporting within NetBackup is skewed as NetBackup believes that there are multiple separate physical storage servers. 4 Manual assignment of NetBackup policies to one of four storage units is required. Alternatively, a storage unit group may be used. 4 NetBackup media server load balancing may not function normally. To overcome this challenge, storage unit groups may be created that utilize Media Server load balancing selection criteria. 4 Administrative complexity and overhead is increased with additional network names, storage servers, disk pools, storage units, and possibly storage unit groups.
2.3 Documentation
With multiple NetBackup media servers, multiple Data Domain systems, and the potential use of multiple networks combined with different geographical locations, the importance of documenting the deployed solution cannot be overemphasized. Proper documentation enables various site and vendor groups including management, data protection administrators, and network administrators to understand and maintain the deployed solution. Should the
3 Optimized Duplication
Optimized duplication replicates deduplicated data between source and destination targets, and typically requires only a fraction of the network bandwidth consumed by backup or recovery jobs. Simple in principle, optimized duplication is also simple to congure once requirements are understood.
Figure 7: Separate source and destination NetBackup media servers Figure 7 depicts optimized duplication between two OpenStorage storage units. The NetBackup media server initiating an optimized duplication job needs to have credentials to access both the source and destination OpenStorage storage units.
Credentials are set by means of the NetBackup tpcong command on each NetBackup media server requiring access to a given OpenStorage storage unit. This allows the NetBackup media server to use the OpenStorage storage unit for backup and recovery jobs, as well as for optimized duplication. In cases where optimized duplication uses a destination OpenStorage storage unit that may be geographically distant from the NetBackup media server initiating optimized duplication, the storage unit denition should not allow the geographically distant NetBackup media server to use the storage unit for backup or recovery jobs. This is easily accomplished from within the NetBackup storage unit dialog window as shown in gure 8.
Figure 8: Storage Unit dialog Use only specic media servers In the example above, the NetBackup storage unit named dd120b-stu has been congured to allow only the NetBackup media server named NBU65OST_Media2 to use it for backup and restore jobs. The NetBackup media server named NBU65OST_Media1 has credentials to access the storage unit for the purpose of initiating optimized duplication jobs.
Beginning with DD OS version 4.6, stream count information is available in the Data Domain Operating System User Guide.
NetBackup monitors the number of jobs running on a particular storage unit in order to enforce the maximum number of current jobs value. Monitored jobs include backup and duplication operations. The storage unit maximum concurrent jobs parameter however, does not distinguish between backup and duplication jobs. There is no facility within NetBackup that can be used to limit backup and duplication jobs separately. Solution architects should be cautious and monitor the number of simultaneously executing backup and duplication jobs based on prescribed limits in order to assure optimal performance.
4 Storage unit groups can be used as backup destinations within storage lifecycle policies, but are not recommended for use as duplication destinations.
Figure 10: Storage lifecycle policy This example contains a backup storage destination equal to storage unit dd120a-stu with a xed retention period of one week. The example also includes a duplication destination equal to dd120b-stu with a xed retention period of six months. The storage lifecycle policy has optionally been assigned a data classication value equal to Platinum. When the duplication task is executed it will result in an optimized duplication job that appears in the NetBackup activity monitor.
Stream count information is available from Data Domain for setting the NetBackup storage unit maximum concurrent jobs parameter.
10
Storage lifecycle policy duplication relies upon certain default settings that control the point at which a duplication job will be launched. An optional conguration le can be created to customize lifecycles to run duplication jobs based on customer requirements. Out of the box defaults as for NetBackup version 6.5 include: 4 MIN_KB_SIZE_PER_DUPLICATION_JOB = 8 GB 4 MAX_KB_SIZE_PER_DUPLICATION_JOB = 25 GB 4 MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB = 30 minutes Optimized duplication testing with backup images less than 8 GB in size may be delayed by up to 30 minutes as a result of the default settings. In a test only environment it may make sense to alter the default value for the MAX_MINUTES_TIL_FORCE_SMALL_ DUPLICATION_JOB to a value of less than 30 minutes. In some environments the default settings may be appropriate. The default settings can be adjusted by creating a LIFECYCLE_ PARAMETERS le. The Veritas NetBackup Administrators Guide, Volume I should be consulted for additional information before adjusting these values.
Figure 11: Maximum backup copies By default the NetBackup global attribute Maximum backup copies is set to a value of two. As shown above, altering the value to accommodate additional copies is easily performed via the administrative GUI.
4 Duplication to Tape
Requirements to retain long term copies of backup images on removable tape media are easily integrated with OpenStorage solutions. Multiple means of accomplishing this objective currently exist, including enhanced functionality with NetBackup version 6.5.4. 4 NetBackup supports the duplication of backup images, not media or specic tape cartridges. 4 NetBackup supports the creation, cataloging, and tracking of up to ten copies of a particular backup image. 4 The default value for Maximum backup copies is two. 4 The Maximum backup copies parameter can be adjusted with the NetBackup administrative GUI via Host Properties > Master Servers > Global Attributes. (Figure 11)
Figure 12: Storage lifecycle policy with hierarchical duplication This storage lifecycle policy example includes an initial backup destination followed by two duplication destinations. The rst duplication destination will be created from the initial backup copy. The second duplication destination (indented) will be created from the previous duplicated copy. Copy 1 is the initial backup, copy 2 is created from copy 1, and copy 3 is created from copy 2
11
12
Data Domain recommends limiting the maximum number of NetBackup domains that share a Data Domain system based on the number of unique network interface connections present on the Data Domain system. For instance, a Data Domain system with two network interface connections could be shared by a maximum of two NetBackup domains. While this type of conguration provides obvious cost benets, there are applicable cautionary statements: 4 NetBackup capacity reporting may be skewed as each NetBackup domain sees the Data Domain system as a unique storage pool and believes that is has complete and total usage of the available capacity. 4 The maximum number of concurrent jobs supported by a single Data Domain system is effectively shared across more than a single NetBackup domain. There is no mechanism available to arbitrate the usage of available backup, restore, or optimized duplication streams between different NetBackup domains. These values are manually set by the user and may result in sub-optimal resource utilization. 4 Backup images cannot be shared between different NetBackup domains by means of conguring a Data Domain system for usage in two or more NetBackup domains.
Figure 14: Data Domain systems in multiple NetBackup domains This gure depicts two Data Domain systems, each of which is shared between two different NetBackup domains. Note that each Data Domain system has been congured with two LSUs, one for each NetBackup master server. Highly recommended in this type of deployment are naming conventions that assist in eliminating any potential confusion over what resources are used by each NetBackup domain.
Deploying a single Data Domain system in multiple NetBackup domains provides cost advantages when compared to the alternative of using different Data Domain systems for each NetBackup domain. Take, for example, the scenario where there are two NetBackup domains. Each NetBackup domain is in a different data center. Data center 1 performs local backups to a Data Domain system and then uses optimized duplication to create a copy of the backup images at data center 2. Likewise, at data center 2 local backups are performed to a Data Domain system and optimized duplicates are created at data center 1. Using non-shared Data Domain systems would require four separate systems. The shared model is cost effective in that it only requires 2 separate systems. Note: It is important to understand that there is no ability to share backups or NetBackup catalog data between NetBackup domains with this implementation. Data Domain recommends using naming conventions that assist in simplifying the shared use of Data Domain systems in multiple NetBackup domains. For instance, a single Data Domain system shared by two NetBackup domains would have two LSUs congured. Both LSUs will be visible to each different NetBackup domain. Naming the LSUs such that they include the Data Domain system name, the NetBackup master server name, and the -lsu sufx assists in properly conguring each LSU as a disk pool within NetBackup.
6 Disaster Recovery
6.1 Within the Same NetBackup Domain
This scenario assumes that the NetBackup instance in which recovery is to be performed is the same NetBackup instance that performed the initial backup and subsequent optimized duplication job. The rst copy of a backup image created by NetBackup is known as copy 1. When initially written, copy 1 is also known as the primary copy. As of NetBackup version 6.5.4 and prior, the primary copy is the copy that is used to fulll restore requests. An optimized duplication job will create copy 2 of the backup image. If copy 1 has a retention period of two weeks and copy 2 has a retention period of one year, copy 1 will be the primary copy until it expires, at which point copy 2 will become the primary copy. In the case where copy 1 has not expired and is still the primary copy, and a need arises to recover data from copy 2, copy 2 must be set to primary such that it can be used to fulll the restore request. Setting a particular copy to primary can be performed via the NetBackup GUI catalog utility.
13
Figure 17: Setting primary copy Setting a non-primary backup image copy to primary can be accomplished via a pop-up menu. This enables the use of a particular backup image to fulll restore requests. This can be useful in cases where recovery from a specic geographical location is desired or in cases where the original primary copy is not available.
7 Additional References
Data Domain secure access customer support site: https://my.datadomain.com/
Figure 15: NetBackup catalog copy 1 primary copy The NetBackup catalog utility can be used to select the primary copy of a backup image.
OpenStorage (OST) User Guide OpenStorage (OST) Quick Start Data Domain Operating System User Guide Symantec: http://www.symantec.com/business/support/documentation.jsp? language=english&view=manuals&pid=15143 NetBackup Administration Guides NetBackup Shared Storage Guide NetBackup Vault Administrators Guide NetBackup Command Guides
Figure 16: NetBackup catalog copy 2 not primary The NetBackup catalog utility can be used to select copy 2 of a backup image.
Setting a non-primary copy to primary is easily accomplished by right-clicking the image and then selecting Set Primary Copy from the pop-up menu.
14
8 Conclusion
Data Domain support for Symantec NetBackup OpenStorage advances the ability to use disk as disk, store more data on disk with inline deduplication, and simplify the creation of backup copies with optimized duplication. Creating duplicate backup copies with optimized duplication enables advanced disaster recovery strategies. Disaster recovery copies of backup images are created faster, and are available at the disaster recovery location sooner when compared to tapebased solutions. Creating any required tape-based duplicate backup copies, sourcing the duplicate from either the initial backup or the optimized duplicate copy, facilitates long-term retention of backup images. Consolidated tape operations, where fewer data centers create tape-based backup copies, is made possible via the exibility to duplicate to tape at either source or destination data centers.
15
Data Domain | 2421 Mission College Blvd., Santa Clara, CA 95054 | 866-WE-DDUPE, 408-980-4800
Copyright 2010 Data Domain LLC. All rights reserved. Data Domain, Inc. believes information in this publication is accurate as of its publication date. This publication could include technical inaccurancies or typographical errors. The information is subject to change without notice. Changes are periodically added to the information herein; these changes will be incorporated in new additions of the publication. Data Domain, Inc. may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time. Reproduction of this publication without prior written permission is forbidden. The information in this publication is provided as is. Data Domain LLC makes no representations or warranties of any kind, with respect to the information in this publication, and specically disclaims implied warranties of merchantability or tness for a particular purpose. Data Domain and Global Compression are trademarks of Data Domain LLC. All other brands, products, service names, trademarks, or registered service marks are used to identify the products or services of their respective owners.WP-OSTBPG-0310
DEDUPLICATION STORAGE
www.datadomain.com