quick start guide solaris file system idataagent -...

QUICK START GUIDESolaris File System iDataAgent

Published On: 11/19/2013 V10 Service Pack 4A of 61

Quick Start - Solaris File System iDataAgent TABLE OF CONTENTS

OVERVIEW

SYSTEM REQUIREMENTS

SUPPORTED FEATURES

GETTING STARTEDDeployment - Global Zone or Solaris Server

Deployment - Non Global Zone

Configuration

Backup

Restore


Overview - UNIX/Linux File SystemsTABLE OF CONTENTS

Introduction

Key FeaturesSimplified Data ManagementPoint-In-Time RecoveryBackup and Recovery FailoversEfficient Job Management and ReportingBlock Level Deduplication

Add-On Components1-TouchOnePass AgentContent Indexing and Search

Terminology

INTRODUCTIONData Protection Suite software provides a simplified end-to-end protection of file system data residing on all the Unix computers in your enterprise. In addition to complete protection of file system data for disaster recovery, it also provides a robust and comprehensive backup and recovery solution with significant speed performance and efficient use of disk and tape drives. It also assists you in full system rebuilds and eliminates recovery failures.

KEY FEATURESThe Unix File System iDataAgents offers the following key features:

SIMPLIFIED DATA MANAGEMENTThe Unix File System iDataAgents enables easy management of all the UNIX systems in your environment, by providing a singular approach to manage the data using the same unified console and infrastructure.

POINT-IN-TIME RECOVERY

In the event of a serious system failure, such as the breakdown of hardware, software, or operating systems, the Unix File System iDataAgent provides point-in-time recovery of files at any given time.

BACKUP AND RECOVERY FAILOVERS

In the event that the MediaAgent used for the backup or recovery operation fails, the backup is automatically resumed on alternate MediaAgents. In such cases, the backup or restore job does not restart from the beginning, but resumes from the point of failure. This is useful for backups and restores of large amount of file system data.

In the event, that a network goes down, the backup and recovery jobs are resumed on alternate data paths. Similarly, in the event of a device failure, the jobs are automatically switched to alternate disk and tape drives.

EFFICIENT JOB MANAGEMENT AND REPORTING

You can view and verify the status of backup and recovery operations from the Job Controller and the Event Viewer within the CommCell Console. You can also track the status of the jobs using Reports, which can be saved and distributed. Generate reports for different aspects of data management. Customize the reports to display only the required data and save them to a specific location in different formats. For example, you can create a backup job summary report to view the completed backup jobs.

You can schedule, generate and send the Reports via email without user intervention.

BLOCK LEVEL DEDUPLICATION

Deduplication provides a smarter way to store data by identifying and eliminating the duplicate items in a data protection operation.

Deduplication at the data block level compares blocks of data against each other. If an object (e.g., file, database) contains blocks of data that are identical to each other, then block level deduplication does not store the redundant data, which reduces the size of the object in storage. This reduces the size of the backup data copies on both the disk and tapes.

ADD-ON COMPONENTS

1-TOUCH

1-Touch recovery helps to recover a crashed system in the least amount of time. By automatically rebuilding the operating system, you can recover systems with defective components such as inaccessible volumes or crashed disks. You don't need to reinstall the individual software packages or operating systems manually.

SIMPANA ONEPASS

The Simpana OnePass is an integrated File System agent that backs up and archives the qualified data. Simpana OnePass also reclaims backup storage space when files and stubs are deleted


on the primary storage.

CONTENT INDEXING AND SEARCH

Content Indexing and Search enables users to content index their data and later search the data from a user-friendly web interface. The users can also perform restore operations or other advanced actions on the searched data.

TERMINOLOGYThe Unix File System documentation uses the following terminology:

CLIENTThe computer in which the iDataAgent is installed and contains the data to be secured.

BACKUP SETA group of subclients which includes all of the data backed up by the iDataAgent.

SUBCLIENTThe Unix file system data to be backed up.


System Requirements - Solaris File System iDataAgentThe following are the requirements for Solaris File System iDataAgent:

CLUSTER - SUPPORT

The software can be installed on a Cluster if clustering is supported by the above-mentioned operating systems.

For information on supported cluster types, see Clustering - Support.

HARD DRIVE

1 GB of minimum disk space is required for installing the software.

5 GB of free disk space is required for job result directory.

3 GB of free disk space is required for log directory.

SOLARIS ZONES/CONTAINERS SUPPORTData Protection of data residing on global and non-global zones is supported.

For a comprehensive list of supported components, see Unix Virtualization.

MISCELLANEOUS

SCHEDULE JOBS USING A CLIENT COMPUTER'S TIME ZONE

The client computer has to be in one of the standard time zones recognized by the CommServe. Otherwise, the CommServe does not get updated with the client computer's time zone and the jobs scheduled using the client computer's time zone might not run.

MICROSOFT VISUAL C++

Microsoft Visual C++ 2010, 2008 and 2005 Redistributable Packages are automatically installed. Note that these Visual C++ Redistributable Packages can co-exist with other versions of this software.

SUPPORTED FILE SYSTEMS

Unix File System (UFS)

Oracle ASM Cluster File System (Oracle ACFS)

VERITAS File System (VxFS)

VERITAS Cluster File System (VxCFS)

Zettabyte File System (ZFS)

VOLUME MANAGERS

Veritas Volume Manager (VxVM) 5.0 or higher

Solaris Volume Manager (SVM)

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software but may not be individually listed in our System Requirements. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software. Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future releases when necessary. Please contact your Software Provider for any problem with 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

OPERATING SYSTEM ARCHITECTURE

