HP Application Recovery Manager software A.06.
Legal and notice information © Copyright 2006, 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Publication history ................................................................ 7 About this guide ................................................................... 9 Reference page organization ................................................................................ 9 Intended audience ............................................................................................. 10 Documentation set .....................................................................................
omnistat ........................................................................................................... 85 omniusers ......................................................................................................... 89 III Section 1M: Administrative Commands .............................. 93 dbtool.pl .......................................................................................................... 95 ob2install ...................................................................
Tables 1 Edition history ................................................................................... 7 2 Documentation map ......................................................................... 12 3 Document conventions ......................................................................
Publication history Guide updates may be issued between editions to correct errors or document product changes. To ensure that you receive updated or new editions, subscribe to the appropriate product support service. See your HP sales representative for details. Table 1 Edition history Part number Guide edition Product T4395-96007 October 2006 Application Recovery Manager Release A.06.00 N/A March 2008 Application Recovery Manager Release A.06.
Publication history
About this guide This guide provides information about: • Application Recovery Manager command line interface commands, their options, and usage This reference guide does not describe concepts, the GUI, or provides details about the integrations. The HP Application Recovery Manager software command line interface reference contains the reference pages for Application Recovery Manager A.06.10 commands. Reference pages are available on UNIX systems as man pages.
All commands in a section are sorted by alphabetical order. Reference pages are often referred by name and section number in the form pagename(section). Intended audience This guide is intended for administrators with knowledge of: • Basic operating system commands and utilities • Command prompt/shell concepts and usage • Application Recovery Manager backup and restore concepts The reference pages supplement other Application Recovery Manager documentation and require good overall knowledge of the product.
This guide describes Application Recovery Manager zero downtime backup and instant recovery concepts and provides background information on how Application Recovery Manager works in a zero downtime backup environment. It is intended to be used with the task-oriented HP Application Recovery Manager software administrator's guide and the HP Application Recovery Manager software integration guide.
• UNIX: Unpack the zipped tar file AppRM_help.tar.gz, and access the online help system through AppRM_help.htm. Documentation map Abbreviations The guide titles are all preceded by the words “HP Application Recovery Manager software”. Map The following table shows where to find information of different kinds. Shaded squares are a good place to look first.
CLI reference Integration guide X Supported configurations Troubleshooting Administrator's guide Concepts guide Product announcements Installation guide Getting started Online Help Support matrices X X X X Document conventions and symbols Table 3 Document conventions Convention Element Blue text: Table 3 on page 13 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
IMPORTANT: Provides clarifying information or specific instructions. NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Reference page conventions All reference pages follow established section formats, but not all sections are present in each reference (man) page. NAME Gives the name of the command and a brief description of the commands purpose. SYNOPSIS Describes the syntax of the command.
• Vertical bars (|) between several arguments indicate that only one argument from the group can be specified at once. Groups can be optional (inside square brackets) or required (inside curly brackets, {}). DESCRIPTION A more detailed description of the command. OPTIONS Detailed descriptions for all options. NOTES Contains important notes. EXAMPLES Provides examples on command usage. SEE ALSO Lists man pages, containing related information.
Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP websites For additional information, see the following HP websites: • • • • • http://www.hp.com http://www.hp.com/go/software http://www.hp.com/service_locator http://www.hp.com/support/manuals http://www.hp.
Section 9: Introduction Command line interface reference 17
Section 9: Introduction
omniintro introduction to HP Application Recovery Manager software command utilities omniintro DESCRIPTION Application Recovery Manager is a scalable recovery software solution providing automated backup and recovery of Exchange, SQL, SAP, and Oracle application data designed to improve application availability with data recovery in minutes. COMMANDS User Commands (1): omniabort Aborts an active session. omnib Backs up filesystems, disk images, SAP R/3 and Oracle databases, and VSS writers.
Queries the VSS database; manages, browses, and lists the items of the VSS database. omnidbxp Queries the ZDB database (XPDB), manipulates the XP LDEV exclude file, and configures the HP StorageWorks Disk Array XP command devices usage. omnidlc Gathers or deletes Application Recovery Manager debug, log and getinfo files from the Application Recovery Manager cell. omnir Restores filesystems, disk images, and application databases backed up using Application Recovery Manager.
Handles various Application Recovery Manager internal database (IDB) maintenance tasks. It can only be run on the Cell Manager. omnidlc Gathers or deletes Application Recovery Manager debug, log and getinfo files from the Application Recovery Manager cell. omnihealthcheck Checks the status of Application Recovery Manager services and the consistency of the Application Recovery Manager internal database (IDB). It can only be run on the Cell Manager.
Possible return values for CLI commands are: 1 Program failed, command syntax error. 2 Program failed, invalid argument. 3 Program failed, internal error. 4 Program failed, reason unknown. Some CLI may return additional error messages. These are described in individual reference pages.
cell cell configuration schedules backup schedules barschedules database backup specification schedules sessions data about sessions options default options sg scripts for Service Guard support /etc/opt/omni/client • Directory containing the client configuration directories and files /opt/omni • Directory containing the following executables directories: bin user Application Recovery Manager commands lbin ZDB Agent files and some administrative commands sbin Cell Manager and Application Recovery Manager int
/var/opt/omni/server/db40/datafiles the IDB tablespaces /var/opt/omni/server/db40/smisdb the ZDB database (SMISDB) /var/opt/omni/server/db40/logfiles the IDB transaction logs and the obdrindex.
schedules backup schedules barschedules database backup specification schedules options default options sessions data about sessions AppRM_home\Config\client • Directory containing the client configuration directories and files AppRM_home\bin • Directory containing Application Recovery Manager commands, message catalogs and commands for Cell Manager maintenance.
• the ZDB database (XPDB) AppRM_home\db40\vssdb • the VSS database (VSSDB) AppRM_home\help • the Application Recovery Manager help subsystem SEE ALSO dbtool(1M), ob2install(1M), omniabort(1), omnib(1), omnicc(1), omnicellinfo(1), omnicheck(1M), omniclus(1), omnidb(1), omnidbcheck(1M), omnidbinit(1M), omnidbsmis(1), omnidbvss(1), omnidbxp(1), omnidlc(1M), manager(5), xomni(5), omnihealthcheck(1M), omniinstlic(1M), omnimigrate.pl(1M), omnidbutil(1M), omnir(1), omnirsh(1M), omnisetup.
Section 1: User Commands Command line interface reference 27
Section 1: User Commands
omniabort aborts an active session. omniabort SYNOPSIS omniabort -version | -help omniabort -session SessionID DESCRIPTION This command aborts an active session, identifying it by the SessionID. A list of all active sessions and their session IDs is available using the omnistat command. OPTIONS -version Displays the version of the omniabort command. -help Displays the usage synopsis for the omniabort command. -session SessionID Specifies the SessionID of the session to be aborted.
omnib backs up filesystems, disk images, SAP R/3 and Oracle databases, and VSS writers.
OPTIONS -version Displays the version of the omnib command -help Displays the usage synopsis for the omnib command -restart SessionID Tries to restart a failed session, specified by its sessionID. -sap_list ListName Specifies the name of the SAP R/3 backup specification file for the backup. The SAP R/3 backup specification contains the SAP R/3 objects to be backed up. -oracle8_list ListName Specifies the name of the Oracle backup specification file for the backup.
-no_monitor By default, the command monitors the session and displays the status of the session during the session. If this option is used, only the SessionKey is displayed, and the command is disconnected from the session. RETURN VALUES See the man page omniintro for return values. Additional return values of the omnib command are: 10 There was an error while backing up some components. All agents completed successfully. 11 One or more agents failed, or there was a database error.
omnicc handles the Application Recovery Manager licensing, reports the number of configured and available Application Recovery Manager licenses, installs the licenses, imports and exports Application Recovery Manager clients, and manages access to secured clients.
If the -detail option is specified, a detailed report is produced. The following information is returned for every license in the cell: license name, licenses installed, licenses used and licenses required. -query Displays information about the number of available licenses. -import_host ClientName [-virtual] Imports the specified client into a cell. This allows you to move a client between two cells without reinstalling the Application Recovery Manager modules.
Application Recovery Manager port is allowed to do so. This security mechanism instructs the client to accept such actions only from the systems specified by this option. -unsecure_client ClientName Specifies the client from which you want to remove security. Such a client will enable access to all systems in the cell. -install_license password Installs an encrypted Application Recovery Manager license. The password must be formatted as a single line and must not contain any embedded carriage returns.
omnicellinfo displays configuration information about the Application Recovery Manager cell.
-db Displays information about the Application Recovery Manager internal database (IDB). The database is divided in logical structures, for each of these structures the report shows: Disk Space Used, Records Used and Records Total. -cell Displays information about the configured clients in the cell. The report shows for each client: client name, operating system, cell console version, and GUI version.
SEE ALSO omnicc(1), omnicheck(1M), omnisv(1M), omnidlc(1M), omniinstlic(1M) Command line interface reference 41
omniclus manages load balancing in a cluster environment in the event of an application (Application Recovery Manager or other) failover.
Specifies the session(s) to which the abort message should be sent. -abortsess Specifies the abort session command. -abortid{== | !=} application_id Specifies the application identification. -inhibit{* | 0 | minutes} Specifies the number of minutes for Cell Manager backup inactivity, where * means forever and 0 means activate now. NOTE The command can only be used in the cluster environment. EXAMPLES Following example illustrates how the omniclus command works. 1.
because an application server switches, while the application server backup can be aborted. 4. Temporarily disabling the Application Recovery Manager cell The following command will inhibit backup sessions for twenty minutes: omniclus -clus cluster.domain.com -inhibit 20 The following command will inhibit backup sessions forever: omniclus -clus cluster.domain.com -inhibit * Note: On UNIX systems replace the * wildcard with '*'.
omnidb queries the Application Recovery Manager internal database (IDB).
• list backed up objects and their details (for example: client name, set, label, object type, object status, backup type), message logs The omnidb command performs basic IDB queries. OPTIONS -version Displays the version of the omnidb command -help Displays the usage synopsis for the omnidb command -since Date Lists sessions since the given Date. -until Date Lists sessions until the given Date. -last n Lists sessions that occurred within the last n days.
Displays session information in a form specially suited for further use of awk, grep or perl. Records are separated with blank lines and line feed is the field separator. If no SessionID is specified, all backup sessions are shown. Each record contains the following fields: the ID, backup specification name, status, start time in format HH:MM and duration in hours as a floating point number. For the example of how this option can be used see the script omninotify.pl.
This option works in three different ways. If sessionID is specified it strips the detail catalogs for all objects of session with specified SessionID. If both SessionID and ObjectName are specified it strips the detail catalog of the object identified by ObjectName for the session with specified SessionID. If no option is specified, it strips catalogs on all data objects that are no longer protected.
omnidbsmis executes administrative tasks required for managing the HP StorageWorks SMI-S EVA provider.
The omnidbsmis command can be used to manipulate the EVA disk group pairs configuration file. By default, the snapclones are created in the same disk group as the source volumes. However, you can define the allocation of snapclones and allocate them to a disk group other than the one used for the source volumes. The omnidbsmis options used for manipulating the EVA disk group pairs configuration filer, which should be used together with the -dgrules option, are: -init, -put, -get, -check.
The omnidbsmis command can be used to delete volumes of specific backup sessions (replicas or replica sets) from the disk array and information about them from the ZDB database. It can perform deletion only for a specific backup session (replica), identified by the backup session ID, or for all backup sessions based on a specific backup specification (replica set), identified by the backup specification name.
The -passwd password option sets the password that will be used for logging in to SMI-S EVA provider. If you omit this parameter, the command will ask for a password interactively. -ompasswd {-remove hostname | -delete hostname} Removes a system with SMI-S EVA provider installed (together with the login and port number information), which has a name hostname, from the SMISDB. The –delete option is only an alias for –remove.
Prepares the EVA disk group pairs configuration file for editing by reading the contents of the file from the SMISDB and saving it under filename. -dgrules -check EVA_name DG_name Provides the information on the disk group that is in pair with the disk group identified by the EVA_name and DG_name. The command returns the information on the 1st disk group name, 2nd disk group name, and EVA name. If there is no rule for the specified disk group, the first and the second disk groups are the same.
If used together with the -excluded option, the command lists the sessions that are excluded from use (replica set rotation and possibility to perform instant recovery). If used together with the -original option, the command lists all original replicas in the IR database. -list -datalist Lists all backup specifications that are part of a replica set with existing members. Note that you will get the same output if you run the omnidbsmis -datalist command without the -list parameter.
If used with the -preview option, the command does not delete anything, but lists replicas/replica sets that will be deleted if -delete -session sessionID or -delete -datalist DatalistName commands are run. -delete -force Forces deletion of the replicas even if they are presented to hosts. -delete -host hostname Sets another location to start the deletion.
You can also set optional parameters, such as the port number and username. If you omit these parameters, the command will take the default values. 4. To perform a health check of you environment on the local host, run the following command: omnidbsmis -ompasswd -check 5.
8. To find out the name, ID, WWW, type, and time stamp of the target volumes created in the backup session with the session ID “2008/05/13-3”, run the following command: omnidbsmis -session 2008/05/13-3 9.
omnidbvss queries the VSS database; manages, browses, and lists the items of the VSS database. omnidbvss SYNOPSIS omnidbvss omnidbvss omnidbvss omnidbvss omnidbvss omnidbvss omnidbvss omnidbvss -init -list session [-barlist barlist] -list disk -remove session SessionID [—reference] -remove disk StorageID [—reference] -purge -barlist BackupSpecName -get session [-export_metadata Folder] -get disk StorageID DESCRIPTION The omnidbvss command is used to query the VSS database.
Marks the specified SessionID for removal. The session’s replicas will be removed from the disk array and from the database at the next backup using the backup specification which created the session or when the -purge option is used. If -reference is specified, an entry is removed only from the database. This option can be used to remove an entry that points to a replica that no longer exists.
omnidbvss -get "STORAGE#Volume#1&30a96598&0&SignatureB6893593Offset7E00Length 3FBB8600#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}" SEE ALSO omnidb(1M), omnidbutil(1M), omnidbcheck(1M) Command line interface reference 63
omnidbxp queries the ZDB database (XPDB), manipulates the XP LDEV exclude file, and configures the HP StorageWorks Disk Array XP command devices usage.
ignored by Application Recovery Manager and such a session fails with critical error. The list of disabled LDEVs is kept in the XP LDEV exclude file on the Cell Manager: /var/opt/omni/server/db40/xpdb/exclude/XPexclude (UNIX Cell Manager) or in AppRM_home\db40\exclude\XPexclude (Windows Cell Manager). The omnidbxp options to be used for querying the XPDB and manipulating the XP LDEV exclude file are: -exclude, -put, -get, -check, -init, -delete, -session, -list, -show, -ir, -ldev, -show.
Optionally, an instance number can be assigned too. If the instance number is not specified, Application Recovery Manager assigns the lowest not yet assigned instance number. The entire information is written in the XPDB. 2. List all command devices in the XPDB. 3. Remove a specific or all command devices from the XPDB or update the information about a specific command device in the XPDB.
Specifies that the current omnidbxp command is executed only for the LDEVs pairs marked for the instant recovery in the XPDB. If this option is not specified, the current command is executed for all LDEVs pairs in the XPDB. -session -list Lists all available sessions in the XPDB. -session -show sessionID Lists all backup system S-VOL LDEVs that were involved in the session with the sessionID. -ldev -list Lists all S-VOL LDEVs in the XPDB together with their corresponding backup sessionID.
The command does not check whether the specified command device or system exist, it only checks if the optional instance number specified is within the correct range and if the command device together with the instance number is not already assigned to be used by some other system. If the checks fail, the command fails with an error message. -cm -remove all Removes the information about all command devices from the XPDB.
omnidbxp -exclude -check 12345 2864 3. To list all backup system LDEVs, regardless of they being marked for instant recovery or not, that were involved in the session with the sessionID “2007/09/18-22”, execute the following command: omnidbxp -session -show 2007/09/18-22 4. To list all command devices in the XPDB, execute the following command: omnidbxp -cm -list 5.
omnir restores filesystems, disk images, and application databases backed up using Application Recovery Manager. omnir SYNOPSIS omnir -version | -help [vss | oracle | sap | filesystem] VSS RESTORE omnir -vss -barhost ClientName -session SessionID -tree TreeName1 [-tree TreeName2...
-session SessionID {DISK_ARRAY_XP_OPTIONS | ENTERPRISE_VIRTUAL_ARRAY_OPTIONS} [-recover {disk | prog ProgramName} {now | time MM/DD/YY hh:mm:ss | logseq LogSeqNum thread ThreadNum | SCN Number} -appname ApplicationDatabaseName -parallelism Number [-open [-resetlogs]] [-user UserName -group GroupName ]] [—preview] [GENERAL_OPTIONS] SAP R/3 RESTORE omnir -sap -host ClientName -session SessionID {DISK_ARRAY_XP_OPTIONS | ENTERPRISE_VIRTUAL_ARRAY_OPTIONS} [ -appname ApplicationDatabaseName [-user UserName -group
DESCRIPTION The omnir command restores objects backed up using Application Recovery Manager. You can use the omnir command to start the instant recovery process of the VSS writers, Oracle databases, SAP R/3 databases, and filesystems. The omnir command also supports parallel restore. You can achieve this by specifying more than one object using the command line options.
VSS_Options -conf_check {strict | non-strict | disabled} Sets the configuration check mode. If the check fails, the instant recovery session will fail. Select the strict mode to check each file or directory. Select the non-strict mode to check each folder. Disable configuration check only if instant recovery cannot be performed with an enabled configuration check and only if you are sure that this will not result in a loss of data during the instant recovery.
Throttles down the consistency check to lessen impact on restore performance. Set the number of input/output operations, after which the check is stopped for one second. Exchange_2007_Specific_Options -appsrv ClientName Specifies the system to which the components are restored. If not specified, the components are always restored to the server from where they were backed up. Note that all objects in one restore session must be restored to the same system.
-target_dir Directory During an instant recovery session, the replica will be mounted to Directory. The target directory for one session must always be the same, for example, you cannot specify one target directory for the store(s) and another one for the logs. Oracle/SAP_Specific_Options -oracle Selects the Oracle options for instant recovery. -sap Selects the SAP R/3 options for instant recovery.
–parallelism Number (Oracle specific option) The number of RMAN channels used for recovery. Mandatory if the -recover option is specified. -open Opens the database after recovery. -resetlogs Resets the logs after the database is opened. Available only if the -open option is specified. This option is not available if the -recovery option is set to now. The following are recommendations on when to reset the logs.
configuration on the node to which instant recovery is to be performed is different from the volume group configuration kept in the XPDB. In such a case the XPDB volume group configuration data is replaced by the current volume group configuration data on the node to which instant recovery is to be performed and the session is not aborted. When performing instant recovery in an MC/ServiceGuard cluster to some other node than the one that was backed up, select this option.
dismounted, SMIS-S Agent will force dismount if the option is selected. Otherwise, instant recovery fails. VSS_ENTERPRISE_VIRTUAL_ARRAY_OPTIONS -no_copy_back If this option is specified, a replica from the specified backup session is switched with the source volume. Once used, the replica is not available for another instant recovery session. -copy_back If this option is specified, copy back is performed. This is also the default behavior when neither -no_copy_back nor -copy_back is specified.
-no_diskarray_wait If this option is specified, the source volume is immediately available while the synchronization or copy process is running in the background (quick restore). The SSE Agent does not wait for the synchronization or copy process to complete. If this option is not specified, there is a 60–minute delay before the background processes can run. GENERAL_OPTIONS -variable VariableName VariableValue This option lets you specify a variable name and its value for proper operation.
EXAMPLES The following examples illustrate how the omnir command works. 1. To perform an instant recovery of filesystem backup data on HP StorageWorks Disk Array XP to the system named “computer” from the backup session “2008/01/02-1”, keeping the replica on the backup system disk: omnir -host computer -session 2008/01/02-1 -keep_version 2.
omnir —vss -use_vds —barhost system1 —session 2007/08/07-9 -tree "/SqlServerWriter(SQL Server 2005:SQLWriter)" -no_recovery 7. To recover an SAP R/3 database, named “sap2.company.com” on the client “san32.company.com” from the session “2007/09/05-18” until the most recent time, and open the database after the recovery, execute the following command: omnir -host san32.company.com -instant_restore -sap -session 2007/09/05-18 –appname sap2.company.com -recovery now -open 8.
Store)/Microsoft Information Store/First Storage Group/Logs" -target_dir "c:\mnt" 11. Restore to a non-Exchange location and create RSG: To restore the Exchange 2007 Writer store “Store One” from the storage group named “First Storage Group” from the backup session “2007/04/10-9“ on the system “exch2007.company.
omnistat displays the status of active Application Recovery Manager backup and restore sessions. omnistat SYNOPSIS omnistat -version | -help omnistat -session SessionID [-status_only | -monitor | -detail] omnistat [-user Username] [-error] [-detail] omnistat -previous [-user Username] [{-since Date | -until Date} | -last Number] [-failed] Date [YY]YY/MM/DD DESCRIPTION The omnistat command displays information on active sessions.
Displays detailed information about all current sessions. -user Username Displays information on active sessions belonging to the specified user. -failed Displays information on sessions containing data objects that failed due to errors. -error Displays information on active sessions with the status "In Progress (errors)" -previous Lists all sessions from the Application Recovery Manager internal database (IDB). -since Date Lists all sessions since the specified Date.
SEE ALSO omniabort(1) Command line interface reference 87
omniusers adds or removes Application Recovery Manager users to or from an existing Application Recovery Manager user group, or lists the configured Application Recovery Manager users. It enables you to use all GUI functionality on a Cell Manager platform on which the GUI is not available, using a GUI installed on another system.
Specifies username of the user to be added/removed. By specifying asterisk (*) as the username, all users from the specified group (on UNIX systems) or domain (on Windows systems) will be granted/revoked access from the specified clients to the Cell Manager. * corresponds to in the Application Recovery Manager GUI. Note that in some shells, backslash and asterisk (\*) must be used instead of *.
UNIX group or Windows domain, fully qualified domain name (FQDN) of the client system from which the user has granted access, and the user description are displayed. Asterisk (*) corresponds to the string in the Application Recovery Manager GUI. RETURN VALUES The return values of the omniusers command are: 0 The command operation completed successfully. 1 A generic error occurred. 2 The operation for adding or removing a user failed. 4 Error parsing options.
3. To add the UNIX user “root” to the Application Recovery Manager “admin” user group and allow access from any UNIX group but only from the system “client.company.com”, run the following command: omniusers -add -type U -name root -usergroup admin -group \* -client client.company.com 4. To display the Application Recovery Manager users in all configured Application Recovery Manager user groups, run the following command: omniusers -list SEE ALSO omnimigrate.pl(1M), ob2install(1M), omnigui(5), omnisetup.
Section 1M: Administrative Commands Command line interface reference 93
Section 1M: Administrative Commands
dbtool.pl backs up and restores the Application Recovery Manager IDB and configuration. dbtool.pl SYNOPSIS perl dbtool.pl -version | -help perl dbtool.pl -config Root= backup_location CountLimit= max_number_of_backups SizeLimit= max_occupied_space [MB | KB | GB] Timeout= time_until_session_completes [sec | min | hour] perl dbtool.pl -backup perl dbtool.pl -restore [FromFile] perl dbtool.pl -getconfig perl dbtool.
-help Displays the usage synopsis of the dbtool.pl command. -configRoot= backup_location CountLimit= max_number_of_backups SizeLimit= max_occupied_space [MB|KB|GB] Timeout=time_until_session_completes[sec|min|hour] Root is the destination folder, in which the backups are stored. The default location is AppRM_home\tmp. The backups are named apprm_idb_YYYYMMDD_HHMMSS.zip, where YYYYMMDD_HHMMSS represents the time at which the backup session was started.
2. Run the backup session: perl dbtool.pl -backup 3. To restore the backup “apprm_idb_20070723_221500.zip” created on the 23rd July 2007 at 22:15:00, run: perl dbtool.pl -restore e:\AppRM_IDB\apprm_idb_20070723_221500.
ob2install runs remote client installation, uninstallation, or check of a client from the selected Installation Server. This command is available on UNIX systems only. ob2install SYNOPSIS ob2install -version | -help ob2install -server installation_server -input filename DESCRIPTION The ob2install command is used for running remote client installation from the Cell Manager. You have to select an Installation Server from which you want to run remote client installation.
-component version Selects the components for the installation. The version argument specifies the version of the product. For the A.06.10 release, for example: -smisa A.06.10. Select only the components that are supported on target Application Recovery Manager system.
General installation type can have two values: 1 or 2. 2 specifies a client installation. 1 is reserved for future extensions. For Application Recovery Manager A.06.10 release only the client installation is supported. InstallationType Specifies installation type: 1 new installation 2 update 3 delete 4 check installation NOTES The command can only be used locally on the UNIX Cell Manager. EXAMPLES The following example illustrates how the ob2install command works.
omnicheck performs a DNS connections check within an Application Recovery Manager cell and lists Application Recovery Manager patches installed on Application Recovery Manager clients.
OPTIONS -version Displays the version of the omnicheck command -help Displays the usage synopsis of the omnicheck command. -dns Checks that the Cell Manager resolves DNS connections to every Application Recovery Manager client in the same cell properly and vice versa. This option performs the same as running the omnicheck -dns -host cell_manager command.
client_1 failed to connect to client_2 checking connection between client_1 and client_2 all checks completed successfully. number_of_failed_checks checks failed. client is not a member of the cell. client contacted, but is apparently an older version. Hostname is not checked.
omnicheck -patches -host backup.system.
omnidbcheck checks the consistency of the Application Recovery Manager internal database (IDB). It can only be run on the Cell Manager. omnidbcheck SYNOPSIS omnidbcheck omnidbcheck omnidbcheck omnidbcheck omnidbcheck omnidbcheck omnidbcheck -version | -help [-quick | -extended] -core [-summary] -filenames [-summary] -bf [-summary] -sibf [-detail] [-summary] -smbf [-detail | dumpmessages] [-summary] Limitscope -hostshost1 [host2 ...
OPTIONS -version Displays the version of the omnidbcheck command. -help Displays the usage synopsis for the omnidbcheck command. -quick Checks the core, CDB filenames and presence and size of DCBF parts of the IDB and displays the summary of the check by executing the omnidbcheck -core -filenames -bf -summary command. -extended Checks the entire IDB with the exception of the SMBF and displays the summary of the check by executing the omnidbcheck -core -filenames -bf -dc -sibf command.
-dumpmessages This option is used with the -smbf option. It sends the session messages in the SMBF to the standard output. -summary Displays only the summary of the check (OK or failed/missing). The option does not impact the thoroughness of the check. LimitScope It is also possible to limit the scope of the DC check to either a set of media or a set of clients: -hosts host1 [host2...] Only Detail Catalogs for the specified clients are checked.
omnidbinit initializes the Application Recovery Manager internal database (IDB). It can only be run on the Cell Manager. omnidbinit SYNOPSIS omnidbinit -version | -help omnidbinit [-force] DESCRIPTION The omnidbinit command initializes the Application Recovery Manager internal database (IDB). All information about sessions, media and objects is lost after the initialization. The command does not delete IDB transaction logs.
SEE ALSO omnidb(1), omnidbcheck(1M), omnidbsmis(1) 112
omnidbutil handles various Application Recovery Manager internal database (IDB) maintenance tasks. It can only be run on the Cell Manager. omnidbutil SYNOPSIS omnidbutil -help omnidbutil -version omnidbutil -readdb [-cdb Directory] omnidbutil -writedb omnidbutil -extendtblspace Tablespace Pathname -maxsize Size_MB omnidbutil -extendinfo omnidbutil -purge {-filenames [host_1 [host_n...
These tasks involve operations such as extending tablespaces, purging the obsolete pathnames from the CDB, displaying the information about the IDB and the IDB upgrade, changing references in object versions from one device to some other device, changing the owner of the CDB to the current Cell Manager, displaying the CDB owner, and more.
The -messages option removes session messages for all sessions older than NumberOfDays. The -daily option starts the same purge session as started every day at 12.00 (depending on the Application Recovery Manager global options file setting) and is a part of Application Recovery Manager daily maintenance tasks.
If you want to associate all media in a CMMDB with the current Cell Manager, it is necessary to run the command once for each Cell Manager that has media associated with it, using the old_host parameter. The old_host parameter must be specified exactly the same as the owner of the media. If the system's Fully Qualified Domain Name (FQDN) is associated with the media, then you must also use the FQDN with this command. If the old_host parameter is not specified correctly, the operation will not be performed.
EXAMPLES The following examples illustrate how the omnidbutil command works. 1. To create a new DC directory in the "c:\temp\test" directory with maximum size 1000 MB, run: omnidbutil -add_dc c:\temp\test -maxsize 1000 SEE ALSO dbtool.
omnidlc gathers or deletes Application Recovery Manager debug, log and getinfo files from the Application Recovery Manager cell. omnidlc SYNOPSIS omnidlc -version | -help omnidlc {-session sessionID | -did debugID | -postfix string | -no_filter} [-hosts list] [-pack filename | -depot [directory] | -space | -delete_dbg] [-no_getinfo] [-no_logs] [-no_debugs] [-no_compress] [-debug_loc dir1 [dir2 ...
Optionally, files can be sent over the network to the Cell Manager uncompressed (if the -no_compress option is specified). Besides that (if the -depot option is specified), the transferred files can be left unpacked in the specified directory on the Cell Manager, in which the directory structure that includes the hostnames, paths and the collected files of the clients involved is generated as follows: On UNIX: ./dlc/system_1/tmp/debug_files ./dlc/system_1/log/log_files ./dlc/system_1/getinfo/get_info.txt .
When collecting or deleting files or when displaying the required disk space, additional criteria can be defined to limit the files selection. Thus, it is possible to exclude the getinfo file, the log files, the debug files or any combination of the three groups of files from the selection. Using the command, the collected files can then be additionally packed to be sent to the support center. The command provides also a means of unpacking the packed collected files.
(on Windows). You cannot add directories, but only files. If the files are not copied to one of the specified directories, the package cannot be unpacked during the unpack phase. -depot [directory] If the directory is specified, the collected files are not packed and are saved to the dlc directory of the specified directory. If the directory is not specified, the files are saved in the AppRM_home\tmp\dlc directory on the Windows Cell Managers, or in the /tmp/dlc on UNIX Cell Managers.
To add files other than the collected files to the package, copy the files to one of the following directories before running the command: dlc/client/getinfo, dlc/client/log, or dlc/client/tmp (on UNIX), or .\dlc\client\getinfo, .\dlc\client\log, or .\dlc\client\tmp (on Windows). You cannot add directories, but only files. If the files are not copied to one of the specified directories, the package cannot be unpacked during the unpack phase.
2. To collect only the log and debug files (without the getinfo files) from the clients “client1.company.com” and “client2.company.com” to the directory “c:\depot” on the Cell Manager, without compressing and packing the files, run: omnidlc -no_filter -hosts client1.company.com client2.company.com -depot c:\depot -no_getinfo -no_compress 3. To collect log, debug, and getinfo files from the client “client1.company.com”, compress and pack them to the “c:\pack\pack.
omnihealthcheck checks the status of Application Recovery Manager services and the consistency of the Application Recovery Manager internal database (IDB). It can only be run on the Cell Manager. omnihealthcheck SYNOPSIS omnihealthcheck -version | -help omnihealthcheck [-config ConfigFile] DESCRIPTION The omnihealthcheck command reads the specified configuration file where each line of the file is treated as a separate command and is executed.
or in /var/opt/omni/server/log/HealthCheck.log on the UNIX Cell Manager. If a timeout occurs, omnihealthcheck fails. Omnihealthcheck is by default scheduled to run daily at 12:00 (Noon) as a part of the Application Recovery Manager check mechanism. The default schedule value can be changed by changing the DailyCheckTime option in the Application Recovery Manager global options file.
omniinstlic starts the HP OpenView AutoPass utility or synchronizes the Application Recovery Manager licenses between Application Recovery Manager and HP OpenView AutoPass. omniinstlic SYNOPSIS omniinstlic -version | -help omniinstlic [-sync] DESCRIPTION If the command is run without options, the licensing data in HP OpenView AutoPass is synchronized with the licensing data in Application Recovery Manager, and then the HP OpenView AutoPass utility is started.
EXAMPLE To start the HP OpenView AutoPass utility, run: omniinstlic SEE ALSO omnicc(1), omnicellinfo(1), omnisv(1M), omnicheck(1M), omnidlc(1M) 128
omnimigrate.pl helps you migrate your existing Cell Manager from a PA-RISC architecture based HP-UX 11.x system to an HP-UX 11.23 system for the Intel Itanium 2 (IA-64) architecture. omnimigrate.pl SYNOPSIS omnimigrate.pl omnimigrate.pl omnimigrate.pl omnimigrate.pl ure_cm] -help -prepare_clients New_CM_ClientName -configure [-configure_clients] [-configure_idb] [-config- DESCRIPTION Omnimigrate.pl helps you migrate your existing Cell Manager from a PA-RISC architecture based HP-UX 11.
If any of the clients is inaccessible, it will not be imported to the new cell. You can re-run the omnimigrate.pl command with this option when the clients are accessible to migrate them to the new Cell Manager. The old Cell Manager will automatically become a client in the new cell. You can uninstall the Cell Manager component from the old Cell Manager, because it is not necessary anymore. The option should be used only on the new Cell Manager.
NOTES This command is supported only on HP-UX systems. EXAMPLES 1. Run the following command on the old Cell Manager to add the new Cell Manager with the client name "dfg.company.com" to the list of trusted hosts on secured clients: omnimigrate.pl -prepare_clients dfg.company.com 2. To migrate the IDB, reconfigure the Cell Manager's settings, export all clients from the old Application Recovery Manager cell and import them to the new cell, run the following command on the new Cell Manager: omnimigrate.
omnirsh returns the hostnames of the physical and virtual nodes for the specified cluster hostname, or returns the cell information stored in the cell_info file on the specified cluster. omnirsh SYNOPSIS omnirsh -version | -help omnirsh cluster_hostname {INFO_CLUS | INFO} DESCRIPTION The omnirsh command returns the hostnames of the physical and virtual nodes for the specified cluster hostname, together with the flag indicating whether a specific node is a physical node or virtual node.
/etc/opt/omni/server/cell (UNIX Cell Manager) directory on the Cell Manager.
omnisetup.sh installs an Application Recovery Manager UNIX Cell Manager, Installation Server, or client system locally. omnisetup.sh SYNOPSIS omnisetup.sh -version | -help omnisetup.
• On the Cell Manager only, when the installation is started, you are prompted to install the HP OpenView AutoPass utility (unless the -autopass option is specified — if it is, the HP OpenView AutoPass utility is installed or upgraded without issuing a prompt). If AutoPass is already installed on the system, it is automatically upgraded, if the prompt is confirmed. When Application Recovery Manager is uninstalled from the system, the HP OpenView AutoPass utility is neither unregistered nor uninstalled.
prompt for every Application Recovery Manager software component supported on the current system OS; prompting whether to install certain Application Recovery Manager software component or not. -CM Installs the Application Recovery Manager Cell Manager. -IS Installs the Application Recovery Manager Installation Server with all push packages. -autopass If this option is specified, the HP OpenView AutoPass utility is automatically installed.
omnisv starts, stops or displays the status of Application Recovery Manager daemons (HP-UX Cell Manager) or services (Windows Cell Manager). It can only be run on the Cell Manager. omnisv SYNOPSIS omnisv -help omnisv -version omnisv {-start | -stop | -status | -start_mon} DESCRIPTION The omnisv command enables you to start or stop Application Recovery Manager services and display their status. Omnisv can start or stop the RDS, CRS, and MMD services on the Cell Manager.
Displays the version of the omnisv command. -help Displays the usage synopsis of the omnisv command. -start Starts the Application Recovery Manager services (on Windows) and adds the omnitrig command to the cron table, thus configuring it as a cron job (on UNIX). -stop Stops the services (on Windows) and removes the omnitrig command from the cron table (on UNIX). -status Displays the status and PID of the services. -start_mon Waits in loop until the CRS, MMD, and RDS services are up and running.
omnitrig triggers Application Recovery Manager scheduled backups. omnitrig SYNOPSIS omnitrig omnitrig omnitrig omnitrig -version | -help [-start] [-log] -stop -run_checks DESCRIPTION The omnitrig command checks and triggers scheduled backups. OPTIONS -version Displays the version of the omnitrig command -help Displays the usage synopsis for the omnitrig command -start Adds the omnitrig command to the cron table and schedules it.
By default, these checks are started automatically every day at 12:30 P.M. You can change the time of these checks or disable them by changing the DailyCheckTime option in the global options file. NOTES The command can only be used locally on the Cell Manager system.
util_cmd sets, retrieves or lists the parameters stored in the Application Recovery Manager Oracle and SAP R/3 configuration files.
• variables that need to be exported prior to starting a backup and which affect every Oracle instance on the Oracle server.
Displays the version of the util_cmd command. -help Displays the usage synopsis for the util_cmd command. -getconf[ig] integration instance Lists the Application Recovery Manager configuration files parameters for the specified integration and instance to the standard output, unless the -local option is specified.
2. To set the Application Recovery Manager “OB2OPTS” and “ORA_NLS_CHARSET” parameters for the SAP R/3 instance “ICE”, run the following commands on the Application Recovery Manager SAP R/3 client: util_cmd -putopt SAP ICE OB2OPTS'-debug 1-200 INSTANCE.txt' -sublist Environment util_cmd -putopt SAP ICE ORA_NLS_CHARSET 'AMERICAN_AMERICA.US7ASCII' -sublist Environment 3. To list the Application Recovery Manager configuration file parameters for the Oracle instance “ICE”, run: util_cmd -getconf Oracle8 ICE 4.
util_oracle8.pl configures an Oracle database and prepares the environment for backup, and checks the configuration of an Oracle database. util_oracle8.pl SYNOPSIS util_oracle8.pl -version | -help util_oracle8.pl -chkconf -dbname DB_NAME [-client CLIENT_NAME] util_oracle8.pl -chkconf_ir -dbname DB_NAME [-clientCLIENT_NAME] util_oracle8.
In an RAC environment: Name of the node or the virtual server of the Oracle resource group. The latter can only be used on HP-UX: Name of the database to be configured. -dbname DB_NAME Name of the database to be configured. -orahome ORACLE_HOME Pathname of the Oracle Server home directory. -config Configures an Oracle database. -chkconf Checks the configuration of an Oracle database. -chkconf_ir Checks if an Oracle configuration is suitable for instant recovery.
/var/opt/omni/tmp directory on the backup host to hold the copy of the raw logical volume. EXAMPLES The following names are used in the examples below: • database name: oracl • Oracle Server home directory: app10g/oracle10g/product/10.1.0 • primary user name: system • primary password: manager • primary net service name 1: netservice1 • primary net service name 2: netservice2 1. The following example illustrates the configuration on HP-UX of an Oracle database: /opt/omni/lbin/util_oracle8.
Section 5: Miscellaneous Command line interface reference 151
Section 5: Miscellaneous
omnigui Describes usage for the Application Recovery Manager Windows command manager and the following Application Recovery Manager UNIX commands: xomni, xomnibackup, xomnimonitor, xomniinstrec.
xomniinstrec starts the Application Recovery Manager GUI with the Instant Recovery context activated Windows command: manager Starts the Application Recovery Manager GUI with all Application Recovery Manager contexts activated, or, when additional options are specified, starts only the specified Application Recovery Manager context(s). OPTIONS -help Displays the usage synopsis for the command. -server hostname Connects to the specified Cell Manager.
This UNIX command will start the Application Recovery Manager GUI with all contexts activated on the system with the hostname “host1”. 2. manager This Windows command will start the Application Recovery Manager GUI with all contexts activated. 3. xomni -monitor -instrec -server host2 This UNIX command will start the Application Recovery Manager GUI with the Monitor and Instant Recovery contexts activated and will connect to the Cell Manager with the hostname “host2”. 4.
