DEPLOYMENT GUIDE
Riverbed® Whitewater® Cloud Storage Gateway Quick Start Guide for Oracle® Database Server Riverbed Technical Marketing
September 2012
RIVERBED WHITEWATER QUICK START GUIDE
© 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 inaccur acies that may appear in this documentation.
© 2012 Riverbed Technology. All rights reserved.
1
RIVERBED WHITEWATER QUICK START GUIDE
TABLE OF CONTENTS Executive Summary .................................................................................................................................................................................................... 3 Oracle Database Server Architecture Overview ......................................................................................................................................................... 3 Riverbed Whitewater Cloud Storage Gateway Overview ........................................................................................................................................... 4 Deploying Whitewater Gateways with Oracle Database Server ................................................................................................................................. 4 Oracle Database Server, Riverbed Whitewater Gateway, and Cloud Storage Configuration Example ..................................................................... 5 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 Licenses ..................................................................................................................................................................... 10 Configuring Whitewater Data Interfaces .......................................................................................................................................................... 10 Configuring Cloud Settings ............................................................................................................................................................................... 11 Configuring a CIFS Share .................................................................................................................................................................................. 12 Configuring NFS ................................................................................................................................................................................................. 14 Configuring Oracle Database Server ........................................................................................................................................................................ 15 Oracle RMAN and Enterprise Manager Overview............................................................................................................................................ 15 Adding a Whitewater Gateway to Oracle RMAN Task..................................................................................................................................... 15
Mount the Whitewater Export (NFS Environments) ................................................................................................................. 16 Configure Backup Device Target to Whitewater ...................................................................................................................... 17 Testing Oracle with Whitewater ................................................................................................................................................................................ 19 Backup to Whitewater Using Oracle RMAN .................................................................................................................................................... 19 Monitoring a Job ................................................................................................................................................................................................. 22 Restore to Oracle Using Whitewater ................................................................................................................................................................ 23 Appendix A. Whitewater Gateway Best Practices for Oracle RMAN ........................................................................................................................ 24 Appendix B. Whitewater Best Practices for Solaris Operating Systems .................................................................................................................. 25 Appendix C. Whitewater Best Practices for Windows 2008 Operating Systems ...................................................................................................... 25 Conclusion ................................................................................................................................................................................................................ 26 About Riverbed ......................................................................................................................................................................................................... 26
© 2012 Riverbed Technology. All rights reserved.
2
RIVERBED WHITEWATER QUICK START GUIDE
Executive Summary This paper outlines the ease of use and deployment of Riverbed® Whitewater® cloud storage gateway with Oracle RMAN. 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 backup target within a database infrastructure backed up by Oracle RMAN, 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%.
Oracle Database Server Architecture Overview Oracle Database Server is a relational database management system which provides one of the most advanced feature sets to allow organizations to better store, view, understand and leverage their data for business activities. Comprised of a myriad of features, Oracle has grown from its humble beginnings to a full-fledged database management server system that provides advanced clustering capabilities, grid infrastructure and automatic storage management, and powerful management and availability features. In regards to protecting Oracle database server, Oracle Recovery Manager (RMAN) has evolved into the preferred backup tool for backing up Oracle Databases. Prior to RMAN, backup jobs had to be scripted and took a database offline for the backup. Scripts were cumbersome to implement and prone to user error. RMAN simplified database backup strategies significantly, and the ability to backup a database while online was a huge advancement for Oracle database administrators that needed to protect their database infrastructure. RMAN is the Oracle database application that uses database server sessions to perform backup and recovery. It stores metadata about its operations in the control file of the target database and can also store this in a recovery catalog schema in an Oracle database. RMAN as a command-line executable started from the operating system prompt, and can also be run via the backup user interface through the Enterprise Manager (EM) GUI. Backups can be written to either the Fast recovery area, disk, or via a third party media manager to Tape storage. See Diagram 1 Typical Oracle RMAN Network View for an image of a typical RMAN deployment.
© 2012 Riverbed Technology. All rights reserved.
3
RIVERBED WHITEWATER QUICK START GUIDE
Diagram 1 Typical Oracle RMAN Network 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 Oracle Database Server Oracle database server with Riverbed Whitewater disk-to-disk backup and archive gateway provide users with a flexible, easy-toconfigure 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 Oracle with Whitewater, please refer to the Whitewater Best Practices Guide for Backup Applications.
© 2012 Riverbed Technology. All rights reserved.
4
RIVERBED WHITEWATER QUICK START GUIDE
Oracle Database Server, Riverbed Whitewater Gateway, and Cloud Storage Configuration Example
Diagram 2 Logical Architecture View
Pre-deployment Checklist 1. A Whitewater physical gateway or virtual Whitewater gateway needs to be online and connected to the physical network infrastructure. 2. All necessary software licenses from each vendor, including Riverbed, will need to be procured and set using vendor-specific guidelines. 3. Physical stacking and racking of equipment at each site. This includes all cabling and power need to be operational. Verify that all LAN and WAN connections are functioning to and from Internet and cloud storage provider(s)
© 2012 Riverbed Technology. All rights reserved.
5
RIVERBED WHITEWATER QUICK START GUIDE
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
© 2012 Riverbed Technology. All rights reserved.
6
RIVERBED WHITEWATER QUICK START GUIDE
EMC Atmos Please refer to EMC Atmos documentation for information about preparing an EMC Atmos system for use with Whitewater. When ready, EMC Atmos will provide the following information for you to enter to Whitewater: Host Name – Hostname or IP address of the EMC Atmos system. 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 Whitewater: 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 configure Whitewater: 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. You should have the following information ready to enter to Whitewater: 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.
© 2012 Riverbed Technology. All rights reserved.
7
RIVERBED WHITEWATER QUICK START GUIDE
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 Licenses Configuring Whitewater Data Interfaces Configuring Cloud Settings Configuring a CIFS Share
Configuring the Whitewater Management Interface Once the gateway is installed and started connect to the Whitewater CLI to configure the management interface of Whitewater: 1. If using a virtual Whitewater gateway, connect directly to the console session using the VMware vSphere client and skip to step 3. If 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
© 2012 Riverbed Technology. All rights reserved.
8
RIVERBED WHITEWATER QUICK START GUIDE
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 you are prompted 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: Alternatively, 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.
© 2012 Riverbed Technology. All rights reserved.
9
RIVERBED WHITEWATER QUICK START GUIDE
Configuring Whitewater 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
© 2012 Riverbed Technology. All rights reserved.
10
RIVERBED WHITEWATER QUICK START GUIDE
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 (for example, Routing Table for eth0_0), configure a static routing in the routing table if your device management network requires static routes. You can add or remove routes from the table 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
© 2012 Riverbed Technology. All rights reserved.
11
RIVERBED WHITEWATER QUICK START GUIDE
2. Under Cloud Settings, complete the configuration as described in the following table. Control
Description
Protocol Typex
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
© 2012 Riverbed Technology. All rights reserved.
12
RIVERBED WHITEWATER QUICK START GUIDE
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.
© 2012 Riverbed Technology. All rights reserved.
13
RIVERBED WHITEWATER QUICK START GUIDE
Configuring NFS You can configure Network File System (NFS) in the Configure > Storage > NFS page. NFS is a protocol that enables a user on a client computer to access files over a network in a manner similar to how local storage is accessed. To configure NFS: 1. Choose Configure > Storage > NFS to display the NFS page as shown in
Figure 7 NFS Page 2. Complete the configuration as described in the following table. Control
Description
Add an Export
Displays the controls to export an NFS share.
Name
Specify the name of the export share.
Export path
Specify the export file pathname. It starts with a forward slash (/). Ensure that the export folder already exists. You cannot export to a folder that does not exist.
Comment
Specify a comment about the NFS share.
Allow All Clients or Allow Specified Clients
Enables all clients connected to the Whitewater system to access the NFS share. Or Enables only the clients that you specify to connect to the Whitewater system to access the NFS share. If you select this option, you must specify the client’s IP address and subnet mask in the text field below it. To enable all clients to access the NFS share, type 0.0.0.0/0 in the Client IP/Network field.
Add
Adds the export path and client IP address to the Whitewater NFS server.
Remove Selected
Deletes an exported NFS share.
The share you configure and its parameters appear in the list of shares on the page. 3. Click Apply to apply your changes to the running configuration.
© 2012 Riverbed Technology. All rights reserved.
14
RIVERBED WHITEWATER QUICK START GUIDE
Configuring Oracle Database Server The following sections describe how to perform basic configuration of Oracle RMAN with the Whitewater gateway - please refer to the Oracle Database Documentation Library for complete details: Oracle RMAN and Enterprise Manager Overview Adding the Whitewater gateway to Oracle RMAN Task o Mount the Whitewater Export (NFS only) o Configure Backup Device Target to Whitewater Testing Oracle with the Whitewater Gateway Monitoring a Job Restore to Oracle using Whitewater
Oracle RMAN and Enterprise Manager Overview Oracle RMAN exists as a command line application, but can be invoked via the Enterprise Manager console. The Enterprise Manager console is the GUI interface that is used among other tasks to help configure many of the backup and restore RMAN settings in an Oracle database server environment. Point a web browser to the Oracle server to begin the login process to that Oracle server, as shown in Figure 8.
Figure 8 Oracle Enterprise Manager Login Panel
Adding a Whitewater Gateway to Oracle RMAN Task When adding a Whitewater gateway to an Oracle RMAN environment there is only one required task, which is to configure a disk backup device location from Oracle to Whitewater. Typically this is set to a disk target, but for the purposes of cloud backup will point to either a Whitewater CIFS share or NFS based export. If the Oracle RMAN backup will send backup data to a NFS export on Whitewater, then a prerequisite step is required to mount the Whitewater NFS export on the Oracle server system.
© 2012 Riverbed Technology. All rights reserved.
15
RIVERBED WHITEWATER QUICK START GUIDE
Mount the Whitewater Export (NFS Environments) When using Whitewater as a NFS target, the NFS export created by Whitewater in the previous step must first be mounted on the server where Oracle is configured. On Unix based Oracle database systems, it is recommended to use Oracle Direct NFS in order to improve performance between Oracle and Whitewater. This NFS client is built directly into the Oracle 11g database kernel, and is recommended when using NAS based disk targets. Further information about Oracle Direct NFS can be reviewed here: http://www.orafaq.com/wiki/Direct_NFS http://www.oracle.com/technetwork/articles/directnfsclient-11gr1-twp-129785.pdf 1. If Oracle Direct NFS client is being used, the Whitewater NFS export must be configured with the insecure option to allow connections from Oracle Direct NFS. This step is not required if using the default NFS client with Linux or Unix. The insecure option is only available via the Whitewater command line interface, and cannot be set via the Whitewater GUI. Configure the NFS export via the Whitewater GUI, then login to the command line interface and issue the following commands: en conf t nfs export modify name insecure For example, to configure the default NFS export Whitewater, issue the following commands: en conf t nfs export modify name Whitewater insecure 2. Mount the Whitewater NFS export on Linux or Unix. From the command prompt of the Linux or Unix operating system issue the following command: mount -o rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,vers=3,timeo=600,actimeo=0 whitewater-name:/rfs/nfs /mnt -o rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,vers=3,timeo=600,actimeo=0 Configure the mount options with a read and write buffer size of 32kb, version 3 TCP, and a time out of 600ms. whitewater-name/rfs/ /mnt Specify the export file pathname that is to be mounted, and the local folder on the Unix or Linux operating system on which to mount the NFS export. The local folder location corresponds to the Disk Backup Location that will be specified in the Oracle Backup Settings Device Tab below (in this example, /mnt).
© 2012 Riverbed Technology. All rights reserved.
16
RIVERBED WHITEWATER QUICK START GUIDE
Configure Backup Device Target to Whitewater 1. From the Oracle Enterprise Manager main page, click on the Availability tab, and when the page refreshes click on Backup Settings to arrive at the Backup Settings Device page as shown in Figure 9.
Figure 9 Backup Settings Device Configuration Parallelism Defines the number of simultaneous streams that are allocated to write data to the backup location. It is recommended to set an initial value of 5 for this option. Disk Backup Location Specify the Whitewater CIFS or NFS target that the backup will be written to. This overrides the fast recovery area disk target for backups. It is not recommended to configure a Whitewater CIFS or NFS share as the fast recovery area disk target. Disk Backup Type Specify Backup Set or Image Copy as the backup type. Refer to documentation for an explanation of backup types. Test Disk Backup Use this button to test the backup configuration with the selected disk backup target.
© 2012 Riverbed Technology. All rights reserved.
17
RIVERBED WHITEWATER QUICK START GUIDE
2. Click on the Policy tab and as shown in Figure 10 configure the backup disk target location for the control file and SPFILE backups. Also specify the retention settings for the database backups and archive redo logs.
Figure 10 Backup Settings Policy Configuration Automatically Backup The Control File Specify the same Whitewater CIFS or NFS target location as with the database backup in step 1. Retention Policy Specify the retention period desired for backups, based on the number of days or number of versions. Archived redo Log Deletion Policy Specify the retention period desired for holding archived redo logs, based on the number of backups taken.
© 2012 Riverbed Technology. All rights reserved.
18
RIVERBED WHITEWATER QUICK START GUIDE
Testing Oracle with Whitewater Backup to Whitewater Using Oracle RMAN To test Oracle RMAN with the Whitewater gateway you can run a manual backup of the database using the configuration settings previously modified. 1. From the Oracle Enterprise Manager main page, click on the Availability tab, and when the page refreshes click on Schedule Backup to arrive at the Schedule Backup entry page as shown in Figure 11. Click on the backup type and click Schedule Customized Backup.
Figure 11 Initiating a Customized Backup
© 2012 Riverbed Technology. All rights reserved.
19
RIVERBED WHITEWATER QUICK START GUIDE
2. When the backup options page appears as shown in Figure 12, select the type of backup, backup mode, and whether to backup archived redo logs. In this step also set the Maximum Files per Backup Set and disable encryption for the backup, since encryption will be provided by Whitewater.
Figure 12 Storage Policy Selection Maximum Files per Backup Set Set this option to control how many backup pieces (files) can be collected together per backup set object written by Oracle RMAN. Provide a value of 1, or leave it blank to accept the default of 1.
© 2012 Riverbed Technology. All rights reserved.
20
RIVERBED WHITEWATER QUICK START GUIDE
3. Select the disk backup target location for this database backup job, which should specify the CIFS share or NFS export backup target location configured within Whitewater previously (Figure 13). In this example, NFS export /mnt is specified.
Figure 13 Backup Target Destination 4. Finally in the Schedule settings (Figure 14) specify the backup job name and description, and identify the frequency of the operation.
Figure 14 Schedule Settings 5. Enterprise Manager also provides the equivalent RMAN script generated by the backup scheduling wizard. In this example the equivalent RMAN commands would be: backup device type disk tag '%TAG' database; backup device type disk tag '%TAG' archivelog all not backed up;
© 2012 Riverbed Technology. All rights reserved.
21
RIVERBED WHITEWATER QUICK START GUIDE
Monitoring a Job Backup Jobs within Oracle can be monitored and reviewed after operation completion by going to the Availability tab, and selecting Jobs from the Related Links section (Figure 15). The resulting job activity will be shown as seen in Figure 16.
Figure 15 Job Activity Monitor
Figure 16 Backup Job Activity
© 2012 Riverbed Technology. All rights reserved.
22
RIVERBED WHITEWATER QUICK START GUIDE
Restore to Oracle Using Whitewater Oracle Enterprise Manager can be used to perform database restores from backups taken above. Unlike Enterprise Manager for backups, recovery equivalent commands for RMAN are not provided as a part of the GUI interface, and recovery options are basic. RMAN commands instead must be manually written. Please refer to the Oracle RMAN commands for further information about recovery commands and options that are not available with Enterprise Manager recovery. 1. From the Oracle Enterprise Manager main page, click on the Availability tab, and when the page refreshes click on Perform Recovery (Figure 17).
Figure 17 Perform Recovery Selection 2. When the Recovery page appears as shown in Figure 18 select the Recovery Scope and click Recover to begin the database restore operation.
Figure 18 Restore Selection
© 2012 Riverbed Technology. All rights reserved.
23
RIVERBED WHITEWATER QUICK START GUIDE
Appendix A. Whitewater Gateway Best Practices for Oracle RMAN Oracle Recovery Manger (RMAN) is the backup utility provided with Oracle database server which provides online and offline backup capabilities for Oracle databases. It can be run via the command line, or can be executed by the Enterprise Manager, which provides a graphical front end interface for backup and restore operations. When configuring Oracle backups via Enterprise Manager configure the target disk and allocated channels appropriately.
Figure 19 Oracle Backup Settings Parallelism Defines the number of allocated channels to stream data to the backup location. It is recommended to set an initial value of 5 for this option. Disk Backup Location Specify the Whitewater CIFS or NFS target that the backup will be written to. This overrides the fast recovery area disk target for backups. It is not recommended to configure a Whitewater CIFS or NFS share as the fast recovery area disk target. Disk Backup Type Specify Backup Set or Image Copy as the backup type. Test Disk Backup Use this button to test the backup configuration with the selected disk backup target. On Unix based Oracle database systems, it is recommended to use Oracle Direct NFS in order to improve performance between Oracle and Whitewater. This NFS client is built directly into the Oracle database kernel, and is recommended when using NAS based disk targets. Further information about Oracle Direct NFS can be reviewed here: http://www.orafaq.com/wiki/Direct_NFS If Oracle Direct NFS client is being used, the Whitewater NFS share must be configured with the insecure option to allow connections from Oracle Direct NFS. This step is not required if using the default NFS client with Linux or Unix. The insecure option is only available via the Whitewater command line interface, and cannot be set via the Whitewater GUI. Configure the NFS share via the Whitewater GUI, then login to the command line interface and issue the following commands: en conf t nfs export modify name insecure It is not recommended to configure a Whitewater CIFS or NFS share as the Fast Recovery Area destination target. As the Fast Recovery Area is intended for localized recovery of Oracle database data (such as online redo logs), Oracle suggests having this on locally attached disk and not utilizing a network share.
© 2012 Riverbed Technology. All rights reserved.
24
RIVERBED WHITEWATER QUICK START GUIDE
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= nfs:nfs3_bsize= 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
© 2012 Riverbed Technology. All rights reserved.
25
RIVERBED WHITEWATER QUICK START GUIDE
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 www.riverbed.com.
Riverbed Technology, Inc. 199 Fremont Street San Francisco, CA 94105 Tel: (415) 247-8800 www.riverbed.com
© 2012 Riverbed Technology. All rights reserved.
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
26
