30
EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.EMC.com EMC ® Atmos Planning Considerations REV A01

EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

  • Upload
    others

  • View
    16

  • Download
    0

Embed Size (px)

Citation preview

Page 1: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

EMC® Atmos™

Planning Considerations

REV A01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

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

Page 2: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

2

Copyright © 2008 - 2011 EMC Corporation. All rights reserved.

Published February, 2011

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

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

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

For the most up-to-date regulatory document for your product line, go to the Technical Documentation andAdvisories 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.

EMC Atmos Planning Considerations

Page 3: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Contents

PrefaceIntroduction ......................................................................................... 6

Chapter 1 Planning ConsiderationsChoosing storage service attributes ............................................... 10Metadata service planning .............................................................. 14Tenancy planning guidelines .......................................................... 15Policy planning guidelines .............................................................. 16

Chapter 2 Installation PlanningAbout the Atmos installation utility .............................................. 18Preparing for the installation .......................................................... 20Choosing an installation strategy ................................................... 23

EMC Atmos Planning Considerations 3

Page 4: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Contents

EMC Atmos Planning Considerations4

Page 5: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Preface

As part of an effort to improve and enhance the performance and capabilitiesof its product lines, EMC periodically releases revisions of its hardware andsoftware. Therefore, some functions described in this document may not besupported by all versions of the software or hardware currently in use. Forthe most up-to-date information on product features, refer to your productrelease notes.

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

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

Preface 5

Page 6: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

6

Preface

Introduction

Audience This document is intended for use by customers and EMC servicepersonnel who are responsible for installing and configuring Atmos.

Relateddocumentation

The following EMC publications provide additional information:

◆ EMC Atmos Release Notes

◆ EMC Atmos Administrator’s Guide

◆ EMC Atmos Programmer’s Guide

◆ EMC Atmos System Management API Guide

◆ EMC Atmos Security Configuration Guide

◆ EMC Atmos Non-EMC Software License Agreements

◆ EMC Atmos Hardware Guide

◆ EMC Atmos online help

Conventions used inthis document

EMC uses the following conventions for special notices:

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

CAUTION!A caution contains information essential to avoid data loss ordamage to the system or equipment.

IMPORTANT!An important notice contains information essential to software orhardware operation.

EMC Atmos Planning Considerations

Page 7: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Preface

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

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, environmentvariables, functions, utilities

• URLs, pathnames, filenames, directory names, computernames, 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 bythe 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 theexample

Introduction 7

Page 8: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

8

Preface

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

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

http://Powerlink.EMC.com

Technical support — For technical support, go to Powerlink andchoose Support. On the Support page, you will see several options,including one for making a service request. Note that to open aservice request, you must have a valid support agreement. Pleasecontact your EMC sales representative for details about obtaining avalid 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 sendyour opinions of this document to:

[email protected]

EMC Atmos Planning Considerations

Page 9: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

1

This chapter describes several features that require thoughtfulplanning before installing an Atmos system. The topics include:

◆ Choosing storage service attributes ................................................ 10◆ Metadata service planning................................................................ 14◆ Tenancy planning guidelines ........................................................... 15◆ Policy planning guidelines ............................................................... 16

PlanningConsiderations

Planning Considerations 9

Page 10: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

10

Planning Considerations

Choosing storage service attributesThe Atmos installer asks you to define the storage service attributesto configure for the disks in your system. Figure 1 illustrates the twolevels of attributes you are required to define.

Figure 1 Storage Service Attributes

Note: Installation is the only time you can specify these attributes. If notspecified, or specified incorrectly, they cannot be changed after the system isinstalled.

Data placement Data placement defines how the storage service allocates new objectsto the physical disks it manages. Your options are:

◆ OPTIMAL

• Disks are written to in a round robin order so that requests arerotated equally among all available storage disks.

• Creates a single ext3 file system per drive.

• The default.

EMC Atmos Planning Considerations

Page 11: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Planning Considerations

◆ GREEN

• Drives are spun up as they are written to so that only one or afew disks are active; the rest are spun down for energyconservation.

• When the active disks fill up, the spun-down disks are wokenup and used.

• Drives spun down after 30 minutes of inactivity.

• Single ext3 file system per drive.

Note: Green is not supported for Atmos Virtual Edition installations.

◆ FAST

