ExaGrid Admin Guide

ExaGrid Administrator’s Administrator’ s Guide

PN: 210-0165-13

Copyright No part of this document document may be be reproduced or transmitted in any form form or by any means means without the express written permission of ExaGrid Systems, Inc. © 2003-2012 ExaGrid Systems, Inc. All rights reserved. Printed in USA. This document, the associated software, and the associated online documentation are the property of of ExaGrid Systems, Inc. Inc. or its licensors, as applicable, and are loaned to the user under the terms of the ExaGrid Systems, Inc. End User License Agreement. Unauthorized copying or use of the software or any associated materials is contrary to the property rights of ExaGrid Systems and is a violation of state and federal law. law.

Trademarks ExaGrid is a registered trademark of ExaGrid Systems, Inc. ExaGrid Systems (Logo), InstantDR, InfiniteFiler, GRIDdisk and Intelligent Disk-based Data Protection are all trademarks of ExaGrid Systems, Inc. All third-party trademarks are the property of their respective owners.

License Agreement This document, the associated software and the associated online documentation are the property of ExaGrid ExaGrid Systems, Inc. or its licensors, licensors, as applicable. applicable. The use of these these materials and the software is strictly limited to those users who have signed the ExaGrid Systems, Inc. End User License Agreement. For any software acquired directly or indirectly on behalf of a unit or agency of the United States Government, whether whether for civilian agencies or for units of the Department of Defense, the software is a commercial item or commercial computer software (and documentation), documentation), and pursuant to Section 12.212 of the Federal Acquisition Regulations (FAR) or DoD FAR Supplement Section 227.7202, is provided under restricted rights as enumerated in the End User License Agreement.

Contents

1.

The ExaGrid System

1

ExaGrid Hub Sites and Spoke Sites 2 Data Flow 3 2.

Networking

4

Network Requirements 4 3.

Power Conditioning

7

4.

Single and Multi-Site Systems

8

Single-Site ExaGrid Systems 8 Multi-site ExaGrid Systems 5.

Shares

9

10

Backup Application Specific Shares 10 Universal Backup Shares InstantDR™ Shares

11

12

TempDR Shares 14 Utility Shares 15 Share Protection 16 Share Migration 16

ExaGrid Administrator ’s Guide iii

6.

The ExaGrid User Interface

Logging In

17

18

7.

Creating Shares

19

8.

Creating TempDR Shares

9.

ExaGrid Reports

22

23

Summary Reports 24 Replication Reports 27 Deduplication Reports 29 10.

Monitoring Your ExaGrid System

SMTP Email Notifications SNMP Traps

30

30

31

Status Monitor

31

ExaGrid MIB 32 11.

Configuring Uninterruptible Power Supplies (UPS)

Power Off Script

37

Power Off Script Parameters 38 Using powerOffExagrid.pl 39 Example powerOffExagrid.pl Command Line 39 12.

IPMI Network Port

40

Resetting the IPMI Network Port User Password Using the IPMI Network Port IPMI and NIC Ports

44

46

Using Server Message Block (SMB) Signing 48 Character Set Allowed for SMB User Names 49 Character Set Allowed for SMB Passwords 50

iv

ExaGrid Systems

41

37

13.

Restoring Files

51

14.

ExaGrid System Maintenance

52

Shutting Down and Restarting an ExaGrid Server Account Management

53

53

Adding Additional ExaGrid Servers 55 Adding an ExaGrid Site to an ExaGrid System 56 Software Upgrade 58 NTP Servers

58

Record Keeping 62 15.

Encryption Capable ExaGrid Servers

Encryption at Rest

63

63

Boot Protection 70 16.

ExaGrid System Disaster Recovery

17.

Troubleshooting

74

75

ExaGrid Status Monitor 75 Disk Failure

76

Disk Safety Halt Protection Disk Numbering

78

Power Supply Failure Fan Failure

77

82

82

Network Debugging Tools

84

Notifications 85 Consumption 86 Replication 18.

87

Performance Tuning

88

ExaGrid Administrator ’s Guide v

vi

ExaGrid Systems

Preface This guide provides an overview of the ExaGrid System and getting started instructions for the novice ExaGrid Administrator. Detailed descriptions of the ExaGrid System and advanced administrator procedures can be found in the ExaGrid System’s online help.

Related Documentation Title

Part Number

Assembling and Initializing Your ExaGrid System

210-0164-xx

ExaGrid Release Notes

210-0174-xx

Contacting ExaGrid Technical Support If you have technical questions about this product that are not answered in this document contact ExaGrid Support: ■ ■

Email: [email protected] Phone: 800-868-6985 and at the prompt, press 2.

ExaGrid Administrator’s Guide

vii

Glossary Understanding these terms will help you better understand the ExaGrid System. Disaster Recovery – In multi-site systems, in the event of a catastrophic loss of an ExaGrid Site, the ability to recover backup data that has been replicated to a surviving ExaGrid Site. ExaGrid Server - The hardware on which the ExaGrid Software runs. There are several ExaGrid Server models, each with a different capacity. ExaGrid Site - A logical collection of ExaGrid Servers. An ExaGrid System can be made up of one or more ExaGrid Sites. File Collection - A set of files associated with a backup application’s backup to an ExaGrid Share. ExaGrid reports will report one or more file collections associated with a backup job. Hub – ExaGrid Systems use a hub-and-spoke topology. In multi-site ExaGrid Systems, one site is designated the hub. When logged into the hub, the hub and all spoke sites are displayed in the navigation tree and system-level reports roll up information from all spokes. When logged into a spoke, only the spoke site and its hub are displayed in the navigation tree. system and site-level reports roll up information for the spoke site only. InstantDR™ Share - A copy of a share at a second ExaGrid Site. When you create an ExaGrid Share you have the option of also creating an InstantDR Share on an ExaGrid Server in another ExaGrid Site. InstantDR Shares are used in disaster recovery operations, remote tape copy operations, and in testing data recovery from another ExaGrid Site. Landing space – The portion of an ExaGrid Server’s disk space dedicated to incoming backup data. The size of the landing space varies by ExaGrid Server model. The landing space is used to store the most recent version of your backup(s). They are stored in their entirety. Since most restores are done from the most recent backup, the landing space ensures rapid restores. Replication - A share setting that instructs the ExaGrid System to maintain a second copy of a share on another ExaGrid Site. Retention Space – The portion of an ExaGrid Server that stores and manages deduplicated “Versions” of backup files. Share - A mount point/folder on an ExaGrid Server to which backup applications write.

viii

ExaGrid Systems

Share Migration - To move a share and its contents from one ExaGrid Server to another. Spoke – ExaGrid Systems use a hub-and-spoke topology. In multi-site ExaGrid Systems, one site is designated the hub. When logged into the hub, the hub and all spoke sites are displayed in the navigation tree and system-level reports roll up information from all spokes. When logged into a spoke, only the spoke site and its hub are displayed in the navigation tree. system and site-level reports roll up information for the spoke site only. TempDR Share - TempDR Shares are built manually from shares that are: replicated to a second ExaGrid Site but were created without a corresponding InstantDR Share. TempDR shares are used for test recover and in disaster recovery operations. Versions – The deduplicated copies of a backup job.

ExaGrid Administrator’s Guide

ix

x

ExaGrid Systems

The ExaGrid System Your ExaGrid System is a disk based backup appliance that sits behind your existing backup server. ExaGrid uses deduplication technology that allows multiple versions of your backups to be stored in a very small storage footprint. In addition, the ExaGrid System works in concert with backup applications to duplicate ExaGrid disk-based backups on to tape. This capability is especially useful to ExaGrid users who: ■ ■

Need a disaster recovery solution for an ExaGrid Single Site configuration Are required to maintain backups on removable media

This chapter provides a high-level overview of the ExaGrid System’s features and capabilities. Consult the ExaGrid online help for detailed descriptions and step-bystep instructions on how to use the ExaGrid System. Caution – Do not install third party software on your ExaGrid Server. Installing third party software may result in a loss of data and void your ExaGrid Warranty.

ExaGrid Servers differ in capacity, physical size and network connectors. All ExaGrid Servers run the same ExaGrid software and may be commingled in an ExaGrid Site.

1

ExaGrid Hub Sites and Spoke Sites The ExaGrid System uses a hub and spoke topology where there is a single ExaGrid Site known as the hub, connected to one or more ExaGrid Sites known as spokes. Note – ExaGrid hub sites can replicate shares to spoke sites. ExaGrid spoke sites can replicate shares to their hub site. ExaGrid spoke sites cannot replicate shares between each other. ot her.

When logged into an ExaGrid Server on a hub site you can: ■

■ ■ ■

See the hub site and all spoke sites displayed in the ExaGrid user interface’s navigation tree. The hub site is always listed as the top-most site in the navigation tree. View reports for the hub site and all spoke sites View events for the hub site and all spoke sites Perform hub site related management tasks

When logged into an ExaGrid Server on a spoke site you can: ■

■ ■ ■

2

ExaG ExaGri rid d Sys Systems tems

See the spoke site and the hub site displayed in the ExaGrid user interface’s navigation tree. Other spoke sites in the system are not displayed. View reports for the spoke site View events for the spoke site Perform spoke site related management tasks

Data Flow The following diagram details the data flow descriptions presented in this section:

ExaGrid System Hub or Spoke Site

Hub or Spoke Site

Landing Space

Landing Space

Retention Space

Retention Space

Data flows into an ExaGrid Share via a backup application: ■ ■

Backup application writes to an ExaGrid share. When the backup is complete, the ExaGrid deduplication engine will deduplicate the backed up data.

Note – As more and more backups land, retained and deduplicated, deduplication ratios will improve. ■ ■ ■

A full copy of the most recent backup is maintained in the Landing Space. The deduplicated versions are kept in the Retention Space. In multi-site ExaGrid Systems, you can specify whether or not to maintain a copy of a share on a second ExaGrid Site.

When a backup application requests a restore: ■

■

Since most restores are done from the most recent backup, the ExaGrid system keeps the most recent backup in its entirety. This ensures extremely fast restores. Restores from an older backup are done by re-assembling the backup from backup versions.

