EMC AlphaStor Release 4.0 Planning Guide · EMC AlphaStor Release 4.0 Planning Guide 5 Preface As...

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC® AlphaStor®Release 4.0

Planning GuideP/N 300-012-457

REV A02

EMC AlphaStor Release 4.0 Planning Guide2

Copyright © 2012 EMC Corporation. All rights reserved.

Published February 6, 2011

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

ContentsContents

Preface

Chapter 1 Introduction About the AlphaStor software .............................................................................. 10

Supported software versions .......................................................................... 10AlphaStor licensing .......................................................................................... 10

Terminology............................................................................................................. 11 AlphaStor components .......................................................................................... 11

AlphaStor software component requirements ............................................. 12 AlphaStor services and communication ports ................................................... 12

AlphaStor services or daemons ...................................................................... 12AlphaStor communication ports .................................................................... 12

Chapter 2 Planning and Practices Plan the AlphaStor environment.......................................................................... 14

Operating systems supported by AlphaStor ................................................ 14About the CLI, DCP and LCP......................................................................... 14Network and firewall settings ........................................................................ 15AlphaStor and Sun Cluster ............................................................................. 15

Site plan and preinstallation requirements ......................................................... 15

Chapter 3 NetWorker Integration AlphaStor and NetWorker configurations.......................................................... 20 Combine existing data zones with AlphaStor .................................................... 20 Example preconfiguration worksheet ................................................................. 21 Migrate NetWorker DDS configurations to AlphaStor ..................................... 23 Naming conventions .............................................................................................. 24

Rotation policy naming ................................................................................... 24Library naming ................................................................................................. 24Device naming .................................................................................................. 24

Scripts and custom actions .................................................................................... 25

EMC AlphaStor Release 4.0 Planning Guide 3

Contents


Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to the AlphaStor release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

Note: This document was accurate as of the time of publication. However, as information is added, new versions of this document may be released to the EMC Powerlink website. Check the Powerlink website to ensure that you are using the latest version of this document.

Purpose This document describes AlphaStor release 4.0, and helps to determine if AlphaStor is the appropriate media management solution for your environment. If it is determined that AlphaStor is a fit, this document guides you through planning the optimum configuration for the environment.

Audience This manual is intended for the host system administrator, system programmer, or operator who will be involved in managing the AlphaStor environment.

Relateddocumentation

The following EMC publications provide additional information:

◆ EMC AlphaStor Release 4.0 Administration and Operation Guide

◆ EMC AlphaStor Release 4.0 Installation Guide

◆ EMC AlphaStor Release 4.0 Command Reference Guide

◆ EMC AlphaStor Release 4.0 Release Notes

◆ EMC AlphaStor Release 4.0 Hardware Compatibility Guide

◆ EMC NetWorker Administration Guide

◆ EMC Information Protection Software Compatibility Guide


Preface

Conventions used inthis document

EMC uses the following conventions for special notices:

Note: A note presents information that is important, but not hazard-related.

IMPORTANT

An important notice contains information essential to software or hardware operation.

Typographical conventionsEMC uses the following type style conventions in this document.

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows, dialog boxes, buttons,

fields, and menus)• Names of resources, attributes, pools, Boolean expressions, buttons, DQL

statements, keywords, clauses, environment variables, functions, utilities• URLs, pathnames, filenames, directory names, computer names, filenames, links,

groups, service keys, file systems, notifications

Bold Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs, processes, services,

applications, utilities, kernels, notifications, system calls, man pages

Used in procedures for:• Names of interface elements (such as names of windows, dialog boxes, buttons,

fields, and menus)• What user specifically selects, clicks, presses, or types

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when shown outside of

running text

Courier bold Used for:• Specific user input (such as commands)

Courier italic Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example


http://Powerlink.EMC.com

Preface

Technical support — For technical support, go to Powerlink and choose Support. On the Support page, you will see several options, including one for making a service request. To open a service request, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:

[email protected]

If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject you are addressing.


Preface


1

This chapter includes the following major sections:

◆ About the AlphaStor software .................................................................................... 10◆ Terminology .................................................................................................................... 11◆ AlphaStor components .................................................................................................. 11◆ AlphaStor services and communication ports .......................................................... 12

Introduction