• Uses non-parity based striping by putting blocks of data of thesame replica on different disks. This mode allows for a betteraggregate throughput to the disks, by using multiple diskheads to access the same replica. This is like RAID striping.FAST

• One file system per every three drives

Note: FAST is not supported for Atmos Virtual Edition installations.

◆ BALANCED

• Data is written to the drive with the most available space

• Single ext3 file system per drive

Data transformation Data transformation specifies the data-at-rest services that areapplied to replicas when they are stored:

◆ NONE

• No services; normal writes and reads.

• This is the default.

◆ COMPRESSION

• Data is compressed on write and decompressed on read toconserve disk space.

• Introduces processing overhead on the server, so typically ithas a negative impact on performance.

• Compression can be used successfully for objects that arewritten once and accessed rarely.

• 64KB chunks

Choosing storage service attributes 11

Page 12: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

12

Planning Considerations

• Per replica (OSD)

◆ DEDUP

• Background process where multiple copies of the data areremoved so that only one copy of the data is maintained.

• Intended to conserve storage capacity.

• Use fewer to increase the odds of deduplication.

◆ Checksum

• The Storage Server generates a checksum for all data saved onit.

• When the data is read, the checksum is verified.

• When the data is re-written, the old data also is verified.

• 64KB chunk

• Stored as metadata

◆ DEDUP,COMPRESSION — Combination of COMPRESSIONand DEDUP.

Storage service attributes and performanceYou should carefully consider how to combine the data placementand data transformation attributes because some combinations mightcause performance degradation. Table 1, Table 2, and Table 3 use thefollowing entries to describe whether data placement/datatransformation impacts performance.

◆ Yes — Consider this combination as part of your overall design.

◆ Not generally recommended— Does not provide any benefits,but does not degrade overall system performance.

EMC Atmos Planning Considerations

Page 13: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Planning Considerations

◆ Do not use — These features are not complementary, and mightnegate the benefits of the individual attributes. Using them incombination might also degrade the overall system performance.

For more information on specifying replica types, see the chapter onmanaging policies in the EMC Atmos Administrator’s Guide.

Table 1 Standard Replica

PlacementPolicy Compression Deduplication

Comp&Dedup Checksum None

Balanced Yes Yes Yes Yes Yes

Green Yes Do not use Do not use Yes Yes

Optimal Yes Yes Yes Yes Yes

Table 2 Striped Replica

PlacementPolicy Compression Deduplication

Comp&Dedup Checksum None

Balanced Not generallyrecommended

Yes Not generallyrecommended

Not generallyrecommended

Yes

Green Not generallyrecommended

Do not use Do not use Not GenerallyRecommended

Yes

Optimal Not generallyrecommended

Yes Not generallyrecommended

Not generallyrecommended

Yes

Table 3 Erasure Coded Replicas

PlacementPolicy Compression Deduplication

Comp&Dedup Checksum None

Balanced Not generallyrecommended

Yes Not generallyrecommended

Yes Yes

Green Not generallyrecommended

Do not use Do not use Yes Yes

Optimal Not generallyrecommended

Yes Not generallyrecommended

Yes Yes

Choosing storage service attributes 13

Page 14: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

14

Planning Considerations

Metadata service planningSome disk capacity per DAE is used to store metadata. Drives that arededicated to metadata are defined and configured during installationin the application configuration page:

The ratio you specify here will determine the number of nodes, perdrive, allocated to metadata rather than user data.

Each object has a fixed amount of metadata when stored in Atmos.This means that large files have less metadata as a percentage of theirsize than small files.

What kind of files will the customer be ingesting?

Remote metadatareplication

If the customer has more than one site, EMC recommendsimplementing remote metadata replication.

When Atmos is installed, there are two MDS instances running ontwo different nodes in the same RMG, in a master-slave mode. Themaster MDS replicates its data to the slave MDS. If this RMG goesoffline (for example, due to a power or network outage), all objectsowned by this MDS pair are unavailable to the user. The MDS remotereplication feature enables you to configure a secondary RMGlocation to replicate metadata. If the primary RMG becomesunavailable, Atmos can read from the secondary RMG.

See the Atmos Administrator’s Guide for more information aboutconfiguring MDS remote replication.

EMC Atmos Planning Considerations

Page 15: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Planning Considerations

Tenancy planning guidelinesIn general, one tenant is acceptable. Subtenants can be customers ordivisions, but it depends on a number of factors.

◆ Tenants can be used to segregate customer access points.

