NetApp SteelStore Solution Guide for Tivoli Storage Manager

October 2014

© 2014 NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent of NetApp, Inc. Specifications are subject to change without

notice. NetApp, the NetApp logo, Go Further, Faster, ASUP, AutoSupport, Campaign Express, Cloud ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone,

FlexPod, FlexScale, FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID-DP, SANtricity, SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator,

SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, WAFL and Whitewater are trademarks or registered trademarks of NetApp, Inc. and its affiliated entities in the United States and/or other countries. SteelStore [and Riverbed] are trademarks of Riverbed Technology used

pursuant to license. Any other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. A current list of certain of NetApp trademarks is available on the Web at http://www.netapp.com/us/legal/netapptmlist.aspx.

TABLE OF CONTENTS

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

TSM Architecture Overview................................................................................................................................................................................................................. 3

SteelStore Appliance Overview .......................................................................................................................................................................................................... 4

Deploying SteelStore Appliances with TSM..................................................................................................................................................................................... 5

TSM, SteelStore Appliance, and Cloud Storage Configuration Example .................................................................................................................................. 5

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

Cloud Storage Provider Required Tasks .......................................................................................................................................................................................... 6 Amazon S3 and Glacier ................................................................................................................................................................................................................ 6

AT&T Synaptic Storage as a Service........................................................................................................................................................................................ 6 Google Cloud ................................................................................................................................................................................................................................... 6 HP Cloud Services.......................................................................................................................................................................................................................... 6 Microsoft Windows Azure ............................................................................................................................................................................................................ 7

Rackspace Cloud Files ................................................................................................................................................................................................................. 7 OpenStack Object Storage (Swift)............................................................................................................................................................................................. 7

Configuring the SteelStore Appliance ............................................................................................................................................................................................... 8 Configuring the SteelStore Management Interface.............................................................................................................................................................. 8

Connecting to the SteelStore Management Console GUI.................................................................................................................................................. 9 Configuring SteelStore Appliance Licenses ........................................................................................................................................................................ 10 Configuring SteelStore Data Interfaces ................................................................................................................................................................................. 10 Configuring Cloud Settings....................................................................................................................................................................................................... 11

Configuring a CIFS Share .......................................................................................................................................................................................................... 13 Configuring NFS ........................................................................................................................................................................................................................... 16

Configuring TSM .................................................................................................................................................................................................................................. 17 TSM Management Console Overview .................................................................................................................................................................................... 17

Adding a SteelStore Appliance to TSM Tasks..................................................................................................................................................................... 17 Create a FILE Device Class ....................................................................................................................................................................................................... 18 Create a Primary or Copy Storage Pool ................................................................................................................................................................................ 20

Associate Backups to the New Primary Storage Pool...................................................................................................................................................... 22

Testing TSM with the SteelStore Appliance................................................................................................................................................................................... 26 Method 1: SteelStore Appliance Used as a Primary Storage Pool ............................................................................................................................... 26 Method 2: SteelStore Appliance Used as the Next Primary Storage Pool in the Storage Pool Hierarchy ....................................................... 29

Method 3: SteelStore appliance Used as a Copy Storage Pool ..................................................................................................................................... 30

Appendix A. SteelStore Best Practices for TSM ........................................................................................................................................................................... 32

Appendix B. SteelStore Best Practices for Solaris Operating Systems ................................................................................................................................... 34

Appendix C. SteelStore Best Practices for Windows 2008 Operating Systems ..................................................................................................................... 34

Appendix D. Disaster Recovery (DR) Procedures ........................................................................................................................................................................ 35 Pre-Disaster Recovery Checklist ............................................................................................................................................................................................. 35

SteelStore Appliance Recovery ............................................................................................................................................................................................... 36

TSM Server Recovery .................................................................................................................................................................................................................. 40 Production Systems Recovery................................................................................................................................................................................................. 41

Executive Summary This paper outlines the ease of use and deployment of a NetApp SteelStore cloud storage appliance (SteelStore Appliance) with IBM Tivoli Storage Manager (TSM). SteelStore appliances provides a simple, efficient way to offsite data to cloud storage providers powered by Amazon® S3 and Glacier, AT&T® Synaptic Storage as a Service, HP® Cloud Services, Google® Cloud, Microsoft® Windows® Azure cloud storage, Rackspace® Cloud Files, and general instances of EMC® Atmos and OpenStack™ (Swift) Object Storage. SteelStore appliances simply act as a storage target within a backup infrastructure managed by TSM, 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 SteelStore appliance 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 NetApp’s industry leading deduplication, compression and WAN optimization technologies, SteelStore appliances 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.

SteelStore appliance 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 SteelStore appliance is an asymmetric, stateless appliance, no hardware is needed in the cloud and you can recover the last known good state of a broken or destroyed SteelStore appliance to a new SteelStore appliance. SteelStore appliances 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%.

TSM Architecture Overview TSM software provides a wide range of storage management capabilities from a single point of control, helping companies ride

the information tidal wave. With its client/server design, TSM helps simplify the protection and management of your 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 TSM all aspects of operations from backups to server management are conducted via the TSM Administration Console. Administrators can run the Administration Console from any server in the network. See Diagram 1 for an image of a typical TSM deployment.

Diagram 1 Typical TSM Network View

SteelStore Appliance Overview

Figure 1 SteelStore Appliance SteelStore appliances are optimized and purpose built for data protection. SteelStore appliances easily integrate into your existing backup infrastructure and favorite cloud storage provider. Set up and installation are easy because backup applications allow you to add a SteelStore appliance as a common target within its existing infrastructure. The backup server connects to the SteelStore appliance using standard CIFS or NFS protocols. When you backup to a SteelStore device, it performs inline, variable segment length deduplication of the backup data to minimize storage consumption and transmission times. SteelStore appliances also use their local disk cache for fast recovery of recent backups, providing LAN performance for the most likely restores. The SteelStore appliance then writes the deduplicated backup data to cloud storage, and also accelerates restores from the cloud by moving only