Introduction 9

Introduction

About the AlphaStor softwareThe EMC® AlphaStor® product is a complete suite of software applications designed to automate media lifecycle, library, and storage area network (SAN) management. The AlphaStor software provides the following features:

◆ Library sharing across multiple data zones:

• Enterprise-wide management of tape

• Full volume lifecycle management with volume location tracking and volume pool management

• Full automation and management of media devices and robotic libraries

◆ Replace NetWorker Dynamic drive sharing configurations for optimal use of available devices:

• Coordination of device requests in a SAN, LAN, or server-attached environment

• Support of media device, robotic library, and SAN components

• Assignment and management of available devices (resources) for configured media pools

◆ Data mover support:

• Support for NetWorker software (data mover) products that require removable storage media for archiving

• Monitoring and reporting of media and device usage

A complete description of the new AlphaStor features, and enhancements is available in the EMC AlphaStor Release 4.0 Release Notes.

Supported software versionsAlphaStor version 4.0 software supports the following software versions:

◆ NetWorker 7.4, 7.5, 7.6.x, and later (7.6.x and later is recommended)

◆ Sun Cluster versions 3.1 and 3.2

The EMC Information Protection Software Compatibility Guide provides complete details onversions of software supported by the AlphaStor software.

AlphaStor licensing AlphaStor release 4.0 software does not require any licensing if used with a fully licensed version of the NetWorker software (all editions).


Introduction

TerminologyTable 1 on page 11 provides a list of the terminology used in this guide. A complete list of AlphaStor terminology is available in the glossary in the EMC AlphaStor Administration and Operation Guide.

AlphaStor componentsThe main AlphaStor software components are as follows:

◆ AlphaStor server--The server is the main component of AlphaStor. The AlphaStor server handles the mount and unmount requests, database management, volume tracking, and so on. It also provides the back end for the administration and operation GUIs. Typically, there is just one AlphaStor server in an environment, with multiple data movers configured to communicate with it. The AlphaStor server is usually installed on a dedicated host, or on a NetWorker server host.

◆ CLI--The command line interface (CLI) component provides command line tools for accessing AlphaStor. These are typically installed on the server and on any host where AlphaStor commands are issued, for example, an AlphaStor operator's workstation.

◆ DCP--The Device Control Program (DCP) component is commonly called the Device Manager. The DCP is the AlphaStor agent that interfaces with the devices connected to a host. It is responsible for unloading devices. It is also used in device auto-detection, and configuration verification. A DCP is installed on each NetWorker storage node and on any host that requires access to devices controlled by AlphaStor.

◆ LCP--The Library Control Program (LCP) component is commonly called the Library Manager. The LCP is the AlphaStor agent that interfaces with the libraries connected to a host through the control port. It issues commands to the library and reports the library status to the AlphaStor server. One LCP can control multiple libraries connected to the same host. There is only one LCP host per library.

Table 1 AlphaStor terminology

Term Description

Application Generally refers to a data mover application.

Data mover Generally refers to backup software such as NetWorker.

Device Refers to the mechanism, usually a tape drive that accesses the contents of a volume.

Library Is the general term that refers to a variety of automated media storage units, including autochanger, autoloader, carousel, datawheel, jukebox, or robot.

Location Is the place where a volume resides.

Volume Is a unit of removable storage media, generally a physical or virtual tape cartridge.

Terminology 11

Introduction

AlphaStor software component requirements

Table 2 on page 12 lists the AlphaStor server, CLI, DCP, and LCP component system requirements. The specific operating system documentation provides complete details.

The file system that contains the AlphaStor server data directory (ASHOME) should have at least 2 GB of available space. Disk space requirements may be greater depending on the number of configured devices, hosts, and volumes, and the frequency of AlphaStor database and event log truncations. A minimum 10 GB of additional disk space should be available if debug tracing will be enabled.

AlphaStor services and communication portsThe AlphaStor installation provides the services and communication ports described in the following sections.

AlphaStor services or daemons

Table 3 on page 12 describes the AlphaStor services or daemons.

AlphaStor communication ports

AlphaStor communication ports and firewalls must be considered when planning to implement AlphaStor in the environment. The EMC AlphaStor Release 4.0 Administration and Operation Guide provides complete details on the recommended communication ports for AlphaStor configurations.