◆ Subtenants have their own namespace and policies. Subtenantsare software enforced virtual partitioning.

Constraints ◆ The number of tenants is physically limited to the number ofnodes in the Atmos system. An access node can belong to onetenant only.

◆ If you have 16 nodes, you can have a maximum of 16 tenants.However, that means a single access point for each tenant. Ideally,for bandwidth and resiliency you'd want at least 2 access nodesper tenant.

◆ Tenant name and IDs are unique within the system.

Tenancy planning guidelines 15

Page 16: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

16

Planning Considerations

Policy planning guidelinesIn general, there is no limit to the number of policies that can becreated.

It’s a good idea to define 99% of the required policies before objectsare ingested.

Remember that policies are applied to an object as it is created. Oncean object is in the system, new policies may not affect existing objects.

Guidelines ◆ Use a policy with replication across RMGs.

◆ EMC recommends 10-20 tenant policies and up to 16 subtenantpolicies. But ideally they should be kept at a manageable number(10 or less).

◆ The more policies that exist, the more overhead the system haswhen running through them to select.

EMC Atmos Planning Considerations

Page 17: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

2

This chapter includes the following topics:

◆ About the Atmos installation utility ............................................... 18◆ Preparing for the installation ........................................................... 20◆ Choosing an installation strategy .................................................... 23

Installation Planning

Installation Planning 17

Page 18: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

18

Installation Planning

About the Atmos installation utilityWhen you install the Atmos software on hardware or in a virtualenvironment, the installer:

◆ Copies the Atmos image to the installation segment’s masternode (this is the eth1 IP address you are prompted for after youaccept the license agreement).

◆ Installs the Atmos software on the installation segment’s masternode. (The Atmos software includes an operating system imageand a configuration file). During this step, it:

• Verifies that the machine meets the installation requirements.

• Configures the machine for network communications.

• Generates a service configuration profile, then configures theservices based on the configuration profile.

• Partitions and assigns the disks for data allocation.

◆ The installer displays its status and indicates the steps that havecompleted. If the installation of the master node fails at any step,the installation stops.

After the master node is successfully installed, the slave nodes areinstalled from the Atmos image copied to the master node. The onlyuser intervention required is to start the slave nodes.

◆ On hardware systems, you can click a button to automaticallystart the slave node installation, or PXE boot each slave nodeindividually.

◆ On virtual systems, you have to power on each virtual machine.

EMC Atmos Planning Considerations

Page 19: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Installation Planning

Installation log files The Atmos installer writes messages to the logs described in Table 4.If you encounter problems (for example, nodes not installing, longerthan normal installation process, and so on), you can review theselogs to determine what might be causing the installation problem.

Atmos installation recommendationsEMC recommends that when you install Atmos, you:

◆ Configure at least two RMGs.

◆ Enable remote metadata replication.

◆ Use a policy with replication across RMGs.

◆ Carefully choose storage service attributes. For more information,see “Choosing storage service attributes” on page 10.

Table 4 Atmos installation logs

This log... includes information about...

/var/log/maui/pxe.log This log shows details of the installation utilitiesoperations and output. It is the first log that youshould examine if you encounter errors during aninstall; for example, if the installation of one nodetakes longer than one hour, or if systemmanagement GUI shows an installation failure.

/var/log/maui/cm.log This log shows whether each install task has beenloaded and executed successfully. Review thecontents of this log if the install is does not completeor is suspended in one stage, but you do not seeerrors in the pxe.log.

/var/log/maui/gui.log This log details the user configuration in the systemmanagement GUI, and it tracks user input andcommunications with the Atmos CM.

About the Atmos installation utility 19

Page 20: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

20

Installation Planning

Preparing for the installation◆ “Learn the configuration details”

◆ “Obtain the software and tools”

◆ “Complete the Network Information form”

Learn the configuration details◆ How many Atmos nodes/servers are you installing?

• PromoCode1 – 6 servers

• PromoCode3 – 16 servers

• PromoCode5 – 8 servers

◆ Do you have the right number of IP addresses?

• One customer IP address is required for each server.

• The IP addresses must be sequential within an IS (rack)

◆ Do you know the location tags the customer wants to use?

◆ What is the unique hostname prefix for each IS?

• Used by customers later to easily identify location of server

• Useful to include location and installation segment inhostname prefix

• Very important when expansion is possible

◆ Do you have the necessary information for each RMG you areinstalling, such as, Name and Location?

