Riverbed® Whitewater® Cloud Storage Gateway Quick … · Data Protector with Whitewater gateways, please refer to the Whitewater Best Practices Guide for Backup Applications. HP

QUICK START GUIDE

Riverbed® Whitewater® Cloud Storage Gateway Quick Start Guide for HP® Data Protector® Riverbed Technical Marketing

September 2012

RIVERBED WHITEWATER QUICK START GUIDE

© 2012 Riverbed Technology. All rights reserved. 1

© 2012 Riverbed Technology. All rights reserved. Riverbed®, Cloud Steelhead®, Granite™, Interceptor®, RiOS®, Steelhead®, Think Fast®, Virtual Steelhead®, Whitewater®,Mazu®, Cascade®, Cascade Pilot™, Shark®, AirPcap®, SkipWare®, TurboCap®, WinPcap®, Wireshark®, and Stingray™ are trademarks or registered trademarks of Riverbed Technology, Inc. in the United States and other countries. Riverbed and any Riverbed product or service name or logo used herein are trademarks of Riverbed Technology. All other trademarks used herein belong to their respective owners. The trademarks and logos displayed herein cannot be used without the prior written consent of Riverbed Technology or their respective owners. Akamai® and the Akamai wave logo are registered trademarks of Akamai Technologies, Inc. SureRoute is a service mark of Akamai. Google® is a registered trademark of Google and its affiliates in the United States and in other countries. Salesforce® is a registered trademark of Salesforce.com and its affiliates in the United States and in other countries. Apple and Mac are registered trademarks of Apple, Incorporated in the United States and in other countries. Cisco is a registered trademark of Cisco Systems, Inc. and its affiliates in the United States and in other countries. EMC, Symmetrix, and SRDF are registered trademarks of EMC Corporation and its affiliates in the United States and in other countries. IBM, iSeries, and AS/400 are registered trademarks of IBM Corporation and its affiliates in the United States and in other countries. Linux is a trademark of Linus Torvalds in the United States and in other countries. Microsoft, Windows, Vista, Outlook, Office 365, BPOS and Internet Explorer are trademarks or registered trademarks of Microsoft Corporation in the United States and in other countries. Oracle and JInitiator are trademarks or registered trademarks of Oracle Corporation in the United States and in other countries. UNIX is a registered trademark in the United States and in other countries, exclusively licensed through X/Open Company, Ltd. VMware, ESX, ESXi are trademarks or registered trademarks of VMware, Incorporated in the United States and in other countries. This documentation is furnished “AS IS” and is subject to change without notice and should not be construed as a commitment by Riverbed Technology. This documentation may not be copied, modified or distributed without the express authorization of Riverbed Techn ology and may be used only in connection with Riverbed products and services. Use, duplication, reproduction, release, modification, disclosure or transfer of this documentation is restricted in accordance with the Federal Acquisition Regulations as applied to civilian agencies and t he Defense Federal Acquisition Regulation Supplement as applied to military agencies. This documentation qualifies as “commercial computer software documentation” and any use by the government shall be governed solely by these terms. All other use is prohibited. Riverbed T echnology assumes no responsibility or liability for any errors or inaccuracies that may appear in this documentation.



TABLE OF CONTENTS

Executive Summary .................................................................................................................................................................................................... 3

HP Data Protector Architecture Overview .................................................................................................................................................................. 3

Riverbed Whitewater Cloud Storage Gateway Overview ........................................................................................................................................... 4

Deploying Whitewater Gateways with HP Data Protector .......................................................................................................................................... 4

HP Data Protector, Riverbed Whitewater Gateway, and Cloud Storage Configuration Example .............................................................................. 4

Pre-deployment Checklist ........................................................................................................................................................................................... 5

Cloud Storage Provider Required Tasks .................................................................................................................................................................... 6 Amazon S3 ............................................................................................................................................................................................................ 6 AT&T Synaptic Storage as a Service .................................................................................................................................................................. 6 Nirvanix Cloud Storage Network ......................................................................................................................................................................... 6 EMC Atmos ............................................................................................................................................................................................................ 7 Microsoft Windows Azure .................................................................................................................................................................................... 7 Rackspace Cloud Files ......................................................................................................................................................................................... 7 OpenStack Object Storage (Swift) ...................................................................................................................................................................... 7

Configuring the Whitewater Gateway ......................................................................................................................................................................... 8 Configuring the Whitewater Management Interface.......................................................................................................................................... 8 Connecting to the Management Console GUI ................................................................................................................................................... 9 Configuring Whitewater Gateway Licenses ..................................................................................................................................................... 10 Configuring Whitewater Data Interfaces .......................................................................................................................................................... 10 Configuring Cloud Settings ............................................................................................................................................................................... 11 Configuring a CIFS Share .................................................................................................................................................................................. 12