ExaGrid Administrato r’s Guide 3

Networking Depending upon the model, ExaGrid Servers come with two, four or six network interface connectors (NICs). NIC

Description

NIC1

Used for communication between ExaGrid Servers. Not used

in single server, single site systems. NI C 2

Used as the primary network connection for all ExaGrid Server models. Over this connection flows: Backups, notifications, and browser sessions.

NIC3, NIC4, NIC5 and NIC6

Additional NICs available on some ExaGrid Server models. Multiple NICs allow you to increase your backup throughput.

Network Requirements This section details the network requirements for ExaGrid Sites and ExaGrid Servers. You may connect all NICs of all ExaGrid Servers in a single ExaGrid Site to the same subnet. The internal ExaGrid network (NIC1) over which ExaGrid Server communicate, can share the same subnet as the other ExaGrid NICs over which backup data flows. Network Security

The ExaGrid internal network NIC1 port is protected by explicit routes and firewall entries in the ExaGrid Servers. ExaGrid Shares are protected by configurable share access lists.

4

ExaG ExaGri rid d Sys Systems tems

ExaGrid NIC1

ExaGrid Servers use their NIC1 port to communicate with other ExaGrid Servers in an ExaGrid Site and with ExaGrid Servers in other ExaGrid Sites. ■ Single-ExaGrid Server single-ExaGrid Site systems do not use their NIC1 port and can be left unconnected. ■ ExaGrid Servers within an ExaGrid Site must connect their NIC1 ports to the same subnet. ■ ExaGrid Servers within one ExaGrid Site cannot connect their NIC1 ports to the same subnet used by NIC1 ports of ExaGrid Servers in another ExaGrid Site. Failure to observe this requirement may cause loss of access to data. ■ NIC1 cannot be used to accept backups from your backup application. Multicasting Considerations for ExaGrid NIC1 ■

Multicasting is used only between ExaGrid Servers in an ExaGrid Site. Via the NIC1, multicast packets must not be routed between ExaGrid Sites. When setting up a subnet for an ExaGrid Site’s NIC1 port, ensure that standard multicasting protocols such as IGMP/IGMP snooping or multicast routing protocols like DVMRP, PIM, and MOSPF are disabled on the subnet used by your ExaGrid system.

For example, Cisco 6500 users, if IGMP snooping is configured on the same subnet to which ExaGrid Servers connect their NIC1 ports, it will not allow multicast packets between ExaGrid Servers. To disable this functionality in IOS: 1. Select a subnet interface: Router(config)# interface subnet subnet_ID

2. Disable IGMP snooping: Router(config-if)# no ip igmp snooping

ExaGrid Backup NICs (NIC2 and Optional NIC3, NIC4, NIC5 and NIC6)

ExaGrid Servers use Backup NICs to accept backups from your backup servers. NIC2 must be enabled before optional NICs 3 and 4 can be enabled.


The following figure details a typical ExaGrid network topology:

Site A

Site B

192.169.99.100

NIC 1

ExaGrid

NIC 2

192.169.99.101

Server 1

NIC 3

192.169.99.102

NIC 4

192.169.99.103

NIC 1

ExaGrid

NIC 2

Server 2

NIC 3 NIC 4

192.169.99.104 192.169.99.105 192.169.99.106 192.169.99.107

FIGURE 1

6

ExaGrid Systems

NIC 1: Each site must be on a separate subnet.

192.169.77.100 192.169.77.101 192.169.77.102 192.169.77.103

NICs 2,3,4,5,6: Addresses must not overlap either sites' subnet. Typically these are on the same subnet as your backup server(s).

ExaGrid Network Topology

192.169.77.104 192.169.77.105 192.169.77.106 192.169.77.107

NIC 1 NIC 2

ExaGrid

NIC 3

Server 1

NIC 4

NIC 1 NIC 2

ExaGrid

NIC 3

Server 2

NIC 4

Power Conditioning Each ExaGrid System requires conditioned power to protect it from unanticipated power events. For details on how to configure the power supplied to your ExaGrid System, consult the Assembling and Initializing Your ExaGrid System guide (PN 210-0164-xx) that came with your ExaGrid System.


Single and Multi-Site Systems The ExaGrid System is made up of physical and virtual storage components. Each component, whether virtual or physical, is represented in the ExaGrid System’s user interface. ■

Virtual Components ■

■

■

■

ExaGrid System — The ExaGrid System represents a network of interconnected sites. Hub Site — A hub site can be made up of one or more ExaGrid Servers. Every ExaGrid System has one hub site. Spoke Sites — A spoke site can be made up of one or more ExaGrid Servers. An ExaGrid System can have multiple spoke sites.

Physical Component ■

ExaGrid Server — Rack mounted devices for the ExaGrid System. Users and applications access the ExaGrid System through ExaGrid Servers.

Single-Site ExaGrid Systems A single site configuration: ■ ■

■

8

ExaGrid Systems

Is made up of one or more ExaGrid Servers. Does not have the extra protection against a full site disaster afforded by a multisite configuration. Can be joined with another site to form a multi-site system.

Multi-site ExaGrid Systems A multi-site configuration: ■ ■ ■ ■ ■

■

Has one site designated as the hub site and one or more spoke sites. Each site can have one or more ExaGrid Servers. Allows the hub site to copy (replicate) its shares to any spoke site Allows a spoke site to replicate its shares to the hub site. Has full site disaster recovery capabilities - If one site is lost, data from a surviving site can be used to reconstruct the lost backups. Can not be split into single-site systems.


Shares Shares are mount points created on ExaGrid Servers to which your backup application can write. An ExaGrid System uses the following types of shares:

Backup Application Specific Shares Application specific shares are tailored to specific backup applications. ExaGrid provides detailed step-by-step instructions on how to use your backup application with these shares: 1. In the ExaGrid main menu, click Help . 2. From the drop down menu, select the Online Library. The Online library is displayed. 3. Scroll down until you see the guide that applies to your application. 4. Right mouse click on the link to the guide and save or print it as needed. To create an application specific share, see “Creating Shares” on page 19.

10 ExaGrid Systems

Universal Backup Shares ExaGrid Universal Backup Shares are designed to accommodate those backup applications that do not have an ExaGrid Share designed specifically for their use. Universal Backup Shares are deduplicated and can be replicated and migrated like other ExaGrid Shares. ExaGrid Systems has qualified a number of backup applications for use with the Universal backup Share. Best practices for the qualified applications may be found in your ExaGrid System’s Online Library. In addition, ExaGrid is continually qualifying backup applications for the Universal Backup Share. The ExaGrid web site (www.exagrid.com) will have the most up-todate list of applications qualified for use with the Universal Backup Share. In most cases, if your backup application has not yet been qualified by ExaGrid for use with the Universal Backup Share; the application will work with the Universal Backup Share provided you follow these simple guidelines: Note – ExaGrid Support may have limited expertise in applications not qualified by ExaGrid Systems

1. Create an ExaGrid Universal Backup Share. See “Creating Shares” on page 19. 2. To write backups to the ExaGrid Universal Backup Share, follow the application’s best practices for writing to disk, 3. In addition to following your backup application’s best practices, if supported by your backup application, ensure that: Compression is OFF ■ Encryption is OFF ■ Multiplexing is OFF ■ Deduplication is OFF ■ Concurrent write operations should not exceed 20. ExaGrid recommends to initially limit concurrent writes to four or five. Over time, increase concurrent writes until you reach a number that maximizes the performance of your backups. Each backup application, due to its particular pattern of interpretability will experience different levels of performance. 4. Run a series of test backups and restores to monitor deduplication ratios and performance and make adjustments as needed.When testing your backups look for: ■

■

Errors or warnings in the ExaGrid Event Viewer

■

Unusual deduplication ratios ExaGrid Administrato r’s Guide 11

■ ■

■

Unusual deduplication rates A sudden increase in backup durations when the retention period for your first backups is reached. Restores from backups at the other edge of your retention period that take an excessive amount of time.

Note – Your Exagrid System does not employ real-time reporting. When monitoring backup results it may take up to fifteen (15) minutes for a report to be updated.

The Universal Backup Share may not be suitable for all backup applications. This includes backup applications that: ■ ■ ■ ■

■

Create file and folder names that do NOT use UTF-8 encoding. Archive data into many small, individual files Backup data into many small, individual files Overwrite large amounts of backup data sent previously to the ExaGrid Universal Backup Share. Overwriting a small amount of “metadata” – e.g. control files, catalogs, etc. – should perform acceptably. Treat the ExaGrid Universal Share as primary storage

InstantDR™ Shares InstantDR Shares are copies of shares that are replicated to a second ExaGrid Site. InstantDR shares can be used to: ■

■

■

■

Recover replicated data after a disaster scenario. In multi-site ExaGrid Systems, backup data in ExaGrid Shares that are set to replicate to a second site, can be recovered. Test recovery of replicated data. You can use InstantDR shares to prove that the data replicated to a second ExaGrid Site is recoverable. Perform remote tape copy operations. Instant DR shares may also be used to make a tape copy of data that has been replicated to a second ExaGrid Site. For details, see the ExaGrid guide that describes how to use your backup application. A copy of your backup application guide can be found in the Online Library. Can be used with Symantec’s OpenStorage to achieve: ■ ■

■

12 ExaGrid Systems

Seamless integration with the ExaGrid disk backup system Unified control and tracking of all copies of data via the Symantec application’s interface -- including copies replicated to disaster recovery sites and tape copies Simplified disaster recovery, as Backup Exec is already aware of all copies of data and individually tracks retention periods for each copy

■

■

■

Fast recovery times due to the combination of Symantec’s and ExaGrid InstantDR capability Short backup window, by load balancing across Symantec media servers into the ExaGrid System Flexibility to retain different amounts of backup data at a local site versus an off-site disaster recovery location, by better utilizing the unique ExaGrid architecture.

To see how InstantDR shares are created, see “Creating Shares” on page 19.