Step 6 on page 17 provides details on determining firewall requirements in the AlphaStor environment.

Table 2 AlphaStor component system requirements

AlphaStor component Minimum system requirements Recommended

Server Minimum operating system requirements plus an additional 256 MB of RAM

512 MB of RAM for AlphaStor use

CLI Minimum operating system requirements

DCP Minimum operating system requirements

LCP Minimum operating system requirements

Table 3 AlphaStor services or daemons

Service or daemon Description Location

AlphaStor Agent Service • Starts the data mover interface and the AlphaStor logs• Handles all requests from the Operations Center• Automatically starts and stops the Apache service

AlphaStor server

AlphaStor Device Manager Device resources control program Each storage node

AlphaStor Library Manager Library resources control program One host designated to control a library


2


◆ Plan the AlphaStor environment ................................................................................ 14◆ Site plan and preinstallation requirements ............................................................... 15

Planning andPractices

Planning and Practices 13

Planning and Practices

Plan the AlphaStor environmentBefore planning the AlphaStor environment, confirm that your libraries are supported by the AlphaStor software. Details are available in the EMC AlphaStor Release 4.0 Hardware Compatibility Guide.

As you plan the AlphaStor environment, consider the following:

◆ Supported operating systems and versions

◆ System requirements

◆ Where to install each AlphaStor component

◆ Network and firewall settings

◆ High availability of the AlphaStor server

◆ Users and privileges

◆ Hostnames

◆ Port numbers

◆ Library names

◆ Control path information

◆ Locations and rotation policies

◆ New media pools and volumes

◆ Existing media pools and volumes

◆ Resource queue status and configuration

Operating systems supported by AlphaStorThe first step of planning is to determine the operating systems on which the AlphaStor software will be installed:

◆ The AlphaStor server can be installed on hosts running Linux, Windows, and Solaris

◆ The AlphaStor CLI, LCP, and DCP can be installed on hosts running Linux, Windows, and most UNIX operating systems

AlphaStor can be installed in a heterogeneous environment. A list of supported operating system versions is available in the EMC Information Protection Software Compatibility Guide.

About the CLI, DCP and LCPIt is recommended that the CLI is installed on the following hosts:

◆ AlphaStor server host

◆ Any other host where a user is required to issue direct requests to the AlphaStor server over the network

The LCP supports a subset of the operating systems, listed in “Operating systems supported by AlphaStor” on page 14 if the library is not SCSI-attached, such as ACSLS, IBM 3494, or ADIC/EMASS. If you have a non-SCSI library, ensure that the LCP can support the chosen library on the operating system. The EMC AlphaStor Hardware Compatibility Guide lists the supported operating systems for each library type.



A typical AlphaStor environment with one library requires one server, one or more DCPs, and one LCP:

◆ The server must be installed on a host that has network access to other LCP and DCP hosts

◆ The DCP must be installed on every host that requires access to a device managed by AlphaStor

◆ The LCP must be installed on a host that can control the library to be managed by AlphaStor

Note: If there is more than one library, multiple LCP hosts might be required.

If AlphaStor is being deployed in an existing NetWorker environment, install:

◆ The DCP on every storage node with access to a device

◆ The LCP on a storage node that controls the library

Details on installing the CLI, DCP, and LCP hosts are available in the EMC AlphaStor Release 4.0 Installation Guide.

Network and firewall settings

Ensure that the public TCP/IP ports that AlphaStor uses are not blocked by a firewall. The firewall must allow communication between the AlphaStor server, DCPs, and LCPs, and network traffic from NetWorker, web browsers (for the GUI), and remote CLI clients to the AlphaStor server. Details are provided in the EMC AlphaStor Release 4.0 Administration and Operation Guide.

AlphaStor and Sun Cluster

AlphaStor provides high server availability in a Sun Cluster. An additional AlphaStor component, the Sun Cluster agent, allows the AlphaStor server to be deployed in a Sun Cluster environment. Details are provided in the EMC AlphaStor Release 4.0 Installation Guide.

The LCP on Solaris 8 and 9 and AIX requires a LUS driver to control a SCSI library. When installing the LCP on such a host, ensure that the NetWorker storage node is installed on the host. The NetWorker storage node provides the LUS driver.