SOLARIS Solaris 11.x x64, Sparc T/M series

Solaris 10.x with a minimum of SunOS (Sparc) Patch 119963-14 Ultra5 or higher recommended

Solaris 10.x (OpenSolaris supported) x64

Solaris 10.x (Flying Zones supported) Ultra5 or higher recommended


Getting Started - Solaris File SystemWHERE TO INSTALL

Install the software on a computer that you want to backup. This can be one of the following:

Solaris Servers

Computer hosting the global zone

It is recommended to install the software on the global zone to protect non-changing or static data on non-global zones. If the data is dynamic or contains application data, install the software on the non-global zone.

The computer will be added as a client in the CommCell as soon as the installation completes successfully.

BEFORE YOU BEGIN

System Requirements

Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements.

Download Software Packages

Download the latest software package to perform the install.

INSTALLATION

METHOD 1: REMOTE INSTALL USING COMMCELL CONSOLE

1. Ensure that the firewall and port settings are configured on the client as described in Firewall and Network Port Requirements.

2. Open CommCell Console:

Click Start and point to All Programs.

Click HDPS .

Click Backup and Recovery Administrative Console.

3. From the CommCell Browser, click Tools | Add/Remove Software | Install Software.

4. Click Next.

5. Select Unix and Linux.

Click Next.

The software can be installed using one of the following methods:


Use this procedure to install remotely on a client computer.

METHOD 2: INTERACTIVE INSTALL

Use this procedure to install the software using the standard installation options.


6. Click Manually Select Computers.

Click Next.

7. Enter the fully qualified domain name of the client computer.

For example: mycomputer.mydomain.mycompany.comClick Next.

Do not use space and the following characters when specifying the Host Name:

