HP StorageWorks Application Recovery Manager Command Line Interface Reference Manufacturing Part Number: T4395-96007 Manual Edition: December 2007 © Copyright 2007 Hewlett-Packard Company.
Document History Introduction to HP StorageWorks Application Recovery Manager Command Line Interface Reference Section 9: Introduction omniintro (9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Section 1: User Commands omniabort (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 omnib (1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
manager (5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Hewlett-Packard Company -3- AppRM A.06.
Document History Manual 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 Manual Edition Product T4395-96007 October 2006 Application Recovery Manager Release A.06.00 T4395-96007 July 2007 Application Recovery Manager Release A.06.00 with patch APPRMWIN_00002.
Introduction to HP StorageWorks Application Recovery Manager Command Line Interface Reference The HP StorageWorks Application Recovery Manager Command Line Interface Reference contains the reference pages for HP StorageWorks Application Recovery Manager A.06.00 commands. The command synopsis for every command is also available using the -help option. For an introduction to Application Recovery Manager A.06.00 commands, refer to the omniintro(9) reference page.
Where: • Italic strings represent variables that should be replaced by the user with the appropriate value. • Square brackets ([]) indicate that the argument is optional. • An ellipsis (...) indicates that the previous argument can be repeated. • 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.
Section 9: Introduction Hewlett-Packard Company -7- AppRM A.06.
omniintro (9) omniintro (9) NAME omniintro – introduction to HP StorageWorks Application Recovery Manager command utilities DESCRIPTION HP StorageWorks Application Recovery Manager is an enterprise backup solution that provides reliable data protection and high accessibility for business data. Application Recovery Manager provides extensive unattended backups, post-backup data management and integrations with various databases.
omniintro (9) omnir Restores filesystems and VSS writers backed up using Application Recovery Manager. omnistat Displays the status of active backup and restore sessions. Administrative Command-line Commands (1M): dbtool.pl Backs up and restores the Application Recovery Manager IDB and configuration. omnicheck Performs DNS connections check within an Application Recovery Manager cell and lists Application Recovery Manager patches installed on Application Recovery Manager clients.
omniintro (9) Return Values 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. The winomnimigrate.pl command returns a different set of errors. See the winomnimigrate.pl(1m) reference page.
omniintro (9) \Config\client Directory containing the client configuration directories and files \bin Directory containing Application Recovery Manager commands, message catalogs and commands for Cell Manager maintenance.
omniintro (9) SEE ALSO omniabort(1), omnib(1), omnicc(1), omnicellinfo(1), omnicheck(1M), omniclus(1), omnidb(1), omnidbcheck(1M), omnidbinit(1M), omnidbsmis(1), omnidbvss(1), omnidlc(1M), manager(5), omnihealthcheck(1M), omniinstlic(1M), omnidbutil(1M), omnir(1), omnirsh(1M), omnistat(1), omnisv(1M), omnitrig(1M), winomnimigrate.pl (1M) AppRM A.06.
Section 1: User Commands Hewlett-Packard Company -13- AppRM A.06.
omniabort (1) omniabort (1) NAME omniabort – aborts an active session 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.
omnib (1) omnib (1) NAME omnib – backs up filesystems and VSS writers. SYNOPSIS omnib -version | -help omnib -msvssw_list ListName [-barmode VSSMode] [LIST_OPTIONS] omnib -restart SessionID LIST_OPTIONS -barcmnd Command -no_monitor OTHER OPTIONS VSSMode = full | copy DESCRIPTION The omnib command uses a backup specification to back up data objects. The following Application Recovery Manager functionality is supported: Session management Controls the backup sessions.
omnib (1) -help Displays the usage synopsis for the omnib command -restart SessionID Tries to restart a failed session, specified by its sessionID. -msvssw_list ListName Specifies the name of the MS VSS backup specification file for the backup. The MS VSS backup specification contains the MS VSS objects to be backed up. LIST OPTIONS -barcmnd Command Specifies the command that will be used instead of the command specified with exec option in the backup specification.
omnib (1) SEE ALSO omnir(1) Hewlett-Packard Company -17- AppRM A.06.
omnicc (1) omnicc (1) NAME omnicc – reports the number of configured and available Application Recovery Manager licenses, installs the licenses, imports and exports systems in and out of a cell, manages access to secured clients.
omnicc (1) If the -detail option is not specified, the command returns information on whether the Application Recovery Manager licensing is covered or not. 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.
omnicc (1) -authorities ClientName [ClientName2...] Specifies systems from which the specified client accepts requests on the Application Recovery Manager port (by default 5555). Consequently, other computers will not be able to access this client. For tasks like backup and restore, starting pre- or post-execution scripts, or importing and exporting clients, the client checks whether the computer which triggers one of these tasks via the Application Recovery Manager port is allowed to do so.
omnicellinfo (1) omnicellinfo (1) NAME omnicellinfo – displays configuration information about the Application Recovery Manager cell SYNOPSIS omnicellinfo -version | -help omnicellinfo -group omnicellinfo {-object [schedule | no_schedule] [-group Group]} | -db omnicellinfo {-dlinfo [-group Group]} | -cell [brief] {-schinfo [Backup_Specification | -days NumberDays | -group Group]} | -allbdf | -acl DESCRIPTION The omnicellinfo command displays information about data objects, clients, database, backup speci
omnicellinfo (1) option, the report only shows those objects which are not scheduled for backup. By default, all objects (scheduled and unscheduled) are listed. -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.
omnicellinfo (1) EXAMPLES The following example illustrates how the omnicellinfo command works. 1. To list detailed information about the selected objects: omnicellinfo -object schedule SEE ALSO omnicc(1), omnicheck(1M), omnisv(1M), omnidlc(1M), omniinstlic(1M) Hewlett-Packard Company -23- AppRM A.06.
omniclus (1) omniclus (1) NAME omniclus – helps to manage load balancing in the cluster environment in case of an application (Application Recovery Manager or other) failover SYNOPSIS omniclus -version | -help omniclus -clus cluster_name -session {* | backup_specification} -abortsess [-abortid {== | !=} application_id] omniclus -clus cluster_name -inhibit {* | 0 | minutes} omniclus -clus cluster_name -session {* | backup_specification} The -noclus option can be specified directly after -clus to prevent lo
omniclus (1) -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. Abort all running sessions omniclus -clus cluster.domain.
omniclus (1) The following command will inhibit backup sessions forever: omniclus -clus cluster.domain.com -inhibit * The following command will re-activate backup sessions immediately: omniclus -clus cluster.domain.com -inhibit 0 SEE ALSO omnirsh(1M) AppRM A.06.
omnidb (1) omnidb (1) NAME omnidb – queries the Application Recovery Manager internal database (IDB) SYNOPSIS omnidb -help | -version omnidb Object [-session SessionID] omnidb -rpt [SessionID] [-detail] omnidb -rpt [-wo start duration] omnidb -session SessionID [{-report Report | -detail | -strip | -purge | -remove_msgs}] omnidb -object | -vss omnidb Object {[-since Date] [-until Date] | [-last NumberOfDays] | [-latest] }[-noexpand] [-detail] omnidb Object {[-since Date] [-until Date] | -last NumberOfDays
omnidb (1) This command can be used to: • list sessions and their summary reports • 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.
omnidb (1) -report Report Lists all messages (of specified report level and higher) which were generated by the specified session. Messages are classified (in ascending order) as: warning, minor, major and critical. For example, if major is selected, only major and critical messages are reported. By default, all messages are reported. -object Displays information on all data objects. The report shows the client name, mountpoint, label, and object type.
omnidb (1) 2. To see critical errors for the session with the sessionID "2006/07/14-17": omnidb -session 2006/07/14-17 -report critical SEE ALSO omnidbcheck(1M), omnidbinit(1M), omnidbutil(1M), omnidbsmis(1) AppRM A.06.
omnidbsmis (1) omnidbsmis (1) NAME omnidbsmis – executes administrative tasks required for managing HP StorageWorks Enterprise Virtual Array.
omnidbsmis (1) The -ssl option specifies that HP StorageWorks EVA SMI-S Provider is SSL-enabled. In this case, the SMI-S Agent uses an SSL-based client connection to communicate with the SMI-S provider. The -port port option specifies the port number on which CV EVA listens to requests. The default port number for CV EVA is 5988 (the -ssl option is not selected) or 5989 (the -ssl option is selected). If your CV EVA is configured to use a different port number, set it using this option.
omnidbsmis (1) If the -user username option is specified, the command will only remove the entries for the specified user. Use this option if you have more than one user configured on the same system, and you want to delete only one user from the configuration. -ompasswd -list hostname Lists all systems that have CV EVA installed, together with the port numbers, on which CV EVAs listen to requests.
omnidbsmis (1) 4. To perform a health check of you environment on the local host, run the following command: omnidbsmis -ompasswd -check SEE ALSO omnidb(1M), omnidbinit(1M), omnidbutil(1M), omnidbcheck(1M) AppRM A.06.
omnidbvss (1) omnidbvss (1) NAME omnidbvss – queries VSS database; manages, browses, and lists the items of the VSS database. SYNOPSIS omnidbvss -init omnidbvss -list session [-barlist barlist] omnidbvss -list disk omnidbvss -remove session SessionID [-reference] omnidbvss -purge -barlist BackupSpecName omnidbvss -get session sessionID [-export_metadata Folder] omnidbvss -get disk StorageID DESCRIPTION The omnidbvss command is used to query the VSS database.
omnidbvss (1) -list disk Queries the VSS database and lists storage IDs. -remove session SessionID [-reference] 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 (1) 3. To list detailed information from the replica table of the VSS database on storage ID “STORAGE#Volume#1&30a96598&0&SignatureB6893593Offset7E00Length3F BB8600#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}”, run the following command: omnidbvss -get "STORAGE#Volume#1&30a96598&0&SignatureB6893593Offset7E00Length3FBB8 600#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}" SEE ALSO omnidb(1M), omnidbutil(1M), omnidbcheck(1M) Hewlett-Packard Company -37- AppRM A.06.
omnir (1) omnir (1) NAME omnir – restores files and databases backed up using Application Recovery Manager SYNOPSIS omnir -version | -help VSS RESTORE omnir -vss -barhost ClientName -session SessionID1 -tree TreeName1 [-tree TreeName2] ... [-session SessionID2 -tree TreeName3 [-tree TreeName4] ... ] ...
omnir (1) EXCHANGE_SPECIFIC_OPTIONS [-exch_check [-exch_throttle value] ] Exchange 2007 specific recovery options [-appsrv HostName] [-tree TreeName [-target_tree TargetTreeName | -exch_RSG RSGTreeName] -target_dir Directory ] ... SessionOptions -report {warning | minor | major | critical} GENERAL_OPTIONS [-pre_exec PathName] [-post_exec PathName] [-variable var_name var_value] [-no_monitor] DESCRIPTION The omnir command restores objects backed up using Application Recovery Manager.
omnir (1) OPTIONS -version Displays the version of the omnir command -help Displays the usage synopsis of the omnir command -vss Selects the VSS object for restore -session SessionID Specifies the session to be used for restore. -tree TreeName Specifies the component or tree to restore. Note that trees must be specified without volumes (drives). For example: -tree / Filesystem/E. -barhost ClientName Specifies the system where the VSS agent is run.
omnir (1) replica is deleted from the database (VSSDB). Does not use a ZDB array specific options or agents. This option must be used after the backup created with the XP provider in the VSS compliant mode. Exchange_Specific_Options -exch_throttle value Throttles down the consistency check to lessen impact on backup/restore performance. Set the number of input/output operations, after which the check is stopped for one second.
omnir (1) -exch_RSG RSGTreeName Creates a new Recovery Storage Group (RSG) and links it to RGSTreeName. This option can be used only once for each -tree option and cannot be specified together with -target_tree. Only one storage group per session can be restored with this option due to an Exchange limitation. RSGTreeName and its TreeName pair must always be fully expanded subcomponents, representing an Exchange store or logs. See also the Exchange 2007 examples.
omnir (1) -variable var_name var_value This option lets you specify a variable name and its value for proper operation. Setting user definable variables (a variable name and its value) enables flexible operation on some platforms and integrations with Application Recovery Manager. The list of variables and their values that are configurable with Application Recovery Manager is dynamic and comes with Application Recovery Manager patches.
omnir (1) EXAMPLES The following examples illustrate how the omnir command works. 1. To specify the -tree option, use the slash (“/“) delimiter.
omnir (1) -target_tree "/Microsoft Exchange Writer(Exchange Information Store)/Microsoft Information Store/Original Storage Group/Logs" -target_dir "c:\mnt" 6. Restore to a non-Exchange location: To restore the Exchange 2007 Writer store “StoreOne” from the storage group “First Storage Group” from the backup session “2007/04/08-9“ on the system “exch2007.company.com” , to the system “server2”, and with the replicas mounted to “c:\mnt”, execute the following command: omnir -vss -barhost exch2007.company.
omnistat (1) omnistat (1) NAME omnistat – displays the status of Application Recovery Manager sessions 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.
omnistat (1) -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. -until Date Lists all sessions until the specified Date. -last n Lists all sessions within the last n days. EXAMPLES The following examples illustrate how some options of the omnistat command work. 1.
Section 1M: Administrative Commands AppRM A.06.
dbtool.pl (1M) dbtool.pl (1M) NAME dbtool.pl – The dbtool command backs up and restores the Application Recovery Manager IDB and configuration. SYNOPSIS perl.exe dbtool.pl -version | -help perl.exe 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.exe dbtool.pl -backup perl.exe dbtool.pl -restore [FromFile] perl.exe dbtool.pl -getconfig perl.exe dbtool.
dbtool.pl (1M) -config Root= 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 \tmp. The backups are named apprm_idb_YYYYMMDD_HHMMSS.zip, where YYYYMMDD_HHMMSS represents the time at which the backup session was started. CountLimit sets the maximum number of backups that are stored.
dbtool.pl (1M) 3. To restore the backup “apprm_idb_20060723_221500.zip” created on the 23rd July 2006 at 22:15:00, run: perl.exe dbtool.pl -restore e:\AppRM_IDB\apprm_idb_20060723_221500.zip SEE ALSO omnidb(1), omnidbutil(1M), omnidbcheck(1M) Hewlett-Packard Company -51- AppRM A.06.
omnicheck (1M) omnicheck (1M) NAME omnicheck – Performs DNS connections check within an Application Recovery Manager cell and lists Application Recovery Manager patches installed on Application Recovery Manager clients.
omnicheck (1M) LISTING PATCHES INSTALLED ON Application Recovery Manager CLIENTS The omnicheck command can be used to list Application Recovery Manager patches installed on a particular client. The omnicheck option used to list Application Recovery Manager patches installed on a particular client is -patches. OPTIONS -version Displays the version of the omnicheck command -help Displays the usage synopsis of the omnicheck command.
omnicheck (1M) 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 (1M) 3. To list the patches installed on client with the hostname backup.system.com, execute the following command: omnicheck -patches -host backup.system.com SEE ALSO omnicc(1), omnicellinfo(1), omnisv(1M), omnidlc(1M), omniinstlic(1M) Hewlett-Packard Company -55- AppRM A.06.
omnidbcheck (1M) omnidbcheck (1M) NAME omnidbcheck – checks the consistency of the Application Recovery Manager internal database (IDB) SYNOPSIS omnidbcheck -version | -help omnidbcheck [-quick | -extended] omnidbcheck -core [-summary] omnidbcheck -filenames [-summary] omnidbcheck -bf [-summary] omnidbcheck -sibf [-detail] [-summary] omnidbcheck -smbf [-detail | dumpmessages] [-summary] omnidbcheck -dc [LimitScope] [-detail] [-summary] Limitscope -hosts host1 [host2...
omnidbcheck (1M) Application Recovery Manager creates a log file for each part of the check in the \log\server directory on: Check_bf.txt Check_core.txt Check_filenames.txt Check_dc.txt Check_smbf.txt Check_sibf.txt There is a timestamp at the beginning of each log file stating when the check was performed. OPTIONS -version Displays the version of the omnidbcheck command. -help Displays the usage synopsis for the omnidbcheck command.
omnidbcheck (1M) Note that if you have removed a SMBF in any way (e.g. using Application Recovery Manager GUI or CLI or deleted the file manually), then this option will report the removed session message as missing. This does not mean that IDB is corrupted - it only indicates that a session has been removed. -dc Checks the consistency between the Core part and DC part of the IDB. This check takes approximately 10 minutes for each GB of the DC part of the IDB.
omnidbcheck (1M) SEE ALSO dbtool.pl(1M),omnidb(1), omnidbinit(1M), omnidbutil(1M), omnidbvss(1) Hewlett-Packard Company -59- AppRM A.06.
omnidbinit (1M) omnidbinit (1M) NAME omnidbinit – initializes the Application Recovery Manager internal database (IDB) SYNOPSIS omnidbinit -version | -help omnidbinit [-force] DESCRIPTION The omnidbinit command initializes the Application Recovery Manager internal database (IDB). All information about sessions and objects is lost after the initialization. The IDB directory structure has to exist in order to initialize the IDB successfully.
omnidbutil (1M) omnidbutil (1M) NAME omnidbutil – handles various Application Recovery Manager internal database (IDB) maintenance tasks SYNOPSIS omnidbutil -help omnidbutil -version omnidbutil -list_dcdirs omnidbutil -add_dcdir Pathname [-maxsize Size_MB] [-maxfiles NumberOfFiles] [-spacelow Size_MB] [-seq Number] omnidbutil -modify_dcdir Pathname [-maxsize Size_MB] [-maxfiles NumberOfFiles] [-spacelow Size_MB] [-seq Number] omnidbutil -remove_dcdir Pathname omnidbutil -remap_dcdir omnidbutil -fixmpos om
omnidbutil (1M) omnidbutil -show_cell_name omnidbutil -set_session_counter new_session_ID omnidbutil -upgrade_info omnidbutil -show_db_files omnidbutil -free_cell_resources DESCRIPTION The omnidbutil command is used for Application Recovery Manager internal database (IDB) maintenance tasks.
omnidbutil (1M) The omnidbutil options used for this group of tasks are: -extendfnames, -extendtblspace, -extendinfo, -purge, -purge_stop, -info, -clear, -change_cell_name, -show_cell_name, -set_session_counter, -upgrade_info, -show_db_files. Certain options require exclusive access to the IDB. Prior to using such options, ensure that no backup, restore or media management sessions are in progress and that no graphical user interfaces are running in the cell.
omnidbutil (1M) DCDirAllocation parameter in the Application Recovery Manager global options file is set to 0. The Application Recovery Manager global options file resides in \config\server\options on the Cell Manager. If the -seq option is not specified, 0 will be used. -modify_dcdir Pathname [-maxsize Size_MB] [-maxfiles NumberOfFiles] [-spacelow Size_MB] [-seq Number] Modifies a DCBF directory under the specified path.
omnidbutil (1M) -fixmpos -readdb Removes invalid references to DCBF. This option should be used in the case of IDB recovery (after tablespaces dbreplay or -import_logs ) or after a DCBF has been manually removed. This option requires exclusive access to the database. [-cdb Directory] [-no_detail] [-check_overs] Reads the files in the specified directories and uses this information to rebuild the IDB.
omnidbutil (1M) Use the -no_detail option to skip the writing of references to DCBF, SMBF and SIBF to files. If these references are skipped, the copy of DCBF, SMBF and SIBF directories is not needed. -purge {-sessions [NumberOfDays] | -days [NumberOfDays] | -messages [NumberOfDays] | -dcbf | -daily} This option allows you to remove obsolete file names, backup, restore, and media management sessions, session messages, and obsolete DCBF files from the IDB.
omnidbutil (1M) -purge_stop Use this option to stop a running file name purge session. This command only sends a stop request to the Purge Session Manager. The response may not be immediate. -extendfnames Pathname -maxsize Size_MB Creates additional extent (tablespace). The directory specified by this option must exist and be capable of holding a tablespace of the size specified by -maxsize parameter prior to executing this option. The tablespace cannot be larger than 2047 MB.
omnidbutil (1M) -show_cell_name Queries the CDB for its owner. If there is no information available, use the -change_cell_name option to update the information. -set_session_counter new_session_ID Sets a new value for the counter that is used for generating the sessionID. This option is used after the restore and recovery of the IDB to enable the import of tapes that were created on the same day. Suggested value is 100. -upgrade_info Displays the information about the upgrade of the IDB.
omnidlc (1M) omnidlc (1M) NAME omnidlc – gathers or deletes Application Recovery Manager debug, log and getinfo files from the Application Recovery Manager cell 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] ...
omnidlc (1M) dlc.pck file. The file includes a generated directory structure that includes the hostnames, paths and the (compressed) collected files of the clients involved. This directory structure is described further on in this man page. Optionally, files can be sent over the network to the Cell Manager uncompressed (if the -no_compress option is specified).
omnidlc (1M) The collected debug files can also be deleted (if the -delete_dbg option is specified), or the disk space required on the Cell Manager for the collected files can be displayed (if the -space option is specified). In these two cases, the selected files are neither transferred from the clients to the Cell Manager nor packed on the Cell Manager. When collecting or deleting files or when displaying the required disk space, additional criteria can be defined to limit the files selection.
omnidlc (1M) -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 \tmp\dlc directory on the Cell Manager. -space Displays the disk space required on the Cell Manager for the collected files. -delete_dbg Deletes the selected files on clients. -no_getinfo Excludes the getinfo file from the selection.
omnidlc (1M) Use this option when the collected (compressed or uncompressed) data was packed on the Cell Manager either using the -pack option or the -localpack option. -uncompress filename Uncompresses the unpacked compressed single file in the current directory. Use this option after the packed data is unpacked using the -unpack option. NOTES The command can only be used on Cell Managers. It cannot be used to collect the Application Recovery Manager installation execution traces.
omnidlc (1M) 4. To delete all debug log files for the session with the ID “2003/08/27-9”, execute the following command: omnidlc -session 2003/08/27-9 -delete_dbg 5. To display disk space needed on the Cell Manager for the uncompressed debug files with the debugID “2351” from the client “client.company.com”, execute the following command: omnidlc -did 2351 -hosts client.company.com -space -no_getinfo -no_logs -no_compress 6.
omnihealthcheck (1M) omnihealthcheck (1M) NAME omnihealthcheck – checks if Application Recovery Manager internal database (IDB) and services are operational. 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.
omnihealthcheck (1M) 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. The Global options file (global) is located on the Cell Manager in the \config\server\options directory.
omniinstlic (1M) omniinstlic (1M) NAME omniinstlic – starts the HP OpenView AutoPass utility or synchronizes the Application Recovery Manager licenses between Application Recovery Manager and HP OpenView AutoPass 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.
omniinstlic (1M) EXAMPLE To start the HP OpenView AutoPass utility, execute the following command: omniinstlic SEE ALSO omnicc(1), omnicellinfo(1), omnisv(1M), omnicheck(1M), omnidlc(1M) AppRM A.06.
omnirsh (1M) omnirsh (1M) NAME 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 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
omnisv (1M) omnisv (1M) NAME omnisv – starts, stops or queries the status of Application Recovery Manager services. 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 service, crs service and mmd service on the Cell Manager.
omnisv (1M) services are up and running, whereas the exit code 1 means that at least one of the relevant Application Recovery Manager services is not running. NOTES On Windows systems, only the users in the Application Recovery Manager admin group can execute this command. This command can only be used locally on the Cell Manager. It is not possible to start or stop services on a cluster using this command.
omnitrig (1M) omnitrig (1M) NAME omnitrig – triggers Application Recovery Manager scheduled backups SYNOPSIS omnitrig -version | -help omnitrig [-start] [-log] omnitrig -stop omnitrig -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 to run at 15 minute intervals.
omnitrig (1M) NOTES The command can only be used locally on the Cell Manager system. SEE ALSO omnihealthcheck(1M) Hewlett-Packard Company -83- AppRM A.06.
winomnimigrate.pl (1M) winomnimigrate.pl (1M) NAME winomnimigrate.pl – helps you migrate your existing Cell Manager from a 32-bit Windows system to a 64-bit Windows system. SYNOPSIS perl.exe winomnimigrate.pl -help perl.exe winomnimigrate.pl -prepare_clients New_CM_Name perl.exe winomnimigrate.pl -configure perl.exe winomnimigrate.pl [-configure_clients] [-configure_idb] [-configure_cm] NOTE: It is assumed that the perl.
winomnimigrate.pl (1M) -configure Combines -configure_clients, -configure_idb, and -configure_cm options. This is the recommended way to run the winomnimigrate.pl command. The option should be used only on the new Cell Manager. -configure_clients Migrates the clients from the old Cell Manager to the new Cell Manager. The old Cell Manager will keep the clients in the configuration files although it will not be their Cell Manager anymore.
winomnimigrate.pl (1M) EXAMPLES 1. Run the following command on the old Cell Manager to add the new Cell Manager with the client name "computer.company.com" to the list of trusted hosts on secured clients: perl.exe winomnimigrate.pl -prepare_clients computer.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: perl.exe winomnimigrate.
Section 5: Miscellaneous Hewlett-Packard Company -87- AppRM A.06.
manager (5) manager (5) NAME manager – Describes usage for the Application Recovery Manager command manager SYNOPSIS manager -help manager [ContextOptions] [-server hostname] ContextOptions -backup -clients -db -monitor -users -instrec DESCRIPTION This command is used to start all or any combination of Application Recovery Manager GUI contexts.
manager (5) -clients Starts the Application Recovery Manager GUI with the Clients context activated. -db Starts the Application Recovery Manager GUI with the Internal Database context activated. -instrec Starts the Application Recovery Manager GUI with the Instant Recovery context activated. -monitor Starts the Application Recovery Manager GUI with the Monitor context activated. -users Starts the Application Recovery Manager GUI with the Users context activated. EXAMPLES 1.