needed segments of deduplicated data over the WAN. An easy to use graphical management console enables you to manage one or more SteelStore appliances through a web browser interface.

Deploying SteelStore Appliances with TSM TSM with SteelStore appliances provides you with a flexible, easy-to-configure and use solution that can be deployed with major cloud storage providers. The sections below provide example configurations and setup steps needed to begin using SteelStore appliances. For further information about performance tuning backup applications with SteelStore appliances, refer to the SteelStore Best Practices Guide for Backup Applications.

Backup Application, SteelStore Appliance, and Cloud Storage Configuration Topology

Diagram 2 Logical Architecture View

Pre-deployment Checklist 1. Users will need a least one server that combines the function of a TSM server and Administration Console into a single computer system. The operating system must be one that TSM supports. Memory requirements will vary, but at minimum a TSM server should have 8GB of RAM or higher. Please check IBM’s support site and related compatibility lists where applicable.

http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager_Extended_Edition 2. Obtain server systems and related software media supported by the operating system selected, TSM and SteelStore appliance. 3. A physical SteelStore appliance or SteelStore cloud storage appliance Virtual Edition (Virtual SteelStore) 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 NetApp, 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.

Cloud Storage Provider Required Tasks

Amazon S3 and Glacier

To sign up for Amazon S3 and Glacier: 1. Go to http://aws.amazon.com/ and click the link Sign Up. 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. Login and get authentication information by selecting your account name from the top menu, and selecting the link Security

Credentials. 5. 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.

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 the link Order Now: https://www.synaptic.att.com/clouduser/html/productdetail/Storage_as_a_Service.htm 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.

Google Cloud

To sign up for Google Cloud: 1. Go to https://cloud.google.com/ and click the link Try It Now. 2. Follow the on-screen instructions.

3. Perform account confirmation via phone or text message and login. 4. Create a new Project using the Create Project link. Provide a Project Name and Project ID. 5. Select Cloud Storage, and click the Enable button to activate cloud storage services. 6. Under API Access generate a client ID using the Create a Client ID link. 7. Record the following information from the created project to enter into the SteelStore GUI:

Project ID – Provide the numeric value of the project created in Google Cloud.

Client ID – Provide the cloud storage client ID for the user that is associated with the project ID above.

Private Key – Provide the private key associated with the above client ID.

HP Cloud Services

To sign up for HP Cloud Services: 1. Go to https://console.hpcloud.com/signup 2. Follow the on-screen instructions.

3. HP Cloud Services will notify you by e-mail when your account is active and available for you to use. 4. Login to HP Cloud Services and activate an availability zone. 5. Create an object container. From the HP Cloud Services console select the ‘Browse Containers’ button from the Management Console and on the next screen, enter a ‘New Container Name’ in the field provided and select the ‘Create’ button. 6. Make sure that you record the following information:

Tenant ID – Specify the endpoint account to use with HP Cloud Services

Access Key - Specify the access key for your HP Cloud Services account.

Secret Key - Specify the secret key for your HP Cloud Services account.

Container Name – Specify the target storage folder name for backup objects

Microsoft Windows Azure

To sign up for Microsoft Windows Azure: 1. Go to http://www.microsoft.com/windowsazure/free-trial/ and click the link Free Trial. 2. Follow the on-screen instructions. 3. Perform account confirmation via phone or text message.

4. Login to the Azure portal https://windows.azure.com/Default.aspx and create a new Storage Account under Hosted Services, Storage Accounts & CDN. 5. Record the following information from the created storage account to enter into the SteelStore GUI:

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

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

Rackspace Cloud Files

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

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

Username – Provide the user name associated with the account.

OpenStack Object Storage (Swift)