\|`~!_@#$%^&*()+=<>/?,[]{}:;'"

8. Choose one of the following:

Click Next if you want to use the default cache location

Click Override Software Cache and specify a new location in the Software Cache box and then click Next

The software cache is the location from where the remote install program installs the software. This screen will not appear if the remote cache is not configured. For more information, see Managing Cache - Remote Cache.


9. Specify the User Name and Password that must be used to access the client computer, and then click Next.

10. Click File System.

Click Next.

11. Select one of the following:

From the Storage Policy to use list, select a storage policy, and then click Next.

From the Subclient Policy to use list, select a subclient policy, and then click Next.

If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 19.

You can also specify the SUDO user credentials here, provided that the user is an Administrator or a member of the Administrator group with root privileges on that computer.

For steps to add a SUDO user to /etc/sudoers, see Frequently Asked Questions - Install.

Account information is required while performing remote installs for the first time on a client. For subsequent remote installs on that client, click Next without specifying the account information.

If you want to add this computer to a client group, select a client group from the Available list and click Add >.This option will be displayed only if client groups are configured in the CommCell Console. For more information, see Client Computer Groups. Select the Configure For Laptop Backups option to install Backup Monitor utility. This utility allows you to view the backup job summary from the client computer without opening the CommCell Console. See Monitor - Laptop User for more information.


12. Click Next.

If necessary you can select additional options. Click the Help button to get more information on the available options.

13. Click Next.

If necessary you can select advanced options. Click the Help button to get more information on the available options.

14. Click Next.

If necessary you can select optional settings. Click the Help button to get more information on the available options.



If firewall configuration is not required, click Next.

If this computer and the CommServe is separated by a firewall, click Configure firewall services.

For firewall options and configuration instructions, see Firewall Configuration and continue with the installation.

16. Select Immediate.

Click Next.

17. Click Finish.

This screen will reflect the components you selected for install, and may look different from the example shown.


18. You can track the progress of the job from the Job Controller window of the CommCell console.

From the Home menu, click Job Controller.

Once the job is complete, view the job details from the Admin Job History.

Right-click the <CommServe>, point to View and then click Admin Job History.

Click Select Install/Upgrade/Remove/Repair Software.

Click OK.

You can view the following by right-clicking the job:

Details of the job

Option to Resubmit the job

Events associated with the job

Logs associated with the job

Option to send the Logs associated with the job

19. To create a storage policy, you must have configured a library in the CommCell.

If you do not already have a library configured, go to Disk Library Creation.

If you have a library configured, go to Storage Policy Creation.

DISK LIBRARY CREATION:

1. From the CommCell Browser, navigate to Storage Resources, right-click the Libraries, point to Add and then click Disk Library...

Alternatively, you can also navigate to MediaAgents, right-click <MediaAgent>, point to All Tasks | Create Library and then click Disk Library...

2. From the Add Disk Library dialog box, specify the following:

In the Name box, specify name of the disk library.

From the MediaAgent list, select the MediaAgent.


Perform one of the following:

Select Local Path if you wish to specify a local path in the MediaAgent computer.

In the Disk Device box, type the name of the folder in which the disk library must located or click button to select the folder.

Select Network Path, if you wish to specify a network path as the target share.

In the Connect As box, type the user name.

In the Password and Verify Password box, type the password to access the network share.

In the Folder box, type the mount path or click button to select a mount path.

Click OK.

3. The newly created disk library will be displayed under Libraries node.

This will create a library and Storage Policy. Click to proceed to the Configuration section.

STORAGE POLICY CREATION

1. From the CommCell Browser, navigate to Policies.

2. Right-click the Storage Policies and then click New Storage Policy.

3. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:

Select the Storage Policy type as Data Protection and Archiving and click Next.

Enter the name in the Storage Policy Name box and click Next.

From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next.

Ensure that you select a library attached to a MediaAgent operating in the current release.

From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.

For the device streams and the retention criteria information, click Next to accept default values.

Select Yes to enable deduplication for the primary copy.

From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication Database (DDB).

In the Location box, type the name of the folder in which the DDB must be located or click the Browse button to select the folder and then click Next.

Review the details and click Finish to create the Storage Policy.

This will create a storage policy. Click to proceed to the Configuration section.

Several additional options are available for remotely installing the software from CommCell Console, refer to Install Software from the CommCell Console (Remote Install) for more information.



1. Logon to the client computer as root.

2. If you are installing the software from the Software Installation Discs, run the following command to mount the CD:

mount -r -F hsfs /dev/sr0 /cdromRun the following command from the Software Installation Package or mount point:

./cvpkgadd3. The product banner and other information is displayed.

Press Enter.

4. Read the license agreement. Type y and press Enter.

5. Press Enter.

Selecting Unix Setup TaskPlease select a setup task you want to perform from the list below:Advanced options provide extra setup features such as creating custom package, recording/replaying user selections and installing External Data Connector software.1) Install data protection agents on this computer2) Advanced options3) Exit this menuYour choice: [1]

6. Press Enter.

Selecting 32bit or 64bit BaseThis machine supports both 32 bit and 64 bit binaries. By default, we will install 32 bit binary set that has full support for all the modules included in this package. Please note that 64 bit binary set currently only support limited modules1) All platforms(32 bit)2) FS and MA only(64 bit)Your Choice: [1]

7. The default network interface name of the client computer is displayed if the computer has only one network interface (NIC card), press Enter to accept.

If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe, and then press Enter.

Setting Client/Physical Machine Host NameWe found one network interface available on your machine. We will associate it with the client being installed, and it will also be used by the CommServe to connect to the client. Note that you will be able to additionally customize Datapipe Interface Pairs used for the backup data traffic later in the Data Protection Suite Java GUI.Please check the interface name below, and make corrections if necessary:Client/Physical Machine Host Name: [myclient.company.com]

8. The local name of the client computer is displayed, press Enter to accept.

If necessary you can also enter a new (friendly) name for the client, and then press Enter. This name will be used in the CommCell and will also be displayed in the CommCell Console.

Do not use spaces when specifying a new name for the client.

Setting Client NamePlease 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.Physical Machine Client name: [myclient]

9. Type the number associated with File System and press Enter.

Selecting Modules to Install.[ ] 1) File System Core [1002] [CVGxBase][ ] 2) File System [1101] [CVGxIDA][ ] 3) MediaAgent [1301] [CVGxMA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA][ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB][ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA][ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostGres iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 2

10. Type d for Done, and press Enter.

Selecting Modules to Install.[ ] 1) File System Core [1002] [CVGxBase][X] 2) File System [1101] [CVGxIDA][ ] 3) MediaAgent [1301] [CVGxMA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA][ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB][ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA]

The interface names and IP addresses depend on the computer in which the software is installed and may be different from the example shown.


[ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostGres iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

11. Press Enter.

Deciding if to Config for Laptop or Desktop BackupsDo you want to configure the iDataAgent for laptop or desktop backups?Config for Laptop or Desktop Backups? [no]

12. Press Enter.

Deciding if to Install Agents for Restore OnlyDo you want to install the agents for restore only without consuming licenses?Install Agents for Restore Only? [no]

13. Verify the default path for software installation.

Press Enter.

If necessary, enter a path to modify the default path and press Enter.

Do not install the software to a mapped network drive

Do not use the following characters when specifying the path:

!@#$%^&*():/?\

It is recommended that you use alphanumeric characters only

Preparing Installation DirectoryPlease specify where you want us to install Data Protection Suite binaries.It must be a local directory and there should be at least 900MB of free space available. All files will be installed in a "hds" subdirectory, so if you enter "/opt", the files will actually be placed into "/opt/hds".Installation Directory: [/opt]

14. Verify the default path for log files.

Press Enter.



!@#$%^&*():/?\


All the modules installed on the computer will store the log files in this directory.

Preparing Log DirectoryPlease specify where you want to keep Data Protection Suite log files.It must be a local directory or NFS share and there should be at least 100MB of free space available. All log files will be created in a "hds/Log_Files" subdirectory, so if you enter "/var/log", the logs will actually be placed into "/var/log/hds/Log_Files".Log Directory: [/var/log]

15. Press Enter.

Deciding If to Use a Unix GroupMost of Data Protection Suite processes run with root privileges, but some are launched by databases and inherit database access rights. To make sure that registry and log files can be written to by both kinds of processes we can either make such files world-writeable or we can grant write access only to processes belonging to a particular group, e.g. a "hds" or a "dba" group.We highly recommend now that you create a new user group and enter its name in the next setup screen. If you choose not to assign a dedicated group to Data Protection Suite processes, you will need to specify the access permissions later.If you're planning to backup Oracle DB you should use "dba" group.Would you like to assign a specific group to Software? [yes]

16. Type the Group name and press Enter.

Press Enter again.

Setting Unix GroupPlease enter the name of the group which will be assigned to all Data Protection Suite files and on behalf of which all Data Protection Suite processes will run.In most of the cases it's a good idea to create a dedicated "hds" group.However, if you're planning to use Oracle iDataAgent or SAP Agent, you should enter Oracle's "dba" group here.Group name: testgrp1REMINDERIf you are planning to install Data Protection Suite Informix, DB2, Sybase or Lotus Notes iDataAgent, please make sure to include Informix, DB2, etc. users into group "testgrp1"..Press <ENTER> to continue...

17. Type d for done with the selection and press Enter.

Setting Access Permissions for Group and Other UsersInstaller will assign full access rights to root user for all installed Data Protection Suite files and its processes.For group and any other users, you can specify the access permissions now.If you did not assign a dedicated group in previous step, make sure you specify sufficient access rights for other users if you are also planning to install Data Protection Suite agents involving third party software protection.[X] 1) Allow read permission to group users[X] 2) Allow write permission to group users[X] 3) Allow execute permission to group users[X] 4) Allow read permission to other users[ ] 5) Allow write permission to other users[X] 6) Allow execute permission to other users


[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

18. The default port numbers used for CommCell communication is displayed. If necessary, you can modify the port numbers.

Press Enter.

Setting Instance Port Number of cvdEvery instance of Data Protection Suite should use a unique set of network ports to avoid interfering with other instances running on the same machine.The port numbers selected must be from the reserved port number range and have not been registered by another application on this machine.Please enter the port numbers.Port Number for CVD : [8400]

19. Press Enter.

Setting Instance Port Number of EvMgrCEvery instance of Data Protection Suite should use a unique set of network ports to avoid interfering with other instances running on the same machine.The port numbers selected must be from the reserved port number range and have not been registered by another application on this machine.Please enter the port numbers.Port Number for CVD: 8400Port Number for EvMgrC: [8402]

20. Do one of the following:

If firewall configuration is not required, press Enter.

If this computer and the CommServe is separated by a firewall, type Yes and then press Enter.

For firewall options and configuration instructions, see Firewall Configuration.

Deciding If to Configure FirewallYou need to configure firewall settings if there is a firewall between this client and the CommServe.Is there a firewall between this client and the CommServe? [no]

21. Type the fully qualified domain of the CommServe host name and press Enter.

Do not use space and the following characters when specifying the CommServe Host Name:

\|`~!@#$%^&*()+=<>/?,[]{}:;'"

