• vRanger integration quick start for DDBoost
vRanger integration quick start for DDBoost
Integrating EMC� Data Domain� Boost (DDBoost�) with vRanger is achieved by adding an EMC� Data Domain� appliance running DDBoost to vRanger as a repository. Backups written to that repository are deduplicated according to your configuration. The following steps describe the integration process at a high level, and provide links to the remaining topics for more exploration. Before implementing this solution in a production environment, read this documentation thoroughly.
1 Install DDBoost: To install and enable DDBoost, perform the following operations:
▪ Obtain the license required to enable DDBoost on the Data Domain system. You can purchase a DDBoost license key directly from EMC. The DDBoost license allows you to back up and restore data.
▪ Enable and configure DDBoost on the Data Domain system. At a minimum, configuration includes specifying the DDBoost user name and password.
▪ Install vRanger, which contains the DDBoost Libraries.
2 Configure DDBoost: After DDBoost is licensed and enabled, perform the following steps, if applicable:
▪ Create DDBoost User: vRanger uses the DDBoost user credentials to connect to the Data Domain system.
▪ Create Storage Units: When used with vRanger, a DDBoost repository is configured at the Storage Unit level, meaning each DDBoost repository in vRanger equates to exactly one Storage Unit. You may create storage units through the vRanger user interface (UI), or directly on the Data Domain system, as described in Creating Storage Units.
▪ Configure Distributed Segment Processing: This step allows parts of the deduplication process to be performed by the DDBoost Library, which avoids sending duplicate data to the DDBoost repository. For more information, see Configuring distributed segment processing.
▪ Configure Advanced Load Balancing and Link Failover: This feature allows for combining multiple Ethernet links into a group. Only one of the interfaces on the Data Domain system is registered with vRanger. The DDBoost Library negotiates with the Data Domain system on the interface registered with vRanger to obtain an interface to send the data. For instructions, see Configuring Advanced Load Balancing and Link Failover.
3 Install vRanger: Using the vRanger installer, install vRanger on a machine meeting the vRanger system requirements. For an overview of the installation process, see Installing vRanger. For detailed information, see the Quest vRanger Installation/Upgrade Guide.
4 Create DDBoost Repository: After vRanger is installed, add the DDBoost instance to vRanger as a repository. Any backup written to this repository is deduplicated according to your Data Domain configuration. For more information, see Managing repository replication.
The following topics provide an overview of vRanger and EMC� Data Domain� Boost (DDBoost�), and important information about the licensing required to integrate the two products.
What is vRanger?
vRanger is the leading VMware� data protection solution that also backs up and recovers Windows� physical servers and files with blazing speed and minimal storage requirements. With vRanger, you get comprehensive protection for both virtual and physical environments that you can manage from one intuitive interface.
vRanger has historically supported EMC� Data Domain� systems as repositories, but required that the Data Domain system was configured as a Common Internet File System (CIFS) share. vRanger extends this functionality to support the more advanced functionality offered by EMC� Data Domain� Boost (DDBoost�), and allow direct configuration of DDBoost repositories.
For virtual machine (VM) backup, a license for vRanger controls the number of source CPUs that you can configure for backup. For licensing purposes, a multi-core processor is counted as a single CPU. For physical backup, each server protected consumes one physical backup license.
Every VMware� ESXi� host for which vRanger is expected to provide protection must be properly licensed, both by VMware and in the vRanger Host Licensing tab.
EMC� Data Domain� Boost (DDBoost�) enables backup servers to communicate with storage systems without the need for EMC� Data Domain� storage systems to emulate tape. There are two components to the software:
• The DDBoost Libraries for integrating with the DDBoost server running on the Data Domain system.
• The DDBoost server that runs on Data Domain systems. A Data Domain system can be a single Data Domain system or a gateway.
The Data Domain system exposes pre-made disk volumes called storage units to a DDBoost-enabled backup server. By using the DDBoost Libraries, multiple backup servers can use the same storage unit on a Data Domain system as a storage server. Each backup server can run a different operating system, if it is supported by Data Domain.
EMC� Data Domain� Boost (DDBoost�) software is an optional product that requires a license to operate on the EMC� Data Domain� system. You can purchase a DDBoost software license key for a Data Domain system directly from EMC.
• vRanger integration quick start for DDBoost
vRanger integration quick start for DDBoost
Integrating EMC� Data Domain� Boost (DDBoost�) with vRanger is achieved by adding an EMC� Data Domain� appliance running DDBoost to vRanger as a repository. Backups written to that repository are deduplicated according to your configuration. The following steps describe the integration process at a high level, and provide links to the remaining topics for more exploration. Before implementing this solution in a production environment, read this documentation thoroughly.
1 Install DDBoost: To install and enable DDBoost, perform the following operations:
▪ Obtain the license required to enable DDBoost on the Data Domain system. You can purchase a DDBoost license key directly from EMC. The DDBoost license allows you to back up and restore data.
▪ Enable and configure DDBoost on the Data Domain system. At a minimum, configuration includes specifying the DDBoost user name and password.
▪ Install vRanger, which contains the DDBoost Libraries.
2 Configure DDBoost: After DDBoost is licensed and enabled, perform the following steps, if applicable:
▪ Create DDBoost User: vRanger uses the DDBoost user credentials to connect to the Data Domain system.
▪ Create Storage Units: When used with vRanger, a DDBoost repository is configured at the Storage Unit level, meaning each DDBoost repository in vRanger equates to exactly one Storage Unit. You may create storage units through the vRanger user interface (UI), or directly on the Data Domain system, as described in Creating Storage Units.
▪ Configure Distributed Segment Processing: This step allows parts of the deduplication process to be performed by the DDBoost Library, which avoids sending duplicate data to the DDBoost repository. For more information, see Configuring distributed segment processing.
▪ Configure Advanced Load Balancing and Link Failover: This feature allows for combining multiple Ethernet links into a group. Only one of the interfaces on the Data Domain system is registered with vRanger. The DDBoost Library negotiates with the Data Domain system on the interface registered with vRanger to obtain an interface to send the data. For instructions, see Configuring Advanced Load Balancing and Link Failover.
3 Install vRanger: Using the vRanger installer, install vRanger on a machine meeting the vRanger system requirements. For an overview of the installation process, see Installing vRanger. For detailed information, see the Quest vRanger Installation/Upgrade Guide.
4 Create DDBoost Repository: After vRanger is installed, add the DDBoost instance to vRanger as a repository. Any backup written to this repository is deduplicated according to your Data Domain configuration. For more information, see Managing repository replication.
The following topics provide an overview of vRanger and EMC� Data Domain� Boost (DDBoost�), and important information about the licensing required to integrate the two products.
What is vRanger?
vRanger is the leading VMware� data protection solution that also backs up and recovers Windows� physical servers and files with blazing speed and minimal storage requirements. With vRanger, you get comprehensive protection for both virtual and physical environments that you can manage from one intuitive interface.
vRanger has historically supported EMC� Data Domain� systems as repositories, but required that the Data Domain system was configured as a Common Internet File System (CIFS) share. vRanger extends this functionality to support the more advanced functionality offered by EMC� Data Domain� Boost (DDBoost�), and allow direct configuration of DDBoost repositories.
For virtual machine (VM) backup, a license for vRanger controls the number of source CPUs that you can configure for backup. For licensing purposes, a multi-core processor is counted as a single CPU. For physical backup, each server protected consumes one physical backup license.
Every VMware� ESXi� host for which vRanger is expected to provide protection must be properly licensed, both by VMware and in the vRanger Host Licensing tab.
EMC� Data Domain� Boost (DDBoost�) enables backup servers to communicate with storage systems without the need for EMC� Data Domain� storage systems to emulate tape. There are two components to the software:
• The DDBoost Libraries for integrating with the DDBoost server running on the Data Domain system.
• The DDBoost server that runs on Data Domain systems. A Data Domain system can be a single Data Domain system or a gateway.
The Data Domain system exposes pre-made disk volumes called storage units to a DDBoost-enabled backup server. By using the DDBoost Libraries, multiple backup servers can use the same storage unit on a Data Domain system as a storage server. Each backup server can run a different operating system, if it is supported by Data Domain.
EMC� Data Domain� Boost (DDBoost�) software is an optional product that requires a license to operate on the EMC� Data Domain� system. You can purchase a DDBoost software license key for a Data Domain system directly from EMC.
Understanding DDBoost
Introducing DDBoost
EMC� Data Domain� Boost (DDBoost�) enables backup servers to communicate with storage systems without the need for EMC� Data Domain� storage systems to emulate tape. There are two components to the software:
• The DDBoost Libraries for integrating with the DDBoost server running on the Data Domain system.
• The DDBoost server that runs on Data Domain systems. A Data Domain system can be a single Data Domain system or a gateway.
The Data Domain system exposes pre-made disk volumes called storage units to a DDBoost-enabled backup server. By using the DDBoost Libraries, multiple vRanger instances can use the same storage unit on a Data Domain system as a storage server. Each backup server can run a different operating system, if it is supported by Data Domain.
EMC� Data Domain� supports EMC� Data Domain� Boost (DDBoost�) on the following Data Domain (OS) versions:
▪ OS 5.7 — requires vRanger 7.3 or later
▪ OS 6.0— requires vRanger 7.6.4 or later
▪ OS 6.1— requires vRanger 7.6.4 or later
▪ OS 6.2— requires vRanger 7.8 or later
The DDBoost Library version must be compatible with your Data Domain system and data protection application configurations.
This topic provides a technical overview of EMC� Data Domain� Boost (DDBoost�) features. Configuration information for these features is described in Configuring the Data Domain system.
• Distributed segment processing
• Advanced Load Balancing and Link Failover
Distributed segment processing
Distributed segment processing allows parts of the deduplication process to be performed by the EMC� Data Domain� Boost (DDBoost�) Library, which avoids sending duplicate data to the EMC� Data Domain� system that is configured as a vRanger repository. The option to distribute the processing is enabled or disabled on the Data Domain system; for more information, see Configuring distributed segment processing. The DDBoost Library negotiates with the Data Domain system for the current setting of the option and behaves appropriately. Therefore, the DDBoost Library offers two modes of operation for sending backup data to a Data Domain system: one with distributed segment processing enabled and the other with the distributed segment processing disabled.
Distributed segment processing provides the following benefits:
• Potentially higher throughput, because the DDBoost Library sends only unique data to a Data Domain system versus sending all the data over the LAN. Throughput improvements depend on the redundant nature of the data being backed up, the overall workload on the backup server, and the capability of the backup server. In general, greater throughput is attained with higher redundancy, greater backup server workload, and backup server capability.
• The network bandwidth requirements are reduced since only the unique data is sent over the LAN to the Data Domain systems.
For more information about local compression and its configuration, see the EMC Data Domain Operating System Administration Guide.
You manage distributed segment processing by using the ddboost option commands, as described in Using the DDBoost commands.
NOTE: EMC recommends that you use distributed segment processing if your network connection is 1 Gb Ethernet.
Distributed segment processing disabled
In this mode, the EMC� Data Domain� Boost (DDBoost�) Library sends the data directly to the Data Domain system over the LAN. The Data Domain system then segments, deduplicates, and compresses the data before it is written to the disk. The DDBoost Library runs on the backup server.
Distributed segment processing enabled
In this mode, the deduplication process is distributed between the EMC� Data Domain� Boost (DDBoost�) Library and the Data Domain system.
NOTE: The DDBoost Library runs on the vRanger server. The DDBoost Library’s handling of data is transparent to vRanger and the library does not store any data on the backup server.
Parts of the deduplication process are run by the DDBoost Library so that only unique data is sent to data to a Data Domain system over the LAN. The DDBoost Library segments, computes IDs for the segments, checks with the Data Domain system for duplicate segments, compresses unique segments that are not found on the Data Domain system, and sends the compressed data to the Data Domain system. The Data Domain system then writes the unique data to disk.
Advanced Load Balancing and Link Failover
vRanger supports a single host name and IP address per repository. For EMC� Data Domain� systems that require multiple 1 GbE links to obtain full system performance, you must set up multiple storage servers on the Data Domain systems — one per interface — and target the backup policies to different storage servers to spread the load on the interfaces.
The Advanced Load Balancing and Link Failover feature allows for combining multiple Ethernet links into a group. Only one of the interfaces on the Data Domain system is registered with vRanger. The EMC� Data Domain� Boost (DDBoost�) Library negotiates with the Data Domain system on the interface registered with vRanger to obtain an interface to send the data. The load balancing provides higher physical throughput to the Data Domain system compared to configuring the interfaces into a virtual interface using Ethernet level aggregation.
The Data Domain system load balances the connections coming in from multiple vRanger instances on all the interfaces in the group. The load balancing is transparent to vRanger. Because Advanced Load Balancing and Link Failover works at the DDBoost Library software layer, it is seamless to the underlying network connectivity and supports both physical and virtual interfaces.
The data transfer is load balanced based on the number of connections outstanding on the interfaces. Only connections for backup and restore jobs are load balanced.
NOTE: The replication connection between the Data Domain systems is not part of the load balancing. A single IP address is used for the target Data Domain system.
IMPORTANT: Quest recommends that you exclude one interface from the ifgroup and reserve it for the replication path between the source and target Data Domain systems.
The Advanced Load Balancing and Link Failover feature can be used with other network layer aggregation and failover technologies. The Advanced Load Balancing and Link Failover functionality also works with other network layer functionality on the Data Domain systems, including VLAN tagging and IP aliasing. This functionality allows additional flexibility in segregating traffic into multiple virtual networks, which run over the same physical links on the Data Domain system.
The benefits of Advanced Load Balancing and Link Failover are as follows:
• Eliminates the need to register multiple storage servers — one for each interface — with vRanger, which can potentially simplify installation management.
• If one of the interfaces in the group goes down while the Data Domain system is still operational, the subsequent incoming backup jobs are routed to the available interfaces.
• The backup and restore jobs are automatically load balanced on multiple interfaces in the group, which can potentially result in higher utilization of the links.
• All in-flight jobs to the failed interface transparently are failed over to healthy operational links. From the point of view of vRanger, the jobs continue uninterrupted.
• The interfaces can be added only to the group using an IP address.
• Even though the Advanced Load Balancing and Link Failover feature works with mixed 1GbE interfaces and 10 GbE interfaces in a group, it is not a recommended setup. Quest recommends that you have interfaces with the same link speed in a group.
• Since only one interface group is supported on the EMC� Data Domain� system, for connecting more than one backup server, a switch is needed in the middle.
File replication replicates a single file. The replication request is initiated by the application. By default, the backup servers set up replication jobs between two EMC� Data Domain� systems after authenticating them using the pre-configured EMC� Data Domain� Boost (DDBoost�) user name and password. If the replication feature is enabled, when an optimized job is set up by backup servers, the session between the source and destination Data Domain systems is encrypted using Secure Sockets Layer (SSL), ensuring all image data and metadata is sent encrypted over the WAN.
Enabling this option on Data Domain system is transparent to the data protection application. When the data protection application requests Data Domain system to perform a replication job, the source and destination systems negotiate automatically to perform encryption without knowledge of the requesting data protection application. Replication uses the ADH-AES256-SHA cipher suite. There is no ability to configure a different suite.
Replication is available to a Data Domain system with an installed Replicator license, and applies to all replication jobs on that system. Both the source and the destination Data Domain systems that are participating in replication jobs must have this option enabled for it to take effect.
Replication can be used with the encryption of data-at-rest feature available on Data Domain operating system with the optional Encryption license. When replication is used with the encryption of data-at-rest feature, the encrypted backup image data is encrypted again using SSL for sending over WAN.
• Both the source and the destination EMC� Data Domain� systems must be running Data Domain OS 5.2 or later to use this feature.
• Enabling this feature does not require restarting the file system on a Data Domain system.
• The low-bandwidth optimization and the encryption options can be used with each other.
The low-bandwidth Replicator option reduces the WAN bandwidth utilization. This option is useful if replication is being performed over a low-bandwidth network (WAN) link. This option provides additional compression during data transfer and is recommended only replication jobs that occur over WAN links that have fewer than 6 Mb/s of available bandwidth.
The low-bandwidth optimization option is available to EMC� Data Domain�s systems with an installed Replicator license. The option is enabled on a Data Domain system and applies to all replication jobs on that system.
Enabling this option on Data Domain system is transparent to the data protection application. When the data protection application requests a Data Domain system to perform a replication job, the source and destination systems automatically perform the additional compression without involving the requesting data protection application.
Each Data Domain system wanting to participate in low-bandwidth replication must have this option enabled.
Understanding DDBoost
Introducing DDBoost
EMC� Data Domain� Boost (DDBoost�) enables backup servers to communicate with storage systems without the need for EMC� Data Domain� storage systems to emulate tape. There are two components to the software:
• The DDBoost Libraries for integrating with the DDBoost server running on the Data Domain system.
• The DDBoost server that runs on Data Domain systems. A Data Domain system can be a single Data Domain system or a gateway.
The Data Domain system exposes pre-made disk volumes called storage units to a DDBoost-enabled backup server. By using the DDBoost Libraries, multiple vRanger instances can use the same storage unit on a Data Domain system as a storage server. Each backup server can run a different operating system, if it is supported by Data Domain.
EMC� Data Domain� supports EMC� Data Domain� Boost (DDBoost�) on the following Data Domain (OS) versions:
▪ OS 5.7 — requires vRanger 7.3 or later
▪ OS 6.0— requires vRanger 7.6.4 or later
▪ OS 6.1— requires vRanger 7.6.4 or later
▪ OS 6.2— requires vRanger 7.8 or later
The DDBoost Library version must be compatible with your Data Domain system and data protection application configurations.
This topic provides a technical overview of EMC� Data Domain� Boost (DDBoost�) features. Configuration information for these features is described in Configuring the Data Domain system.
• Distributed segment processing
• Advanced Load Balancing and Link Failover
Distributed segment processing
Distributed segment processing allows parts of the deduplication process to be performed by the EMC� Data Domain� Boost (DDBoost�) Library, which avoids sending duplicate data to the EMC� Data Domain� system that is configured as a vRanger repository. The option to distribute the processing is enabled or disabled on the Data Domain system; for more information, see Configuring distributed segment processing. The DDBoost Library negotiates with the Data Domain system for the current setting of the option and behaves appropriately. Therefore, the DDBoost Library offers two modes of operation for sending backup data to a Data Domain system: one with distributed segment processing enabled and the other with the distributed segment processing disabled.
Distributed segment processing provides the following benefits:
• Potentially higher throughput, because the DDBoost Library sends only unique data to a Data Domain system versus sending all the data over the LAN. Throughput improvements depend on the redundant nature of the data being backed up, the overall workload on the backup server, and the capability of the backup server. In general, greater throughput is attained with higher redundancy, greater backup server workload, and backup server capability.
• The network bandwidth requirements are reduced since only the unique data is sent over the LAN to the Data Domain systems.
For more information about local compression and its configuration, see the EMC Data Domain Operating System Administration Guide.
You manage distributed segment processing by using the ddboost option commands, as described in Using the DDBoost commands.
NOTE: EMC recommends that you use distributed segment processing if your network connection is 1 Gb Ethernet.
Distributed segment processing disabled
In this mode, the EMC� Data Domain� Boost (DDBoost�) Library sends the data directly to the Data Domain system over the LAN. The Data Domain system then segments, deduplicates, and compresses the data before it is written to the disk. The DDBoost Library runs on the backup server.
Distributed segment processing enabled
In this mode, the deduplication process is distributed between the EMC� Data Domain� Boost (DDBoost�) Library and the Data Domain system.
NOTE: The DDBoost Library runs on the vRanger server. The DDBoost Library’s handling of data is transparent to vRanger and the library does not store any data on the backup server.
Parts of the deduplication process are run by the DDBoost Library so that only unique data is sent to data to a Data Domain system over the LAN. The DDBoost Library segments, computes IDs for the segments, checks with the Data Domain system for duplicate segments, compresses unique segments that are not found on the Data Domain system, and sends the compressed data to the Data Domain system. The Data Domain system then writes the unique data to disk.
Advanced Load Balancing and Link Failover
vRanger supports a single host name and IP address per repository. For EMC� Data Domain� systems that require multiple 1 GbE links to obtain full system performance, you must set up multiple storage servers on the Data Domain systems — one per interface — and target the backup policies to different storage servers to spread the load on the interfaces.
The Advanced Load Balancing and Link Failover feature allows for combining multiple Ethernet links into a group. Only one of the interfaces on the Data Domain system is registered with vRanger. The EMC� Data Domain� Boost (DDBoost�) Library negotiates with the Data Domain system on the interface registered with vRanger to obtain an interface to send the data. The load balancing provides higher physical throughput to the Data Domain system compared to configuring the interfaces into a virtual interface using Ethernet level aggregation.
The Data Domain system load balances the connections coming in from multiple vRanger instances on all the interfaces in the group. The load balancing is transparent to vRanger. Because Advanced Load Balancing and Link Failover works at the DDBoost Library software layer, it is seamless to the underlying network connectivity and supports both physical and virtual interfaces.
The data transfer is load balanced based on the number of connections outstanding on the interfaces. Only connections for backup and restore jobs are load balanced.
NOTE: The replication connection between the Data Domain systems is not part of the load balancing. A single IP address is used for the target Data Domain system.
IMPORTANT: Quest recommends that you exclude one interface from the ifgroup and reserve it for the replication path between the source and target Data Domain systems.
The Advanced Load Balancing and Link Failover feature can be used with other network layer aggregation and failover technologies. The Advanced Load Balancing and Link Failover functionality also works with other network layer functionality on the Data Domain systems, including VLAN tagging and IP aliasing. This functionality allows additional flexibility in segregating traffic into multiple virtual networks, which run over the same physical links on the Data Domain system.
The benefits of Advanced Load Balancing and Link Failover are as follows:
• Eliminates the need to register multiple storage servers — one for each interface — with vRanger, which can potentially simplify installation management.
• If one of the interfaces in the group goes down while the Data Domain system is still operational, the subsequent incoming backup jobs are routed to the available interfaces.
• The backup and restore jobs are automatically load balanced on multiple interfaces in the group, which can potentially result in higher utilization of the links.
• All in-flight jobs to the failed interface transparently are failed over to healthy operational links. From the point of view of vRanger, the jobs continue uninterrupted.
• The interfaces can be added only to the group using an IP address.
• Even though the Advanced Load Balancing and Link Failover feature works with mixed 1GbE interfaces and 10 GbE interfaces in a group, it is not a recommended setup. Quest recommends that you have interfaces with the same link speed in a group.
• Since only one interface group is supported on the EMC� Data Domain� system, for connecting more than one backup server, a switch is needed in the middle.
File replication replicates a single file. The replication request is initiated by the application. By default, the backup servers set up replication jobs between two EMC� Data Domain� systems after authenticating them using the pre-configured EMC� Data Domain� Boost (DDBoost�) user name and password. If the replication feature is enabled, when an optimized job is set up by backup servers, the session between the source and destination Data Domain systems is encrypted using Secure Sockets Layer (SSL), ensuring all image data and metadata is sent encrypted over the WAN.
Enabling this option on Data Domain system is transparent to the data protection application. When the data protection application requests Data Domain system to perform a replication job, the source and destination systems negotiate automatically to perform encryption without knowledge of the requesting data protection application. Replication uses the ADH-AES256-SHA cipher suite. There is no ability to configure a different suite.
Replication is available to a Data Domain system with an installed Replicator license, and applies to all replication jobs on that system. Both the source and the destination Data Domain systems that are participating in replication jobs must have this option enabled for it to take effect.
Replication can be used with the encryption of data-at-rest feature available on Data Domain operating system with the optional Encryption license. When replication is used with the encryption of data-at-rest feature, the encrypted backup image data is encrypted again using SSL for sending over WAN.
• Both the source and the destination EMC� Data Domain� systems must be running Data Domain OS 5.2 or later to use this feature.
• Enabling this feature does not require restarting the file system on a Data Domain system.
• The low-bandwidth optimization and the encryption options can be used with each other.
The low-bandwidth Replicator option reduces the WAN bandwidth utilization. This option is useful if replication is being performed over a low-bandwidth network (WAN) link. This option provides additional compression during data transfer and is recommended only replication jobs that occur over WAN links that have fewer than 6 Mb/s of available bandwidth.
The low-bandwidth optimization option is available to EMC� Data Domain�s systems with an installed Replicator license. The option is enabled on a Data Domain system and applies to all replication jobs on that system.
Enabling this option on Data Domain system is transparent to the data protection application. When the data protection application requests a Data Domain system to perform a replication job, the source and destination systems automatically perform the additional compression without involving the requesting data protection application.
Each Data Domain system wanting to participate in low-bandwidth replication must have this option enabled.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center