TempDR Shares TempDR Shares are built manually from shares that are: replicated to a second ExaGrid Site but were created without a corresponding InstantDR Share. Note – In most cases InstantDR will meet your test recover and disaster recovery requirements. You will need to use TempDR shares only in those rare situations for replicated shares that do not have corresponding InstantDR shares.

A TempDR Share is a “snap shot” of the replicated contents of a share that does not have a corresponding InstantDR Share. New data can not be written to them. As the name implies, they are meant to be temporary. TempDR shares are not deduplicated or replicated. TempDR shares are used for: ■

■

Test recovery operations: You can use TempDR shares to prove that the data replicated to a second ExaGrid Site is recoverable. Disaster recovery: To recover data while you are waiting for the lost site to be recovered.

To create a TempDR Share, see “Creating TempDR Shares” on page 22.

14 ExaGrid Systems

Utility Shares Utility Shares are designed to accommodate any data type. Data may be copied manually, through a script or from an application to a Utility Share. When you create a Utility Share you must allocate a specific amount of storage space to the Utility Share. The space allocated is taken proportionately from the host ExaGrid Server’s landing space and retention space. ■

■ ■

■

Data in Utility Shares is not deduplicated and can not be replicated to a second ExaGrid Site. You may only create one Utility Share per ExaGrid Server. When you create a Utility Share, the amount of available landing space and retention space reported in Summary Reports will be automatically adjusted. When allocating space, you must consider the impact of the space allocation on your backup landing space as well as your retention space.

Caution – It is possible to allocate space for a Utility Share such that it interferes with your ExaGrid Server’s ability to accept and retain backups from other backup applications. Because of this, ExaGrid recommends that you allocate no more than twenty percent (20%) of the ExaGrid Server’s space to a Utility Share

To create a Utility Share, see “Creating Shares” on page 19


Share Protection Shares, and the data they contain, are protected in several ways: 1. The ExaGrid System and the data backed up to it are in your data center. 2. When you create a share you must define a whitelist of either DNS names or IP addresses and subnet masks. Only backup application servers and users logged into machines that match the share’s whitelist entries are allowed to read from or write to the share. 3. Multi-site configurations provide an additional level of data security. Copies of backup files can be kept on a second site. In case of a catastrophic event where one site has been damaged or destroyed, copies of backups on the second site can be used to rebuild your backups. 4. ExaGrid provides an SMB signing option that allows you to define security credentials used to access ExaGrid Shares. See “Using Server Message Block (SMB) Signing” on page 48 for details. 5. ExaGrid provides a hardware option that employs Encryption at Rest and Boot Protection. See “Encryption Capable ExaGrid Servers” on page 63 for details.

Share Migration Over time, your backup requirements will change. Because of these changes you may find it necessary to expand your ExaGrid System and/or add and move shares from one ExaGrid Server to another. To help you balance your backup load, the ExaGrid System allows you to move shares from one ExaGrid Server to another. This process is known as Migration. Note – Once a share has been migrated, backup jobs writing to the share have to be adjusted to accommodate the share’s new location.

16 ExaGrid Systems

The ExaGrid User Interface ExaGrid presents a unified, browser-based user interface for all ExaGrid Sites and ExaGrid Servers in an ExaGrid System. A single login gives you reports on, and administrative access to, all ExaGrid Sites and ExaGrid Servers in your ExaGrid System. The following screen capture and table detail the main components of the ExaGrid user interface:. 2

1

3

Call out

Description

1

Navigation tree: A tree view of the devices in the ExaGrid System. The hub site is always displayed as the top-most site. The navigation tree also displays a device’s status.

2

Main menu: Drop down menus that support functions for the currently selected device. Drop down menus change depending on the device selected. When logged into a spoke site, if you select the hub site or one of its ExaGrid Servers, the Manage option in the main menu is not displayed.

3

Work area: Used to display reports, configure properties, and manage the ExaGrid System.


Logging In You can access the ExaGrid user interface through any web browser on your network. To log in to the ExaGrid user interface: 1. Open a browser browser and enter enter the URL or IP address address of an ExaGrid ExaGrid Site’s ExaGrid Server. You can specify any ExaGrid Server but the one closest to your location will have the best performance. For example: http://ExaGridServerName or http://192.168.55.3 2. Press Return . The ExaGrid Login screen is displayed. 3. Enter your ExaGrid Administrator account’s user name and password. 4. Click OK and the ExaGrid user interface is displayed.

18 ExaG ExaGri rid d Syst System ems s

Creating Shares Caution – Never create or delete ExaGrid shares on an ExaGrid System with external commands or utilities. Always create and delete ExaGrid shares from the ExaGrid user interface.

To create a share: 1. In the navigation navigation tree, select select the ExaGrid Server Server on which which you want want to create the the share. 2. In the main menu, click click Manage . 3. From the drop down menu select Shares . The ExaGrid Shares page is displayed


4. Under the Tasks heading, click New. The Create New Share page is displayed .

5. From the drop drop down menu, select the share type 6. In the space provided, enter a name for the share. You You must use unique share names on each ExaGrid Server. In addition, ExaGrid recommends using unique share names across your ExaGrid System. Doing so will: ■

Make ExaGrid reports easier to interpret

■

Avoid share name conflicts in disaster recovery scenarios

Avoid share name conflicts if you decide to migrate a share to another ExaGrid Server. 7. Select the protocol the application backup server will use to write to the ExaGrid Share: CIFS, NFS or OST. 8. If creating a Utility share, select the amount of space assigned to the share. 9. If this is a multi-site configuration, configura tion, you may specify an ExaGrid Site to which this share will replicate its data: select Replicate data for this share to: Doing so puts an additional copy of the share’s contents on another site. Putting a copy onto another site provides an additional layer of protection for your data. ■

For example, you can create a share dedicated to full backups and keep a copy of those backups on the other site. At the same time you can create a share dedicated to incremental backups and not copy the share to the other site. Tip – For hub sites, consider replicating all shares to the same spoke. Doing so will make a disaster recovery easier and faster.

10. If the share is being replicated to another ExaGrid Site you may select a specific ExaGrid Server on the other ExaGrid Site on which the InstantDR™ share will be created. Doing so allows you to balance where data on the other ExaGrid Site is being placed. From the drop down list, select an ExaGrid E xaGrid Server on the t he other ot her ExaGrid Site.

20 ExaG ExaGri rid d Syst System ems s

Note – If your backup application supports Open Storage Technology (OST), InstantDR Shares allow you to take full advantage of OST functionality.

11. In the spaces provided, enter the share access white list information: a. In the spaces provided enter the IP address or DNS names of backup servers allowed to backup to this share. If a backup server uses multiple IP addresses, all IPs for that server must be entered in the list. b. In the spaces provided, enter the subnet mask associated with the backup servers that are allowed to write to this share. If you have specified an IP address for the backup server(s), leaving this filed blank will restrict access to the specified IP address. 12. To add the IP addresses and subnet masks, click Add. 13. Click Create .The new share confirmation screen is displayed. 14. Click OK and the new ExaGrid Share is created. Note – If you create a share and then some time later mark the share to replicate to a second ExaGrid Site, the “age” of the share’s replication queue is based on when the share was created and not when it was marked to be replicated.


Creating TempDR Shares A TempDR share is created from replicated data and is used as a new mount point for your backup job(s) while you are waiting for the site that hosts the source ExaGrid Share to come back on line. To create a TempDR Share, the ExaGrid Site that hosts the source ExaGrid Share must not be reachable by the ExaGrid Site to which it replicates. The ExaGrid Site’s unavailability may be the result of a disaster scenario or in the case of a test recover operation, the result of you manually disconnecting the host ExaGrid Site’s NIC1 connection from the network. 1. Via your web browser, log into the ExaGrid Site to which the source ExaGrid Share replicates. 2. In the ExaGrid navigation tree, select the ExaGrid Server that hosts the source ExaGrid Share. 3. In the main menu click Manage 4. From the drop down menu select Shares the ExaGrid Share page is displayed 5. Select the ExaGrid source share from which you will create the TempDR Share. 6. In the task area of the page click Create TempDR Share. The Create TempDR Share page is displayed. 7. Select the ExaGrid Server on which you want to create the TempDR Share. 8. Click Create and a TempDR Share with the same name as the source share is created.

22 ExaGrid Systems

ExaGrid Reports Because your ExaGrid System employs a unified user interface, via a single log in, you can view reports for all ExaGrid Sites and ExaGrid Servers in your ExaGrid System. ExaGrid reports use the following icons: ExaGrid System ExaGrid Site

ExaGrid Server ExaGrid Share

Backup File Collections Backup file collection NOTE: Some backup applications create multiple file collections for a single backup job. Replication and/or deduplication is in progress Replication and/or deduplication is complete

Note – The ExaGrid System is not a real time reporting system. Most reports are updated every fifteen minutes. If a report displays data that appears to be out of date, you may be viewing data between update cycles

Report data is rolled up according to what is selected in the navigation tree. When you select: ■ ■

■

The ExaGrid icon, you will see reports on the entire ExaGrid System. An ExaGrid Site name, you will see reports on all ExaGrid Servers in the selected ExaGrid Site. An ExaGrid Server, you will see reports specific to the selected ExaGrid Server.

Note – All ExaGrid reports may be exported to a file in XML format.


Summary Reports A summary report is the default report displayed when you select an item in the ExaGrid navigation tree.

Summary reports provide rolled up, high-level details on: ■ ■ ■

Landing Space Retention Space Deduplication

Landing Space Summary The ExaGrid System allows you to write your backup directly to disk, at the speed of disk, without any preprocessing. This approach requires the ExaGrid System to provide a dedicated area to write backup data. The size of this dedicated area or “landing space” varies by ExaGrid Server model. The larger the ExaGrid Server, the larger the landing space. This section of the Summary report allows you to determine whether or not there is enough landing space available on an ExaGrid Server for its next backup. In most cases the space available will be 100% of the system's rating; even if a backup job was just written to the ExaGrid Server. This is because ExaGrid Servers can dynamically allocate space from their retention space on an as needed basis. As long as your backup job size does not exceed your ExaGrid System's rating, your next backup will fit.