Site plan and preinstallation requirementsBefore installing and configuring AlphaStor in your environment, complete the following steps:

1. Create or obtain a diagram that shows all of the main components and hosts (servers, storage nodes, and libraries) involved. This diagram should be supported by a site survey to capture the details that will be needed during the installation and configuration.

2. Create a list of all hostnames in the environment.

Site plan and preinstallation requirements 15


3. Create a list of each media location that you expect to use in the environment, including:

• Multipath rotation locations (rotations with more than one location outside of the library)

• Stand-alone device locations

Note: When libraries are created in AlphaStor, they are automatically assigned the location name of inside<libraryname> for use in AlphaStor attributes and reports where libraryname is the name of the library that is assigned by the administrator.

AlphaStor provides the following default locations:

• ASlost--Used by AlphaStor for volumes that it cannot find in the expected location. This location is not used in rotation policies

• Offline--Used for volumes that are outside of a library but are still within the data center

• Offsite--Used for volumes that are outside of a library and outside the data center

Guidelines for location names in AlphaStor:

• Short descriptive names. For example, StrongHold is a better name than Loc1

• Choose names that will have longevity

• Combine the physical location name with the purpose of the location. For example, LondonOffsite or Area52Archive

• Keep names consistent by using a standard pattern for prefixes and suffixes. Common patterns are <physical_location>+<purpose> such as LondonOffsite, or <purpose>+<physical_location> such as OffsiteLondon

• Use an underscore as a separator. For example, Paris_Offsite

4. Define the volume rotation policies. Name rotation policies based on the length of time the data must remain available. The following are example rotation policy names:

• Offsite60--Associated volumes are in the location Offsite for 60 days

• Archive1yr--Associated volumes are in the location Archive for 1 year

“Rotation policy naming” on page 24 provides details on the recommended rotation policy naming conventions.

The EMC AlphaStor Release 4.0 Administration and Operation Guide provides complete details on efficient and inefficient rotation policies and how to configure them.

5. List the NetWorker servers to be added as data mover applications in this format:

NetWorker@server

where server is the hostname of the NetWorker server.



6. List the firewall requirements. AlphaStor depends on network communication for proper operation. Firewall considerations are as follows:

• A firewall between the AlphaStor server and the LCP must allow connections from AlphaStor to the LCP.

• A firewall between the AlphaStor server and the DCP must allow connections from AlphaStor to the DCP.

• A firewall between the DCP and the LCP must allow connections from the DCP to the LCP (for logging).

• A firewall between data movers and the AlphaStor server must allow connections from data movers to the AlphaStor server.

• A firewall between AlphaStor GUI clients and the AlphaStor server must allow incoming connections from AlphaStor GUI clients.

7. Identify the following for the library configuration wizard:

• Name of the library. “Library naming” on page 24 provides details on recommended library naming conventions.

Note: Library names cannot begin with a number.

• Control path host (the name of the host that has direct access to the library).

• Media type (media types include DLT, LTO and multiple media types).

• Library type (library types include SCSI and ACSLS).

• Library control device file (the library configuration wizard provides options in some cases).

• The barcode ranges that AlphaStor controls, if AlphaStor shares library access with other products.

• How many devices are required and which hosts will have access to which devices.

To simplify configuration in a SAN environment, it is recommended that every host has access to every device. This is accomplished by zoning the SAN fabric so that each host has a path to each tape device.

8. Identify the following for the NetWorker jbconfig program:

• The name of the virtual library (virtual jukebox) to create

• The corresponding AlphaStor library name as described in step 7

• The logical device names to configure for each storage node. If you are not sure how many logical devices to assign to a storage node, use the default of four devices. Logical devices can be added and removed at any time by using the jbedit program

Note: It is recommended to use a naming format similar to storagenodehostname_libraryname_#. This format makes it easy to determine which logical device belongs to which storage node and library.

IMPORTANT

Ensure that the names defined in AlphaStor for the application (typically NetWorker@shorthostname) and the library are entered exactly in jbconfig.

Site plan and preinstallation requirements 17



3