◆ What will you set the SecurityAdmin password to?

◆ Who will be assigned to the SysAdmin role, and what is thepassword?

◆ Do you have the complete set of network information (see“Complete the Network Information form” on page 21?

◆ Do you know what storage services the customer wants to use?For more information, see “Choosing storage service attributes”on page 10.

◆ Do you know what to set the metadata ratio to? For moreinformation, see “Metadata service planning” on page 14.

◆ Do you have access to the customer network?

EMC Atmos Planning Considerations

Page 21: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Installation Planning

Obtain the software and toolsYou must have these items:

◆ Atmos Installation CD

◆ 10-foot Cat 6 Ethernet cable

You should try to have these items:

◆ AT DB-9 to RJ-45 switch cable

◆ 6 in one screwdriver

◆ Wire side cutter (nipper) pliers

◆ Crescent wrench

◆ USB to PS/2 converter

◆ PDU to 110VAC receptacle converter cable

◆ 1 to 3 power splitter

Complete the Network Information formWhen you install Atmos, you are prompted for detailed networkconfiguration information. For this reason, EMC recommends thatyou complete a network information form before you begin theAtmos installation. The form below contains the information that youare prompted for.

Figure 2 Atmos installation network information form

Item Field Your Value

RMG Name

Location (for example, Boston)

NTP Server Name (forexample, time-a.nist.gov)

SMTP Server IP Address

Preparing for the installation 21

Page 22: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

22

Installation Planning

Installation Segment 1 Hostname prefix (for example,Prod-Atmos)

Consecutive, static, public IPaddress range for eth1 of thenodes in this IS

From:To:

Subnet mask

Gateway

Primary DNS

Secondary DNS

Installation Segment 2 Hostname prefix (for example,Prod-Atmos)

Consecutive, static, public IPaddress range for eth1 of thenodes in this IS

From:To:

Subnet mask

Gateway

Primary DNS

Secondary DNS

Item Field Your Value

EMC Atmos Planning Considerations

Page 23: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Installation Planning

Choosing an installation strategyIf you are installing more than one RMG or installation segment (IS),you can install them:

◆ Serially — Install Atmos one RMG or IS at a time. For example, ifyou have one RMG with multiple installation segments, youwould install all of the nodes in the first installation segment,followed by all of the nodes in the second installation segment,and so on. Installing Atmos in this way can be time-consuming(depending on the size of the installation).

◆ In parallel — In parallel mode, you can install the master nodes ofthe RMGs or installation segments first. Once all of the masternodes are installed, you can install all of the slave nodes.However, when you do an parallel install, you must:

• Install all of the master nodes first (via CD), then install theslave nodes. Do not mix the installation of master and slavenodes or the installation fails.

• Add the installation segments to the RMG or add the RMGs tothe system one at a time.

To learn more about installing Atmos in different configurations, andhow to add the master nodes in the correct order, review thesescenarios:

• “Installing one RMG with one IS”

• “Installing one RMG with multiple ISs”

• “Installing multiple RMGs in parallel”

• “Installing multiple RMGs serially”

Installing one RMG with one ISThis section describes the order for installing one Atmos RMG with aone installation segment. This is the typical serial installation mode.

Choosing an installation strategy 23

Page 24: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

24

Installation Planning

Figure 3 Installing one RMG with one IS

Figure 3 shows a single RMG (Boston RMG) and the installationsegment (IS01). IS01 has Node 1 through Node 8. Table 5 describesthe order that you would perform that Atmos install for thisconfiguration.

Note: If you install slave nodes in parallel and the installation segmentincludes more than 16 nodes, EMC suggests that you only install 16 nodes ata time to help reduce the load on master node of the installation segment.

Table 5 Installing one RMG with one IS

Step What you’ll do

1 Launch the Atmos install by putting the Atmos CD in the first node in the rack.Install Atmos on the master node of the installation segments.

2 Add an RMG.

3 After you have completed the add RMG steps, the Atmos installation GUI willnotify you that you can add the slave nodes.

Note: In this configuration, you can add all of the slave nodes at the same.

EMC Atmos Planning Considerations

Page 25: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Installation Planning

Installing one RMG with multiple ISsThis section describes how to install a single RMG with more thanone installation segment in parallel as shown in Figure 4.

Figure 4 Installing one RMG with two ISs

Choosing an installation strategy 25

Page 26: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

26

Installation Planning

Boston RMG has two installation segments called IS01 and IS02. Eachinstallation segment has 8 nodes. In this scenario, you can install theIS’s master nodes (IS01 Node 1 and IS02 Node 1) at the same time.Once the installation of the master nodes is complete, you can installthe slave nodes.

Table 6 Installing One RMG with two ISs

Step What you’ll do

1 Install Atmos on the master node of each of the installation segments.

Note: Perform this step on both master nodes.

2 Add the first RMG to the system. For example, specify IS01, Node 1 as thesystem’s initial master node.

Note: Use the IP address for IS01, Node 1 when you perform the securityadmin tasks and initiate the system.

3 Add the IS02 installation segment to the system.Repeat this step for any additional installation segments.To learn how to add an installation segment, see EMC AtmosAdministrator’s Guide

4 Install the Atmos software on all of the slave nodes in the RMG in parallel.

EMC Atmos Planning Considerations

Page 27: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Installation Planning

Installing multiple RMGs in parallelThis section describes how to install multiple RMGs with multipleinstallation segments in parallel.

Figure 5 Installing three RMGs in parallel

In this scenario, you can install the Atmos software on the masternodes of all of the RMGs at the same time (Boston RMG 1 IS01 Node1, Boston RMG2 IS01, Node 1, and Boston RMG3 IS01 Node 1). Toensure that the installation is successful, you must make sure thatNode 1 of the Boston RMG is configured first, and that each RMG orIS is added to the system one at a time.

Table 7 Installing three RMGs in parallel

Step What you’ll do

1 Install Atmos on the master nodes of each RMG.

2 Add the first RMG to the system. (In this example, Boston RMG1).

Note: Use the IP address of Boston RMG, IS01, Node 1 for these steps.

Choosing an installation strategy 27

Page 28: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

28

Installation Planning

Installing multipleRMGs serially

This section describes how to install multiple RMGs with multipleinstallation segments, one at a time. This is useful if you are installingmultiple RMGs at geographically dispersed data centers. See Figure 6for an example of this configuration.

◆ Boston RMG has a two installation segments IS01 and IS02. EachIS has 8 nodes. It is the first RMG configured for the system, soNode 1 becomes the initial master node for the system.

◆ London RMG has two installation segments IS01 and IS02. EachIS has 8 nodes.

◆ Tokyo RMG has two installation segments IS01 and IS02. Each IShas 8 nodes.

4 Add Boston RMG2 to the system, then add Boston RMG3 to the system.

5 Add the installation segments to the system. Boston RMG1 IS02, Boston RMG2IS02, Boston RMG3, IS02, and so on.See the section on adding an installation segment in the online help or the EMCAtmos Administrator’s Guide.

6 Install the slave nodes for all IS’s in parallel.

Table 7 Installing three RMGs in parallel

Step What you’ll do

EMC Atmos Planning Considerations

Page 29: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

Installation Planning

Figure 6 Installing multiple RMGs serially

Table 8 Installing multiple RMGs serially

Step What you’ll do

1 Install Atmos on the IS01 Node 1 of the Boston RMG.

Note: Use the IP address of Boston RMG, IS01, Node 1 when you perform thesecurity admin tasks and initiate the system.

2 Install Atmos on IS02 Node 1 of the Boston RMG.Add IS02 to the Boston RMG.See the section on adding installation segments in the online help or the EMCAtmos Administrator’s Guide.

3 Install all of the slave nodes in the Boston RMG.

4 On the second RMG (London RMG), install the Atmos software on the masternodes of each installation segment in parallel.Do not install the slave nodes.

5 Add the London RMG to the Boston RMG.When prompted for an IP address, use the IP address of London RMG IS01,Node 1.

Choosing an installation strategy 29

Page 30: EMC Atmos Planning Considerations · 12 EMC Atmos Planning Considerations Planning Considerations † Per replica (OSD) DEDUP † Background process where multiple copies of the data

30

Installation Planning

6 Add London’s second IS to the London RMG.See the section on adding installation segments in the online help or the EMCAtmos Administrator’s Guide.Use the IP address of London RMG IS02, Node 1 when adding the second ISto the London RMG.

7 Install all of the slave nodes in London RMG.

8 Follow steps 4-7 for the Tokyo RMG.

Table 8 Installing multiple RMGs serially

Step What you’ll do

EMC Atmos Planning Considerations