24 ExaGrid Systems

Note – Do not confuse landing space with the total ExaGrid System space. Landing Space size is determined by ExaGrid Server model number. It is the maximum backup size for which the ExaGrid Server has been rated. Your ExaGrid Server has much more storage space than what is reported in the landing space section of this report.

Orange Landing Space Indicator If an ExaGrid Server has retained a large number of backups, there may not be enough retention space to allocate to the landing space. In this situation, if this report is viewed while the ExaGrid Server is deduplicating a previous backup job, the space available may be less than 100% and a portion of the bar graph will turn orange to indicate how much space is used by the previous backup. As processing progresses, the space available will return to 100%.

Red Landing Space Indicator If you begin to outgrow an ExaGrid Server, the retention space may begin using space from the landing space. In this situation, the landing space available may be less than 100% and a portion of the bar graph will turn red to indicate how much space is now used as retention space. When landing space is used as retention space, it cannot be reclaimed until one of the following things happen: ■ ■ ■

The amount of retained data is reduced Shares are migrated to a different ExaGrid Server Additional ExaGrid Servers are added

When landing space is consumed by retained data, to determine if your next backup job will fit on the ExaGrid Server, compare the amount of landing space available with the amount of space required to accommodate the next backup.

Retention Space Summary Retention space is the amount of space dedicated to retaining versions of your backups. The amount of retention space varies by ExaGrid Server model. The amount of retention space consumed is determined by: ■ ■ ■

Size of backups The number of backups retained How long backups are retained ExaGrid Administrato r’s Guide 25

■

How well each backup deduplicates

If your backup requirements change and you begin to outgrow the ExaGrid Server, the retention space may begin using space from the landing space. In such cases you should evaluate the amount of data you are retaining and whether or not you need to retain less data or add capacity to your ExaGrid System.

Orange Retention Space Indicator As your ExaGrid System begins to retain deduplicated versions of backups, the space consumed by those retained backups will be represented by the “Orange” portion of the Retention Space Indicator. The orange portion of the indicator will continue to grow until your backups reach their defined retention period. At that time, the growth of the orange portion of the indicator will stabilize as new versions of your backups are retained and your backup application removes versions that exceed its defined retention period.

Red Retention Space Indicator If you begin to exceed the rating of your ExaGrid System i.e. writing 5.3TB of data to an EX5000, the ExaGrid Server will try to accommodate the backup by borrowing space from its retention space. That “borrowed” space will be represented in red on the Retention Space Indicator. In such cases you must consider either restructuring your backup jobs or adding more capacity to your ExaGrid System.

Deduplication Summary This section provides a high-level view of how well your data is deduplicating. The deduplication ratio shows how well your backups are deduplicating. The deduplication ratio is based on the total amount of backup data written and the amount of space actually consumed after deduplication. Note – Each time a backup job runs, you will see increasingly better data deduplication ratios.

26 ExaGrid Systems

Replication Reports Replication reports provide detailed information about backup data replicating between ExaGrid Sites. Replicated data may be reported by: ■ ■ ■

Server Share File collection - A file collection is a set of backup files that have landed on an ExaGrid Server during a specified period of time.

You may view replication reports by selecting Reports in the main menu, then from the drop down menu select a table-based report of: ■ ■

In Progress Completed

Table-based Replication Reports The Replication In Progress and Completed reports are displayed in a table format and displays information down to the file collection level. You may set a date range for the data reported. For example: From this report you can determine the amount of data transferred and when it was transferred. Large swings in the amount of data transferred may indicate that something major has changed in a backup job. A detailed description of replication tabular reports can be found in the ExaGrid online help.

Graph-based Replication Reports You can display graph-based reports for the Replication Queue History, Transfer History or Transfer Rate History for a selected ExaGrid Server(s) for the backup jobs written to an ExaGrid Server.


The following is an example of a Replication Queue History by backup Server report:

Graph-based reports allow you to easily see trends in your ExaGrid System’s replication. The graphs also provide controls that allow you to filter out individual items and to zoom into more detailed dates and times. A detailed description of replication graph-based reports can be found in the ExaGrid online help.

28 ExaGrid Systems

Deduplication Reports Deduplication reports provide detailed table-based information about how data in your ExaGrid System is deduplicating. Deduplicated data may be reported by: ■ ■ ■

Server Share File collection - A file collection is a set of backup files that have landed on an ExaGrid Server during a specified period of time.

You may view deduplication reports by selecting Reports in the main menu, then from the drop down menu select either: ■ ■ ■

In Progress Completed By Share

From this report you can determine the amount of data actually backed up, the amount of space it consumes on the ExaGrid Server, deduplication ratio for each file collection as well as a roll up of the deduplication ratio for all file collections. A detailed description of replication table-based reports can be found in the ExaGrid online help.


Monitoring Your ExaGrid System As detailed in “ExaGrid Reports” on page 23 the ExaGrid system allows you to manually log in and view the status of your ExaGrid System. In addition, the ExaGrid System also provides several automated tools that monitor and report status.

SMTP Email Notifications You may configure the ExaGrid System to automatically send you or others in your organization an email when the ExaGrid System generates an event. You may also configure the ExaGrid System to send a daily status report. The status report consists of a summary of the ExaGrid System’s landing space, retention space deduplication and optionally detailed backup information. The daily status report may be sent at a specific hour of the day, to several individuals in your organization, and may be sent in HTML, or text format. Setting the format to NONE will disable sending the status report to the associated email address. To display the SMTP Email configuration page: 1. 2. 3. 4.

From the Navigation Tree, select an ExaGrid Site. From the main menu, click Manage. From the drop down menu, select Alert Configuration . From the secondary menu, select SMTP Email. The SMTP page is displayed.

The online help has detailed instructions on how to setup SMTP Email alerting.

30 ExaGrid Systems

SNMP Traps You may also configure your ExaGrid System to send alerts about events in the ExaGrid System via SNMP traps. To display the SNMP Trap configuration page: 1. 2. 3. 4.

From the Navigation Tree, select an ExaGrid Site. From the main menu, click Manage. From the drop down menu, select Alert Configuration . From the secondary menu, select SNMP Traps. The SNMP Traps page is displayed.

The online help has detailed instructions on how to setup SNMP Trap alerting. Configure your MIB browser to use SNMP V2. If you plan to use an SNMP management application, such as Hewlett-Packard’s OpenView, you can download the ExaGrid Management Information Base (MIB): 1. In the ExaGrid user interface’s Main menu click Help. 2. From the drop down menu select Online Library. The ExaGrid Online Library is displayed. 3. Scroll down and right-click on ExaGrid Grid SNMP Management Information Base (MIB) and save the MIB file to your required location.

Status Monitor Your ExaGrid System has a “phone home” capability. The Status Monitor allows you to configure your ExaGrid System to send system information back to ExaGrid Support. Reports are ExaGrid Site specific. Customers with multiple ExaGrid Sites can set up status monitoring for each of their ExaGrid Sites. ExaGrid Support will automatically run tools against the report. Potential issues can be identified long before they become a problem. You may send reports to ExaGrid via FTP or email. To configure the Status Monitor for an ExaGrid Site: 1. From the Navigation Tree, select an ExaGrid Site. 2. From the main menu, click Manage. ExaGrid Administrato r’s Guide 31

3. From the drop down menu, select Status Monitor. The Status Monitor page is displayed.

ExaGrid MIB The ExaGrid MIB is made up of industry standard MIB and ExaGrid specific MIB objects. A copy of the ExaGrid MIB file can be found in the ExaGrid Online Library. To save a copy of the ExaGrid MIB file: 1. 2. 3. 4.

From the main menu, click Help. From the drop down menu, click Online Library. The online library is displayed. Scroll down the library entries and right click on the ExaGrid MIB file. From the pop up menus, click Save as... and save the MIB file with a name and to a location as needed

Note – Before you can use the ExaGrid MIB, you must enable SNMP on each ExaGrid Server you want to monitor.

To enable SNMP on an ExaGrid Server: 1. From the ExaGrid navigation tree, select an ExaGrid Server

32 ExaGrid Systems

2. From the main menu select Identification . The Identification page is displayed:

3. On the Identification page configure the following SNMP fields: Field

Description

SNMP location

The MIB-2 system group sysLocation

SNMP System Contact

The MIB-2 system group sysContact

SNMP v2c Read Community String

Must be set to Public

Enable Access to SNMP Agent

Must be checked to enable SNMP reporting for the ExaGrid Server.

Standard MIB Objects The ExaGrid MIB supports the following “standard” MIB objects: ■ ■

■

System group from RFC 1213. See table below. The entire “ifMIB” Module (Interface MIB) – this includes 64 bit counters useful for network utilization calculations. Host resources The hrStorage table is implemented. This table includes memory statistics including total memory available (hrStorageSize) and memory used (hrStorageUsed). ■


■

The Host Resources hrProcessorLoad MIB object is implemented for all processors. This MIB object contains: The average, over the last minute, of the percentage of time that this processor was not idle.

ExaGrid MIB Objects ExaGrid MIB objects are made up of WholeGigaBytes and FractionalGigabytes. A 32 bit gauge does not hold values large enough to represent the bytes counts found in an ExaGrid System. To accommodate the 32 bit limitation each data item has been broken into two 32 bit counters, one for the “whole” part and one for the “fractional” part. The “whole” part contains a scaled truncated value representing GigaBytes. The fractional part contains the remainder in bytes. For example, to determine the byte count for a landing space objects, multiply the egLandingSpaceConfiguredWholeGigabytes value by 1,000,000,000 (10 9) and then add the egLandingSpaceConfiguredFractionalGigabytes.

ExaGrid Object Tree The ExaGrid MIB specifies the following object tree: exagridServerData (branch) ■

■

■

34 ExaGrid Systems

exagridLandingSpace (branch) ■

egLandingSpaceConfiguredWholeGigabytes (32 bit Gauge)

■

egLandingSpaceConfiguredFractionalGigabytes (32 bit Gauge)

■

egLandingSpaceAvailableWholeGigabytes (32 bit Gauge)