◆ AlphaStor and NetWorker configurations ................................................................ 20◆ Combine existing data zones with AlphaStor .......................................................... 20◆ Migrate NetWorker DDS configurations to AlphaStor ........................................... 23◆ Naming conventions..................................................................................................... 24◆ Scripts and custom actions........................................................................................... 25

NetWorkerIntegration

NetWorker Integration 19

NetWorker Integration

AlphaStor and NetWorker configurationsThe addition of AlphaStor to a NetWorker configuration provides the following types of advantages:

◆ Where NetWorker volumes are regularly imported or exported, AlphaStor rotation policies make these tasks easier.

◆ Where several NetWorker data zones operate independently, AlphaStor makes more efficient use of the libraries and their associated devices.

◆ Where NetWorker and dynamic drive sharing (DDS) is implemented, AlphaStor makes more efficient use of the library and its devices.

Note: The NetWorker software can use a mix of devices that are either controlled or not controlled by AlphaStor.

Combine existing data zones with AlphaStorThe AlphaStor software simplifies configuration and improves the efficiency of existing libraries and devices.

Unlike NetWorker, which requires that each library must be dedicated to a data zone (owned by a NetWorker server), the AlphaStor software can share libraries across multiple data zones. If the backup load varies among the data zones then the devices in a library in one data zone may be unused while another data zone has more backup jobs than available devices. AlphaStor allows the library resources to be shared among the data zones maximizing the use of the devices and reducing the total backup time. Example 1 on page 20 is a common scenario for moving existing data zones into the AlphaStor environment.

Example 1 Combine separate data zones

In this example, there are two NetWorker data zones, each with a SCSI-attached library containing six devices.

To add AlphaStor to this environment:

1. Make the devices in each library accessible to each storage node.

2. Install the AlphaStor server on one of the NetWorker server hosts.

3. Install the AlphaStor LCP on each host that is directly connected to a library.

4. Install the AlphaStor DCP on each NetWorker storage node.

5. Configure the AlphaStor software.

6. Reconfigure the NetWorker software to use the libraries that are controlled by AlphaStor.



Example preconfiguration worksheet1. Create a diagram of the main components and hosts in the AlphaStor

environment. Figure 1 on page 21 illustrates an example layout of AlphaStor and NetWorker components after the integration. The AlphaStor DCP and NetWorker storage node lines are the SAN connections to the devices only, they are not connected to each other. The DCP and NetWorker storage node components do not communicate with each other directly. All the hosts are on the same TCP/IP network (not illustrated).

In this example, the AlphaStor server is installed on the NetWorker server host to be restored first in a disaster recovery scenario. Also, the AlphaStor server can be installed on a dedicated host or a Solaris High Availability cluster.

Figure 1 Sample data zone

Example preconfiguration worksheet 21


2. Determine the hostnames that will be involved in the AlphaStor installation and configuration:

a. List the hostname where the AlphaStor server will be installed:

nwserv1

b. List the hostnames of all the NetWorker servers that will be changed to use a library managed by AlphaStor:

nwserv1, nwserv2

c. List the hostnames that will be controlling a library and which libraries each host will control. The AlphaStor LCP package will be installed on these hosts:

nwserv1 Library1nwserv2 Library2

d. List the hostnames of all NetWorker storage nodes that will be accessing devices managed by AlphaStor. The AlphaStor DCP package will be installed on these hosts:

nwserv1, nwserv2, nwnode1, nwnode2

3. Create a list of each media location that you expect to use in the environment. Table 3 on page 22 provides examples of media locations and names:

4. List the rotation policies needed. For each policy list each step's location and duration:

Offsite_30 -- Offsite for 30 days@Home 0 -- inside the libraryDataWarehouse 30 -- At data warehouse

LondonArchive_1yr -- In London archive for 1 year@Home 0London_Archive 365

5. List the data mover application name for each data mover. For NetWorker, the recommended application name format is NetWorker@shorthostname:

NetWorker@nwserv1 NetWorker@nwserv2

6. List firewall requirements. In this example, there are no firewall considerations.

7. Identify the following as listed in Table 5 on page 22 for the library configuration wizard:

Table 4 AlphaStor media locations

Physical location AlphaStor location name

Archive facility in London London_Archive

Local data warehouse DataWarehouse

Table 5 Information required for the library configuration wizard

Library model AlphaStor library name LCP host