Configuring HP Data Protector ................................................................................................................................................................................. 14 HP Data Protector Management Console Overview ........................................................................................................................................ 14 Adding a Whitewater Gateway to HP Data Protector Domain Tasks ............................................................................................................ 14 Data Protector Device Creation ......................................................................................................................................................................... 14 Associate a Data Protector Job to the Newly Created Device ....................................................................................................................... 20

Testing Data Protector with Whitewater ................................................................................................................................................................... 22 Backup to Whitewater Using Data Protector ................................................................................................................................................... 22 Job Monitor ......................................................................................................................................................................................................... 23 Restore from Data Protector Using Whitewater .............................................................................................................................................. 23

Appendix A. Whitewater Gateway Best Practices for HP Data Protector ................................................................................................................. 26

Appendix B. Whitewater Best Practices for Solaris Operating Systems .................................................................................................................. 27

Appendix C. Whitewater Best Practices for Windows 2008 Operating Systems ...................................................................................................... 27

Conclusion ................................................................................................................................................................................................................ 28

About Riverbed ......................................................................................................................................................................................................... 28



Executive Summary This paper outlines the ease of use and deployment of Riverbed® Whitewater® cloud storage gateway with HP Data Protector. Whitewater gateways provides a simple, efficient way to offsite data to cloud storage providers powered by Amazon® S3, AT&T® Synaptic Storage as a Service, HP® Cloud Services, Microsoft® Windows® Azure cloud storage, Nirvanix® Cloud Storage Network, Rackspace® Cloud Files, and general instances of EMC® Atmos and OpenStack™ (Swift) Object Storage. Whitewater gateways simply act as a storage unit within a backup infrastructure managed by HP Data Protector, enabling organizations to eliminate their reliance on tape infrastructure and all of its associated capital and operational costs, while improving backup windows and disaster recovery capabilities. It is simple to set up the Whitewater gateway and start moving data to the cloud in a few hours, compared to setting up tape or other disk replication infrastructures which can take days. Leveraging Riverbed’s industry leading deduplication, compression and WAN optimization technologies, Whitewater gateways shrink data set sizes by 10 to 30x substantially reducing cloud storage costs, accelerating data transfers and storing more data within the local cache, speeding recovery. Security is provided by encrypting data on-site, in-flight, as well as in the cloud using 256-bit AES encryption and SSL v3. Whitewater gateway provides a dual layer of encryption that ensures that any data moved into the cloud is not compromised, and it creates a complete end-to-end security solution for cloud storage. Since a Whitewater appliance is an asymmetric, stateless gateway, no hardware is needed in the cloud and you can recover the last known good state of a broken or destroyed Whitewater gateway to a new Whitewater gateway. Whitewater gateways provide flexibility to scale cloud storage as the business requirements change. All capital expenditure planning required with tape and disk replication based solutions is avoided, saving organizations 30-50%.

HP Data Protector Architecture Overview HP Data Protector is a backup solution that provides reliable data protection and high accessibility for your fast growing business data. Data Protector offers comprehensive backup and restore functionality specifically tailored for enterprise-wide and distributed environments. HP Data Protector software is designed specifically to reduce the PC protection burden on IT staff, address the needs of remote workers, and help ensure that PC data is centrally protected to reduce your organization’s legal and compliance risks. See Diagram 1 Typical Data Protector Network View for an image of a typical HP Data Protector deployment.

Diagram 1 Typical Data Protector Network View (Physical and Logical View)



Riverbed Whitewater Cloud Storage Gateway Overview

Figure 1 Whitewater gateway The Riverbed Whitewater gateway is a disk-to-disk backup and archive storage gateway with unique cloud storage capabilities. Whitewater gateways easily integrate into your existing backup infrastructure and cloud storage. All of the standard backup applications allow you to add a Whitewater gateway as a common target within its existing infrastructure. The backup server connects to the Whitewater gateway using standard CIFS or NFS protocols. When you backup to a Whitewater device, it performs byte-level inline deduplication of the backup data to minimize storage consumption and transmission times. Whitewater gateways also use their local disk cache for local storage and recovery of recent backups, providing LAN performance for the most likely restores. The Whitewater gateway then writes the deduplicated backup data to cloud storage, and also accelerate restores from the cloud by moving only deduplicated data over the WAN. The gateway management console enables you to manage all of this through a web browser interface.

Deploying Whitewater Gateways with HP Data Protector HP Data Protector with Riverbed Whitewater disk-to-disk backup and archive gateway provide users with a flexible, easy-to-configure and use solution that can be deployed with major cloud storage providers. The sections below provide example configurations and setup steps needed to begin using Whitewater gateways. For further information about performance tuning HP Data Protector with Whitewater gateways, please refer to the Whitewater Best Practices Guide for Backup Applications.

HP Data Protector, Riverbed Whitewater Gateway, and Cloud Storage Configuration Example

Diagram 2 Logical Architecture View



