Riverbed Whitewater Cloud Storage Gateway

Transcription

1 QUICK START GUIDE Riverbed Whitewater Cloud Storage Gateway Quick Start Guide for CA ARCserve Backup Riverbed Technical Marketing September 2012

2 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 Riverbed Technology. All rights reserved. 1

3 TABLE OF CONTENTS Executive Summary... 3 CA ARCserve Backup Architecture Overview... 3 Riverbed Whitewater Cloud Storage Gateway Overview... 4 Deploying Whitewater Gateways with CA ARCserve Backup... 4 CA ARCserve Backup, Riverbed Whitewater Gateway, and Cloud Storage Configuration Example... 5 Pre-Deployment Checklist... 5 Cloud Storage Provider Required Tasks... 6 Amazon S 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 Configuring Whitewater Data Interfaces Configuring Cloud Settings Configuring a CIFS Share Configuring CA ARCserve Backup CA ARCserve Backup Manager Console Overview Adding a Whitewater Gateway to CA ARCserve Backup Tasks Create a Disk-Based Device Assign the Disk-Based Device to a File System Device (FSD) Group Testing CA ARCserve Backup with Whitewater Backup to the Whitewater Gateway Using CA ARCserve Backup Job Status Restore from CA ARCserve Backup Using the Whitewater Gateway Appendix A. Whitewater Gateway Best Practices for CA ARCserve Appendix B. Whitewater Best Practices for Solaris Operating Systems Appendix C. Whitewater Best Practices for Windows 2008 Operating Systems Conclusion About Riverbed Riverbed Technology. All rights reserved. 2

4 Executive Summary This paper outlines the ease of use and deployment of Riverbed Whitewater cloud storage gateway with CA ARCserve Backup. Whitewater 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 CA ARCserve Backup, 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%. CA ARCserve Backup Architecture Overview CA ARCserve Backup provides enterprise class backup and recovery functionality, optimized to support business no matter how simple or complex the IT infrastructure is. Delivering cost- and management-efficient operational and disaster recovery capabilities for local and remote sites, CA ARCserve Backup helps simplify the protection and management of data, addresses business continuity by helping to shorten backup and recovery times, and helps to maximize application availability with advanced data recovery management technologies. In CA ARCserve Backup, all aspects of operations from backups to server management are conducted via the CA ARCserve Manager Console. Administrators can run the Manager Console from any server in the network. A primary backup server provides database management of backups across one or more member/media backup servers. Configuration consists of device setup, backup schedules and group creation, after which the CA ARCserve backup server can automatically backup the clients. All interaction with CA ARCserve Backup, such as starting manual backups, viewing results, and performing device and media operations, is performed through the Manager Console. See Diagram 1 for an image of a typical CA ARCserve deployment Riverbed Technology. All rights reserved. 3

5 Diagram 1 Typical CA ARCserve Backup Overview 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 CA ARCserve Backup CA ARCserve Backup with Riverbed s 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 following sections provide example configurations and show you how to use Whitewater gateways. For further information about performance tuning vranger with Whitewater gateways, refer to the Whitewater Best Practices Guide for Backup Applications Riverbed Technology. All rights reserved. 4

6 CA ARCserve Backup, 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 CA ARCserve primary backup server and Manager Console into a single computer system. The operating system must be either Windows 2003 or Windows Memory requirements will vary, but at minimum a CA ARCserve backup server should have 1GB of RAM or higher. Please check CA s support site and related compatibility lists where applicable. 2. Obtain server systems and related software media supported by Windows 2003 or Windows 2008 R2, CA ARCserve 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 Riverbed Technology. All rights reserved. 5

7 Cloud Storage Provider Required Tasks Amazon S3 To sign up for Amazon S3: 1. Go to and click 2. Follow the on-screen instructions. 3. AWS will notify you by when your account is active and available for you to use. 4. Create a bucket: 5. Follow the link to continue with the process: 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: 2. Follow the on-screen instructions. 3. Receive the confirmation 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 and click 2. Follow the on-screen instructions. 3. Receive the confirmation and login to the Nirvanix Cloud Storage Network: 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 Riverbed Technology. All rights reserved. 6