DD660 Library1 nwserv1

MSL8096 Library2 nwserv2



8. Identify the following for the jbconfig program:

• The names of the virtual libraries (virtual jukeboxes) to create:

Library1 Library2

• The corresponding AlphaStor library name as described in step 7 :

Library1 Library2

• The logical device names to configure for each storage node. In this example there are two logical devices per storage node for each virtual library:

– For data zone 1, virtual library 1:nwserv1: serv1_lib1_1 serv1_lib1_2nwnode1: node1_lib1_1 node1_lib1_2




Migrate NetWorker DDS configurations to AlphaStorDDS is commonly used in a NetWorker configuration to make more efficient use of available devices. However with DDS, each storage node still has access only to its given subset of devices. This can lead to cases where available devices stand idle because all of the devices to which the storage node has access are busy.

Installing AlphaStor in the environment provides more flexibility, eliminates the need for DDS to be configured, and enables better use of available devices. Example 2 on page 23 is a common scenario for moving from NetWorker with DDS to AlphaStor.

Example 2 Replace NetWorker dynamic drive sharing

In this example, there are three NetWorker data zones, each accessing the same library that contains 15 devices. With DDS, a storage node has access to a set of 6 defined devices of 15 total devices. If all 6 of the devices are busy, then the storage node is forced to wait, even if other devices are available. With AlphaStor, the storage node can use any of the 15 available devices, up to a maximum of 6 jobs.

To add AlphaStor to the environment:

1. Make the devices in each library accessible to each storage node.

2. Install the AlphaStor server on one of the NetWorker hosts.

3. Install the AlphaStor LCP on each host that is directly connected to a library.

4. Install the AlphaStor DCP on each NetWorker storage node.

5. Configure the AlphaStor software.

Migrate NetWorker DDS configurations to AlphaStor 23


6. Reconfigure the NetWorker software to stop using DDS, and to use the libraries controlled by AlphaStor.

In this example, each storage node must be configured with 6 logical devices to ensure that a maximum of 6 jobs are active on any storage node.

Complete details on replacing NetWorker DDS are available in the EMC AlphaStor Release 4.0 Installation Guide and the EMC AlphaStor Release 4.0 Administration and Operation Guide.

Naming conventionsThe following sections describe recommended naming conventions for rotation policies, libraries, and devices in the AlphaStor environment.

Rotation policy namingThe following is the recommended practice for rotation policy naming:

◆ Use @Home as the first location of every rotation policy.

◆ Base the rotation policy name on its duration and either its purpose or the offsite location.

The following are examples of this naming convention:

◆ Offsite_60--Associated volumes are moved offsite for 60 days.

◆ Vault_30day--Associated volumes are moved to the vault for 30 days.

◆ Archive_1yr--Associated volumes are archived for 1 year.

Using the @Home location reduces the number of rotation policies required because they can be applied to the volumes in different libraries.

Library namingThe following are recommendations for naming libraries:

◆ Model-based names--Base the AlphaStor library name on the model name of the library. For example, DD660 or i500.

◆ Location-based names--Base the AlphaStor library name on the physical location of the library. For example, DataCenterLib2.

Device namingThe default name that AlphaStor uses for a device is based on the name of the library that contains the device with a number appended to it. For example, if the AlphaStor library DD660 has two devices, the default names would be DD6601 and DD6602.

Use an underscore in the device name prefix to separate the library name from the device number if it is preferred. In this example, using DD660_ will result in DD660_1 and DD660_2 for the device names.

Note: For ease of use in day-to-day operations, include the library name as part of the associated device names.



Scripts and custom actionsThe AlphaStor software provides a user callout mechanism that can be used to take specific action when a tape is imported, exported, or moved. If you use custom scripts in the current environment, they might need to be revised to work with the AlphaStor software. More information on user callout routines is available in the EMC AlphaStor Release 4.0 Administration and Operation Guide.

Note: The AlphaStor software does not require user callout scripts for normal operation.

Scripts and custom actions 25



Date post:	27-Jun-2020
Category:	Documents
Upload:	others
View:	5 times
Download:	0 times

EMC AlphaStor Release 4.0 Planning Guide · EMC AlphaStor Release 4.0 Planning Guide 5 Preface As...

Documents