Pre-deployment Checklist 1. You will need at least one server that combines the function of a master/media server into a single computer system. It is recommended to separate the master and master servers so the systems will not be overloaded. These servers, along with clients, need minimum a minimum of 2.26 GHz processors and 4GB RAM. Most clients will also run Windows Server 2008 R2. Please check the HP Data Protector support site and related compatibility lists where applicable. 2. Obtain server systems and related software media supported by Windows 2008 R2, HP Data Protector and Riverbed Whitewater gateway. 3. A Whitewater physical gateway or virtual Whitewater gateway needs to be online and connected to the physical network infrastructure. 4. You must procure and setup all necessary software licenses from each vendor, including Riverbed, using vendor-specific guidelines. 5. Physical stacking and racking of equipment at each site. All cabling and power must be operational. Verify that all LAN and WAN connections are functioning to and from Internet and cloud storage provider(s) 6. Set up the Windows server(s) within an existing or new created naming service such as Active Directory.

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&contentType=SupportManual&prodTypeId=18964&prodSeriesId=3889913#0



Cloud Storage Provider Required Tasks

Amazon S3

To sign up for Amazon S3:

1. Go to http://aws.amazon.com/s3 and click 2. Follow the on-screen instructions. 3. AWS will notify you by e-mail when your account is active and available for you to use. 4. Create a bucket: http://docs.amazonwebservices.com/AmazonS3/latest/gsg/CreatingABucket.html 5. Follow the link to continue with the process: http://docs.amazonwebservices.com/AmazonS3/latest/gsg 6. Make sure that you record the following information:

Access Key - Specify the access key (similar to the user name) for your Amazon S3 (AWS) account.

Secret Key - Specify the secret key (password) for your Amazon S3 provider account.

Bucket Name – Specify the bucket name created in step 4 above.

AT&T Synaptic Storage as a Service

To sign up for AT&T Synaptic Storage as a Service: 1. Go to the following website and click Sign Up Now: http://www.business.att.com/enterprise/Family/application-hosting-enterprise/storage-as-a-service-enterprise/ 2. Follow the on-screen instructions. 3. Receive the confirmation email and login to the AT&T Synaptic Storage as a Service website. 4. Record the following information:

Tenant ID - Specify the tenant ID that AT&T Synaptic Storage as a Service uses to authenticate each request.

UID - Specify the application ID (also known as UID) used to authenticate each request.

Shared Secret - Specify the shared secret that AT&T Synaptic Storage as a Service uses to authenticate each request.

Nirvanix Cloud Storage Network

To sign up for Nirvanix Cloud Storage Network:

1. Go to http://www.nirvanix.com/how-to-buy/index.aspx and click 2. Follow the on-screen instructions. 3. Receive the confirmation email and login to the Nirvanix Cloud Storage Network: https://nmp.nirvanix.com/default.aspx 4. Create an application name, and record the following information related to that application:

Application Key - Specify the application key established during account registration.

Application Name - Specify the application key established during account registration.

UserName - Specify the user account name established during account registration.

Password - Specify the password established during account registration. Note: Users can get the Application Name/Key by going to https://nmp.nirvanix.com/applications.aspx

http://aws.amazon.com/s3

http://docs.amazonwebservices.com/AmazonS3/latest/gsg/CreatingABucket.html

http://docs.amazonwebservices.com/AmazonS3/latest/gsg

http://www.business.att.com/enterprise/Family/application-hosting-enterprise/storage-as-a-service-enterprise/

http://www.nirvanix.com/how-to-buy/index.aspx

https://nmp.nirvanix.com/default.aspx

https://nmp.nirvanix.com/applications.aspx

http://aws.amazon.com/s3

http://www.business.att.com/enterprise/Family/application-hosting-enterprise/storage-as-a-service-enterprise/



EMC Atmos

Please refer to EMC Atmos documentation for information about preparing EMC Atmos for use with a Whitewater gateway. When ready, EMC Atmos will provide the following information for you to enter into the Whitewater GUI:

Host Name – Hostname or IP address of the EMC Atmos gateway.

Sub Tenant ID – Specify the tenant ID that is used to authenticate each request.

UID – Specify the user ID that is used to authenticate each request.

Shared Secret - Specify the shared secret used to authenticate each request.

Microsoft Windows Azure

To sign up for Microsoft Windows Azure:

1. Go to http://www.microsoft.com/windowsazure/free-trial/ and click 2. Follow the on-screen instructions. 3. Perform account confirmation via phone or text message. 4. Login to the Azure portal https://windows.azure.com/Default.aspx and create a new Storage Account under Hosted Services, Storage Accounts & CDN. 5. Record the following information from the created storage account to enter into the Whitewater GUI:

Storage Account – Provide the name of the storage account created in Azure.

Primary/Secondary Key – Provide either the primary or secondary access key from the storage account created.

Rackspace Cloud Files

To sign up for Rackspace Cloud Files:

1. Go to https://signup.rackspacecloud.com/signup and sign up for 2. Once account registration is complete, login to the Rackspace portal: US: https://manage.rackspacecloud.com/pages/Login.jsp UK: https://lon.manage.rackspacecloud.com/pages/Login.jsp 3. Access Your Account > API Access, and record the following information to enter into the Whitewater GUI:

Access Key – Provide the API key used to access the cloud account.

Username – Provide the user name associated with the account.

OpenStack Object Storage (Swift)

Please refer to OpenStack documentation (http://docs.openstack.org/) for information about deploying an OpenStack Object Storage cluster for use with Whitewater gateways. You should have the following information ready to enter into the Whitewater GUI:

Host Name – Hostname or IP address of the OpenStack Object Storage Proxy server

Port – Port on which the OpenStack Object Storage Proxy server listens to

Username – Specify the username that is used to authenticate each request.

Password – Specify the password that is used to authenticate each request.

http://www.microsoft.com/windowsazure/free-trial/

https://windows.azure.com/Default.aspx

https://signup.rackspacecloud.com/signup

https://manage.rackspacecloud.com/pages/Login.jsp

https://lon.manage.rackspacecloud.com/pages/Login.jsp

http://docs.openstack.org/



Configuring the Whitewater Gateway The Whitewater Installation Guide and Whitewater User’s Guide provide full details for requirements and installation of the Whitewater gateway. The configuration is broken down into the following activities:

Configuring the Whitewater Management Interface

Connecting to the Whitewater Management Console

Configuring Whitewater Gateway Licenses

Configuring Whitewater Data Interfaces

Configuring Cloud Settings

Configuring a CIFS Share

Configuring the Whitewater Management Interface

After you install and start the Whitewater appliance, connect to the Whitewater CLI to configure the management interface: 1. If you are using a virtual Whitewater gateway, connect directly to the console session using the VMware vSphere client and skip to step 3. If you are using a physical Whitewater gateway, plug the serial cable into the Console port and a terminal. 2. Start your terminal emulation program, such as Tera Term Pro. The terminal device must have the following settings: Baud rate: 9600 bps Data bits: 8 Parity: none Stop bits: 1 vt100 emulation No flow control Note: If you are using Whitewater with a terminal server, the terminal server must use hardware flow control for the port connected to Whitewater. 3. Log in as an administrator user (admin) and enter the default password (password): login as: admin password: password 4. The configuration wizard automatically starts after you have entered the login and default password. Enter yes at the system prompt to begin the configuration wizard. For example: Do you want to use the configuration wizard for initial configuration? yes 5. Complete the configuration wizard steps on the client side and server side:

Wizard Prompt Description Example

Step 1: Host name? Enter the host name for Whitewater. Step 1: Hostname? Amnesiac

Step 2: Use DHCP on the primary interface?

You are given the option to enable the DHCP to automatically assign an IP address to the primary interface for Whitewater. Riverbed recommends that you do not set DHCP. The default value is no.

Step 2: Use DHCP? no

Step 3: Primary IP address? Enter the IP address for Whitewater. Step 3: Primary IP address? 10.10.10.6

Step 4: Netmask? Enter the netmask address. Step 4: Netmask? 255.255.0.0

Step 5: Default gateway? Enter the default gateway for Whitewater. Step 5: Default gateway? 10.0.0.1

Step 6: Primary DNS server? Enter the primary DNS server IP address. You must specify the primary DNS server for cloud provider name resolution. If you do not specify a valid DNS server, the system will not start.

Step 6: Primary DNS server? 10.0.0.2

Step 7: Domain name? Enter the domain name for the network where Whitewater is to reside. If you set a domain name, you can enter host names in the system without the domain name.

Step 7: Domain name? example.com

Step 8: Admin password? Riverbed strongly recommends that you change the default administrator password (password) at this time. The new password must be a minimum of 6 characters.

Step 8: Admin password? xxxyyy

6. To log out of the system, enter the following command at the system prompt: amnesiac> exit



Connecting to the Management Console GUI

After you configure Whitewater, you can verify and modify your configuration settings and view performance reports and system logs in the Management Console. You can connect to the Management Console through any supported Web browser. To connect to the Management Console you must know the host, domain, and administrator password that you assigned in the configuration wizard. Note: Cookies and JavaScript must be enabled in your Web browser. To connect to the Management Console: 1. Enter the URL for the Management Console in the location box of your Web browser: protocol://host.domain – protocol is http or https. https uses the SSL protocol to ensure a secure environment. If you use https to connect, the system prompts you to inspect and verify the SSL key. – host is the host name you assigned to Whitewater during initial configuration. If your DNS server maps that IP address to a name, you can specify the DNS name. – domain is the full domain name for Whitewater. Note: You can specify the IP address instead of the host and domain. 2. The Management Console appears, displaying the login page as shown in Figure 2.

Figure 2 Riverbed Whitewater Management Console

-In the Username text box, type the user login: admin or monitor. The default login is admin. Users with administrator (admin) privileges can configure and administer Whitewater. Users with monitor (monitor) privileges can view connected Whitewaters, reports, and system logs. -In the Password text box, type the password that you assigned in the configuration wizard. By default the password is password. -Click Log In to display the Home page. The Home page summarizes the current status of your system.



Configuring Whitewater Gateway Licenses

You can add or remove a license in the Configure > Maintenance > Licenses page. You install a license on a Whitewater gateway after receiving it from Riverbed Technical Support or Sales. To add or remove a license: 1. Choose Configure > Maintenance > Licenses to display the Licenses page, as shown in Figure 3.

Figure 3 Whitewater Gateway Licenses Page

2. Complete the configuration as described in the following table.

Control Description

Add a New License Displays the controls (licenses text box) to add a new license.

Remove Selected Displays the controls to remove a license. Select the license you wish to delete and click Remove Selected to delete it.

Licenses Text Box Copy and paste the license key provided by Riverbed Technical Support or Sales into the text box. Tip: Separate multiple license keys with a space, Tab, or Enter.

Add Adds the license.

3. Click Save to save your settings permanently.

Configuring Whitewater Data Interfaces

You can view and modify settings for the data interfaces in the Configure > Networking > Data Interfaces page. To display and modify the configuration for data interfaces: 1. Choose Configure > Networking > Data Interfaces to display the Data Interfaces page, as shown in Figure 4.

Figure 4 Whitewater Data Interface Page



2. Under Data Network Interfaces, complete the configuration as described in the following table.

Control Description

Network Interface Displays the controls to add a network interface. Click the magnifying glass icon next to an interface to display the controls to configure the interface. Riverbed recommends that you use the network interfaces for backup and LAN traffic.

IP Configuration Displays the IP address of the network interface.

Enable Data Interface

Check this check box to enable the data interface and specify the following settings: • IPv4 Address - Specify an IP address. • IPv4 Subnet Mask - Specify a subnet mask. • Data Gateway IP - Specify the data gateway IP address. The data gateway must be in the same network as the data interface. • MTU - Specify the MTU value. The MTU is the largest physical packet size, measured in bytes, that a network can send. The default value is 1500.

3. Under Routing Table for <network interface> (for example, Routing Table for eth0_0), configure static routing in the routing table if your device management network requires static routes. You can add or remove routes as described in following table. Click Apply to apply your changes to the running configuration, and click Save to save your changes permanently.

Control Description

Add a New Route Displays the controls for adding a new route.

Destination Specify the destination IP address for the gateway.

Subnet Mask Specify the subnet mask.

Gateway Specify the IP address for the gateway. The gateway must be in the same network as the network interface you are configuring.

Add Adds the route to the table list.

Remove Selected Check the check box next to the name and click Remove Selected.

Configuring Cloud Settings

You can specify cloud settings, replication scheduling, and bandwidth limit settings in the Configure > Storage > Cloud Settings page. Replication is the process that transfers deduplicated data from Whitewater to the cloud asynchronously. A storage replication service provides an extra measure of redundancy that can be invaluable if the main storage backup system fails. Immediate access to the replicated data minimizes downtime and its associated costs. Replication streamlines disaster recovery processes by generating duplicate copies of all backed-up files on a continuous basis. It can also simplify recovery from all types of disasters including fire, flood, hurricane, virus, or worm. Note: Before you configure cloud settings, configure DNS settings to access the cloud service provider host machine. To configure cloud settings: 1. Choose Configure > Storage > Cloud Settings to display the Cloud Settings page, as shown in Figure 5.

Figure 5 Cloud Settings Page



2. Under Cloud Settings, complete the configuration as described in the following table.

Control Description

Protocol Type

Select the cloud service provider from the drop-down menu. If you select Amazon S3, you must also specify the following: • Access Key - Specify the access key (similar to the user name) for your Amazon S3 (AWS) account. • Secret Key - Specify the secret key (password) for your cloud service provider account. If you select AT&T Synaptic Storage, you must specify the following: • Sub Tenant ID - Specify the sub tenant ID that AT&T Synaptic Storage uses to authenticate each request. • UID - Specify the user ID that AT&T Synaptic Storage uses to authenticate each request. • Shared Secret - Specify the shared secret that AT&T Synaptic Storage uses to authenticate each request. When the client application builds a Web service request, AT&T Synaptic Storage uses the shared secret to create a signature entry as a part of the request. The shared secret must be associated with the tenant ID and application ID created by AT&T Synaptic Storage. If you select Nirvanix Storage, you must specify the following: • Application Key - Specify the application (access) key for your Nirvanix Storage account. • Application Name - Specify the application name of your Nirvanix Storage account. • Username - Specify the user name that Nirvanix Storage uses to authenticate each request. • Password - Specify the password that Nirvanix Storage uses to authenticate each request. If you select EMC Atmos, you must specify the following: • Sub Tenant ID - Specify the subtenant ID that EMC Atmos uses to authenticate each request. • UID - Specify the user ID that EMC Atmos uses to authenticate each request. • Shared Secret - Specify the shared secret that EMC Atmos uses to authenticate each request. When the client application builds a Web service request, EMC Atmos uses the shared secret to create a signature entry as a part of the request. The shared secret must be associated with the subtenant ID and application ID created by the EMC Atmos-based storage provider. If you select Microsoft Windows Azure, you must specify the following: • Storage Account – Provide the name of the storage account created in Azure. • Primary/Secondary Key – Provide either the primary or secondary access key from the storage account created. If you select Rackspace Cloud Files, you must specify the following: • Access Key - Specify the access key for the Rackspace account. • Username - Specify the user name associated with the Rackspace account. If you select OpenStack Object Storage, you must specify the following: • Password - Specify the password that OpenStack uses to authenticate each request. • Username - Specify the user name that OpenStack uses to authenticate each request.

Hostname Specify the hostname of the cloud provider on which Whitewater stores the replicated data. For example, s3.amazonaws.com or storage.synaptic.att.com.

Port Specify the port through which replication occurs. Amazon uses port 80, which is an unsecured port, or port 443, which is a secure port. AT&T Synaptic Storage, Nirvanix Storage, and EMC Atmos use port 443. The default value is 443, which works for all cloud providers.

Bucket Name Specify the bucket name associated with your cloud service provider account. Buckets are containers (similar to folders) that store deduplicated data sent from Whitewater.

Configuring a CIFS Share

You can configure Common Internet File System (CIFS) access to Whitewater in the Configure > Storage > CIFS page. CIFS is a protocol that allows programs to make requests for files and services on remote computers on the Internet. The share you configured appears in the list of shares on the page. When you add a CIFS share to Whitewater, you can enable authentication or leave it disabled (allowing all users to access the CIFS share). If you enable authentication, you must add CIFS users who can access the share. To configure CIFS: 1. Choose Configure > Storage > CIFS to display the CIFS page, as shown in Figure 6.

Figure 6 Adding a CIFS Share



2. To add a CIFS share, complete the configuration as described in the following table.

Control Description

Add CIFS Share Displays the controls to add a new CIFS share.

Share Name Specify the name of the share to be added.

Path Specify the pathname to the share to be added. It starts with a forward slash (/).

Comment Specify a comment about the share. You can only use alphanumeric, underscore (_), hyphen (-) characters and space in this field.

Read Only Check this check box if you want the share to be a read-only share.

Allow Everyone Access Check this check box to enable all clients connected to the Whitewater system to access the CIFS share.

Remove Selected Deletes the selected CIFS share.

Add Share Adds the CIFS share to the Whitewater CIFS server. The share you add appears in the list of shares on the page.

3. To add a CIFS user, complete the configuration as described in the following table.

Control Description

Add CIFS User Displays the controls to add a user to the Whitewater CIFS server.

User Name Specify the user name of a user to access the CIFS shares.

Password Specify the password to authenticate the user.

Password Confirm Specify the password again to confirm authentication.

Remove Selected Deletes the selected user name from the CIFS server.

Add Adds the user name and password to the Whitewater CIFS server.

4. To add Whitewater to an Active Directory (AD) domain, complete the configuration as described in the following table.

Control Description

Join Domain Displays the controls to add Whitewater to your AD domain.

Domain Name Specify the domain name of the AD that Whitewater must join. If your system has an AD domain, then you can add Whitewater to your AD domain and create share permissions for AD users and groups.

User Name Specify the user name of a user to access the AD domain. The user name must be a part of theAD and the user must have permissions to add computers to the domain.

Password Specify the password to authenticate the user.

DNS Domain Optionally, specify the DNS name of the domain.

Organization Unit Optionally, specify the organization unit within the domain to which Whitewater must join.

Hostname Optionally, specify the hostname that Whitewater must use to join the domain. Whitewater then appears as the specified hostname in the AD.

5. Under Global CIFS Settings, specify the values for SMB (Server Message Block) Signing and Guest Account. This setting overrides the setting under Add CIFS User. Select one of the following values for SMB Signing:

Disabled - The CIFS server does not offer SMB signing. This is the default value.

Auto - Enables SMB signing automatically. The CIFS server offers SMB signing, but does not enforce it. You can choose to enable or disable it.

Mandatory - The CIFS server enforces SMB signing. You must use SMB signing if you select this option. Select one of the following values for Guest Account:

Enabled - Activates the guest account. A user may authenticate as a guest user and access a CIFS share (which allows guest users) using any user name and password. If you want to enable any user to access the share, you can use this feature.

Disabled - De-activates the guest account. Note: Windows provides the ability to sign CIFS messages to prevent man-in-the-middle attacks when sharing files. Each CIFS message has a unique signature, which prevents the message from being tampered with. Note: Enabling SMB signing degrades Whitewater performance.



Configuring HP Data Protector The following sections describe how to configure and use Data Protector with the Whitewater gateway - please refer to the HP Data Protector Installation Guide for complete details:

HP Data Protector Administration Console Overview

Adding the Whitewater gateway to HP Data Protector Domain Tasks o Data Protector device creation o Associate a Data Protector job to the newly created device

Testing Data Protector with the Whitewater gateway

Job Monitor

Testing a File Restore

HP Data Protector Management Console Overview

The Data Protector Management Console is the interface that is used to configure all settings in a Data Protector environment. In order for the Data Protector management console to make changes it must point to the desired Data Protector server. By default the management console will locate the Data Protector server on the local system. The management console can also be pointed at other Data Protector servers in the domain to monitor activities and statistics for those particular servers. To point the management console to a different media server use the Connect to Cell Manager drop down menu item indicated in Figure 7.

Figure 7 Data Protector Management Console

Adding a Whitewater Gateway to HP Data Protector Domain Tasks

When adding a Whitewater gateway to a Data Protector environment there are two primary tasks that are required. The first is to create a device, and define a directory to a CIFS share created on the Whitewater gateway. The second is to modify or setup a backup job that will use the newly created device:

Data Protector device creation (required)

Associate a Data Protector job to the newly created device (required)

Data Protector Device Creation

A device is a physical device configured by Data Protector to accept writes and reads to storage media. The following describes the steps to create a device and associate it to the Whitewater gateway. These steps use the best practice configuration for the Data Protector with the Whitewater gateway. 1. Open the Management Console, select File Connect to Cell Manager (if not local to the management console system) and enter the host name and click Connect (Figure 8).

http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&prodSeriesId=3889913&targetPage=http%3A%2F%2Fbizsupport2.austin.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc01631236%2Fc01631236.pdf

http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&prodSeriesId=3889913&targetPage=http%3A%2F%2Fbizsupport2.austin.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc01631236%2Fc01631236.pdf



Figure 8 Cell Manager Connection

2. Click on the drop down menu and select Devices & Media (Figure 9).

Figure 9 New Device Menu Option 3. Right click on Devices in the list and select Add Device (Figure 10):

Figure 10 New Device Properties



4. When the add device pane opens on the right side, enter in the following information as shown in Figure 11.

Figure 11 Add Device

Device Name

Type a unique name for the device. This is the target used by the backup job Description

Provide an optional description about the device Device Type

Select File Library from the drop down menu of choices 5. Provide the CIFS path to the Whitewater share created previously and click on Add. Select the newly created CIFS share from the list in the lower portion of the window and then click Properties, as shown in Figure 12.

Figure 12 Specify CIFS target path to device



6. In the properties window that appears, adjust the Maximum size of file depot from 5 to 20, as shown in Figure 13. Click OK, then click Next when you return to the previous screen.

Figure 13 File Library Device Properties

6. Make sure the Media Type is set to the value of File, and click Next as shown in Figure 14. Click Finish to complete the wizard.

Figure 14 Media Type Selection



7. Select and expand the newly created device that appears on the left tree. Expand Drives and right click and select Properties for the drive listed, as shown in Figure 15.

Figure 15 Drive View after File Library Creation

8. When the drive properties window appears on the right, select the Settings tab, and click on the Advanced button as shown in Figure 16.

Figure 16 Drive Properties Window



9. In the Settings tab of the window that appears, adjust the Concurrency value. It is recommended to use an initial value of 5, as shown in Figure 17.

Figure 17 Drive Advanced Properties Settings Tab

10. Select the Sizes tab, and adjust the Block size value to 1024 from the drop down menu, as shown in Figure 18. Click OK and then click Apply at the previous screen to save the changes.

Figure 18 Drive Advanced Properties Sizes Tab



Associate a Data Protector Job to the Newly Created Device

Data Protector backups can be performed as jobs under the Backup drop down menu item. Using policies help align similar aspects of associated backup job properties, so that separate backup jobs do not need to be configured individually. Among the properties that can be configured for a job or a policy is the target to which the backup data will be written. Use the following steps to associate a Data Protector job or policy to a Whitewater based device. 1. Click on the Job Setup button, right click on an existing job name and select Properties (Figure 19).

Figure 19 Backup Selection Drop Down

2. On the Backup pane that appears, select the backup job to be modified. On the right pane, go to the Destination tab, and make sure that the new Whitewater device is selected from the list (Figure 20).

Figure 20 Access the Job Properties



3. On the Options tab, select the Advanced button in the section Filesystem Options (Figure 21).

Figure 21 Filesystem Backup Options

4. When the Filesystem Options screen appears make sure that the Software Compression checkbox is not selected and Data security is set to None under the Other tab (Figure 22). Click OK, and click Apply on the previous panel to submit the change.

Figure 22 Advanced Filesystem Backup Options



Testing Data Protector with Whitewater

Backup to Whitewater Using Data Protector

To test Data Protector with the Whitewater gateway you can run a manual backup of a job modified in the previous step. To run a manual backup right-click on the backup job then select Start Backup (Figure 23).

Figure 23 Initiating a Manual Backup

2. Select the backup type and click OK to begin the operation (Figure 24).

Figure 24 Backup Type Selection



Job Monitor

The backup will report its status within the Backup view that appears when the backup is running. You may also find the Backup view within the Monitor drop down, as shown in Figure 25.

Figure 25 Job Monitor Report

Restore from Data Protector Using Whitewater

When the backup is complete, perform a restore to validate that a Whitewater gateway can restore the backed up data. 1. From the Data Protector Management console, select the Restore drop down. When the restore tree appears, expand the file system tree and select the server and drive you wish to restore objects for, as shown in Figure 26.

Figure 26 Client Side Backup/Restore GUI

2. On the right pane, select the objects from the backup you want to restore, as shown in Figure 27.



Figure 27 Restore Files Selection

3. In the Destination tab select the target where you would like to restore the files, as shown in Figure 28.

Figure 28 Restore Files Selection



4. Click the Restore button to bring up the Start Restore Session window. Click Finish to begin the operation (Figure 29).

Figure 29 Operation Confirmation



Appendix A. Whitewater Gateway Best Practices for HP Data Protector HP Data Protector uses Devices to send backups to Whitewater gateways. Backup jobs should also be tuned for use with Whitewater gateways. Configuration of both areas can be performed within the Data Protector GUI.

Set the Concurrency value to an initial value of 5. This may be increased upwards accordingly given the available

resources on the network.

Set the Block Size to the maximum value of 1024 for best backup performance.



Appendix B. Whitewater Best Practices for Solaris Operating Systems NFS networking parameters on Solaris operating systems should be configured to optimally send data to Whitewater via configured NFS mounts. In addition to tuning the rsize and wsize mount options appropriately, nfs3_max_transfer_size and nfs3_bsize should also be tuned. nfs3_max_transfer_size and nfs3_bsize should be greater than or equal to minimum of rsize and wsize. To set the values, edit the /etc/system file and change/add the following lines to the file: nfs:nfs3_max_transfer_size=<value>

nfs:nfs3_bsize=<value>

A reboot of the system is required in order for the configuration changes to take effect.

Appendix C. Whitewater Best Practices for Windows 2008 Operating Systems Windows networking parameters for CIFS can be modified to improve overall backup application performance. To make these changes, go to Start Menu and enter regedit to start the Windows registry editor. Provide administrative permissions if prompted. Note that changes made within Windows registry editor are permanent upon entry so use extreme caution when making the changes/additions. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parame

ters]