■

egLandingSpaceAvailableFractionalGigabytes (32 bit Gauge)

exagridRetentionSpace (branch) ■

egRetentionSpaceConfiguredWholeGigabytes (32 bit Gauge)

■

egRetentionSpaceConfiguredFractionalGigabytes (32 bit Gauge)

■

egRetentionSpaceAvailableWholeGigabytes (32 bit Gauge)

■

egRetentionSpaceAvailableFractionalGigabytes (32 bit Gauge)

exagridDeduplicationRatio (branch) ■

egBackupDataAvailableWholeGigabytes (32 bit Gauge)

■

egBackupDataAvailableFractionalGigabytes (32 bit Gauge)

■

egBackupDataSpaceConsumedWholeGigabytes (32 bit Gauge)

■

egBackupDataSpaceConsumedFractionalGigabytes (32 bit Gauge)

■

■

■

exagridPendingDeduplication (branch) ■

egPendingDeduplicationWholeGigabytes (32 bit Gauge)

■

egPendingDeduplicationFractionalGigabytes (32 bit Gauge)

■

egPendingDeduplicationAge (timeticks)

exagridPendingReplication (branch) ■

egPendingReplicationWholeGigabytes (32 bit Gauge)

■

egPendingReplicationFractionalGigabytes (32 bit Gauge)

■

egPendingReplicationAge (timeticks)

exagridServerStatus (branch) ■

egServerAlarmState (integer) 1.No alarms 2. One or more minor alarms outstanding (warning/yellow) 3. One or more major alarms outstanding (error/red)

How to Calculate ■

Retention Capacity The amount of unused retention space available is found by querying the egRetentionSpaceAvailableWholeGigabytes and egRetentionSpaceAvailableFractionalGigabytes MIB objects, scaling the whole portion and then adding the fractional portion.

■

Deduplication Ratios Query all 4 objects in the exagridDeduplicationRatio group, scale the returned values to 64 bits and then convert available/consumed into a ratio.

■

CPU utilization Average for the most recent minute CPU utilization is directly available as the hrProcessorLoad MIB object.

■

Memory utilization Point in time memory utilization is directly available as the hrStorageUsed column in the appropriate row in the hrStorage table. The row index may change with each SNMP agent restart, so the hrStorageType object must be queried to determine the correct index to use.

■

Network Utilization


Several MIB objects supplied by the ifXTable in the ifMIB can assist in determining Network Utilization. Of particular interest are: ifHCInOctets and ifHCOutOctets. ifHCInOctets is defined as: The total number of octets received on the interface, including framing characters. This object is a 64-bit version of ifInOctets” Note – Cisco has published an article titled How to calculate bandwidth utilization using SNMP. It is available at: http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a008009496e.shtml

This article describes how these counters can be used over time to determine network utilization. With full duplex media, two formulas are required, one for input and one for output. The ifInOctets and ifOutOctets high capacity counters should be polled keeping track of the time between polls. The Formulas become: input utilization = change in ifInOctets * 8 * 100 / pollSeconds * ifSpeed output utilization = change in ifOutOctets * 8 * 100 / pollSeconds * ifSpeed

36 ExaGrid Systems

Configuring Uninterruptible Power Supplies (UPS) Each ExaGrid System requires an uninterruptible power supply (UPS). To protect your ExaGrid System, your UPS management console must execute an ExaGrid perl script that, during an unplanned power event, will facilitate an orderly shutdown of the ExaGrid System. Your UPS must: ■

■ ■

■

Provide enough power to hold up the ExaGrid System for at least five (5) minutes while the ExaGrid System shuts down. After five minutes, power down the ExaGrid System. Automatically power up the ExaGrid System after power is restored and the UPS batteries have been recharged at least 90 percent. Be configured in such a way as not initiate a shutdown sequence for minor power events.

Power Off Script A copy of the ExaGrid power off perl script (PowerOffExagrid.pl) resides in the ExaGrid Manager’s Online Library. Download a copy of the script from the library and use the script in conjunction with your UPS Management software to facilitate a clean shut down of your ExaGrid Site. To download a copy of the perl script: 1. From the ExaGrid user interface’s main menu, click Help . 2. From the drop down menu, click Online Library. The online library is displayed. 3. Scroll down to, then right-mouse click ExaGrid UPS Integration Script .


4. Save a copy of the script to a location where it can be executed by your power management software.

Power Off Script Parameters Calls to the powerOffExagrid.pl perl script use the following parameters: 1. -ip
Where
is the IP address of an ExaGrid Server in the Site being protected. The ExaGrid Server selected will coordinate the clean shutdown of the other components in the Site. 2. -port Where is the ExaGrid Server’s port number. The default port number is 80. 3. -user Where is the ExaGrid Server’s admin account’s user name 4. -pass Where is the ExaGrid Server’s admin account’s password 5. -omitMe -omitMe option is only used if the script is running on an ExaGrid Server. It prevents the ExaGrid Server from powering off before the UPS has had a chance to properly power off the other Site components. 6. -skip < ip address>, Where are the ip addresses of other ExaGrid Servers in the Site that are protected by another UPS device.

38 ExaGrid Systems

Using powerOffExagrid.pl Note – How powerOffExagrid.pl is integrated into and called from a UPS management station is unique to each UPS manufacturer. Consult your UPS management station documentation for details.

To use the powerOffExagrid.pl perl script: 1. 2. 3. 4.

Create or edit your existing UPS command file (.cmd). Include a call to powerOffExagrid.pl in the .cmd file. In the call to powerOffExagrid.pl, use all parameters that pertain to your system. Via your UPS management console, include the .cmd file in the list of tasks that must be performed during a power event.

Example powerOffExagrid.pl Command Line The following is an example power off command line used within a .cmd file: powerOffExagrid.pl -ip 10.168.0.1 -port 80 -user admin -pass xxxxx -omitMe -skip 10.168.0.2


IPMI Network Port An IPMI port is are located in the back of you ExaGrid Servers. The actual location varies by ExaGrid Model, but like NIC posts, IPMI ports are clearly labeled. Warning – The following procedure exposes a system interface, that if improperly used can cause a loss of data and void your system warranty.

For ExaGrid Servers with IPMI network ports, you may configure the IPMI network port as follows: 1. In the ExaGrid navigation tree, select the ExaGrid Server whose IPMI network port you want to configure. 2. From the Manage drop down menu, select Network. 3. From the secondary menu select IPMI Configuration and the IPMI network Configuration page is displayed:

4. In the spaces provided enter: a. An IP address 40 ExaGrid Systems

b. A subnet mask c. Gateway IP 5. Click Apply and the IPMI network port will be configured.

Resetting the IPMI Network Port User Password The default user name and password for the IPMI network port are: ADMIN/ADMIN. All capital letters. Caution – ExaGrid recommends that you change the default password.

Warning – ExaGrid cannot retrieve lost passwords. If a password is lost, your data is at risk.

To change the password: 1. Enter the IPMI network port address via a web browser session and the login page is displayed:


2. Log into the page with the login username and password and the System Information page is displayed:

3. In the main menu, click Configuration and the configuration page is displayed:

42 ExaGrid Systems

4. From the Options list, click Users and the user list is displayed:

5. Select the ADMIN user. 6. Click Modify User and the Modify User page is displayed:

7. In the spaces provided, enter the new password. 8. Click Modify, and the password is changed.


Using the IPMI Network Port To use the ExaGrid IPMI network port: 1. Enter the IPMI network port address via a secure (HTTPS) web browser session and the login page is displayed:

2. Log into the page with the login username and password and the System Information page is displayed:

44 ExaGrid Systems

3. In the main menu, click the Remote Control tab and the Remote Control page is displayed:

4. Click Remote Console and a command window is displayed:

5. At the Please enter the pass phrase: prompt, enter the Encryption password you assigned to ExaGrid Servers in this ExaGrid Site. 6. Press Enter and the ExaGrid Server will reboot. 7. Repeat this process for each ExaGrid Server in your ExaGrid Site.


IPMI and NIC Ports Your ExaGrid Server may be configured with two, four or six NICs. In addition, your ExaGrid Server has an IPMI port. All of which are clearly labeled. Caution – For systems with six NICs, pay close attention to the positions of NICs 5 and 6 IPMI

NIC2

NIC3

NIC1

NIC4

NIC6 NIC5

ExaGrid 2U Server IPMI and NIC Port Locations. Optional NICs 5 and 6 Shown

IPMI

NIC1

NIC6

NIC3

NIC2

NIC5

NIC4

ExaGrid 3U Server IPMI and NIC Port Locations NIC locations vary from model to model, and are clearly labeled. The NIC locations on your ExaGrid Server may differ from what are called out in these illustrations.

46 ExaGrid Systems


Using Server Message Block (SMB) Signing Note – SMB applies only to CIFS shares, not Symantec OpenStorage or NFS shares.

SMB Signing is a feature that allows communications to be digitally signed at the packet level. Digitally signing the packets enables the recipient of the packets to confirm their point of origination and their authenticity. This security mechanism in the SMB protocol helps avoid issues like tampering of packets and “man in the middle” attacks. SMB signing does not encrypt data. In addition, SMB signing augments the ExaGrid Share whitelist to control who and what has access to the backup data on ExaGrid Shares. To use SMB signing with your ExaGrid System you must: ■

Enable SMB signing on your Microsoft ® Windows® backup servers through either: ■

■

Enabling the Local Security Policy for the Microsoft network client: Digitally signed communications (always). Setting up a security policy that includes the enabled Microsoft network client: Digitally signed communications (always) on a Windows domain through the use of Group Policy Objects (GPO), and applying it to the backup server.

To ensure these changes are fully in place, restart your backup server. Caution – Backups must not be running while you are enabling SMB signing.

Caution – Once SMB signing is enabled, you must specify credentials on your backup application and on the ExaGrid System. Not doing so will cause your backups to fail. ■

■

Determine which local windows account (NOT the local system account) or domain account credentials you will specify in your backup application and on the ExaGrid System. Enable and define security credentials on your ExaGrid System:

1. In the navigation tree, click ExaGrid 2. From the main menu, click Manage

48 ExaGrid Systems

3. From the drop down menu select Security Credentials and the Security Credentials Configuration page is displayed. 4. Click the online help link in the upper right-hand corner of the Security Credentials Configuration page for instructions on how to configure credentials. The credentials you specify on the ExaGrid System must match an existing local or domain user account. Domain accounts must be entered without the domain information. ■

Define long in credentials in you backup application as detailed in the ExaGrid documentation for your backup application.

Character Set Allowed for SMB User Names The character set allowed for user names defined in the ExaGrid System are: ■

User names must not contain more than 32 characters

■

User name must begin with an upper or lower case letter A-Z or a-z

For the rest of the name, you may use any of the following: ■ ■ ■

Upper/lower case A-Z Numeric 0-9 . - _ (period, hyphen, underscore)

Although Windows® accepts more characters than this set, your ExaGrid System is Linux-based and therefore restricts the list of allowable characters.


Character Set Allowed for SMB Passwords The character set allowed for passwords defined in the ExaGrid System are: ■

■

■ ■

■

50 ExaGrid Systems

Uppercase characters of European languages (A through Z, including diacritic marks, Greek and Cyrillic characters) Lowercase characters of European languages (a through z, sharp-s, including diacritic marks, Greek and Cyrillic characters) Base 10 digits (0 through 9) The following non-alphanumeric characters:

Any Unicode character that is categorized as an alphabetic character but is not uppercase or lowercase. This includes Unicode characters from Asian languages.

Restoring Files All restores are done via your backup application. From you backup application’s perspective, there is no difference between restoring from an ExaGrid System and a tape system. Consult your backup application’s documentation for details on how to restore data.


ExaGrid System Maintenance Management and maintenance tasks for your ExaGrid System include: 1. 2. 3. 4. 5.

52 ExaGrid Systems

Shutting down and restarting ExaGrid Servers Managing ExaGrid accounts Adding additional ExaGrid Servers Software upgrade Record keeping

Shutting Down and Restarting an ExaGrid Server Caution – NEVER shut down or restart an ExaGrid Server by cutting power or pressing the power or restart buttons on the front panel. ExaGrid Servers must be shutdown or restarted via the ExaGrid user interface.

To shut down an ExaGrid Server: 1. In the navigation tree, select the ExaGrid Server to be shut down. 2. From the main menu, click Manage . 3. From the drop down menu, click Administrative State . The Administrative State page is displayed. 4. Click Shutdown . To restart an ExaGrid Server: 1. In the navigation tree, select the ExaGrid Server to be restarted. 2. From the main menu, click Manage . 3. From the drop down menu, click Administrative State . The Administrative State page is displayed. 4. Click Restart.

Account Management Admin accounts are used to access the ExaGrid System. The ExaGrid Manager Admin account comes with a default password. The account name and password were given to you when your system was installed. ExaGrid recommends that you change the default passwords.


Admin Accounts Use the ExaGrid Manager Admin account to perform management tasks and view reports. The default user name is admin. The default password was given to you when your ExaGrid System was installed. When logged into an ExaGrid Manager Admin account, you can manage all devices in the Site.

Changing ExaGrid Admin Passwords To change an ExaGrid Admin account password: 1. From a web browser, enter the URL or IP address of a ExaGrid Site’s ExaGrid Server. For example: http://ExaGridName or http://192.168.55.3. You can specify any ExaGrid Server but the one closest to your location will have the best network performance. 2. At the log in prompt, enter the Admin user name and password and click OK. 3. From the navigation tree, select an ExaGrid site. 4. In the main menu, click Manage . 5. From the drop down menu, select Administrators . 6. In the right-hand frame, select the Admin account and click Modify Login. 7. Enter a new password in the Password box. Passwords may contain any character. 8. Click Apply. The new password will be set.

54 ExaGrid Systems

Adding Additional ExaGrid Servers As your backup requirements grow, you may find it necessary to add additional ExaGrid Servers to your ExaGrid System. Note – Step-by-step instructions on how to install and initialize a new ExaGrid Server can be found in the Assembling and Initializing Your ExaGrid System guide that came with your new ExaGrid Server.

When you add an ExaGrid Server, you not only increase the amount of storage space in your ExaGrid System, you also increase the system’s ability to take in and process backup data. More ExaGrid Servers mean more memory, CPUs and ports over which backup data can flow. When a new ExaGrid Server is added, the ExaGrid System will automatically redistribute retained backup versions to balance the storage load across the ExaGrid Servers. Note – Adding a new server will not automatically move (migrate) shares to a new server. Share migration is a manual process.

To take advantage of the additional ports on the new ExaGrid Server(s): 1. Evaluate existing shares and the jobs writing to them to identify which shares, if moved (migrated) to the new ExaGrid Server, would improve your backup throughput. 2. Migrate the share(s) to the new ExaGrid Server(s). 3. Redirect backup job(s) to the new share location. Note – Consult the ExaGrid System’s online help for instructions on how to migrate a share.


Adding an ExaGrid Site to an ExaGrid System The ExaGrid System uses a hub and spoke topology. Every ExaGrid System has one hub site. A single-site ExaGrid System is a hub site. Multi-site systems have one hub and may have one or more spoke sites. In most cases, ExaGrid Hub and Spoke Sites will be designated as such during the initialization process. To add an ExaGrid Site designated as ExaGrid Spoke Site to an ExaGrid System: 1. In the left-hand navigation tree, select the ExaGrid icon. 2. In the main menu, click Manage, 3. From the drop down menu, select Add Spoke. The Adding a New Spoke page is displayed. 4. In the space provided, enter the IP address of the spoke to be added. To find the IP address of the ExaGrid Site, via a web browser, navigate to an ExaGrid Server in the ExaGrid Site. In the ExaGrid navigation tree, place your mouse cursor over the ExaGrid Site’s name. The displayed tool tip contains the ExaGrid Site’s IP address. For example:

In some cases you may want an existing, single-site ExaGrid System to be joined with another ExaGrid Site. To do so, via the ExaGrid user interface you must: 1. Reconfigure the existing single-site ExaGrid System as an ExaGrid Spoke Site. 2. Join the newly designated ExaGrid Spoke Site to an ExaGrid Hub Site.

56 ExaGrid Systems

Reconfiguring a Single-site as a Spoke Site Note – Only single-site ExaGrid Systems can be reconfigured as an ExaGrid Spoke Site.

The ExaGrid Site in a single-site ExaGrid System is an ExaGrid Hub Site. To reconfigure the ExaGrid single-site as an ExaGrid Spoke Site: 1. Log into an ExaGrid Server on the ExaGrid System to be redesignated as an ExaGrid Spoke Site. 2. In the ExaGrid user interface’s navigation tree, click ExaGrid . 3. In the main menu click Manage . 4. From the drop down menu click Network . 5. From the secondary menu, click Topology. The Change Topology page is displayed. 6. Click Make Spoke . The site will be redesignated as a spoke.

Joining an ExaGrid Spoke Site to an ExaGrid Hub Site To join an ExaGrid Spoke Site to an ExaGrid Hub Site: 1. 2. 3. 4. 5. 6.

Log into an ExaGrid Server on the hub site. From the navigation tree, select ExaGrid. In the main menu, click Manage . From the drop down menu, select Add Spoke. In the space provided, enter the IP address of the ExaGrid Spoke Site. Click Add and the ExaGrid Spoke Site will be joined with the ExaGrid Hub Site.


Software Upgrade Software upgrades are available through your ExaGrid Technical Support Representative. Upgrades can be downloaded from the ExaGrid Support web site, or a copy can be sent to you. To view the Software Upgrade page: 1. In the ExaGrid user interface’s navigation tree, select an ExaGrid Site. 2. In the main menu, click Manage . 3. From the drop down menu, select Software Upgrade . The Software Upgrade page is displayed. From the software upgrade page you can: ■

■

■

■ ■ ■

Determine the current version and status of ExaGrid Software across the selected ExaGrid site. Review the list of upgrade packages that have been uploaded and currently available to be installed. Enter a path, or browse to, an upgrade package to be uploaded to this ExaGrid site. Test/Retest an uploaded upgrade package. Apply an ExaGrid upgrade package to the selected site. Remove upgrade packages once they have been applied.

NTP Servers The ExaGrid Hub Site is set at the time of manufacture to use the public NTP server pool to synchronize time. ExaGrid Spoke Sites are configured by default to use the ExaGrid Hub Site as their NTP server(s). You may make changes to the ExaGrid Hub Site’s factory defaults as needed. Caution – For ExaGrid Spoke sites, using an NTP server other than their ExaGrid Hub Site may cause unexpected results.

To display an ExaGrid Site’s NTP Settings: 1. In the ExaGrid user interface, select the ExaGrid Site. 2. In the main menu, click Manage

58 ExaGrid Systems

3. From the drop down menu, select Time and the NTP settings page is displayed:

NTP Settings page for an ExaGrid Hub Site

NTP Settings page for an ExaGrid Spoke Site

Windows® NTP Servers If you use a Microsoft ® Windows® server as an NTP server, that server must be running Windows 2008R1 or later. To enable NTP Service on Windows: 1. On the Windows NTP server, from the Start menu, start the Run application:


2. In the space provided enter regedit and click OK. The Registry Editor is displayed. 3. Locate and then expand the following registry entry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\

4. In the right pane, right-click AnnounceFlags, then click Modify.

5. In the Edit DWORD Value dialog box, under Value data, enter 5, and then click OK. 6. Locate and then expand the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\ TimeProviders\NtpServer\

60 ExaGrid Systems

7. In the right pane, right-click Enabled , and then click Modify.

8. In the Edit DWORD Value dialog box, enter 1 under Value data, and then click OK. 9. Exit the Registry Editor. 10. At the command prompt, run the following command to restart the Windows: net stop w32time && net start w32time


Record Keeping ExaGrid recommends that you keep detailed records for each share. Whether online or paper, keep the records in a secure place. The contents of a share record will aid current and future members of your organization. The following is an example of a share record.