Setting CommServe Host NamePlease specify hostname of the CommServe below. Make sure the hostname is fully qualified, resolvable by the name services configured on this machine.CommServe Host Name: mycommserve.company.com

22. If you have enabled per-client certificate on CommServe, type y and press Enter.

Else, press Enter.

Specifying If CommServe Per-Client Certificate is EnabledIf you have checked "Force per-client certificate authentication on CommServe" on the CommServe or Proxy, you need to provide installer with a Temp Certificate.This Temp Certificate can be obtained by opening "Certificate Administration Applet" from the Java GUI's Control Panel, clicking "Temp Certificate" button, selecting newly created client in the popped up window and copying/pasting generated certificate to a local file accessible from this installer.Have you enabled per-client certificate authentication on CommServe? [no]


1 - To inherit global filter policy configuration set for the CommCell.

2 - To apply the global filters policy to the default subclient regardless of the policy set for the CommCell.

3 - If you plan to define specific filters for the Agent.

Press Enter.

Selecting How to Set Commcell Level Global FiltersCommcell Level Global Filters are set through Data Protection Suite GUI's Control Panel in order to filter out certain directories or files from backup Commcell-widely.If you turn on the Global filters, they will be effective to the default subclient.There are three options you can choose to set the filters. Please select how to set the Global Filters for the default subclient?1) Use Cell level policy2) Always use Global filters3) Do not use Global filtersYour Choice: [1]

24. Type the appropriate number to select the Client Group and press Enter.