"SESSTIMEOUT"=dword:00000e10

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AFD\Parameters]

"DefaultSendWindow"=dword:00040000

"DefaultReceiveWindow"=dword:00040000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

"GlobalMaxTcpWindowSize"=dword:00040000

"TcpWindowSize"=dword:00040000

"Tcp1323Opts"=dword:00000003



Conclusion Riverbed is extending its industry-proven deduplication to cloud storage. Riverbed deduplication make replication more efficient than in the past by reducing the amount of data that is transferred. Now, the Whitewater gateway will extend those industry-leading deduplication capabilities to cloud storage, cutting the cost of data backup and disaster recovery by significantly reducing the capital and operational costs of storage consumed as well as the bandwidth requirements for moving backup data into and out of the cloud. Backup policies can easily be reconfigured to take advantage of Riverbeds core technology strengths, resulting in improved backup and recovery benefits and increasing availability of data to users.

About Riverbed Riverbed delivers performance for the globally connected enterprise. With Riverbed, enterprises can successfully and intelligently implement strategic initiatives such as virtualization, consolidation, cloud computing, and disaster recovery without fear of compromising performance. By giving enterprises the platform they need to understand, optimize and consolidate their IT, Riverbed helps enterprises to build a fast, fluid and dynamic IT architecture that aligns with the business needs of the organization. Additional information about Riverbed (NASDAQ: RVBD) is available at www.riverbed.com.

Riverbed Technology, Inc. 199 Fremont Street San Francisco, CA 94105 Tel: (415) 247-8800 www.riverbed.com

Riverbed Technology Ltd. One Thames Valley Wokingham Road, Level 2 Bracknell. RG42 1NG United Kingdom Tel: +44 1344 31 7100

Riverbed Technology Pte. Ltd. 391A Orchard Road #22-06/10 Ngee Ann City Tower A Singapore 238873 Tel: +65 6508-7400

Riverbed Technology K.K. Shiba-Koen Plaza Building 9F 3-6-9, Shiba, Minato-ku Tokyo, Japan 105-0014 Tel: +81 3 5419 1990

http://www.riverbed.com/

Documents

Riverbed® Whitewater® Cloud Storage Gateway Quick … · Data Protector with Whitewater gateways, please refer to the Whitewater Best Practices Guide for Backup Applications. HP