Features - NAS NDMP Client

(1)

Features - NAS NDMP Client

Overview - NAS NDMP Client

Choose from the following topics:

z Introduction

z Supported Data Types

z Tree Levels in the NAS NDMP C lient z Drive Pools Configured on a MediaAgent z Load Balancing

z License Requirement z Vendor Specific Features

{ NAS-Attached Libraries { NAS-Attached Drive Pools

Introduction

The NAS NDMP Client is the backup and restore vehicle for data (i.e., files and folders) residing on the NAS file server.

There is no separate iDataAgent software to install for NAS NDMP clients; all required components are installed automatically with the MediaAgent software. After a MediaAgent has been installed, which has connectivity to the NAS file server, a NAS NDMP client can be added to the CommCell and configured, using the CommCell Browser. When a suitable Storage Policy is selected, the client can then perform data protection and recovery operations. For more details about required software and configuration, see

Deployment - NAS NDMP Clients .

The NAS NDMP client provides backup and restore support for different kinds of data in what is often a heterogeneous network environment. The following figure shows one such example.

Supported Data Types

The NAS NDMP client can backup all content that can be stored on a NAS file server. Backing up data on a NetApp vFiler is supported on its own NAS client. However, backing up to a local tape drive for a NAS vFiler is not

(3)

Back to Top

Tree Levels in the NAS NDMP Client

When the NAS NDMP client is installed, the following levels are automatically created in the CommCell Browser. The following is an example of a BlueArc NAS client:

Back to Top

Drive Pools Configured on a MediaAgent

This iDataAgent can utilize drive pools configured on a MediaAgent for data protection and recovery operations, which requires the installation of the NDMP Remote Server (NRS). For additional information about the installation and use of NRS, see NDMP Remote Server (NRS).

Back to Top

Load Balancing

A Windows File System client viewed in the CommCell Browser represents a single physical computer with iDataAgent software installed on it. By contrast, a NAS NDMP client viewed in the browser

represents not a physical computer with iDataAgent software installed, but rather a NAS NDMP file server and the ability for any MediaAgent in the CommCell to back up its data. This is an important distinction; when Windows File System iDataAgent software is installed on a computer, that computer must perform all of the job processes required for backup, restore, and Auxiliary Copy jobs for its data; by contrast, for a NAS NDMP client, these jobs and thus their associated processes can be made to run on different MediaAgents; this allows you to load-balance these processing tasks for what often proves to be very large quantities of data, ensuring that no single computer is overburdened.

For more information, see Subclients - NAS NDMP - Load-Balancing Considerations.

Back to Top

License Requirement

supported. contour: Client BlueArc NAS NDMP: Agent defaultBackupSet: Backup Sets default: Subclients

(4)

To perform a data protection operation using this Agent a specific Product License must be available in the CommServe® Server.

Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information.

Back to Top

Vendor Specific Features

Support for the following features vary according to vendor. For more information, see NAS NDMP - Vendor Specific Features for details.

NAS-Attached Libraries

When you add a NAS NDMP client for a NAS file server with an attached library, the arm changer can be configured and controlled through the NAS NDMP client. For additional information, see NAS NDMP Library and Drive Configuration.

NAS-Attached Drive Pools

When you add a NAS NDMP client for a NAS file server with an attached drive pool, data from any Agent can be backed up to that drive pool by selecting a Storage Policy for the NAS-attached drive pool. For additional information, see Storage Policy Considerations.

For support information regarding auxiliary copy, see Auxiliary Copy - Support. A license will be required when you Add a Client for NAS NDMP in the CommCell Browser, not at the point of software installation on the MediaAgent.

(5)

System Requirements - NAS NDMP iDataAgent

The following requirements are for the NAS NDMP iDataAgent:

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our software. Although we may list such revisions and/or service packs as “supported” in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for a specific application or operating system.

Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable.

File Server Operating System

For information on NAS NDMP file server support, see NAS NDMP Compatibility Matrix.

MediaAgent Operating System

The NAS NDMP software is installed on a MediaAgent computer running a supported version of the following operating systems:

z AIX

z Linux (except Itanium varieties) z Solaris

z Windows

See System Requirements - MediaAgent for information on specific versions supported with these operating systems.

Memory and Hard Disk

See System Requirements - MediaAgent

It is recommended that the MediaAgent computer also have additional physical memory available equaling 0.1% of the total backup size for the largest amount of data being backup up at any given time. (As an

example, for 1 terabyte of backup data, you should have an additional 1 gigabyte of physical memory available.)

Peripherals

DVD-ROM drive

Network Interface Card

Miscellaneous

TCP/IP Services configured on the computer.

If media changers and/or tape drives are attached to the NetApp file server, all hardware (including the SAN networking hardware) must be of a type supported by the file server.

There is no separate software to install for the NAS NDMP Clients; all required components are installed automatically with the MediaAgent software. See System Requirements - MediaAgent for information on install information specific to the MediaAgent.

(6)

Install the MediaAgent - Windows

Click on a link below to go to a specific section of the software installation:

z Install Requirements z Install Checklist z Before You Begin z Install Procedure

{ Getting Started

{ Select Components for Installation { Firewall Configuration

{ Configuration of Other Installation Options { Index Cache

{ Client Group Selection

{ Verify Summary of Install Options { Schedule Automatic Update { Install Remaining Cluster Nodes { Setup Complete

z Post-Install Considerations

Install Requirements

The Windows MediaAgent is installed on a computer that satisfies the minimum requirements specified in System Requirements - MediaAgent.

The following procedure describes the steps involved in installing the Windows MediaAgent. If you choose to install multiple components simultaneously, refer to the appropriate procedures for installation requirements and steps specific to the component.

Review the following Install Requirements before installing the software:

General

z The MediaAgent can only be installed after the CommServe® software has already been installed.

Also, keep in mind that the CommServe® software must be running (but not necessarily on the same computer) before you can install the MediaAgent.

z This version of the software is intended to be installed where the CommServe Server is in 8.0.0. z Ensure that you have an available license on the CommServe for the MediaAgent. Also, if you wish to

install the NDMP Remote Server, make sure that you have an appropriate license.

z Do not install the MediaAgent on a compressed drive.

z Close all applications and disable any programs that run automatically, including anti-virus, screen

savers and operating system utilities. Some of the programs, including many anti-virus programs, may be running as a service. Stop and disable such services before you begin. You can re-enable them after the installation.

z Ensure the account under which the Bull Calypso Communications Service (GxCVD) runs has

Full permissions to all files and folders on drives where backups will occur. By default the iDataAgent uses the System account, which should have access to all objects on the client.

z Verify that you have the software installation disc that is appropriate to the destination computer’s

operating system.

Make sure that you have the latest software installation disc before you start to install the software. If you are not sure, contact your software provider.

(7)

Network

z If your MediaAgent computer has multiple Network Interface Cards and IP addresses, make certain

that all network communication paths are working. Also, make sure that the network interface to be used in the MediaAgent installation is set as the first one to be bound on the network. For more information on Network Interface Cards, see Network Requirements.

Firewall

z If the CommServe® Server, MediaAgent and/or Clients communicate across two-way firewall(s): { Ensure port 8400 is allowed connections through the firewall.

{ In addition a range of bi-directional ports (consecutive or discrete) must also be allowed

connections through the firewall.

For information on configuring the range of ports, see Port Requirements for Two-way Firewall.

z If the CommServe Server, MediaAgent and/or Clients communicate across one-way firewall(s): { Identify a range of outbound ports (consecutive or discrete) for use by the software.

For information on configuring the range of ports, see Port Requirements for One-way Firewall.

z If the MediaAgent/Client communicates with the CommServe Server across a one-way firewall, you

must add the MediaAgent/Client host name (or the IP address) in the CommServe computer before installing the necessary software on the MediaAgent/Client computer.

MediaAgent

z On Windows 2000 and Windows 2003 Server:

For devices using the iSCSI and Storport drivers make sure that the medium changer for the library is enabled in the Windows Computer Management window. For all other drivers we recommend that the media changer is disabled in the Windows Computer Management window. For more information on how to enable or disable the media changer, see Driver Configurations.

z The following loopback address must be present in the /etc/hosts file for all Unix clients:

127.0.0.1 localhost

NetApp NAS File Servers

z For information on connecting the storage devices, refer to your vendor's documentation.

z After attaching the NetApp NAS file server and MediaAgent machine to the library and before you

begin your installation, verify that the NDMP service is enabled in the NetApp file server.

Installing On Microsoft Virtual Server

z For information on installing the MediaAgent software on the Microsoft Virtual Server, see

Considerations for backing up the Microsoft Virtual Server.

Multi Instancing

z By utilizing the Multi Instancing feature, the same Agent and MediaAgent software can be installed

on a computer multiple times, but not all components support Multi Instancing. This limitation can apply to the component you are installing, or to one already installed on the computer. Prior to installing multiple instances of a software component on the same computer, carefully review the information contained in Multi Instancing, and follow the instructions in the How to Use Multi Instancing section for the additional screens that will appear during the installation process.

Install Checklist

Collect the following information before installing the software. Use the space provided to record the information, and retain this information in your Disaster Recovery binder.

(8)

location:________________________________________________________________ See Select Components for Installation for more information.

2. If the CommServe Server and the client computer communicate across a firewall: Firewall ports:

______________________________________________________________________ Hostnames and/or IP Addresses and corresponding GxCVD port numbers of computers on the other side of the firewall:______________

Keep Alive Interval

minutes:____________________________________________________________ Hostname for outgoing tunnel

connections:_________________________________________________ Tunnel Initialization Interval

seconds:_____________________________________________________ See Firewall Configuration for more information.

3. CommServe Host Name or the CommServe IP

address:______________________________________

See Configuration of Other Installation Options for more information. 4. Client computer's Host name (NetBIOS name) or IP

address____________________________________

See Configuration of Other Installation Options for more information. 5. Index Cache folder

location:_____________________________________________________________ See Index Cache for more information.

6. Client Group to which this Client will be

associated:_____________________________________________ See Client Group Selection for more information.

7. Time and frequency for Install of Automatic

Updates:_________________________________________ See Schedule Automatic Update for more information.

Before You Begin

z Log on to the computer that will serve as the MediaAgent as a local Administrator or as a member

of the Administrators group on that computer.

Install Procedure

Getting Started

1. Place the software installation disc for the Windows platform into the disc drive.

After a few seconds, the installation program is launched.

(9)

automatically:

z Click the Start button on the Windows task bar, and

then click Run.

z Browse to the installation disc drive, select

Setup.exe, click Open, then click OK. NOTES

z If you are installing on a x64 version of Windows

2008 Server Core R2, go to the AMD64 folder and run Setup.exe.

2. In this screen, you choose the language you want to use during installation. Click the down arrow, select the desired language from the pull-down list, and click Next to continue.

3. Select the option to install software. NOTES

z This screen will only appear when the

bAllow32BitInstallOn64Bit registry key has been

created and enabled on this computer.

4. Select the option to install software on this computer. NOTES

z The options that appear on this screen depend on the

computer in which the software is being installed. 5. Read the Welcome screen.

Click Next to continue, if no other applications are running.

6. Read the virus scanning software warning.

Click OK to continue, if virus scanning software is disabled.

7. Read the license agreement, then select I accept the terms in the license agreement.

Click Next to continue.

Select Components for Installation

8. Select the component(s) to install.

NOTES

z Your screen may look different from the example

shown.

z Components that either have already been

installed, or which cannot be installed, will be dimmed. Hover over the component for additional details.

z The Special Registry Keys In Use field will be

enabled when GalaxyInstallerFlags registry keys have been enabled on this computer. Hover over the field to see which keys have been set,

(10)

as well as their values. For more information, see

Registry Keys. Click Next to continue.

To install the MediaAgent, under Common Technology Engine expand the MediaAgent Modules and select MediaAgent.

Optionally you can also select the following MediaAgent components at this time:

z NDMP Remote Server - Select this option if your

MediaAgent has a library attached and is used by a NAS NDMP client to backup data. (Requires that you have an appropriate license on the CommServe.)

z Shared Dynamic Disks - Select this option if

you wish to share a disk for storage, among multiple MediaAgents in a SAN.

See Install the Shared Dynamic Disk Driver for more information on this component.

9. Specify the location where you want to install the software.

NOTES

z Do not install the software to a mapped network

drive.

z Do not use the following characters when

specifying the destination path: / : * ? " < > |

It is recommended that you use alphanumeric characters only.

z If you intend to install other components on this

computer, the selected installation directory will be automatically used for that software as well.

z If a component has already been installed, this

screen may not be displayed if the installer can use the same install location as previously used.

z If you intend to use the SnapProtect™ feature

for Windows File System iDataAgent, the agent should be installed on a non-system drive and not a filer volume.

Click Browse to change directories. Click Next to continue.

Firewall Configuration

10. Select from the following:

z If this Client communicates with the CommServe

Server and/or MediaAgent across a firewall, select Yes, configure firewall services, and then click Next to continue. Proceed to the next Step.

(11)

do not configure firewall services and then click Next to continue. Proceed to the next section.

NOTES

z Operating systems, such as Windows 2008 and

Windows Vista, may have more than one profile present. When you select No to configure firewall services, verify that firewall settings are not enabled in the profile(s).

z If the system detects firewall settings are

present in the profile(s), you must select from the following:

{ Disable firewall for ALL profiles: Employ

caution when choosing this option; firewall settings will be disabled in all profiles. This requires a system reboot; installation automatically resumes after reboot.

{ No, Firewall is not enabled: Select this

option if your firewall settings allow communication with the CommServe computer.

Click Back to configure firewall services. 11. Click the Specify list of machine across the

firewall option and then specify the list of hosts separated from this computer by a firewall. Make sure you correctly describe whether the firewall allows two-way communication (but on a limited range of ports), or one-way communication (with either only remote host being able to make connections to this computer, or vice versa). For all one-way firewalls allowing incoming connections and those one-way firewalls allowing outgoing connections without additional port filtering, skip this step.

Click Next to continue. NOTES

z Consider the following:

{ On the CommServe Server, this list should

include all the MediaAgents and Clients that are on the other side of the firewall.

{ On the MediaAgents/Clients this should

include the CommServe computer, and any other Clients/MediaAgents on the other side of the firewall with which communications will be established.

z For each machine on the other side of the

firewall that you want to configure, choose the type of firewall configuration based on the firewall setup in your environment. Choose from the following options:

{ Click on 2-way firewall if you can open

(12)

{ Click 1-way firewall; host is reachable

from this machine on the machine that is on the secure side of the firewall.

{ Click 1-way firewall; host is NOT

reachable from this machine on the machine that is on the public / DMZ side of the firewall.

z If you wish to communicate with computers in a

clustered environment, ensure that you add the Host Name/IP Address of all physical nodes in the cluster (even if no CommCell components are installed) and all the virtual nodes in which CommCell components are installed.

z Type the host name or the IP address and the

GxCVD port number of the host name, and click Add to place it in the Host Name/IP Address List. 12. Click the Specify list of restricted open ports

option and then specify the port range. Add the starting and ending port range and then click Add to place it in the Open Port List. Repeat as needed.

If firewall separating this computer from others allows incoming connections, but these connections can be made only on a limited set of ports, then configure the appropriate port range here. For all other scenarios, skip this step.

Note that if you do not specify hostname(s) as well as port number(s), then the firewall services will not be configured.

NOTES

z Typically in a two-way firewall, the open ports

must be indicated for all computers. In a one-way firewall, the ports must be specified on computers in the open side, if they are open in a restricted way. Note that the port ranges are not required for computers that are fully closed in the one-way firewall. For example, laptops which are configured as clients in the Workstation Backup Agent.

z In a clustered environment, make sure the

firewall ports specified here are open for

communication on all the physical nodes as well as the virtual nodes.

13. If desired, modify the Keep Alive interval. Click Next to continue.

(13)

14. Optionally, select Advanced Firewall

Configuration and specify a local host name interface to use for outgoing tunnel connections through the firewall. Otherwise, the interface and port is automatically selected for you by the OS. Click Next to continue.

15. If desired, modify the Tunnel Initialization interval. Click Next to continue.

Configuration of Other Installation Options

16. Enter the fully qualified domain name of the

CommServe computer. (TCP/IP network name. e.g., computer.company.com)

NOTES

z Do not use spaces when specifying a new name

for the CommServe Host Name.

screen will not be displayed; instead, the installer will use the same Server Name as

(14)

previously specified. Click Next to continue.

17. Enter the username and password information for an external domain user account or a CommCell user account. This authorizes the installation of an agent on the CommCell.

NOTES

z This window is only displayed when the Require

Authentication for Agent Installation option is selected in the CommCell Properties. Users must belong to a User Group with Administrative Management capabilities to enable this feature. For more information, see Authentication for Agent Installs.

Click Next to continue. 18. Enter the following:

z The local (NetBIOS) name of the client

computer.

z The TCP/IP IP host name of the NIC that the

client computer must use to communicate with the CommServe Server.

NOTES

z Do not use spaces when specifying a new name

for the Client.

z The default network interface name of the client

computer is displayed if the computer has only one network interface. If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe Server.

screen will not be displayed; instead, the install program will use the same name as previously specified.

19. Specify the following and click Next to continue:

z Type the location of the client's job results

directory, or click Browse. NOTES

(15)

z The Agent uses the job results directory to store

the client's backup and restore job results.

z UNC paths are supported for Windows and

Exchange Database 2007 iDataAgents with Cluster Continuous Replication (CCR), but cannot be specified on this screen. After the installation completes, you can change the Job Results path to a UNC path. For comprehensive information on UNC paths, see Using UNC Paths for Job Results Directory.

z VSS and non-VSS system state restores require

that the Job Result Path reside on the same drive as the data to be restored.

z For SnapProtect, the Job Results directory must

reside on the system drive.

Client Group Selection

20. Select a Client Group from the list. Click Next to continue.

NOTES

z This screen will be displayed only if Client Groups

are configured in the CommCell Console. For more information, see Client Computer Groups.

21. Select Yes to stop Removable Storage Services on the MediaAgent.

NOTES

z This prompt will not appear if Removable

Storage Services are already disabled on the computer.

Index Cache

22. Specify the location for the MediaAgent's Index Cache.

NOTES

z You can accept the default or choose another

(16)

local.

If desired, you can change the index cache location to a network drive from the CommCell Console, any time after you have installed the MediaAgent software.

z On Windows 2000, if you choose a network path

for index cache, you may be prompted to logoff and login to continue the installation.

z It is recommended that the index cache location

to be on a partitioned drive used exclusively for holding an index cache.

z For information on calculating the space

requirements for index cache, see Calculating the Storage Space Required for Index Cache.

Click Browse to change directories. Click Next to continue.

23. Select Download Pack(s) and Install to download and install the latest service packs and post packs from the software provider.

NOTES

z Internet connectivity is required to download

updates.

z This step is applicable when installing on the first

instance.

z Updates are downloaded to the following

directory: <software

installation>/Base/Temp/DownloadedPacks. They are launched silently and installed

automatically for the first instance. Click Next to continue.

Verify Summary of Install Options

24. Verify the summary of selected options.

NOTES

z The Summary on your screen should reflect the

components you selected for install, and may look different from the example shown. Click Next to continue or Back to change any of the options.

The install program now starts copying the software to the computer. This step may take several

minutes to complete.

25. The System Reboot message may be displayed. If so, select one of the following:

(17)

This option will be displayed if the install program finds any files belonging to other applications, that need to be replaced. As these files are not critical for this installation, you may skip the reboot and continue the installation and reboot the computer at a later time.

z Reboot Now

If this option is displayed without the Skip Reboot option, the install program has found files required by the software that are in use and need to be replaced. If Reboot Now is displayed without the Skip Reboot option, reboot the computer at this point. The install program will automatically continue after the reboot.

z Exit Setup

If you want to exit the install program, click Exit Setup.

Schedule Automatic Update

26. If necessary, select this option to schedule an automatic installation of software updates. NOTES

z Install Updates Schedule allows automatic

installation of the necessary software updates on the computer on a single or weekly basis. If you do not select this option, you can schedule these updates later from the CommCell Console.

z To avoid conflict, do not schedule the automatic

installation of software updates to occur at the same time as the automatic FTP downloading of software updates.

z You may be prompted to reboot the computer

before restarting services.

screen will not be displayed; instead, the installer will use the same option as previously specified.

Install Remaining Cluster Nodes

27. If you are installing/upgrading the software on the physical node in a clustered environment, use this option to install/upgrade the software on the remaining physical nodes of the cluster.

z To install/upgrade the software on the remaining

nodes of the cluster, click Yes.

z To complete the install/upgrade for this node

only, click No.

See Install/Upgrade Remaining Cluster Nodes for step-by-step instructions.

(18)

Setup Complete

28. Setup displays the successfully installed components.

NOTES

z The Setup Complete message displayed on

your screen will reflect the components you installed, and may look different from the example shown.

z If you install an Agent with the CommCell

Console open, you need to refresh the CommCell Console (F5) to see the new Agents.

z If Reboot Now button is displayed make sure to

reboot the computer before performing any other operations from the computer.

Click Finish to close the install program. The installation is now complete.

Post-Install Considerations

General

z Install post-release updates or Service Packs that may have been released after the release of the

software. If you are installing a Service Pack, verify and ensure that it is the same version as the one installed in the CommServe Server. Alternatively, you can enable Automatic Updates for quick and easy installation of updates in the CommCell component.

z After installing the CommServe® or MediaAgent software, it will be listed as a client computer in the

host computer's CommCell Browser. The alert icon preceding the CommServe or MediaAgent client computer in the CommCell Console indicates that agent software must be installed on that computer for it to be utilized as a client.

MediaAgent Specific

z You must configure the libraries and drives before using the MediaAgent for data protection

operations. (For more information, see Library and Drive Configuration.)

The MediaAgent software supports various types of libraries and library configurations. See the following sections for more information:

{ Blind Libraries { Centera Clusters { Cloud Storage

{ Direct-Attached Libraries

{ Direct-Attached Shared Libraries { HDS Data Retention Utility (DRU)

{ IP Libraries (Like libraries attached to ACSLS Server) { Magnetic Libraries

{ NAS NDMP Libraries { Optical Libraries

{ SAN-Attached Libraries { Stand-Alone Drives { Virtual Tape Libraries

(19)

Install the NDMP Remote Server (NRS) - Unix

If your Unix MediaAgent has a library attached and is used by the NAS NDMP iDataAgent to back up data, you must install the NRS software.

Click on a link below to go to a specific section of the software installation:

z Install Requirements z Before You Begin z Install Procedure

{ Getting Started

{ Select Components for Installation { Setup Complete

z Post-Install Considerations z Related Topics:

{ NDMP Remote Server (NRS)

{ Upgrade the NDMP Remote Server (NRS)

Install Requirements

z The Unix MediaAgent must support NDMP Remote Server. z The CommServe must be running.

z You must have an available license for the NDMP Remote Server. See License Administration for

more information.

z If your network does not have DNS lookup or some other name resolution facility, you may be asked

to enter the IP address of the CommServe computer.

z Perform the following if the CommServe, MediaAgent and/or Client are communicating across firewall

(s):

{ Ensure that port 8400 and one additional port is open for connections through the firewall.

Depending on the direction of the firewall, this additional port must be provided either on

MediaAgent/CommServe using the Firewall Configuration utility or on the client during installation.

{ For NDMP Remote Server, you must specify port 10000.

{ In addition a range of ports must also be allowed connections through the firewall.

For information on calculating the range of ports, see Firewall Requirements.

z If you choose to install multiple components simultaneously, refer to Installation for procedures

specific to each component.

Before You Begin

z Log on to the MediaAgent as root.

Install Procedure

Getting Started

1. Place the software installation disc for the Unix platform into the disc drive.

You can also install the product using a disc drive

(20)

mounted on another computer on the network.

z On Solaris, double-click the cvpkgadd program

from the File Manager window.

z On other Unix platforms, open the Terminal window,

navigate to the software installation disc and then enter cvpkgadd.

2. The product banner and other information is displayed. Press Enter to continue.

3. Read the license agreement. Type y and press Enter to continue.

4. This prompt is displayed only when you are installing on AIX, HP-UX, Linux, or Solaris computers.

Press Enter to continue NOTES

z When you install on non-clustered computer, you

must select the number associated with the option Install on a physical machine.

Certain Calypso packages can be associated with a virtual IP, or in other words, installed on a

"virtual machine" belonging to some cluster. At any given time the virtual machine's services and IP address are active on only one of the cluster's servers. The virtual machine can "fail-over" from one server to another, which includes stopping services and deactivating IP address on the first server and activating the IP address/services on the other server.

You now have a choice of performing a regular Calypso install on the physical host or installing Calypso on a virtual machine for operation within a cluster.

Most users should select "Install on a physical machine" here. 1) Install on a physical machine 2) Install on a virtual machine 3) Exit

Your choice: [1] 5. If you have only one network interface, press Enter to

accept the default network interface name and continue.

If you have multiple network interfaces, enter the number corresponding to the network interface that you wish to use as default, and then press Enter to continue.

NOTES

z The interface name and IP addresses depend on the

computer in which the software is installed and may be different from the example shown.

Network interface with the following IPs have been found available on your system. One of these interfaces should be

associated with the physical machine being installed. It will also be used by the CommServe to initiate connections to the physical machine. Note that you will be able to additionally

customize Datapipe Interface Pairs used for the backup data traffic later in the Calypso Java GUI. Please select the correct network interface below.

1) client (201.42.33.598) 2) hk97::489:9glg:hk8d:9490

(21)

3) client.company.com

(hr90:8842:2:78:013:8ghh:hg8k:9x54) Interface number: [1]

Verify the default network interface name.

Press Enter to accept the default network interface name and continue, or

Type the default network interface name, and then press Enter to continue.

NOTES

z This prompt will be displayed only when you have

multiple network interfaces for the computer.

Please verify the physical machine interface name below. Make it as complete (with fully qualified domain name) as possible: Physical Machine Host Name: [angel.company.com]

6. Specify the client name for the computer.

Press Enter to accept the default name and continue, or

Enter a new client name for the computer and then press Enter to continue.

Please specify the client name for this machine. It does not have to be the network host name: you can enter any word here without spaces. The only requirement is that it must be unique on the CommServe. Client name: [angel]

Select Components for Installation

8. Enter the number corresponding to the CVGxNRS module.

NOTES

z Your screen may look different from the example

shown.

z Components that either have already been installed,

or which cannot be installed, will not be shown.

z In addition, the list of modules that appear depends

on the specific Unix File System in which the package is installed. (e.g., CVGxWA will appear only when the installation package is run on a Solaris

computer.)

Press Enter to continue.

Install Calypso on physical machine client.company.com Select the Calypso module that you would like to install 1) Media Agent <= CVGxMA

2) FileSystem iDataAgent <= CVGxIDA

3) Exit this menu Module number: [1]

Setup Complete

9. Press Enter to continue. We are now ready to copy

binaries.

Press ENTER to begin ...

10. Press Enter to continue. _{Successfully installed CVGxNRS.}

Press ENTER to continue ... 11. Enter the appropriate value to exit the install program. Install Calypso on physical

machine client.company.com Select the Calypso module that you would like to install 1) Media Agent <= CVGxMA

(22)

Back to Top

2) FileSystem iDataAgent <= CVGxIDA

3) Exit this menu Module number: [1]

Post-Install Considerations

z If you have not already configured the library and drives attached to the MediaAgent, you must do

so now. For more information, see Library and Drive Configuration.

z Once the library and drives have been configured, if you have not already added the NAS NDMP

(23)

File System NDMP Restore Enabler

Topics | How To | Related Topics Overview Installation Considerations Upgrade License Requirements

Overview

The File System NDMP Restore Enabler allows NAS NDMP data that was backed up from a NetApp or EMC Celerra file server to be restored to a Windows or Unix computer. A file system NDMP restore is a cross-platform restore, where the data is restored to a computer with a different operating system (e.g., ONTAP on a NetApp NAS NDMP file server) to a file system. To restore NAS NDMP data to a file system, the File System NDMP Restore Enabler as well as the File System iDataAgent, must be installed on the destination computer.

Installation

Install the File System NDMP Restore Enabler (Windows) provides for step-by-step instructions for installing the optional File System NDMP Restore Enabler, which allows NAS data to be restored to a Windows computer. Install the File System NDMP Restore Enabler (Unix) provides for step-by-step instructions for installing the optional File System NDMP Restore Enabler, which allows NAS data to be restored to a Unix computer. You must have an available license for the File System NDMP Restore Enabler. See License Administration for more information.

Considerations

When restoring NAS NDMP data to a file system, you should consider how the data is restored under certain circumstances. When data is restored to an environment from which it did not originate, the data does not always assume its original characteristics. Consider the following:

z Files and directories that contain ACLs or Unix permissions will not have those ACLs or permissions

restored.

z File and directory names with case only differences will be treated like files and directories of the same

name. This may cause one file/directory to overwrite another during the restore. (Windows only)

z Files and directories with names containing Unix-specific characters may have those characters

replaced with a "_" character or have some other form of modification in the restored file/directory name. (Windows only)

z Windows allows 1024 characters for filenames, including the path. A filename, including the path, with

more than 1024 characters will not be restored to the Windows computer. (Windows only)

z Files with links may not be restored with those links.

Upgrade

The File System NDMP Restore Enabler is only supported for NetApp and EMC Celerra file servers.

(24)

The File System NDMP Restore Enabler is installed on a computer with the File System iDataAgent and hence automatically upgraded when a File System iDataAgent upgrade is performed. For details, refer to

Upgrade the File System NDMP Restore Enabler.

License Requirements

This feature requires a Feature License to be available in the CommServe® Server.

Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information.

(25)

Backup - NAS NDMP

Topics | How To | Related Topics Overview

Supported Backup Types NAS NDMP Backup Jobs

z Two Way Backups z Three Way Backups

z Multiple Data Stream Backups

Backup Considerations

z General

z Hitachi and NetApp Clients - Incremental Backups z Hitachi Clients

z NetApp Clients

NAS Vendor Specific Backup Features Advanced Backup Options

Related Reports

Overview

Before you begin using the NAS NDMP client for data protection operations, ensure that you have completed the required Configuration tasks:

z NAS NDMP Client Configuration

Plan your backup jobs for this agent by reviewing the following information:

z For an overview of backup jobs, see Backup Data.

z For a list of supported data types for these agents, see Supported Data Types. z For information on subclients, see Subclients.

{ For information on configuring subclients for these agents, see Subclients - NAS NDMP. { For information on excluding data via subclients, see Excluding Data from Data Protection

Operations.

Supported Backup Types

NAS NDMP clients support the following backup types:

z Full Backups

z Differential Backups z Incremental Backups

NAS NDMP Backup Jobs

There are several advanced options specific to NAS NDMP clients. For more information, see NAS Options. For procedures, see Start a Backup with NAS Options Selected.

(26)

In addition, NAS NDMP clients have the following unique backup functionality.

Two Way Backups

A two-way backup is the process of backing up data from a NAS NDMP data server to a storage device attached to that same NAS NDMP data server.

Three Way Backups

A three-way backup is the process of backing up data from a NAS NDMP data server to a storage device attached to another NAS NDMP data server of the same type (NetApp to NetApp, for example). Keep in mind that the source data server does not need to be attached to a storage device.

Multiple Data Stream Backups

Multiple Data Readers can be specified for backup jobs, providing the facility to use multiple data streams without having to create multiple subclients and start separate backup jobs. This allows backups of multiple paths in a NAS subclient to run concurrently, as part of the same job, thus reducing the total number of running jobs. This ability is based on the number of resources (drives) available and the setting for Number of Data Readers in the Subclient Properties (General) tab, which is the number of paths in the subclient that will run concurrently given sufficient available resources.

This feature is useful only for a NAS client which has subclients with multiple data content paths defined, or (for all NAS clients except Hitachi) specifies a content path of "/" and has more then one volume or root file system. If this is not true of a NAS subclient, then its backups will not utilize multiple data streams.

How to configure Multiple Stream Backups for NAS data

The following section provides the steps for configuring Multiple Stream Backups: 1. Create a new Subclient or configure an existing one.

{ In the Content tab of the Subclient Properties assign multiple content paths to this subclient (or if

this subclient is to backup the entire NAS client) use the â€œ\â€ content path.

{ In the General tab of the Subclient Properties, specify the Number of Data Readers, i.e., the

maximum number of backup threads that you would like to run concurrently.

{ In the Storage Device tab of the Subclient Properties, assign a Storage Policy with a sufficient

number of streams to meet the expected conditions.

2. Run a backup. For instructions, see Backup - NAS NDMP - How To.

3. To confirm the backup job is using multiple streams, right click the job in the Job Controller window, select Detail..., and in the Job Details window select the Streams tab. Note that the actual number of streams shown will vary as the job progresses.

NOTES

z The actual number of concurrent backup streams employed during a backup job is limited by the

number of resources available to the Storage Policy, whether other subclients are also using the same Storage Policy, number of remaining subclient content paths that have not finished being backed up, and the Number Of Data Readers value specified for this subclient.

z After a given subclient content path has been backed up (for a particular thread) the backup of the

next subclient content path will begin, until a backup thread has been started for each subclient content path.

z If the number of available resources for a storage policy is the limiting factor for a multiple stream

backup job, it will use all of the resources that are available, rather than fail or wait until more

resources become available. However, the number of streams used for the job will not increase when more streams become available. Thus, for example, if a Storage Policy has a specified Device Stream value of 5, and there are already 4 other jobs running, using up 4 of the Device Streams, then the backup job will use the 1 remaining stream, until the entire backup job completes.

z When multiple data streams are active, any action imposed on one stream (such as suspending) will

(27)

Backup Considerations

Before performing any backup procedures for this agent, review the following information: General

z For NetApp only, ensure that the NAS NDMP file server has NDMP turned on before you begin

performing backups The can be done by executing the command ndmp on from the file server's console window.

z The backup size will never equal a sum of the file sizes in a NAS backup. There is a backup header and

file headers inserted into the backup file. Additionally, Celerra has a minimum file size of 8k.

z Filters can be used in conjunction with the "Items That Failed" list on the data protection Job History

Report to eliminate backup or archive failures by excluding items which consistently fail that are not integral to the operation of the system or applications. Some items fail because they are locked by the operating system or application and cannot be opened at the time of the data protection operation. This often occurs with certain system-related files and database application files.

Also, keep in mind that you will need to run a full backup after adding failed files to the filter in order to remove them.

z For NetApp only, data verification can be performed for Read-Only volumes when a writable location is

specified on the file server with the sDATAVERIFICATION_DESTINATIONDIR Registry key. This is useful if backing up a Snap mirror destination volume to a tape drive on the file server.

z If you have installed NDMP Remote Server (NRS) on your MediaAgent, and want to back up your data

to a library attached to the MediaAgent, be sure that the Storage Policy you select for backups uses a drive pool configured to that MediaAgent.

z Deduplication is supported when backing up data to magnetic libraries attached to a MediaAgent.

Backing up deduplicated data on EMC Celerra and NetApp filers requires installing NDMP Remote Server (NRS) on your MediaAgent.

z NAS NDMP Load-Balancing - The Drive Pools, Storage Policies, and Subclients for NAS NDMP can be

configured so that backup, restore, and auxiliary copy jobs will be spread among different MediaAgent, and thus the processor load for these jobs will occur on different machines. For more information, see

Subclients - NAS NDMP - Load-Balancing Considerations.

z The number of tape drives in use on a particular NAS file server can be limited through an option in

the Media Management (Service Configuration) tab. This is useful since some file servers have an upper limit to the number of concurrent backup or restore jobs that can be run. The number entered with the Maximum allowed number of drive reservations per NAS Filer option will limit the number of tape drives that can be in use at a given time. For example, if five backup jobs were started for a particular NAS file server, but the number specified with this option was set to four, then the fifth job will be held in a waiting state until one of the jobs completes.

Hitachi and NetApp Clients - Incremental Backups

Incremental backups are supported on Hitachi clients and NetApp clients, with the following limitations:

z After a full backup, a maximum of 9 incremental backups can be run in a row. At this point a full or

differential backup must be run.

z After a differential backup is run, you can run another 8 incremental backups before performing

another full or differential backups.

z An incremental backup can be automatically converted to a full backup, when required, through the

use of the sConvertToFull registry key. You may wish to set the key to Y if backups are generating

this event nasBackup: Exceeded maximum number of incremental backups. Must run full or differential backup as opposed to failing the job. Only if all the paths of the subclient content generate this event will a new Full backup job be run.

Hitachi Clients

z To perform a backup from a Snapshot (i.e., back up data from a read-only copy of the current file

(28)

server associated with this NAS client and the Backup from Snapshot option on the client's Advanced Backup Options (NAS Options) dialog must be configured to match how the file server has been configured. For more information about the Hitachi NAS file server snapshot settings, refer to Hitachi's documentation.

NetApp Clients

z SnapMirror-To-Tape is available for a NetApp NDMP client by enabling a Registry key. Please contact

your software vendor for assistance in configuring SnapMirror-To-Tape.

z To successfully browse and restore data, it is recommended to use the UTF-8 setting for filer volumes.

Please consult with NetApp for implications of changing volume language.

z Backing up data on a NetApp vFiler is supported on its own NAS client. However, backing up to a local

tape drive for a NAS vFiler is not supported.

Related Reports

NAS NDMP Backup Archives Report

The NAS NDMP Backup Archives Reportprovides information on data protection archive jobs based on the selected filter criteria.

Back to Top

Backup - NAS NDMP - How To

Topics | How To | Related Topics Start a Backup

Schedule Backups

Start a Backup in the Suspended State

Start a Backup on New Media

Start a Backup that Creates a New Index

Start a Backup that Marks Media Full on Completion

Start a Backup that Reserves Resources Before Scan

Start a Backup with a Set Job Priority

Start a Backup with Vault Tracking enabled

Two Way Backups for NAS Three Way Backups for NAS

Start a Backup with NAS Options Selected

Start a Backup

Before You Begin

z You can perform the following types of backup operations: Full, Incremental, Differential or

Synthetic Full.

{ Read Full Backups before performing a Full Backup.

(29)

{ Read Differential Backups before performing a Differential Backup. { Read Synthetic Full Backups before performing a Synthetic Full Backup. Required Capability: See Capabilities and Permitted Actions

To start an immediate backup job:

1. From the CommCell Browser, expand Client Computers by double-clicking Client Computers | iDA File System | defaultBackupSet. The default and other subclients (if available) are displayed on the right-hand windowpane.

2. To back up the default subclient, right-click the subclient, and click Backup. 3. From the Backup Options dialog box, select Run Immediately.

4. Select Full, Incremental, Differential or Synthetic Full backup.

In certain circumstances a non-full backup may automatically be converted to a full backup. For a listing of these circumstances, see When a Non-Full Backup is Automatically Converted to a Full Backup.

5. Click OK. You can track the progress of the backup job from the Job Controller window. If you are using a stand-alone drive, you are prompted to load a specific cartridge into the drive. If you are using a library, you will not receive this prompt. The system loads the tapes automatically. Your cartridges should be appropriately labeled. This will enable you to locate the correct cartridge for a restore job, if necessary.

6. When the backup has completed, the Job Controller displays Completed.

After running a backup, you may want to verify the backup data. You can do this by viewing the Backup History. For more information, see Backup Job History.

Schedule Backups

You can schedule backups to occur with the following procedure. You will be prompted to create a

schedule for the data protection operation after selecting your data protection options.

z You can also run backups of the following:

{ For a user-defined backup set or instance, right-click the backup set

you want to back up, click All Tasks, and click Backup All Subclients.

{ For the Lotus Notes Document iDataAgent, to back up a partition,

right-click the partition you want to back up, click All Tasks, and click Backup Default Backup Set.

For the Lotus Notes Database iDataAgent, to back up a partition, right-click the partition you want to back up, click All Tasks, and click Backup All Subclients.

{ For Agents that do not have backup set or instance levels, to back

up all subclients, right-click the agent icon, click All Tasks, and click Backup All Subclients.

If you chose a level higher than subclient (i.e., backup set, etc.),

you are prompted to confirm that you want to back up all the subclients below that level/node. Click Yes.

Starting a data protection operation on a backup set, instance or

agent level causes the system to start individual data protection operations for each subclient contained therein. If the subclients are associated with the same storage policy, then their operations will run sequentially unless that storage policy is configured to accommodate multiple data streams.

(30)

Before You Begin

z All Agents

{ Be sure all of the subclients are backed up, or scheduled to be backed up as needed, in order to

secure all of the data for the agent. Note this does not apply to archive operations.

Required Capability: See Capabilities and Permitted Actions

To schedule a backup operation:

1. From the CommCell Browser, select one of the following:

{ To back up a subclient, right-click the subclient and click Backup.

{ To back up a backup set or instance, right-click the backup set or instance, click All Tasks, and

click Backup All Subclients.

{ To back up the default backup set, right-click the agent or instance node, click All Tasks, and

click Backup Default Backup Set.

{ For the Lotus Notes Document iDataAgent, to back up a partition, right-click the partition you

want to back up, click All Tasks, and click Backup Default Backup Set.

For the Lotus Notes Database iDataAgent, to back up a partition, right-click the partition you want to back up, click All Tasks, and click Backup All Subclients.

{ For Agents that do not have backup set or instance levels, to back up all subclients, right-click the

agent icon, click All Tasks, and click Backup All Subclients.

2. If you chose a level higher than subclient (i.e., backup set, etc.), you are prompted to confirm that you want to back up all the subclients below that level/node. Click Yes.

3. From the Backup Options dialog box, select the type of backup that you want to initiate. In certain circumstances a non-full backup may automatically be converted to a full backup. For a listing of these circumstances, see When a Non-Full Backup is Automatically Converted to a Full Backup. 4. Click Schedule. Click OK to continue.

5. From the Schedule Details (Schedule Details) dialog box, create a schedule for this operation. For step-by-step instructions, see Create a Job Schedule. Click OK to continue.

6. Your backup operation will execute according to the specified schedule.

Start a Backup in the Suspended State

Use the following procedure to start a backup in the suspended state. Before You Begin

z Be sure all of the subclients are backed up, or scheduled to be backed up as needed, in order to

To start an immediate backup job with advanced backup options: 1. From the CommCell Browser, select one of the following:

{ To backup a subclient, right-click the subclient to want to backup and click Backup.

{ To backup a user-defined backup set or instance, right-click the backup set you want to backup,

click All Tasks, and click Backup All Subclients.

Starting a data protection operation on a backup set, instance or agent level causes the system to start individual data protection operations for each subclient contained therein. If the subclients are associated with the same storage policy, then their operations will run sequentially unless that storage policy is configured to accommodate multiple data streams.

(31)

{ To backup the default backup set, right-click the agent or instance node, click All Tasks, and

{ For Lotus Notes iDataAgent, to backup a partition, right-click the partition you want to backup,

click All Tasks, and click Backup Default Backup Set.

{ For Agents that do not have backup set or instance levels, to backup all subclients, right-click the

3. From the Backup Options dialog box, select Run Immediately. 4. Select the type of backup that you want to initiate.

5. Click the Advanced button to open the Advanced Backup Options dialog box.

6. Click on the Advanced Backup Options (Startup) tab, and select Startup in suspended state and click OK.

7. From the Backup Options dialog box, click OK. You can track the progress of the backup job from the Job Controller window.

8. If you are using a stand-alone drive, you are prompted to load a specific cartridge into the drive. If you are using a library, you will not receive this prompt. The system loads the tapes automatically.

9. When the backup has completed, Job Controller displays Completed.

Start a Backup on New Media

Use the following procedure to start a backup on new media. Before You Begin

Your cartridges should be appropriately labeled. This will enable you to locate the correct cartridge for a restore job, if necessary.

(32)

6. Click on the Advanced Backup Options (Media) tab, and select Start new media and click OK. If you would like jobs with other Job IDs to use this new media, also select the Allow other schedule to use media set option.

7. From the Backup Options dialog box, click OK. You can track the progress of the backup job from the Job Controller window.

Start a Backup that Creates a New Index

Use the following procedure to start a backup that creates a new Index. Before You Begin

secure all of the data for the agent.

To start an immediate backup job with advanced backup options: 1. Select one of the following:

{ To backup a user-defined backup set, right-click the backup set you want to backup, click All

Tasks, and click Backup All Subclients.

{ For the Microsoft SQL Server iDataAgent, to backup a database, right-click the database you want

to backup, click All Tasks, and click Backup Database.

{ For the Microsoft SQL Server iDataAgent, to backup up an instance, right-click the instance you

(33)

want to backup, click All Tasks, and click Backup SQL Server.

6. Click on the Advanced Backup Options (Data) tab, and select Create new index and click OK. 7. From the Backup Options dialog box, click OK. You can track the progress of the backup job from

the Job Controller window.

Start a Backup that Marks Media Full on Completion

Use the following procedure to start a backup that marks media full on completion. Before You Begin

Starting a backup on a backup set, instance or agent level causes the system to start individual backup jobs for each subclient contained therein. If the subclients are associated with the same storage policy, then their jobs will run sequentially unless that storage policy is configured to accommodate multiple data streams.

Features - NAS NDMP Client