8 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 and click 2. Follow the on-screen instructions. 3. Perform account confirmation via phone or text message. 4. Login to the Azure portal 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 and sign up for 2. Once account registration is complete, login to the Rackspace portal: US: UK: 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 ( 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 Riverbed Technology. All rights reserved. 7

9 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? Step 4: Netmask? Enter the netmask address. Step 4: Netmask? Step 5: Default gateway? Enter the default gateway for Whitewater. Step 5: Default gateway? Step 6: Primary DNS server? Step 7: Domain name? Step 8: Admin password? 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. 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. Riverbed strongly recommends that you change the default administrator password (password) at this time. The new password must be a minimum of 6 characters. 6. To log out of the system, enter the following command at the system prompt: amnesiac> exit Step 6: Primary DNS server? Step 7: Domain name? example.com Step 8: Admin password? xxxyyy 2012 Riverbed Technology. All rights reserved. 8

10 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 Riverbed Technology. All rights reserved. 9

11 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 Add a New License Remove Selected Licenses Text Box Add Description Displays the controls (licenses text box) to add a new license. Displays the controls to remove a license. Select the license you wish to delete and click Remove Selected to delete it. 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. 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 2012 Riverbed Technology. All rights reserved. 10

12 2. Under Data Network Interfaces, complete the configuration as described in the following table. Control Network Interface IP Configuration Enable Data Interface Description 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. Displays the IP address of the network 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 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 Add a New Route Destination Subnet Mask Gateway Add Remove Selected Description Displays the controls for adding a new route. Specify the destination IP address for the gateway. Specify the subnet mask. Specify the IP address for the gateway. The gateway must be in the same network as the network interface you are configuring. Adds the route to the table list. 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 2012 Riverbed Technology. All rights reserved. 11

13 2. Under Cloud Settings, complete the configuration as described in the following table. Control Protocol Type Hostname Port Bucket Name Description 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. Specify the hostname of the cloud provider on which Whitewater stores the replicated data. For example, s3.amazonaws.com or storage.synaptic.att.com. 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. 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 2012 Riverbed Technology. All rights reserved. 12

14 2. To add a CIFS share, complete the configuration as described in the following table. Control Add CIFS Share Share Name Description Displays the controls to add a new CIFS share. 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 Read Only Allow Everyone Access Remove Selected Add Share Specify a comment about the share. You can only use alphanumeric, underscore (_), hyphen (-) characters and space in this field. Check this check box if you want the share to be a read-only share. Check this check box to enable all clients connected to the Whitewater system to access the CIFS share. Deletes the selected CIFS 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 Add CIFS User User Name Password Password Confirm Remove Selected Add Description Displays the controls to add a user to the Whitewater CIFS server. Specify the user name of a user to access the CIFS shares. Specify the password to authenticate the user. Specify the password again to confirm authentication. Deletes the selected user name from the CIFS server. 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 Join Domain Domain Name User Name Password DNS Domain Organization Unit Hostname Description Displays the controls to add Whitewater to your AD domain. 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. 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. Specify the password to authenticate the user. Optionally, specify the DNS name of the domain. Optionally, specify the organization unit within the domain to which Whitewater must join. 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 Riverbed Technology. All rights reserved. 13

15 Configuring CA ARCserve Backup The following sections describe how to configure and use CA ARCserve Backup with the Whitewater gateway - please refer to the CA ARCserve Administrator s Guide for complete details: CA ARCserve Manager Console Overview Adding the Whitewater gateway to CA ARCserve Tasks o Create a Disk-Based Device (required) o Associate the Disk-Based Device to a File System Device (FSD) Group (optional) Testing CA ARCserve with the Whitewater gateway o Backup to Whitewater Using CA ARCserve Backup o Job Status o Restore from CA ARCserve Backup Using Whitewater CA ARCserve Backup Manager Console Overview The CA ARCserve Manager Console is the interface that is used to configure all settings in a CA ARCserve server environment. In order to use the CA ARCserve Manager Console it must point to the desired CA ARCserve server. The Manager Console can also be pointed at other CA ARCserve servers in environment to monitor activities and statistics for those particular CA ARCserve servers. To point the Manager Console to a different CA ARCserve server, use the Select Server drop down as shown in Figure 7 and Figure 8. Figure 7 CA ARCserve Manager Console 2012 Riverbed Technology. All rights reserved. 14

16 Figure 8 Server Configuration Dialog page Adding a Whitewater Gateway to CA ARCserve Backup Tasks When adding a Whitewater gateway to a CA ARCserve environment there is only one primary task that is required, and one optional task. The required task is to create a disk-based device, which is associated with a CIFS share created on the Whitewater gateway. The optional task is to assign the disk-based device to a specific file system device (FSD) group. Create a Disk-Based Device (required) Assign the Disk-Based Device to a File System Device (FSD) Group (optional) Create a Disk-Based Device A Disk-Based device describes the location of the file based storage on disk, and to which File System Device (FSD) Group the device belongs. The following describes the steps to create an Disk-Based device target and associate it to the Whitewater gateway. These steps use the best practice configuration for CA ARCserve with the Whitewater gateway Riverbed Technology. All rights reserved. 15

17 1. From the CA ARCserve Manager Console, click on the Quick Start menu item and select Administration Device, as shown in Figure 9. Figure 9 Launch CA ARCserve Administration Application 2. When the Devices page appears right-click on the server you wish to modify and select Create Disk-Based Devices as shown in Figure 10. Figure 10 Starting the New Device Wizard 2012 Riverbed Technology. All rights reserved. 16

18 3. When the Disk-Based Devices Configuration wizard starts, click the Add button as shown in Figure 11 below. Figure 11 Advanced File Type Device Selection Device Name This is the device name as displayed within CA ARCserve Description This provides a description fo the device you are creating Data File Location This identifies the CIFS folder path to where you will write media files for this device Group Name This identifies the File System Device (FSD) Group to which this device will belong. If no value is provided, a new FSD Group will be automatically created and assigned for this device (Figure 12). Figure 12 Device Path Entry 2012 Riverbed Technology. All rights reserved. 17

19 Assign the Disk-Based Device to a File System Device (FSD) Group CA ARCserve uses FSD groups to identify common properties of devices stored in a group. Each backup will send data to a FSD group. Note that devices will automatically be assigned to a FSD group when created, so this step is considered optional.to configure the device to use a pre-existing FSD group, follow the steps below. 1. From the CA ARCserve Manager Console, select the Configure Groups button. In the screen that appears select the Device you wish to add to the FSD group from the Available Devices list then click the Assign button, as shown in Figure 13. If the device is already assigned to a FSD group, click on the device and then click the Remove button to shift it to the Available Devices list. Figure 13 View Group Client Properties Testing CA ARCserve Backup with Whitewater Backup to the Whitewater Gateway Using CA ARCserve Backup To test CA ARCserve with the Whitewater gateway you can run a manual backup. 1. Select the Backup menu item out of the Quick Start Menu, as shown in Figure 14. Figure 14 CA ARCserve User GUI Backup Selection 2012 Riverbed Technology. All rights reserved. 18

20 2. When the backup screen appears, make sure the normal backup is selected from the Start Tab, as shown in Figure 15. Figure 15 Initiating a Manual Backup 3. Under the Source tab, select the objects you wish to backup as shown in Figure 16. Figure 16 CA ARCserve User Backup Status 2012 Riverbed Technology. All rights reserved. 19

21 4. On the Schedule tab, optionally configure the schedule to perform backups at a pre-determined time, as shown in Figure 17. Figure 17 CA ARCserve Schedule Screen Custom Schedule Configure custom schedules that meet the backup requirements. Do not use a rotation scheme configuration, as this is not supported. 5. Finally, click on the destination tab and select the Whitewater based File System Device (FSD) Group that was configured in Step 1, and provide a Media Pool to use. and click Submit to begin the backup as shown in Figure 18. Figure 18 Initiating a Backup 2012 Riverbed Technology. All rights reserved. 20

22 Job Status Use the job status screen to view details about the ongoing backup job 1. To view status, select the Monitor & Reports Job Status item from the Quick Start menu, as shown in Figure 19. Figure 19 Job Status Menu Item 2. When the Job Status screen appears, view the backup job details under the Job Queue tab, as shown in Figure 20. Figure 20 Backup Job Status 2012 Riverbed Technology. All rights reserved. 21

23 Restore from CA ARCserve Backup Using the Whitewater Gateway 1. To perform a restore, select the Restore item from the Quick Start menu, as shown in Figure 21. Figure 21 Restore Menu Item 2. When the restore screen appears, identify the data to restore using the Source tab, as shown in Figure 22. Figure 22 Restore Selection Screen 2012 Riverbed Technology. All rights reserved. 22

24 3. Select Restore files to the original location(s) in the Destination tab, and click Submit as shown in Figure 23. Figure 23 Restore Job Destination Screen 4. Use the job status view to monitor the state of the restore operation as it proceeds, as shown in Figure 24. Figure 24 Restore Job Status 2012 Riverbed Technology. All rights reserved. 23

25 Appendix A. Whitewater Gateway Best Practices for CA ARCserve CA ARCserve uses Disk-Based devices associated with clients via File System Device (FSD) Groups to store data from client systems. Devices and Groups can be viewed and modified from the Quick Start menu item and selecting Administration Device from the drop down. Figure 25 Manager Console Device Drop Down Figure 26 Devices and Groups Currently CA ARCserve only allows one backup operation to use one device at a time. To configure multiple backups to use the Whitewater gateway, configure multiple devices that point to separate folders configured on the Whitewater gateway, and assign each device to a separate FSD group. Then configure each backup job to use one of the configured FSD groups Riverbed Technology. All rights reserved. 24

26 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: "DefaultReceiveWindow"=dword: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters] "GlobalMaxTcpWindowSize"=dword: "TcpWindowSize"=dword: "Tcp1323Opts"=dword: Riverbed Technology. All rights reserved. 25

27 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 industryleading 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 Riverbed Technology, Inc. 199 Fremont Street San Francisco, CA Tel: (415) Riverbed Technology Ltd. One Thames Valley Wokingham Road, Level 2 Bracknell. RG42 1NG United Kingdom Tel: Riverbed Technology Pte. Ltd. 391A Orchard Road #22-06/10 Ngee Ann City Tower A Singapore Tel: Riverbed Technology K.K. Shiba-Koen Plaza Building 9F 3-6-9, Shiba, Minato-ku Tokyo, Japan Tel: Riverbed Technology. All rights reserved. 26