Please refer to OpenStack documentation (http://docs.openstack.org/) for information about deploying an OpenStack Object Storage cluster for use with SteelStore appliances. You should have the following information ready to enter into the SteelStore 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.

Configuring the SteelStore Appliance The following procedures are basic configurations. The SteelStore Installation Guide and SteelStore User’s Guide provide full details for requirements and installation of the SteelStore appliance. The configuration is broken down into the following activities:

Configuring the SteelStore Management Interface

Connecting to the SteelStore Management Console

Configuring SteelStore appliance Licenses

Configuring SteelStore Data Interfaces

Configuring Cloud Settings

Configuring a CIFS Share

Configuring the SteelStore Management Interface

After you install and start the SteelStore appliance, connect to the SteelStore CLI to configure the management interface: 1. If you are using a Virtual SteelStore, connect directly to the console session using the VMware vSphere client and skip to step 3. If you are using a physical SteelStore appliance, 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 SteelStore with a terminal server, the terminal server must use hardware flow control for the port connected to SteelStore.

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 SteelStore. 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 SteelStore. NetApp 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 SteelStore. 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 SteelStore. 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 SteelStore 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? NetApp strongly recommends that you change the default administrator password (password) at this time. The new password must be a minimum of 6 characters.

Step 8: Admin password? xxxyyy

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

Connecting to the SteelStore Management Console GUI

After you configure SteelStore, you can verify and modify your configuration settings and view performance reports and system logs in the SteelStore Management Console. You can connect to the SteelStore Management Console through any supported Web browser. To connect to the SteelStore 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 SteelStore Management Console: 1. Enter the URL for the SteelStore Management Console in the location box of your web browser: protocol://host.domain – protocol is either 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 SteelStore appliance 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 the SteelStore appliance. Note: You can specify the IP address instead of the host and domain. 2. The SteelStore Management Console appears, displaying the login page as shown in Figure 2.

Figure 2 NetApp SteelStore 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 SteelStore. Users with monitor (monitor) privileges can view connected SteelStores, reports, and system logs. -In the Password text box, type the password that you assigned in the configuration wizard. By default the password is password. -Click Log In to display the Home page. The Home page summarizes the current status of your system.

Configuring SteelStore Appliance Licenses

You can add or remove a license in the Configure > Maintenance > Licenses page. You install a license on a SteelStore appliance after receiving it from 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 SteelStore Appliance 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 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 SteelStore 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 SteelStore Data Interface Page

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

Control Description

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

IP Configuration Displays the IP address of the network interface.

Enable Data Interface

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

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

Control Description

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

Destination Specify the destination IP address for the gateway.

Subnet Mask Specify the subnet mask.

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

Add Adds the route to the table list.

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

Configuring Cloud Settings

You can specify cloud settings, replication scheduling, and bandwidth limit settings in the Configure > Storage > Cloud Settings page. Replication is the process that transfers deduplicated data from SteelStore 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 recover y processes by generating duplicate copies of all backed-up files on a continuous basis. It can also simplify recovery from all types of disasters including fire, flood, hurricane, virus, or worm. Note: Before you configure cloud settings, configure DNS settings to access the cloud service provider host machine. To configure cloud settings:

1. Choose Configure > Storage > Cloud Settings to display the Cloud Settings page, as shown in Figure 5.

Figure 5 Cloud Settings Page

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

Control Description

Protocol Type

Select the cloud service provider from the drop-down menu. If you select Amazon S3, you must also specify the following: • Region - Select an Amazon region from the drop-down list. You can choose a Region to optimize for latency, minimize costs, or address regulatory requirements. You can select one of the following regions: – Asia Pacific (Singapore) – Asia Pacific (Sydney) – Asia Pacific (Tokyo) – EU (Ireland) – South America – US Standard – US-West (N. California) – US-West (Oregon) • 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, specify the following: • Storage Policy - Select one of the following storage policies from the drop down list: • Local Replication - Stores data stored in one location and protects it using erasure coding (which is a software-based data protection scheme that allows for data recovery in the event of hardware failures). • Remote Replication - Stores data in two locations—maintains a copy in one data center and replicates it to a geographically remote data center. • 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 thatAT&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 EMC Atmos, 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 Glacier Service, you must also specify the following: • Region - Select an Amazon Glacier region from the drop-down list. You can choose to store your data in the Amazon Glacier Region that meets your regulatory, throughput, and geographic redundancy criteria. You can select one of the following regions: – Asia Pacific (Tokyo) – EU (Ireland) – US Standard – US-West (N. California) – US-West (Oregon) • Access Key - Specify the access key (similar to the user name) for your Glacier account. • Secret Key - Specify the secret key (password) for your cloud service provider account. • Dedupe against cloud - Select this checkbox to specify that the SteelStore appliance must check the incoming data for deduplication against the entire data set, both in the Glacier cloud and in the local disk cache. This is the same procedure that the SteelStore appliance uses for other (non-Glacier) cloud providers. The pros of this approach are that the deduplication factor (ratio of expanded data and deduplicated data) is high. If the incoming data is not found on the SteelStore appliance cache and is found only in the Glacier cloud, then the SteelStore appliance must first restore the data from Glacier in order to perform deduplication on the incoming data stream. This impacts costs and performance. \ Note: If you enable the Dedupe against Cloud option, inline deduplication is performed for data written to the SteelStore appliance without data being restored from Glacier. However, when you verify the backup, it requires data to be restored from Glacier and can result in very slow verification and possible time-outs. This option is not selected by default. Leave this checkbox unchecked to specify that the SteelStore appliance must check the incoming data for deduplication only against the local disk cache of the SteelStore appliance. It does not match the incoming data with the data in the Glacier cloud. The pros of this approach are that it minimizes impacts to cost and performance of reading data to find duplicate matches, since the SteelStore appliance only references the local SteelStore appliance disk cache. The cons of this approach are that the deduplication factor is low because the SteelStore appliance does not consider the entire data set. If you select Google Cloud Storage, specify the following: • Location - Select your location from the drop-down list. The choices are: – EU: Specifies Europe as the location. – US: Specifies the United States of America as the location. • Project ID - Specify the project ID associated with the bucket. The project ID tells Google Cloud Storage which project you want to create a bucket in or which project to list buckets for. Each project is identified by its unique project ID. Since it is possible to have multiple projects, this ensures that the request is properly completed in the right project. • Client ID - Specify the client ID used to access the bucket. • Private Key - Specify the private key (password) for your cloud service provider account. If you select HP Cloud Object Storage, specify the following: • Region - Select one of the following regions from the drop-down list: – US West – US East • Authentication - Specify one of the following methods that the cloud provider uses to authenticate each request. – Access Key ID/Secret Key: Select this option and specify the access key ID and secret key to authenticate your account. – Username/Password: Select this option and specify the user name and password to authenticate your account. • Tenant ID - Specify the tenant ID for your HP Cloud Object Storage account.

If you select Microsoft Windows Azure Storage, specify the following: • Storage Account - Specify the Windows Azure storage account name. • Primary or Secondary Access Key - Specify the primary or secondary Windows Azure storage access key that you generated when you created your Windows Azure storage account. The secondary key provides the same access as the primary key and is used for backup purposes. You can regenerate each key in case either one is compromised. If you select OpenStack Object Storage (Swift), specify the following: • Authentication - Specify one of the following methods that OpenStack Object Storage (Swift) uses to authenticate each request. – Access Key ID/Secret Key – Username/Password – Username/API access key • API Access Key - Specify the API access key for your OpenStack Object Storage (Swift) account. • Tenant ID - Specify the tenant ID that OpenStack Object Storage (Swift) uses to authenticate each request. • Authentication URL - Specify the cloud server API URL for OpenStack Object Storage (Swift) to authenticate the request. • Web Protocol - Specify whether to use the HTTP or HTTPS protocol. HTTPS is the secure version of the HTTP protocol, where packets are encrypted before they are transmitted. It uses the SSL protocol to ensure a secure environment. If you select Rackspace Cloud Files, specify the following: • Region - Select the region from the drop-down list. The choices are US Based or UK Based. • Username - Specify the user name that Rackspace uses to authenticate each request. • API Access Key - Specify the API access key for your Rackspace account.

Hostname Specify the hostname of the cloud provider on which SteelStore 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, EMC Atmos, Microsoft Windows Azure Storage, and OpenStack Object Storage (Swift) use port 443. HP uses port 35357. The default value is 443, which works for all of the other 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 the SteelStore appliance. If the bucket name does not exist, the bucket is created during initial SteelStore appliance replication. For Azure, the bucket name must be a valid DNS name, conforming to the following naming rules: • Bucket names must start with a letter or number, and can contain only letters, numbers, and the - (dash) character. • Every - (dash) character must be immediately preceded and followed by a letter or number; consecutive dashes are not permitted. • All letters in a bucket name must be lowercase. • Bucket names must be from 3 through 63 characters long. For Amazon (in the US Standard region only) and AT&T Synaptic Storage, the bucket name must conform to the following rules: • Bucket names can only contain numbers, and the following characters: .(period), - (dash), and _ (underscore). • Bucket names must start with a number or letter. • Bucket names must be from 3 through 255 characters long. For Amazon, if the region is not US Standard, the bucket names cannot contain _ (undersores) and they must be 3 through 63 characters long. For all other cloud providers, you can use bucket names that are alphanumeric and contain the following characters: . (period), - (dash), _ (underscore), and ~ (tilde).

Configuring a CIFS Share

You can configure Common Internet File System (CIFS) access to the SteelStore appliance 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 Interne t.

To configure CIFS: 1. Choose Configure > Storage > CIFS to display the CIFS page, as shown in Figure 6.

Figure 6 Adding a CIFS Share

2. If your network has an Active Directory (AD) domain, you can add the SteelStore appliance to the domain and enable domain users to access SteelStore appliance CIFS shares. You can add the SteelStore appliance to only one domain. You cannot add it to multiple domains. Ensure that you have permissions to join appliances to the domain and add users who can access the domain. To join the SteelStore appliance to an AD domain, complete the configuration as described in the following table.

Control Description

Join Domain Displays the controls to add the SteelStore appliance to your AD domain.

Domain Name Specify the fully qualified domain name of the AD that the SteelStore appliance must join. If your system has an AD domain, then you can add the SteelStore appliance 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 the AD and the user must have permissions to add computers to the domain.

Password Specify the domain password to authenticate the user.

Click Advanced Settings to display Advanced Settings to (optionally) configure the domain. Complete the configuration as displayed in the following table.

Control Description

Organizational Unit SteelStore appliance must join. Organizational units are Active Directory containers into which you can place users, groups, computers, and other organizational units. An organizational unit cannot contain objects from other domains. For an overview of organizational units, go to: http://technet.microsoft.com/library/cc758565.aspx

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

Host DNS Domain Optionally, specify the host DNS name that is used to join the SteelStore appliance to the domain. The default domain name is the AD domain name.

3. After you join an AD domain, you can add you can add domain users and groups who can access the SteelStore appliance CIFS shares. 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 SteelStore system to access the CIFS share.

Remove Selected Deletes the selected CIFS share.

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

4. When you add a CIFS share to the SteelStore appliance, 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 enable authentication, ensure that you delete the user “Everyone” from the access control list of the share. 5. If you did not join the SteelStore appliance to an AD domain, you must add a CIFS user. 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 SteelStore CIFS server.

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

Password Specify the password to authenticate the user.

Account Select one of the following options from the drop-down list: Enabled - Enables the CIFS user to access the SteelStore appliance CIFS share. Disabled - Disables the CIFS user from accessing the SteelStore appliance CIFS share.

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 SteelStore CIFS server.

6. Under Global CIFS Settings, specify the values for Server Message Block (SMB) 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 SteelStore performance.

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 (Figure 7).

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.

Export Asynchronously

Select the check box to export the NFS share asynchronously. Click the icon i for the following information: Exporting NFS asynchronously forces the server to drop all "fsync" requests from the client. This is a feature of NFS protocol. It is required to obtain good performance with NFS clients that issue frequent NFS COMMIT operations, which might degrade the SteelStore appliance performance significantly. Many Unix clients often execute NFS COMMIT operations when low on memory. To understand the circumstances that cause this behavior and to detect and prevent it, contact your client operating system vendor. The SteelStore appliance automatically synchronizes any file that is idle for a configurable amount of time (default 10s). Although there is a window of time (after the server responds with success for a "fsync" request, and before the data is written to disk), this window is small and performance benefits are large. NetApp recommends exporting NFS asynchronously.

Allow All Clients or Allow Specified Clients

Enables all clients connected to the SteelStore system to access the NFS share. Or Enables only the clients that you specify to connect to the SteelStore appliance 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 SteelStore appliance 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.

Configuring TSM The following sections describe how to configure and use TSM with the SteelStore appliance - please refer to the IBM TSM

Administrator’s Guide for complete details:

TSM Administration Console Overview

Adding the SteelStore Appliance to TSM Tasks o Create a FILE device class o Create a primary or copy storage pool o Associate backups to the new primary storage pool

Method 1: Associate a policy domain to the new primary storage pool Method 2: Assign the new storage pool as the next storage pool in the hierarchy

Testing TSM with the SteelStore Appliance o Method 1: SteelStore appliance used as a primary storage pool o Method 2: SteelStore appliance used as the next primary storage pool in the storage pool hierarchy o Method 3: SteelStore appliance used as a copy storage pool

TSM Management Console Overview

The TSM Administration Console is the interface that is used to configure all settings in a TSM server environment. In order for the Administration Console to make changes the administration console must point to the desired TSM server. By default the Administration Console will locate the TSM server on the local system if present. The Administration Console can also be pointed at other TSM servers in environment to monitor activities and statistics for those particular TSM servers. To point the Administration Console to additional TSM servers, use the Manage Servers panel (Figure 8).

Figure 8 TSM Administration Console

Adding a SteelStore Appliance to TSM Tasks

When adding a SteelStore appliance to a TSM environment there are three primary tasks that are required. The first is to create a FILE device class, which is associated with a CIFS share created on the SteelStore appliance. The second is to create a storage pool using that FILE device class so data volumes can be written to SteelStore based storage. Lastly, the policy domain must be modified so client backups are directed to use the new storage pool target.

Create a FILE device class (required)

Create a primary or copy storage pool (required)

Associate a policy domain to the new storage pool (required)

Create a FILE Device Class

A FILE device class is a device descriptor which specifies the device type and media management information, such as the recording format, estimated capacity, and labeling prefixes. TSM associates device classes with physical storage. The following describes the steps to create a FILE device class and associate it to the SteelStore appliance. These steps use the best practice configuration for TSM with the SteelStore appliance.

1. Use the Storage Devices panel and select the radio button for the TSM server you wish to work with. Then click on the Select Action drop down menu and select View Device Classes (Figure 9).

Figure 9 View Device Classes Drop Down 2. When the Device Classes panel appears, click the Select Action drop down menu and select Create A Device Class (Figure 10).

Figure 10 Create a Device Class Drop Down

3. When the Create a Device Class wizard starts, click the Select a Device Type drop down menu and click on FILE (uses sequential-access volumes on disk) (Figure 11). Click on Next to continue.

Figure 11 Selecting a Device Type Drop Down 4. Provide a new device class name, SteelStore CIFS share path name, and set the mount limit and maximum size values

(Figure 12). Click on Next to continue.

Figure 12 Create a Device Class Configuration Screen Name

Provide a new device class name. It cannot match an existing device class name. Path to Store Files

Enter a fully qualified domain name CIFS share path value which corresponds to the SteelStore CIFS share. Mount Limit

Recommend setting an initial value of 5 or less. This option controls the number of volumes that can be mounted

simultaneously on a TSM server. Maximum File Size

Recommend setting a value of 20GB or less. This option controls the maximum device file object size that can be created on SteelStore by TSM.

Create a Primary or Copy Storage Pool

A TSM storage pool is a collection of volumes that are associated with one device class and one media type. Storage pools can have volumes that are predefined or volumes that are created from a scratch pool of volumes. Scratch volumes are created by TSM. Backup data is written by a TSM client to a storage pool target.

1. Use the Storage Devices panel and select the radio button for the TSM server you wish to work with. Then click on the Select Action drop down menu and select View Storage Pools (Figure 13).

Figure 13 View Storage Pools Drop Down

2. When the Stoage Pools panel appears, click the Select Action drop down menu and select Create A Storage Pool (Figure 14).

Figure 14 Create a Storage Pool Drop Down

3. When the Create a Stoage Pool wizard starts, provide a new Storage Pool Name, select the Sequential Access radio button, and select whether the storage pool will be use in a primary or copy capacity (Figure 15). Click on Next to continue.

Figure 15 Storage Pool Name and Type Entry

Storage Pool Name

Provide a new storage pool name. It cannot match an existing storage pool name. Storage Pool Type

Select sequential access since SteelStore uses a FILE device class.

Primary or Copy Storage Pool

Identifies whether the storage pool will be used for primary backups of data from TSM clients, or used for receiving copies of backup data stored in primary storage pools via the BACKUP STGPOOL command.

4. Click on the Device Class Name drop down and select the device class name created previously in Step 1. Also enter a value for the Maximum number of scratch volumes (Figure 16). Click Next to continue.

Figure 16 Device Class Name Selection and Maximum Volume Entry

Device Class Name

Provide the device class name created in Step1 above. Maximum Number of Scratch Volumes

This option controls the maximum number of scratch volumes that TSM will be allowed to create using the target device class media properties. This value can be set to whatever value you need, but should at most represent the total size of the SteelStore licensed cloud capacity when multiplied by the per volume size specified in the Device Class creation step above.

Associate Backups to the New Primary Storage Pool

Once the storage pool is created, TSM must be configured to send data to the storage pool. In method 1, a policy domain can b e updated to send data to that storage pool. In method 2, an existing storage pool can be associated to send data to the SteelStore storage pool as the next pool in the storage hierarchy. NOTE: Perform the following ONLY if you create a primary storage pool in step 2 above. If you create a copy storage

pool, then skip this section. Method 1: Associate a Policy Domain to the new Primary Storage Pool

A policy domain describes how storage and management of backup data within a TSM server is performed. Policies are rules that you set at the TSM server to help you manage the client data lifecycle. Policies control how and when client data is stored, and where that data resides within the TSM storage devices. Note: It is not generally recommended to set the SteelStore appliance as the direct destination for TSM backup policies,

due to the sequentially designed nature of SteelStore appliances and the additional network requirements to perform backups to TSM and data movement to SteelStore simultaneously. 1. Use the Policy Domains panel and select the radio button for the TSM server you wish to work with. Then click on the Select Action drop down menu and select View Policy Domains (Figure 17).

Figure 17 View Policy Domains Drop Down 2. Select the radio button for the policy domain you wish to work with. Then click on the Select Action drop down menu and select Modify Policy Domain (Figure 18).

Figure 18 Modify Policy Domain Drop Down

3. Expand the Management Classes twistie, then click the check box of the management name you wish to edit. Then click on the Select Action drop down menu and select Modify Management Class (Figure 19).

Figure 19 Select the Management Class for Modification

4. In the management class properties panel that appears click on Backup Settings and select the storage pool created previously from the Where to Store Files drop down (Figure 20). Click OK to continue.

Figure 20 Modify the Storage Pool Target for Backups 5. After returning to the Policy Domain panel, you will need to activate the policy change. Click the Select Action drop down and select Manage Pending Changes (Figure 21).

Figure 21 Manage Pending Changes Drop Down

6. At the Manage Pending Changes panel, click the Activate Changes button to initiate the change for all future backups that are associated with this policy (Figure 22). Click OK.

Figure 22 Activate Changes for Policy Domain

Method 2: Assign the New Storage Pool as the Next Storage Pool in the Hierarchy

Storage pools can be setup in a hierarchy, such that data flows from one storage pool to another at regulated schedules or in the event of data overflow. Using a SteelStore appliance in this fashion will reduce the amount of simultaneous traffic on the network as opposed to method 1, since data flow to the SteelStore storage pool will be separate from backup data flow into the TSM server. 1. Use the Storage Devices panel and select the radio button for the TSM server you wish to work with. Then click on the Select Action drop down menu and select View Storage Pools (Figure 23).

Figure 23 View Storage Pools Drop Down

2. Select the radio button for the storage pool that will send data to the SteelStore storage pool, and from the drop down menu select Modify a Storage Pool (Figure 24).

Figure 24 Modify Storage Pool Drop Down

3. When the Storage Pool Properties window appears, select the Next Storage Pool dropdown, select the storage pool created in step 2 above and click Apply (Figure 25).

Figure 25 Next Storage Pool Selection

Testing TSM with the SteelStore Appliance

Method 1: SteelStore Appliance Used as a Primary Storage Pool

Note: This applies only if you configured the SteelStore appliance as a primary storage pool for backups from a policy domain. If you configured the SteelStore appliance as the next primary storage pool in a storage pool hierarchy, go to Method 2 below. If you configured the SteelStore appliance as a copy storage pool, go to Method 3 below. Note: It is not generally recommended to set the SteelStore appliance as the direct destination for TSM backup policies,

due to the sequentially designed nature of the SteelStore appliance, and the additional network requirements to perform backups to TSM and data movement to the SteelStore appliance simultaneously. 1. To use TSM with the SteelStore appliance you can run a manual backup. Start the TSM Backup-Archive GUI, and when the window appears click on Backup. In the Backup window that appears select the local drives or files to backup, and click Backup to begin the operation (Figure 26).

Figure 26 Initiating a Manual Backup

2. Backup activity will be provided in the Task List window, as shown in Figure 27. By clicking the Report button you can view detailed status of the operation, including throughput metrics and object counts (Figure 28).

Figure 27 Task List Status

Figure 28 Backup Detailed Status Report 3. When the backup is complete, perform a restore to validate that the SteelStore appliance can restore the backed up data. From the TSM Backup-Archive GUI, click on Restore. In the Restore window that appears select the local drives or files to

restore, and click Restore to begin the operation (Figure 29).

Figure 29 Initiating a Restore

4. Restore activity will be provided in the Task List window (Figure 30). By clicking the Report button you can view detailed status of the operation, including throughput metrics and object counts (Figure 31).

Figure 30 Task List Status

Figure 31 Restore Detailed Status Report

Method 2: SteelStore Appliance Used as the Next Primary Storage Pool in the Storage Pool Hierarchy

Note: This applies only if you configured the SteelStore appliance as the next primary storage pool in a storage pool hierarchy. If you configured the SteelStore appliance as a copy storage pool, go to Method 3 below. To move data to the SteelStore storage pool, update the migration thresholds for the storage pool that points to the SteelStore

storage pool. This will trigger a migration process which will migrate data from the storage pool to the SteelStore appliance. 1. Use the Storage Devices panel and select the radio button for the TSM server you wish to work with. Then click on the Select Action drop down menu and select View Storage Pools (Figure 32).

Figure 32 View Storage Pools Drop Down 2. Select the storage pool from the list. When the properties page for the storage pool appears (Figure 33), click on the Migration tab. In the right pane, adjust the migration thresholds to lower values such that a migration process is triggered by TSM.

Figure 33 Migration Threshold Adjustment View 3. When migration thresholds are met, migration begins automatically and can be viewed as TSM server processes.

Method 3: SteelStore appliance Used as a Copy Storage Pool

Note: This applies only if you configured the SteelStore appliance as a copy storage pool. If you configured the SteelStore appliance as a primary storage pool, go to Method 1 or Method 2 above. To use TSM with the SteelStore appliance perform a copy storage pool backup. Start the TSM Administration Console, and

expand TSM in the left tree. Click on Storage Devices. In the Storage Devices panel and select the radio button for the TSM server you wish to work with. Then click on the Select Action drop down menu and select View Storage Pools (Figure 34).

Figure 34 View Storage Pools Drop Down

When the Stoage Pools panel appears, click the radio button next to the primray storage pool you wish to backup. Then click o n the Select Action drop down menu and select Back Up Storage Pool (Figure 35).

Figure 35 Backup Storage Pool Action

Select the copy storage pool from the Copy storage pool drop down (Figure 36). Click on OK to begin the backup storage pool process.

Figure 36 Copy Storage Pool Selection

Appendix A. SteelStore Best Practices for TSM TSM uses Device Classes and Storage Pools to store backup data from client systems. TSM Device Classes and Storage Pools can be viewed and modified from the Storage Devices Panel of the TSM Administration Console.

Figure 37 TSM Device Class Properties

TSM uses SteelStore CIFS shares as a FILE device class. Each FILE device class can point to one or more SteelStore

CIFS share(s) via the directory option. It is recommended that each share path be comprised of a unique SteelStore hostname and share name value. Do not use SteelStore CIFS shares as a DISK device class.

Mount Limit should be set to an initial value higher than 5 per SteelStore based FILE device class.

Maximum Volume Capacity should be set to an initial value of 20GB (20480 MB).

Figure 38 TSM Storage Pool Properties

Reclamation Threshold should be set to a value of no lower than 80. Reclaiming volumes which have lower than 80% reclaimable space can cause unnecessary disk read and write activity, as well as unnecessary cloud storage restore activity.

Maximum number of scratch volumes can be set to any value allowed by TSM. If you wish to limit the total amount of data stored to the cloud by TSM, set a maximum scratch volume limit which will accomplish this size requirement. For example, if you wish to only use a maximum of 40TB of space in the cloud and maximum volume capacity is set to 20GB, then the maximum number of scratch volumes value should be set to 40,000GB / 20GB = 2,000.

Number of days before an empty volume is reused should be set to 0 (default). This will immediately allow a volume

to be reused for holding new backup data.

Figure 39 TSM Storage Pool Identify Duplicates

When creating a SteelStore based storage pool, leave the Identify the duplicate data in this storage pool checkbox unchecked, and click Next and Finish to complete the wizard.

TSM Storage Pool Setup

There are 3 ways to setup SteelStore appliances with TSM: 1. Setup the SteelStore appliance as a primary sequential storage pool behind the existing disk storage pool. TSM uses the existing disk storage pool for fast writes for backups, and then migrates the data during the day to the SteelStore appliance. This

method separates the network requirements of backups from the migration operations that move data to the SteelStore appliance. The SteelStore appliance can also serve as an offsite copy backup, but without having to implement a TSM copy storage pool configuration, saving time and resources on the TSM server. 2. Setup the SteelStore appliance as a copy storage pool. Similar to method 1, there will be no contention for network resources between backups and the copy storage pool operations to the SteelStore appliance, but in this setup the SteelStore serves only as the offsite copy. TSM Administrators will still need to configure a local onsite storage pool behind their primary disk p ool.

3. Setup the SteelStore appliance as the primary disk storage pool. This is not recommended for most scenarios as the SteelStore appliance will likely be unable to keep up with the write requirements for many simulatenous backup streams, and the TSM server network resources will be in contention for both inbound backup and outbound SteelStore appliance activity. It is possible to configure the SteelStore appliance to be the primary and copy storage pool target (for example, if combining methods 1 and 2 above), but note that this will require additional network and cloud resources to perform, as wel l as reduce the amount of usable cache space since the SteelStore cache will have to make multiple references for each type of operation.

Appendix B. SteelStore Best Practices for Solaris Operating Systems NFS networking parameters on Solaris operating systems should be configured to optimally send data to SteelStore through 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. SteelStore 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. A reboot is required. [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

Appendix D. Disaster Recovery (DR) Procedures Disaster recovery (DR) is the process of recovering the technology infrastructure after a natural or man-made disaster.

Diagram 3 Disaster Recovery - Functional Architecture View For example, consider a TSM DR scenario with a SteelStore appliance where the entire production site, including the SteelStore appliance and the TSM server, are lost. However, at least one or more backups of that production environment exist in the cloud storage. To recover the data at the DR Site you need a new TSM server and a new physical SteelStore appliance or Virtual SteelStore (Diagram 3).

Note: You do not need a SteelStore license to restore the data. Moreover, the Virtual SteelStore can be downloaded from the support site at https://support.riverbed.com.

Pre-Disaster Recovery Checklist

1. Export the current SteelStore Configuration and Encryption Key. Browse to the menu Configure -> Setup Wizard (Figure 40) and select Export Configuration to export the configuration

file. By default the naming of the file will be SteelStore_config_(HOSTNAME)_(DATETIME).tgz.

Figure 40 Setup Wizard to Export Configuration and Encryption Key

Note: NetApp recommends that you store the exported configuration file in different physical locations. You should also keep the configuration file within the DR Site.

2. If using the SteelStore appliance as a copy storage pool target, prepare the TSM server environment with TSM Disaster Recovery Manager (DRM).

Issue the following TSM server commands to set up DRM to manage SteelStore copy storage pool volumes: o SET DRMCOPYSTGPOOL <SteelStore-copy-storagepool-name> o SET DRMFILEPROCESS YES o QUERY DRMEDIA COPYSTGPOOL=<SteelStore-copy-storagepool-name>

Manage the DRM volumes and place them offsite as you would any typical DRM volumes using the MOVE DRMEDIA

command. 3. Perform the TSM command PREPARE to have a DR plan file created. Refer to the TSM administrative guide and TSM administrative command line reference for further details on using this command.

SteelStore Appliance Recovery

The first step to recover from a catastrophic failure of your production site is to install and configure for disaster recovery a new physical or virtual SteelStore appliance. It is recommended to use a Virtual SteelStore for the initial recovery, which can be downloaded from the support website and quickly deployed within a VMware environment at the DR Site. While not required, the

SteelStore at the DR site is suggested to have the same or greater local storage capacity as the original SteelStore at the lost production site, should you decide to make these resources at the DR site your production resources after the DR is complete. The following describes the steps to fully recover and restore the backup data from the cloud to the new physical or virtual SteelStore appliance. 1. Configure SteelStore to the new network environment at the DR site.

Plug a serial cable into the Console port and a terminal, or in the case of Virtual SteelStore use the virtual VMware

console. Log in to the SteelStore appliance using the default login admin and default password password. Configure the SteelStore network information (Figure 41). For details, see the SteelStore Installation Guide.

Figure 41 SteelStore Configuration Wizard

2. Recover the original configuration of the SteelStore appliance to the new SteelStore appliance at the DR site.

Browse to the menu Configure -> Setup Wizard (Figure 42) and import the previously saved configuration file. Make sure you leave the default Import Shared Data Only checkbox selected.

Figure 42 Setup Wizard to Import Configuration

3. Configure SteelStore Data Interfaces to the new network environment at the DR site. Browse to the menu Configure -> Networking -> Data Interfaces (Figure 43) and configure Data Interfaces network

information.

Figure 43 Data Interfaces Configuration Menu

4. Once the configuration is complete, connect to the SteelStore CLI using SSH and initiate the Replication Recovery procedure. For details, see the Command-Line Interface Reference Manual. Issue the following commands:

SteelStore > enable SteelStore # configure terminal SteelStore (config) # no service enable

SteelStore (config) # replication recovery enable SteelStore (config) # service restart

Note that the replication recovery enable command will fail to execute if the optimization service is enabled, or if the SteelStore appliancedetects existing data in the new SteelStore cache. Assuming this is a new, empty SteelStore appliance, you will not receive any failures and the commands will all be executed without error. This process can take a few seconds to a few hours depending on the backup(s) being restored. During the recovery process, the system communicates with the cloud provider and

recovers all the namespace files that existed before the failure. 5. (Optional) Because the recovery process downloads only the namespace and metadata, initial file access might be slow, because the SteelStore appliance downloads all of the data from the cloud. Therefore, it is recommended that you also populate the actual data from the cloud back onto the new SteelStore appliance in order to accelerate the recovery of your production systems. This can be accomplished by using the SteelStore GUI menu item Reports > Optimization > Prepopulation (Figure 44). Select the folders or files from the list, or provide a list of file objects in the text box and click the Prepopulate Selected Files button. A prepopulation job will be added to the Status tab, indicating progress and completion.

Figure 44 Prepopulation GUI Page To do prepopulation via the CLI, enter the following:

SteelStore (config) # datastore prepop {[num-days <number of days>] | [pattern <pattern>] | [recursive]}

Where the parameters are provided as shown in the following Table 1

Parameter Description

num-days <number of days> Filters the data retrieved by number of last-modified days.

pattern <pattern> Filters the data retrieved by the pattern you specify.

Recursive Enables the data to be prepopulated in subdirectories under a given directory.

Table 1 Datastore Prepop Command Parameters Refer to the SteelStore Users Guide for further details on this command. Note: If the SteelStore appliance storage capacity is less than the space used in the cloud, you can still initiate the recovery process. However, in this case the SteelStore appliance will only recover as much actual data as the size of its storage. If the

recovery process attempts to bring back more data than the disaster recovery SteelStore can handle, then the recovery process might fail. Virtual SteelStore for example can store up to 8 TB of cloud data. For more details on SteelStore appliance sizes, see the SteelStore Installation Guide. At this point the SteelStore recovery procedure is complete, now you need to recover the TSM server.

TSM Server Recovery

After the SteelStore appliance has been recovered you need to install and configure the TSM server. The below procedures assume that you are using TSM Disaster Recovery Manager (DRM), and have taken appropriate TSM server database backups. Refer to the TSM Disaster Recovery redbook available at http://redbooks.ibm.com for further details.

1. Install TSM server to a new host system at the DR site. Make sure that the installation and configuration of the TSM server db, log, and disk volumes is the same as in the previous production site, and that the DRM files are split up in preparation for disaster recovery. Several of the DRM files can help you identify the paths for each of the above items. 2. Edit the DRM file DEVICE.CONFIGURATION.FILE using a text editor and adjust the SteelStore device class name to reflect the new IP addressing of the SteelStore interfaces available at the DR site, as shown in Figure 45.

Figure 45 Device Configuration File 3a. If the SteelStore appliance at the production site was used as a primary storage pool with TSM, edit the DRM file PRIMARY.VOLUMES.DESTROYED.MAC (Figure 46) and remove lines that refer to the SteelStore based volumes. Since the SteelStore appliance at the DR site will have recovered the data from the cloud storage provider, there will be no destroyed

volumes that DRM will have to report to TSM, and they will be available when TSM is brought up.

Figure 46 Primary Volumes Destroyed File

3b. If the SteelStore appliance at the production site was used as a copy storage pool with TSM, edit the DRM file COPYSTGPOOL.VOLUMES.AVAILABLE.MAC and adjust the SteelStore copy storage pool volume directory path to reflect the new IP addressing of the SteelStore interfaces available at the DR site. Since the SteelStore appliance at the DR site will have recovered the data from the cloud provider, there will be no unavailable volumes that DRM will have to report to TSM, and they will be available when TSM is brought up to recover the primary storage pool. 4. Run the DRM executable command file RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE.CMD (Figure 47) to begin the process of restoring the TSM server to the last database backup state.

Figure 47 TSM Server Recovery Script

5. When the restore procedure is complete, start the TSM server. Login to the TSM management console interface, and u se the Storage Devices panel and select the radio button for the TSM server you wish to work with. Then click on the Select Action drop down menu and select View Device Classes (Figure 48).

Figure 48 View Device Classes Drop Down 6. When the device classes list appears, click on the device class name that corresponds to the SteelStore device class. The properties window will appear, and here you will edit the device class directory path to reflect the new network configuration of SteelStore at the DR site (Figure 49). Click OK to apply the changes.

Figure 49 Device Class Properties View

Production Systems Recovery

From this point forward, SteelStore and TSM are now configured as they were prior to the disaster, and you can now begin system restores of any production systems that need to be recovered at the DR site using normal TSM recove ry strategies. Please refer to TSM documentation for recovering additional systems.

NetApp provides no representations or warranties regarding the accuracy, reliability , or serviceability of any information or recommendations provided in this publication, or with respect to any results that may be

obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS, and the use of this information or the implementation of any recommendations or techniques herein is a customer’s responsibility and depends on the customer’s

ability to evaluate and integrate them into the customer’s operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.

© 2014 NetApp, Inc. All rights reserved. No portions of this document may be reproduced w ithout prior w ritten consent of NetApp,

Inc. Specif ications are subject to change w ithout notice. NetApp, the NetApp logo, Go further, faster, xxx, and xxx are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks or

registered trademarks of their respective holders and should be treated as such.

Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact product and feature versions described in this document are supported for your specific environment. The NetApp

IMT defines the product components and versions that can be used to construct configurations that are supported by NetApp. Specific results depend on each customer's installation in accordance with published specifications.