Share Record Form Share name: Date created:

Created by:

Date modified:

Modified by

Date deleted:

Deleted by:

Replicated to a second Site

Yes____

No____

Yes____

No____

Backup Server Type Type of data being backed up Copy to tape

62 ExaGrid Systems

Encryption Capable ExaGrid Servers Encryption Capable ExaGrid Servers run the same ExaGrid software as other ExaGrid Servers, with the added features of Encryption at Rest and Boot Protection. You may not mix Encryption Capable and non-Encryption Capable ExaGrid Servers in an ExaGrid System. Encryption Capable ExaGrid Server’s can be identified by the -SEC suffix appended to their name. For example: EX13000E-SEC. Encryption at Rest and Boot Protection are enabled via the ExaGrid user interface at the ExaGrid Site level. This ensures that all ExaGrid Servers in a site use the same settings and password. Warning – ExaGrid cannot retrieve lost passwords. If a password is lost your data is at risk.

Encryption at Rest Warning – ExaGrid cannot retrieve lost passwords. If a password is lost your data is at risk.

When Encryption at Rest is enabled, if a disk is removed from an Encryption Capable ExaGrid Server, its data is encrypted and cannot be read. However, if the entire Encryption Capable ExaGrid Server is removed it can be restarted and its data can be read.


Once Encryption at Rest has been enabled and the password established, it cannot be disabled. Warning – You will be required to provide your Encryption at Rest password if an Encryption Capable ExaGrid Server is replaced as a result of a disaster or if your ExaGrid Server requires a major overhaul i.e. chassis swap, new RAID card, etc. In such cases, if you can not provide your password, all of your data will be lost .

Encryption at Rest Passwords Warning – ExaGrid cannot retrieve lost passwords. If a password is lost your data is at risk.

Encryption at Rest passwords: ■ ■ ■ ■

Are case sensitive Must be between 8 and 32 characters Must not contain the character Must contain at least One number One lowercase letter One uppercase letter One non-alphanumeric character from the set: @#^*-_=+ ■ ■ ■ ■

Note – If you can not enable or change your Encryption at Rest password, check for a failed drive or a drive logging errors in your system. Follow normal support procedures to replace the problem drive. Encryption at Rest password management will function normally once the problem drive is replaced.

Enabling Encryption at Rest When an ExaGrid Encryption Capable Server is first initialized it appears in the ExaGrid navigation tree in an “alarmed state” until you explicitly enable or opt out of the security Encryption at Rest and/or Boot protection.

64 ExaGrid Systems

If you mouse over the ExaGrid Site name, details about the alarm are displayed:

To enable or opt-out of Encryption at Rest: 1. 2. 3. 4.

In the left-hand navigation tree, select the ExaGrid Site From the main menu, click Manage From the drop down menu select Security. From the secondary menu, select Encryption at Rest and the Encryption at Rest Management page is displayed:

5. Click Configure and the Enable Encryption at Rest dialog box is displayed:


6. Select either: a. No, do not enable Encryption at Rest now . Doing so will clear the Encryption at Rest alarm and does not apply a password for encryption at rest. You may revisit this page at another time and enable Encryption at rest b. Yes, enable Encryption at rest Now. Doing so will require you to enter a new password. Warning – ExaGrid cannot retrieve lost passwords. If a password is lost your data is at risk.

7. Click Apply and your selection will be applied:

Adding a New Encryption Capable Server to a Site To add a new Encryption Capable server to an Encryption Capable ExaGrid Site: 1. Initialize the ExaGrid Server and add it to the site as detailed in the ExaGrid Assembling and Initializing your ExaGrid Server guide. 2. When the server has been initialized and added to the site, in the left-hand navigation tree, select the ExaGrid Site. 3. From the main menu, click Manage . 4. From the drop down menu, select Security.

66 ExaGrid Systems

5. From the secondary menu, select Encryption at Rest and the Encryption at Rest Management page is displayed:

6. In the space provided, enter the site’s Encryption at Rest password. Warning – ExaGrid cannot retrieve lost passwords. If a password is lost your data is at risk.

7. Click Confirm Password and the ExaGrid Servers in the site are listed. The new ExaGrid Server will be listed as Not Configured.

Click the Configure button and the new ExaGrid Server will be configured with the same password and boot protection setting as the other ExaGrid Servers in the site.


Server’s Encryption Password Does Not Match Site’s Password In the rare event that an Encryption Capable Server’s password does not match that of the other servers in a site, the ExaGrid navigation tree will display an alarm:

Navigate to the Encryption at Rest Management page: 1. 2. 3. 4.

In the left-hand navigation tree, select the ExaGrid Site. From the main menu, click Manage From the drop down menu, select Security. From the secondary menu, select Encryption at Rest and the Encryption at Rest Management page is displayed:

5. In the space provided, enter the site’s Encryption at Rest password. Warning – ExaGrid cannot retrieve lost passwords. If a password is lost your data is at risk.

68 ExaGrid Systems

6. Click Confirm Password and the ExaGrid Servers in the site are listed. The new ExaGrid Server will be listed as having an Incorrect Password.

7. Click the Update Password button and the update password dialog box is displayed:

8. In the space provided, enter the current Encryption at Rest password for the server. Warning – ExaGrid cannot retrieve lost passwords. If a password is lost your data is at risk.

9. Click Update , and if you entered the correct password, the server will use the same password as the other servers in the site.


Boot Protection Warning – ExaGrid cannot retrieve lost passwords. If boot protection is enabled and the password is lost, at the next reboot your data will be inaccessible until the Encryption at Rest password is provided .

To enable Boot Protection, you must contact ExaGrid Support. Boot Protection uses the Encryption at Rest password. An Encryption Capable ExaGrid server encrypts the data on its disks. If a disk is taken, its data is encrypted and cannot be read. Enabling boot protection will protect data even if the entire server is taken. When a server with Boot Protection is restarted, data cannot be accessed until the Boot Protection encryption password is provided. ExaGrid recommends using the IPMI network port at the back of your Encryption Enabled ExaGrid Server. Doing so will facilitate entering your encryption password when your ExaGrid Server is rebooted. See “Using the IPMI Network Port to Enter Boot Protection Password” on page 72. for details on how to setup and use your ExaGrid Server’s IPMI network port. Software upgrades, system maintenance, power events can all require or cause system reboots. Each rebooted system will require a console connection to enter the boot protection password. Tip – For system maintenance procedures that require reboots, deactivate Boot Protection for the duration of the procedure. Once complete, reactivate Boot Protection.

Enabling Boot Protection Call ExaGrid Support. Your ExaGrid Customer Support representative will via remote login, enable boot protection on your Encryption Enabled ExaGrid Servers. Once Boot Protection is enabled: 1. In the left-hand navigation tree, select the ExaGrid Site 2. From the main menu, click Manage 3. From the drop down menu select Security.

70 ExaGrid Systems

4. From the secondary menu, select Encryption at Rest and the Encryption at Rest Management page is displayed:

5. In the space provided, enter the Encryption Password. 6. Click Confirm Password and the Encryption Management page will display the encryption details for the selected ExaGrid Site:

7. Click Configure and the Encryption at Rest Settings dialog box is displayed:

8. From this dialog box you can change the current Encryption at Rest password and/or enable/disable Boot Protection. 9. Make your selections as needed.


10. Click Apply and you will be prompted to ensure that you want to enable Boot Protection:

11. If you enabled Boot Protection, the Encryption at Rest Management details page is updated with the Boot Protection listed as On:

Using the IPMI Network Port to Enter Boot Protection Password Each ExaGrid Sever has an IPMI network port that you can configure. 72 ExaGrid Systems

Using the IPMI network port will facilitate entering your encryption password when boot protection is enabled. See “IPMI and NIC Ports” on page 46. to identify the location of these ports. Warning – The following procedure exposes a system interface, that if improperly used can cause a loss of data and void your system warranty.

Configuring the IPMI Network Port For ExaGrid Servers with IPMI network ports you may configure the IPMI network port as follows: 1. In the ExaGrid navigation tree, select the ExaGrid Server whose IPMI network port you want to configure. 2. From the Manage drop down menu, select Network . 3. From the secondary menu, select IPMI Configuration and the IPMI network Configuration page is displayed:

4. In the spaces provided enter: a. An IP address b. A subnet mask c. Gateway IP 5. Click Apply and the IPMI network port will be configured.


ExaGrid System Disaster Recovery In the event of a catastrophic event where an entire ExaGrid site is no longer available, the data from the lost site can be recovered if: ■ ■ ■

The lost site was part of a multi-site system The second site is still available Shares on the lost site were configured to replicate to the second site

To perform a disaster recovery, in your surviving ExaGrid System’s online library, consult: ■

■

74 ExaGrid Systems

The ExaGrid Disaster Recovery Guide. This guide provides step-by-step instructions on how to recover your lost ExaGrid System. Once the ExaGrid System has been recovered, consult the ExaGrid application guide for your backup application. This guide provides step-by-step instructions on how to recover your data via your backup application.

Troubleshooting In the unlikely event that your ExaGrid System experiences a failure, use this section to help troubleshoot that failure.

ExaGrid Status Monitor The ExaGrid Status Monitor provides a window in to the background operations of your ExaGrid System. The Status Monitor is useful to determine the status of an operation that typically takes an extended period of time: For example: ■

■ ■

An ExaGrid Share migration, depending on how much data is being moved can take some time to complete. Initial replication of data. RAID rebuild.

In addition, in the unlikely event that your ExaGrid user interface becomes unresponsive, you can use the status monitor to determine the status of your ExaGrid System. To display the status monitor: 1. In a browser’s address space, enter the IP address or DNS name of the ExaGrid of interest. 2. Follow the address with the port of :9080


3. Press return and the ExaGrid Status Monitor is displayed:

Disk Failure Depending upon the model, an ExaGrid Server chassis contains 12, 14, 16 or 24 disk drives. Each ExaGrid Server has RAID 6 with a hot spare. This means that an ExaGrid Server can lose up to three disks and continue functioning. However, to ensure optimum performance, failed disks should be replaced as soon as possible. Replace the disk in accordance with the maintenance plan that came with your ExaGrid Server. If an ExaGrid Server disk fails, an alert will be generated indicating that the failure has occurred and which disk has failed. The alert will be sent to all users who normally receive email alerts from your ExaGrid System. The alert message will also appear in the Events report in the ExaGrid System’s user interface. ExaGrid Server disk failure alerts will contain the disk number that failed. See “Disk Numbering” on page 78 for disk locations.

76 ExaGrid Systems

Removing Disks Before physically removing a disk from an ExaGrid System, first go to the Disk Management page and perform a software removal of the disk. 1. In the navigation tree select the ExaGrid Server that contains the disk to be removed. 2. From the main menu click Manage 3. From the drop down menu select Disk and the Disk Management page is displayed. 4. Follow the instructions on the page to perform a software remove and get status of other disks in the ExaGrid Server.

Disk Safety Halt Protection ExaGrid Servers use RAID 6 with a hot spare. Disk Safety Halt is initiated if an ExaGrid Server’s RAID is degraded because: ■

Two drives are in a failed state and there is no spare. The ExaGrid Server will automatically go into Disk Safety Halt mode. Once the failed drives are replaced, the ExaGrid Server ’s RAID will rebuild and will resume operation.

or ■

Two drives fail - the second drive failed before the spare drive completes its rebuild. The ExaGrid Server will automatically go into Disk Safety Halt mode and when the spare drive completes rebuilding, the ExaGrid Server resumes operation.

While in Disk Safety Halt mode, an ExaGrid Server will not accept backups. Although the primary ExaGrid user interface is not viewable during a disk safety halt, you may use ExaGrid’s Status Monitor to view the status of the system’s RAID and which disks are involved.


To display the ExaGrid Status Monitor, in your browser’s address space, enter the IP address or DNS name of the ExaGrid Server followed by the port number:9080. For example

Disk Numbering The following illustrations detail disk numbers, spares and empty disk bays for each ExaGrid model. Note – The following drawings identify the location of spare disk drives when an ExaGrid Server is first installed. If a disk drive fails, the spare will take the failed drive’s place. When you replace the failed drive, the replacement drive will become the spare.

3

Empty

Empty

Empty

2

Spare

Empty

Empty

Empty

Empty

1

4

EX1000 Disk Numbering Models with 1TB disks

78 ExaGrid Systems

3

6

9

Empty

2

5

8

Spare

1

4

7

10

EX4000 Disk Numbering

4

8

12

Empty

3

7

11

Empty

2

6

10

Empty

1

5

9

Spare

Spare


4

8

12

3

7

11

15

2

6

10

14

1

5

9

13


80 ExaGrid Systems

Power Supply Failure Depending upon the model, an ExaGrid Server chassis uses two or three power supplies. In the event of a power supply failure, the ExaGrid Server can continue functioning. However, to maintain the safety margin found in having redundant power supplies, the failed power supply should be replaced as soon as possible. Replace the power supply in accordance with the maintenance plan that came with your ExaGrid Server. If an ExaGrid Server power supply fails, a “90530” alert will be generated indicating that the failure has occurred. The alert will be sent to all users who normally receive email alerts from your ExaGrid Server. The alert message will also appear in the Events report in the ExaGrid System’s user interface. In addition, the failed power supply’s LED status indicator will change from green to amber. ExaGrid Server power supply failure alerts use the following format: Event ID: 90530 Severity/Type: Warning Grid Name: Grid Name Site Name: Your_Site SiteGrid Name: name Device Name: Server Name Description: Power Supply Fault Detail: Power supplies are indicating a fault condition

Fan Failure Depending upon the model, an ExaGrid Server chassis may use up to six customer replaceable fans. In the event of a fan failure an event will be generated detailing which fan has failed. In such cases, contact ExaGrid Support and depending on your support maintenance contract, you will be sent a replacement fan, along with step-by-step instructions on how to replace the fan. To replace a fan: 1. From the event message that identified the failed fan, record the fan’s name and location. 2. Ensure backup jobs are not writing to the ExaGrid Server.

82 ExaGrid Systems

3. Via the ExaGrid user interface, shut down the ExaGrid Server. http://se2/manager.html

2.Click Manage

File Edit View Favorites Tools Help

Go

B oo km ar ks

5 19 0 bl oc ke d

C he ck

AutoLink

Settings

Send to P ag e

ExaGridSystemsManagementApplication3...

T oo ls

3.Click Admin.State Chan

4.Click Shutdown

Refresh ExaGrid Site:SystemEngineer2 SE2:EX1000 Site:SystemEngineer1 SE2:EX1000

The ExaGrid ServerSE2is Online. Restart Shutdown

1.Click ExaGridServer !

Warning: The functionalityon this page willinterupt the operation of the selected ExaGrid Serverand may cause backup jobs to fail.

4. Remove the ExaGrid Server from the rack. Caution – At least two people are needed to lift the ExaGrid Server from the rack.

5. Remove the top cover. 6. Before continuing, properly connect an anti-static strap to yourself. 7. Use the following fan map to locate the fan identified in the fan failure event message:

REAR-D REAR-E

MID-A

MID-B

MID-C

Front of ExaGrid Server


8. To remove the defective fan, press its side release latch and lift the fan out:

9. To insert the replacement fan, align the fan into the fan rails and gently push the fan in place until it is completely seated into its electrical connector. 10. Replace the top cover. 11. Re-rack the ExaGrid Server. 12. Reconnect cables. 13. Power on the ExaGrid Server.

Network Debugging Tools ExaGrid Systems are appliances. Access to an ExaGrid System is through the ExaGrid System’s web-based user interface. In the unlikely event you need to debug your ExaGrid network settings, the ExaGrid System’s user interface provides the following tools: 1. 2. 3. 4.

Ping Traceroute Network interface statistics Network performance test

To use these tools: 1. 2. 3. 4.

84 ExaGrid Systems

In the navigation tree select ExaGrid, an ExaGrid site or an ExaGrid Server. In the main menu, click Manage . From the drop down menu select Network . From the secondary drop down menu, select Diagnostics. The network Diagnostics page is displayed.

Notifications If you encounter issues with receiving email alerts or SNMP traps from your ExaGrid System: ■

■

■

If your email server is relay enabled, a missing Send from password will cause the system to send all messages as relays. Relayed messages are often times treated as spam by spam filters and filtered out. If you must configure messages as relays, ensure that the recipient’s spam filters allow relayed messages from this site. See “Network Debugging Tools” on page 84. to determine proper network connectivity for each ExaGrid Server. Double check the DNS definition for each ExaGrid Server:

1. 2. 3. 4.

In the navigation tree, select an ExaGrid Server. In the Main menu, click Manage . From the drop down menu select Network . From the drop down menu select Configuration . The Network Configuration page for the selected server is displayed. 5. Ensure the DNS IP address is correct. If it is not, enter the correct IP address and click OK. ■ For SNMP traps, ensure that you are using the latest ExaGrid MIB: 1. In the ExaGrid user interface’s Main menu click Help. 2. From the drop down menu select Online Library. The ExaGrid Online Library is displayed. 3. Scroll down and right-click on ExaGrid Grid SNMP Management Information Base (MIB). 4. Save the MIB file to your required location.


Consumption In the unlikely event that your ExaGrid System begins experiencing rapid consumption of storage space: Ensure the size of your backups and the length of time they are retained does not exceed your system’s rating. When you purchased your ExaGrid System, your ExaGrid System Engineer sized your system according to your current and future backup requirements. If those requirements have changed, it is possible that you are now be exceeding your system’s rated capabilities. Review your current backup sizes and retention periods. Ensure your backup deduplication ratios are getting consistently better over time. Review the Deduplication reports. Each time a job runs, its deduplication ratios should improve.

The site-level Deduplication Summary report will give you a general overview of deduplication in your ExaGrid System. Use the Deduplication report for All Backups to gather more detailed information about your ExaGrid System’s deduplication.

86 ExaGrid Systems

Replication In the unlikely event that your ExaGrid System experiences issues replicating deduplicated data to another site use the following suggestions to troubleshoot the issue: ■

■

1. 2. 3. 4. ■

■

■

See the ExaGrid “Network Debugging Tools” on page 84 to ensure that the necessary network bandwidth is available. Review the ExaGrid Site’s replication schedule and ensure it provides a wide enough time window to replicate the ExaGrid Site’s data. To view an ExaGrid Site’s replication schedule: In the navigation tree, select an ExaGrid Site’s name In the main menu, click Manage . From the drop down menu, select Replication . From the drop down menu, select Schedule . The ExaGrid Site’s replication schedule is displayed. Use the ExaGrid Server-level Replication Transfer Rate History report to identify daily replication trends. Look for changes in the replication rate. A change may indicate other network traffic is competing with the transfer of your deduplicated data. Use the Replication Transfer History report to identify when a backup job’s data was available to be replicated. Use the Replication History report to identify how much data each job contributes to overall replication.


Performance Tuning Your ExaGrid Server will accept data as fast as your backup server or media server can write it. Most backup application vendors provide performance tuning documentation. If you experience slower than expected writes to your ExaGrid System, ExaGrid recommends that you consult the backup vendor’s documentation to get the most out of your backup application. In general, ExaGrid has found that the following types of things, if addressed, will maximize backing up to an ExaGrid System: ■

■

■

■

■

88 ExaGrid Systems

If your backup server or media server is equipped with a network card that has off loading capabilities, off load as much processing as possible to the network card. This will free up the server’s CPU to process and write the backup faster. Review and adjust your backup server’s or media server’s network buffer size. Optimal settings will vary according to backup application and server type. NetBackup users should review their Shared memory settings (number and size of data buffers). Consult the NetBackup’s Tuning guide that came with your NetBackup backup application. NetBackup users should review their client communications buffer size. When NetBackup clients are installed, buffers are set from 16K to 64K. ExaGrid has found that 128K or larger can enhance performance. NetBackup users should review their server and client communications buffer size and ensure that they are both set to the same value.

ExaGrid Admin Guide

Recommend Documents