Selecting Client Computer GroupsClient Group(s) is currently configured on CommServe mycommserve.company.com. Please choose the group(s) that you want to add this client myclient.company.com to.[ ] 1) Client Grp1[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 1


Selecting Client Computer GroupsClient Group(s) is currently configured on CommServe mycommserve.company.com. Please choose the group(s) that you want to add this client myclient.company.com to.[X] 1) Client Grp1[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

26. Press Enter.

This screen will be displayed only if Client Groups are configured for the CommCell.


Deciding if to Configure Storage PolicyWould you like to configure Storage Policy on this client?Configure? [no]

Adjusting modes and permissions of files...done.Starting Data Protection Suite services...done.Thank you for choosing Data Protection Suite.

If you do not have Storage Policy created, this message will be displayed. You may not be prompted for user input. You can create the Storage Policy later in step 26.

There seem to be no Storage Policies configured on the CommServe. Before you can run any backups of this IDA, you will need to install a MediaAgent, create a Storage Policy and assign it to all subclients..

















Click OK.

















If you already have a storage policy selected in step 24, click to proceed to the Configuration section.

If you do not have Storage Policy created, continue with the following step.



ADDITIONAL INSTALLATION METHODS

Remote Install

Deploy the software from CommCell Console on multiple clients.


Getting Started - Solaris File SystemSKIP THIS PAGE IF YOU ARE NOT INSTALLING THIS AGENT ON A NON-GLOBAL ZONE.Click to continue with the deployment.

WHERE TO INSTALL

Install the software on a computer that you want to backup on a Non-Global Zone.

It is recommended to install the software on the global zone to protect non-changing or static data on non-global zones. If the data is dynamic or contains application data, install the software on the non-global zone.

In a clustered environment, install the software on the physical computer.

The computer will be added as a client in the CommCell as soon as the installation completes successfully.

BEFORE YOU BEGIN

System Requirements




INSTALLATION





Click HDPS .



4. Click Next.


Click Next.

The software can be installed using one of the following methods:


Use this procedure to install remotely on a client computer.


Use this procedure to install the software using the standard installation options.



Click Next.

7. Enter the fully qualified domain name of the client computer.

For example: mycomputer.mydomain.mycompany.comClick Next.

Do not use space and the following characters when specifying the Host Name:

\|`~!_@#$%^&*()+=<>/?,[]{}:;'"






9. Specify the User Name and Password that must be used to access the client computer, and then click Next.


Click Next.




If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 19.

You can also specify the SUDO user credentials here, provided that the user is an Administrator or a member of the Administrator group with root privileges on that computer.

For steps to add a SUDO user to /etc/sudoers, see Frequently Asked Questions - Install.

Account information is required while performing remote installs for the first time on a client. For subsequent remote installs on that client, click Next without specifying the account information.



12. Click Next.


13. Click Next.


14. Click Next.








Click Next.

17. Click Finish.








Click OK.


Details of the job






















Click OK.


















Several additional options are available for remotely installing the software from CommCell Console, refer to Install Software from the CommCell Console (Remote Install) for more information.




2. If you are installing the software from the Software Installation Discs, run the following command to mount the CD on the non-global zone:

mkdir <Non-Global Zone root location>/<Non-Global Zone local directory>

mount –F lofs <Global zone software Install package mount point> <Non-Global Zone root location>/<Non-Global Zone local directory>

Connect to Non-Global Zone terminal

Run the following command from the Software Installation Package or mount point:


Press Enter.


5. Press Enter.


6. Press Enter.












Selecting Modules to Install.[ ] 1) File System Core [1002] [CVGxBase][X] 2) File System [1101] [CVGxIDA][ ] 3) MediaAgent [1301] [CVGxMA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA]



[ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB][ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA][ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostGres iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

11. Press Enter.


12. Press Enter.



Press Enter.




!@#$%^&*():/?\




Press Enter.



!@#$%^&*():/?\




15. Press Enter.



Press Enter again.



Setting Access Permissions for Group and Other UsersInstaller will assign full access rights to root user for all installed Data Protection Suite files and its processes.For group and any other users, you can specify the access permissions now.If you did not assign a dedicated group in previous step, make sure you specify sufficient access rights for other users if you are also planning to install Data Protection Suite agents involving third party software protection.[X] 1) Allow read permission to group users[X] 2) Allow write permission to group users


[X] 3) Allow execute permission to group users[X] 4) Allow read permission to other users[ ] 5) Allow write permission to other users[X] 6) Allow execute permission to other users[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d


Press Enter.


19. Press Enter.









\|`~!@#$%^&*()+=<>/?,[]{}:;'"



Else, press Enter.






Press Enter.





Selecting Client Computer GroupsClient Group(s) is currently configured on CommServe mycommserve.company.com. Please choose the group(s) that you want to add this client myclient.company.com to.



[X] 1) Client Grp1[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

26. Press Enter.



If you do not have Storage Policy created, this message will be displayed. You may not be prompted for user input. You can create the Storage Policy later in step 26.


















Click OK.














If you already have a storage policy selected in step 24, click to proceed to the Configuration section.

If you do not have Storage Policy created, continue with the following step.






ADDITIONAL INSTALLATION METHODS

Custom Package

Create a compact software package for quick deployment to multiple clients.

Decoupled Install

Install the software first and later register the client in the CommCell.

Remote Install

Deploy the software from CommCell Console on multiple clients.

Installing Restore Only Agents

Setup a client in the CommCell for restore purposes.

Silent Install

Deploy the software silently on multiple clients.


Getting Started - Solaris File System - Deployment on a Veritas Cluster

SKIP THIS PAGE IF YOU ARE NOT INSTALLING THIS AGENT ON A VERITAS CLUSTER. CLICK TO CONTINUE WITH THE DEPLOYMENT.

Steps involved in installing the File System Agent in a Clustered environment:

1. INSTALL THE SOFTWARE ON PHYSICAL NODES

2. CONFIGURE THE CLUSTER GROUP CLIENT

BEFORE YOU BEGIN

System Requirements


Network TCP Port Requirements

Review the Network TCP Port requirements specified in Network TCP Port Requirements.

License Requirements

Review the license requirements specified in License Requirements.



INSTALL THE SOFTWARE ON PHYSICAL NODES





Click HDPS .



4. Click Next.


Deployment - Global Zone Deployment - Non-Global Zone Deployment - Veritas Cluster Deployment - Non-Veritas Cluster Configuration Backup Restore

The software can be installed on the Physical nodes using one of the following methods:

METHOD 1 : REMOTE INSTALL USING COMMCELL CONSOLE

Use this procedure to install remotely on the physical nodes.

METHOD 2 : INTERACTIVE INSTALL

Use this procedure to Install the software on the physical nodes from the active node of a cluster group.


Click Next.


Click Next.

7. Enter the fully qualified domain name of each of the physical computers (nodes) on which you want to install the software.

Fully qualified domain name of each physical computer must be specified in a separate line.

For example, if your cluster group is hosted on two nodes (physicalcomputer1 and physicalcomputer2), then specify as following:

physicalcomputer1.mydomain.mycompany.comphysicalcomputer2.mydomain.mycompany.com

Click Next.




Make sure that the physical computers (active node and passive node) that you specify here are reachable from the CommServe computer. Do not use space and the following characters when specifying the Host Name:

\|`~!_@#$%^&*()+=<>/?,[]{}:;'"



9. Specify the User Name and Password that can be used to access the physical computers that you specified in step 6, and then click Next.


Click Next.




If you do not have a Storage Policy, the list will not be displayed. You can create a Storage Policy later using the steps described in the Configuring storage Policy section.

You can also specify SUDO user account credentials here, provided that the user is an Administrator or a member of the Administrator group with root privileges on all the physical computers.

For steps to create a SUDO user, see Frequently Asked Questions - Install.

Account information is required while performing remote installs for the first time on a client. For subsequent remote installs on the same clients, you can click Nextwithout specifying the account information.



12. Click Next.


13. Click Next.


14. Click Next.








Click Next.

17. Click Finish.








Click OK.


Details of the job





After installing the software successfully on all the physical computers that host the Cluster Group, refer to the Configure the Cluster Group Client section for step-by-step instructions to configure the cluster group client from the CommCell Console.


The File System agent software component must be installed on all the physical nodes that host the Cluster Group.



Repeat the following steps on each of the physical nodes that host the Cluster Group.




Press Enter.


5. Press Enter.


6. Press Enter.












Selecting Modules to Install.[ ] 1) File System Core [1002] [CVGxBase][X] 2) File System [1101] [CVGxIDA][ ] 3) MediaAgent [1301] [CVGxMA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA][ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB][ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA][ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostGres iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>




11. Press Enter.


12. Press Enter.



Press Enter.




!@#$%^&*():/?\




Press Enter.



!@#$%^&*():/?\




15. Press Enter.



Press Enter again.



Setting Access Permissions for Group and Other UsersInstaller will assign full access rights to root user for all installed Data Protection Suite files and its processes.For group and any other users, you can specify the access permissions now.If you did not assign a dedicated group in previous step, make sure you specify sufficient access rights for other users if you are also planning to install Data Protection Suite agents involving third party software protection.[X] 1) Allow read permission to group users[X] 2) Allow write permission to group users[X] 3) Allow execute permission to group users[X] 4) Allow read permission to other users[ ] 5) Allow write permission to other users[X] 6) Allow execute permission to other users[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d


Press Enter.



19. Press Enter.









\|`~!@#$%^&*()+=<>/?,[]{}:;'"



Else, press Enter.






Press Enter.






26. Press Enter.







After installing the software successfully on all the physical computers that host the Cluster Group, refer to the Configure the Cluster Group Client section for step-by-step instructions to configure the cluster group client from the CommCell Console.

CONFIGURE THE CLUSTER GROUP CLIENT

After installing the software successfully on all the physical nodes that host the cluster group, you must configure the cluster group client from the CommCell Console. Use the following steps to configure the cluster group client.

1. From the CommCell Browser, right-click the Client Computers node, point to New Client | Clustered Server and then click Unix Cluster.

2. In the Client Name box, type a name for the cluster group. The client name can be any unique name.

In the Host Name box, you can type either the fully qualified domain name of the cluster group or the IP address of the cluster group.

3. Review the cluster group information and click Finish.

Advanced Client Properties window is displayed now.

4. On the Advanced Client Properties dialog box, click the Cluster Group Configuration tab.

All the Linux clients that are available in the CommCell will be listed in the Available list. Select the physical computers (nodes) where you installed the necessary agents from the Available list, and then click Add > to move the client to the Selected list.

Click the Agents tab.Select the agents you want to use in the cluster group client from the Available list and click Add > to move the Agent to the Selected list.

The Host name of the cluster group client should not be used by any existing client in your CommCell. If you want to specify the IP address of the cluster group, ensure that the IP address is static.

If the client computer properties dialog box is not displayed automatically, then you need to open it manually: Right-click the <Cluster Group Client>, and then click Properties. Click Advanced on the Client Computer Properties dialog box. Click Cluster Group Configuration tab on the Advanced Client Properties dialog box.


5. Click the Agents tab.

Select the agents you want to use in the cluster group client from the Available list and click Add > to move the agent to the Selected list.

6. Click the Job Configuration tab.

Type or click Browse to specify the path for the Job Results Directory in the cluster group client.

Click OK.

7. Click OK.

The cluster group client is successfully created.

CONFIGURING STORAGE POLICY

If you do not have a Storage Policy created, use the following steps to create a storage policy:

In order to configure a Cluster Group Client, the agents should be installed on all the clustered nodes for proper failover. If an agent is not installed on all the nodes, then the agents selection tab on the Advanced Client Properties window will display the agent name in plain text (not in bold). However, you can still configure the Cluster Group Client even when the Agents are not installed on a particular node; installation can be done later using remote install procedure.

Ensure that the Job Results Directory resides on a shared clustered drive. In the case of MediaAgent and ContinuousDataReplicator, the Job Result directory path will be used for the Index Cache and CDR Log directories respectively if no directory location is provided.


To create a storage policy, you must have configured a library in the CommCell.
















Click OK.

















Getting Started - Solaris File System - Deployment on a Non-Veritas ClusterSKIP THIS PAGE IF YOU ARE NOT INSTALLING THIS AGENT ON A NON-VERITAS CLUSTER. CLICK TO CONTINUE WITH THE CONFIGURATION.

Steps involved in installing the File System Agent in a Clustered environment:

1. INSTALL THE SOFTWARE ON PHYSICAL COMPUTERS

2. CONFIGURE THE CLUSTER GROUP CLIENT

3. CONFIGURE CLUSTER RESOURCES

4. CONFIGURE FAILOVERS

BEFORE YOU BEGIN

System Requirements


Network TCP Port Requirements

Review the Network TCP Port requirements specified in Network TCP Port Requirements.

License Requirements

Review the license requirements specified in License Requirements.



INSTALL THE SOFTWARE ON PHYSICAL NODES





Click HDPS .



4. Click Next.

The software can be installed on the Physical nodes using one of the following methods:

METHOD 1 : REMOTE INSTALL USING COMMCELL CONSOLE

Use this procedure to install remotely on the physical nodes.

METHOD 2 : INTERACTIVE INSTALL

Use this procedure to Install the software on the physical nodes from the active node of a cluster group.



Click Next.


Click Next.

7. Enter the fully qualified domain name of each of the physical computers (nodes) on which you want to install the software.

Fully qualified domain name of each physical computer must be specified in a separate line.

For example, if your cluster group is hosted on two nodes (physicalcomputer1 and physicalcomputer2), then specify as following:

physicalcomputer1.mydomain.mycompany.comphysicalcomputer2.mydomain.mycompany.com

Click Next.




Make sure that the physical computers (active node and passive node) that you specify here are reachable from the CommServe computer. Do not use space and the following characters when specifying the Host Name:

\|`~!_@#$%^&*()+=<>/?,[]{}:;'"

The software cache is the location from where the remote install program installs the software.


9. Specify the User Name and Password that can be used to access the physical computers that you specified in step 6, and then click Next.


Click Next.





This screen will not appear if the remote cache is not configured. For more information, see Managing Cache - Remote Cache.

You can also specify SUDO user account credentials here, provided that the user is an Administrator or a member of the Administrator group with root privileges on all the physical computers.

For steps to create a SUDO user, see Frequently Asked Questions - Install.

Account information is required while performing remote installs for the first time on a client. For subsequent remote installs on the same clients, you can click Nextwithout specifying the account information.



12. Click Next.


13. Click Next.


14. Click Next.








Click Next.

17. Click Finish.








Click OK.


Details of the job





After installing the software successfully on all the physical computers that host the cluster group, you must configure the Cluster Group Client from the CommCell Console. Use the steps described in the Configure the Cluster Group Client section for configuring the Cluster Group Client.


The File System agent software component must be installed on all the physical nodes that host the Cluster Group.



Repeat the following steps on each of the physical nodes that host the Cluster Group.




Press Enter.


5. Press Enter.


6. Press Enter.












Selecting Modules to Install.[ ] 1) File System Core [1002] [CVGxBase][X] 2) File System [1101] [CVGxIDA][ ] 3) MediaAgent [1301] [CVGxMA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA][ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB][ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA][ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostGres iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>




11. Press Enter.


12. Press Enter.



Press Enter.




!@#$%^&*():/?\




Press Enter.



!@#$%^&*():/?\




15. Press Enter.



Press Enter again.



Setting Access Permissions for Group and Other UsersInstaller will assign full access rights to root user for all installed Data Protection Suite files and its processes.For group and any other users, you can specify the access permissions now.If you did not assign a dedicated group in previous step, make sure you specify sufficient access rights for other users if you are also planning to install Data Protection Suite agents involving third party software protection.[X] 1) Allow read permission to group users[X] 2) Allow write permission to group users[X] 3) Allow execute permission to group users[X] 4) Allow read permission to other users[ ] 5) Allow write permission to other users[X] 6) Allow execute permission to other users[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d


Press Enter.



19. Press Enter.









\|`~!@#$%^&*()+=<>/?,[]{}:;'"



Else, press Enter.






Press Enter.






26. Press Enter.







After installing the software successfully on all the physical computers that host the cluster group, you must configure the Cluster Group Client from the CommCell Console. Use the steps described in the Configure the Cluster Group Client section for configuring the Cluster Group Client.

CONFIGURE THE CLUSTER GROUP CLIENT

After installing the software successfully on all the physical nodes that host the cluster group, you must configure the cluster group client from the CommCell Console. Use the following steps to configure the cluster group client.

1. From the CommCell Browser, right-click the Client Computers node, point to New Client | Clustered Server and then click Unix Cluster.

2. In the Client Name box, type a name for the cluster group. The client name can be any unique name.

In the Host Name box, you can type either the fully qualified domain name of the cluster group or the IP address of the cluster group.

3. Review the cluster group information and click Finish.

Advanced Client Properties window is displayed now.

4. On the Advanced Client Properties dialog box, click the Cluster Group Configuration tab.

All the Linux clients that are available in the CommCell will be listed in the Available list. Select the physical computers (nodes) where you installed the necessary agents from the Available list, and then click Add > to move the client to the Selected list.

Click the Agents tab.Select the agents you want to use in the cluster group client from the Available list and click Add > to move the Agent to the Selected list.

The Host name of the cluster group client should not be used by any existing client in your CommCell. If you want to specify the IP address of the cluster group, ensure that the IP address is static.

If the client computer properties dialog box is not displayed automatically, then you need to open it manually: Right-click the <Cluster Group Client>, and then click Properties. Click Advanced on the Client Computer Properties dialog box. Click Cluster Group Configuration tab on the Advanced Client Properties dialog box.


5. Click the Agents tab.

Select the agents you want to use in the cluster group client from the Available list and click Add > to move the agent to the Selected list.

6. Click the Job Configuration tab.

Type or click Browse to specify the path for the Job Results Directory in the cluster group client.

Click OK.

7. Click OK.

The cluster group client is successfully created.

CONFIGURE CLUSTER RESOURCES

After installing the software component (s) on the physical nodes and the cluster group client is configured, you must configure the Cluster resources.

In order to configure a Cluster Group Client, the agents should be installed on all the clustered nodes for proper failover. If an agent is not installed on all the nodes, then the agents selection tab on the Advanced Client Properties window will display the agent name in plain text (not in bold). However, you can still configure the Cluster Group Client even when the Agents are not installed on a particular node; installation can be done later using remote install procedure.

Ensure that the Job Results Directory resides on a shared clustered drive. In the case of MediaAgent and ContinuousDataReplicator, the Job Result directory path will be used for the Index Cache and CDR Log directories respectively if no directory location is provided.


Configure Services using VERITAS Cluster Administrator.

Create a resource for the cluster plugin service.

Add Service Dependencies.

CONFIGURE FAILOVERS

A failure of any Agent software on the active node in a UNIX cluster will not cause a failover to be initiated.

The cvclusternotify script should be added as part of the normal cluster startup/shutdown procedure. The script is provided as a generic template, and it must be run at the beginning of node shutdown and at the end of new active node startup. In both cases, data protection services must be up and running.

Run the following command to notify Data Protection Suite that the specified "Cluster Group" is going up or down because of a cluster failover:

Usage:

cvclusternotify -inst <Instance> -cn <Client Name> -start|-shutdownWhere:

cvclusternotify - Program to notify Data Protection Suite of cluster failovers

Example:

For a two-node cluster, if the cluster group client name is "ClusterGroup1" and the application instance is "Instance001", run the following command:

To shutdown:

cvclusternotify -inst Instance001 -cn "ClusterGroup1" -shutdown

To start up:

cvclusternotify -inst Instance001 -cn "ClusterGroup1" -start

CONFIGURING STORAGE POLICY

If you do not have a Storage Policy created, use the following steps to create a storage policy:

To create a storage policy, you must have configured a library in the CommCell.
















Click OK.

















Getting Started - Solaris File SystemCONFIGURATION

Once installed, follow the steps given below to assign a storage policy with the default subclient.

1. From the CommCell Browser:

Navigate to <Client> | File System | defaultBackupSet.

Right click the default subclient and click Properties.

2. Click the Storage Device tab.

In the Storage Policy box, select the storage policy.

Click OK.

Click to continue. If you do not have Storage Policy created, follow the step given below to create a storage policy.

3. Creating a Storage Policy:

a. Click Create Storage Policy.

b. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:

i. Select the Storage Policy type as Data Protection and Archiving and click Next.

ii. Enter the name in the Storage Policy Name box and click Next.

iii. From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next.


iv. From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.

v. For the device streams and the retention criteria information, click Next to accept default values.

vi. Select Yes to enable deduplication for the primary copy.

vii. From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication database (DDB).

In the Location box, type the name of the folder in which the DDB must be located or click the Browse to select the folder, and then click Next.

viii. Review the details and click Finish to create the Storage Policy.


Getting Started - Solaris File System

PERFORM A BACKUP

Once the storage policy is configured, you are ready to perform your first backup.

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | defaultBackupSet.

Right-click the default subclient and click Backup.

2. Click Full as backup type and then click Immediate.

Click OK.


4. Once the job is complete, view the job details from the Backup History. Right-click the Subclient and select Backup History.

5. Click OK.

Deployment - Global Zone Deployment - Non-Global Zone Deployment - Veritas Cluster Deployment - Non-Veritas Cluster Configuration Backup Restore


6. You can right-click the job and view the following details:

Items that failed during the job

Details of the job

Events of the job

Log files of the job

Media associated with the job

WHAT GETS BACKED UP WHAT DOES NOT GET BACKED UP

FILE SYSTEMS

Unix File System (UFS)

Oracle ASM Cluster File System (Oracle ACFS)

VERITAS File System (VxFS)

VERITAS Cluster File System (VxCFS)

Zettabyte File System (ZFS)

Extended attributes in the VxFS, UFS, and ZFS file systems

In a zone environment, Loopback File System (LOFS) is backed up by default. If you do not want to backup LOFS file system, you can exclude it by Configuring Filters For Backups.

VOLUME MANAGERS

Veritas Volume Manager (VxVM) 5.0 or higher

Solaris Volume Manager (SVM)

By default, the following file systems are automatically skipped during backups:

nfs nfs3 nfs4 hsfs autofs mvfs lofs tmpfs proc ctfs

FILE SYSTEM ELEMENTS

Files with holes

Files with Advisory Locks

Raw device files

Symbolic links that are browsed or manually added to the data contents

Files with names containing non-ASCII characters as long as the appropriate locales are set

Shares with Macintosh File System data

Files for which the file path or file name contains more than 1024 characters

Files with mandatory locks - these files are not backed up by default. See Configuring Backups For Locked Files to backup files with mandatory locks.


Getting Started - Solaris File SystemPERFORM A RESTORE

It is recommended that you perform a restore operation immediately after your first full backup to understand the process. The following section explains how to restore the etc folder to a new location.

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | defaultBackupSet.

Right-click the default subclient and then click Browse and Restore.

2. Click the Advanced Options tab.

Select the MediaAgent that was used during the storage policy creation from the Use MediaAgent drop-down list. This MediaAgent should be the one you installed along with your agent.

Click View Content.

3. Expand the defaultBackupSet and navigate to etc folder.

Select the etc folder.

Click Recover All Selected.

4. Clear the Overwrite Files and Restore to same folder options.

Specify the destination path by clicking Browse button.

This will ensure that the existing files are not overwritten.

Click OK.


5. Click the Job Initiation tab.

Select Immediate to run the job immediately.

Click OK.

6. You can monitor the progress of the restore job in the Job Controller window of the CommCell Console.

7. Once the restore job is complete, right-click the defaultBackupSet , point to View, and then click Restore History.

8. Click OK.


9. You can right-click the job and view the following details:

View Restore Items

You can view them as Successful, Failed, Skipped or All.

View Job Details

View Events of the restore job

View Log files of the restore job

10. Once the restore job completes successfully, verify that the restored files/folders are available in the restore destination provided during step 4.

[derp] # ls /.etc

etc

CONGRATULATIONS - YOU HAVE SUCCESSFULLY COMPLETED YOUR FIRST BACKUP AND RESTORE.

If you want to further explore this Agent's features read the Advanced sections of this documentation.


quick start guide solaris file system idataagent -...

Documents