Page 1 HP Data Protector A.06.1 1 Command line interface reference Part number: N/A First edition: September 2009...
Page 2 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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services.
Page 3: Table Of Contents
Integrations ..................16 Document conventions and symbols ..............18 Reference page conventions ................19 General information ..................20 HP technical support ..................20 Subscription service ................... 20 HP websites ...................... 21 Documentation feedback ..................21 I Section 9: Introduction ............23 omniintro ......................
Page 4: Table Of Contents
omnidbva ....................... 121 omnidbvss ...................... 125 omnidbxp ...................... 131 omnidownload ....................137 omniiso ......................139 omnimcopy ....................143 omniminit ....................... 147 omnimlist ......................151 omnimm ......................155 omnimnt ......................167 omnimver ....................... 169 omniobjconsolidate ..................171 omniobjcopy ....................179 omniobjverify ....................189 omnir ......................
Page 5: Table Of Contents
omnimigrate.pl ....................361 omniofflr ......................365 omniresolve ....................373 omnirsh ......................375 omnisetup.sh ....................377 omnisrdupdate ....................383 omnistoreapputil ....................387 omnisv ......................389 omnitrig ......................391 sanconf ......................393 uma ......................403 upgrade_cm_from_evaa ................... 411 util_cmd ......................413 util_oracle8.pl ....................421 util_vmware.exe ....................
Page 6 Tables Edition history ................... 7 Document conventions ..............18...
Page 7: 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...
Page 8 Publication history...
Page 9: About This Guide
This reference guide does not describe concepts, the GUI, or provides details about the integrations. The HP Data Protector command line interface reference contains the reference pages for Data Protector A.06.1 1 commands. Reference pages are available on UNIX systems as man pages. For more information about man pages, refer to the man page for man using the command man man.
Page 10: Intended Audience
Documentation & Help component on Windows or the OB2-DOCS component on UNIX. Once installed, the guides reside in the Data_Protector_home\docs directory on Windows and in the /opt/omni/doc/C directory on UNIX. You can find these documents from the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals In the Storage section, click Storage Software and then select your product.
Page 11 This guide describes the integrations of Data Protector with Oracle, SAP R/3, and SAP DB/MaxDB. • HP Data Protector integration guide for IBM applications: Informix, DB2, and Lotus Notes/Domino This guide describes the integrations of Data Protector with the following IBM applications: Informix Server, IBM DB2, and Lotus Notes/Domino Server.
Page 12 HP Data Protector integration guide for HP Reporter This manual describes how to install, configure, and use the integration of Data Protector with HP Reporter. It is intended for backup administrators. It discusses how to use the application for Data Protector service management.
Page 13: Online Help
• HP Data Protector product announcements, software notes, and references This guide gives a description of new features of HP Data Protector A.06.1 1. It also provides information on installation requirements, required patches, and limitations, as well as known issues and workarounds.
Page 14: Documentation Map
Documentation map Abbreviations Abbreviations in the documentation map that follows are explained below. The guide titles are all preceded by the words “HP Data Protector”. Abbreviation Guide Command line interface reference Concepts Concepts guide Disaster recovery guide Getting started guide...
Page 15 Abbreviation Guide Install Installation and licensing guide MO GS Media Operations getting started guide MO RN Media Operations product announcements, software notes, and references MO UG Media Operations user guide MPE/iX MPE/iX system user guide Product announcements, software notes, and references Trouble Troubleshooting guide ZDB Admin...
Page 16: Integrations
Integrations Look in these guides for details of the following integrations: Integration Guide HP Operations Manager for UNIX/for Windows IG-OMU, IG-OMW HP Performance Manager IG-PM/PA HP Performance Agent IG-PM/PA About this guide...
Page 17 Integration Guide HP Reporter IG-R HP Service Information Portal IG-SIP HP StorageWorks Disk Array XP all ZDB HP StorageWorks Enterprise Virtual Array (EVA) all ZDB HP StorageWorks Virtual Array (VA) all ZDB IBM DB2 UDB IG-IBM Informix IG-IBM Lotus Notes/Domino...
Page 18: Document Conventions And Symbols
Document conventions and symbols Table 2 Document conventions Convention Element Blue text: Table 2 on page 18 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.com Website addresses Italic text Text emphasis • File and directory names • System output Monospace text •...
Page 19: Reference Page Conventions
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.
Page 20: General Information
Operating system type and revision level • Detailed questions 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.
Page 21: Hp Websites
• http://www.hp.com • http://www.hp.com/go/software • http://www.hp.com/support/manuals • http://h20230.www2.hp.com/selfsolve/manuals • http://www.hp.com/support/downloads Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to DP.DocFeedback@hp.com. All submissions become the property of HP. Command line interface reference...
Page 22 About this guide...
Page 23 Section 9: Introduction Command line interface reference...
Page 24 Section 9: Introduction...
Page 25: Omniintro
HP Data Protector command utilities omniintro DESCRIPTION HP Data Protector is an enterprise backup solution that provides reliable data protection and high accessibility for business data. Data Protector provides extensive media management, unattended backups, post-backup data management, integrations with various databases and supports various backup and other backup-dedicated devices.
Page 26 Support component installed (Windows systems) and on the Data Protector Cell Manager (UNIX systems). omnicreatedl Creates a Data Protectorbackup specification file (datalist); or an HP StorageWorks Disk Array XP, HP StorageWorks Virtual Array, or HP StorageWorks Enterprise Virtual Array Microsoft Exchange Server ZDB backup specification file (datalist).
Page 27 Queries the ZDB database (XPDB), manipulates the XP LDEV exclude file, and configures the HP StorageWorks Disk Array XP command devices usage. This command is available on systems with the Data Protector User Interface component installed. omnidownload Downloads information about a backup device and a library from the Data Protector internal database (IDB).
Page 28 This command is available on systems with the Data Protector User Interface component installed. omnimver Verifies data on a medium. This command is available on systems with the Data Protector User Interface component installed. omniobjconsolidate Consolidates Data Protector backup objects into synthetic full backups. This command is available on systems with the Data Protector User Interface component installed.
Page 29 Displays the status of active Data Protector backup and restore sessions. This command is available on systems with the Data Protector User Interface component installed. omniupload Uploads information about a backup device from an ASCII file to the Data Protector internal database (IDB). This command is available on systems with the Data Protector User Interface component installed.
Page 30 This command is available on systems with any Data Protector component installed. omniinstlic Starts the HP AutoPass utility or synchronizes the Data Protector licenses between Data Protector and HP AutoPass. This command is available on the Data Protector Cell Manager.
Page 31 Helps you migrate your existing Cell Manager from a PA-RISC architecture based HP-UX 1 1.x system to an HP-UX 1 1.23 system for the Intel Itanium 2 (IA-64) architecture. This command is available on the Data Protector Cell Manager.
Page 32 This command is available on systems with the Data Protector User Interface component installed. omnisv Starts, stops, or displays the status of Data Protector daemons (HP-UX, Solaris, or Linux systems) or services (Windows systems). This command is available on the Data Protector Cell Manager.
Page 33 NNMpost.ovpl A script with no arguments that resumes the eight processes paused by NNMpre.ovpl. This command is available on systems with the Data Protector HP Network Node Manager Integration component installed. NNMpre.ovpl Starts NNM embedded database backup. This command is available on systems with the Data Protector HP Network Node Manager Integration component installed.
Page 34 RETURN VALUES: Possible return values of commands are: Program failed, command syntax error. Program failed, invalid argument. Program failed, internal error. Program failed, reason unknown. Some commands 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.
Page 35 javadpguimom Starts the Data Protector Manager-of-Managers Java GUI with all Data Protector contexts activated (with the exception of the Internal Database and Devices & Media contexts), or, when additional context options are specified, starts only the specified Data Protector contexts. This command is available on systems with the Data Protector Java GUI Client component installed.
Page 36 users user configuration cell cell configuration schedules backup schedules barschedules database backup specification schedules sessions data about sessions options default options scripts for Service Guard support snmp OpenView/SNMP trap sending configuration /etc/opt/omni/client • Directory containing the client configuration directories and files /etc/opt/omni/server/dr •...
Page 37 Cell Manager and Data Protector Internal Database (IDB) administrative commands /var/opt/omni • Directory containing the following directories: /var/opt/omni/log and /var/opt/omni/server/log log files /var/opt/omni/tmp temporary files /var/opt/omni/server/sessions data about sessions /var/opt/omni/server/export/keys and /var/opt/omni/server/import/keys encryption keys /var/opt/omni/server/db40 • Directory containing the following Data Protector Internal Database (IDB) directories: /var/opt/omni/server/db40/datafiles the IDB tablespaces...
Page 38 /var/opt/omni/server/db40/xpdb the ZDB database (XPDB) /opt/omni/lib • Directory containing the following directories: /opt/omni/lib/nls message catalogs /opt/omni/lib/man Data Protector man pages /opt/omni/help/C • The Data Protector help subsystem /opt/omni/java • Directory containing the following directories: /opt/omni/java/server/bin Java GUI Server (UIProxy service) executables /opt/omni/java/client/bin Java GUI Client executables DIRECTORY STRUCTURE ON WINDOWS CELL...
Page 39 users the user configuration cell the cell configuration schedules backup schedules barschedules database backup specification schedules options default options sessions data about sessions snmp OpenView/SNMP trap sending configuration Data_Protector_program_data\Config\client • Directory containing the client configuration directories and files Data_Protector_program_data\Config\Server\export\keys and Data_Protector_program_data\Config\Server\import\keys •...
Page 40 • The Java GUI Client executables Data_Protector_home\help • The Data Protector help subsystem Data_Protector_home\docs • HP Data Protector command line interface reference Other Windows operating systems Data_Protector_home • Data Protector home directory Data_Protector_home\Config\Server • Directory containing the following configuration directories:...
Page 41 the cell configuration schedules backup schedules barschedules database backup specification schedules options default options sessions data about sessions snmp OpenView/SNMP trap sending configuration Data_Protector_home\Config\client • Directory containing the client configuration directories and files Data_Protector_home\Config\Server\dr • Directory containing the following disaster recovery directories: P1S files for Enhanced Automated Disaster Recovery SRD files ASR archive files...
Page 42 The ZDB database (XPDB) Data_Protector_home\db40\vssdb • The VSS database (VSSDB) Data_Protector_home\java\server\bin • The Java GUI Server (UIProxy service) executables Data_Protector_home\java\client\bin • The Java GUI Client executables Data_Protector_home\help • The Data Protector help subsystem Data_Protector_home\docs • HP Data Protector command line interface reference...
Page 43: See Also
SEE ALSO ob2install(1M), omniabort(1), omniamo(1), omnib(1), omnicc(1), omnicellinfo(1), omnicheck(1M), omniclus(1), omnicreatedl(1), omnidb(1), omnidbcheck(1M), omnidbinit(1M), omnidbsmis(1), omnidbva(1), omnidbvss(1), omnidbxp(1), omnidlc(1M), omnidownload(1), omnidr(1M), omnigui(5), omnihealthcheck(1M), omniinetpasswd(1M), omniinstlic(1M), omniiso(1), omnikeymigrate(1M), omnikeytool(1M), omnimcopy(1), omniminit(1), omnimigrate.pl(1M), omnimlist(1), omnimm(1), omnimnt(1), omnimver(1), omniobjcopy(1), omniobjconsolidate(1), omniofflr(1M), omnidbupgrade(1M), omnidbrestore(1M), omnidbutil(1M), omnir(1), omniresolve(1M), omnirpt(1), omnirsh(1M), omnisetup.sh(1M), omnisrdupdate(1M), omnistat(1), omnisv(1M), omnitrig(1M), omniupload(1), omniusers(1), sanconf(1M), syb_tool(1), uma(1M), upgrade_cm_from_evaa(1M), util_cmd(1M),...
Page 45 Section 1: User Commands Command line interface reference...
Page 46 Section 1: User Commands...
Page 47: Omniabort
omniabort aborts an active session (this command is available on systems with the Data Protector User Interface component installed) 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.
Page 48 SEE ALSO omnistat(1)
Page 49: Omniamo
omniamo starts an automated media operation session (this command is available on the Data Protector Cell Manager) omniamo SYNOPSIS omniamo -version | -help omniamo -amc ConfigurationName {-post_backup | -scheduled} DESCRIPTION This command starts an automated media operation session for the specified post-backup or scheduled configuration.
Page 50 To start the post-backup automated media copy operation with the configuration name "MyFiles" and session ID 2008/09/13-0001 on Windows, run: set SESSIONID=2008/09/13-0001 omniamo -amc MyFiles -post_backup To start the post-backup automated media copy operation with the configuration name "MyDocs" and session ID 2008/09/13-0002 on UNIX, if you are using an sh-like shell, run: SESSIONID=2008/09/13-0002 export SESSIONID...
Page 51: Omnib
omnib backs up filesystems, disk images, the Data Protector internal database (IDB), Microsoft Exchange Server single mailboxes and Public Folders, Microsoft Exchange Server, Microsoft SQL Server, Microsoft SharePoint Portal Server (SPS), SAP R/3, SAP DB/MaxDB, Oracle, Informix Server, VMware Virtual Infrastructure (VMware), Sybase, Lotus, IBM DB2 UDB, NetWare objects, and NDMP objects.
Page 52 omnib -msese_list ListName [-barmode MSExchangeMode] [LIST_OPTIONS] omnib -mbx_list ListName [-barmode MSMailboxMode] [LIST_OPTIONS] omnib -lotus_list ListName [-barmode LotusMode] [LIST_OPTIONS] omnib -msvssw_list ListName [-barmode VSSMode] [LIST_OPTIONS] omnib -db2_list ListName [-barmode DB2Mode] [LIST_OPTIONS] omnib -restart SessionID omnib -resume SessionID [-no_monitor] MIRROR_OPTIONS -mirror BackupDevice [ -pool MediaPool -prealloc MediaList ] GENERAL_OPTIONS -preview -pool MediaPool...
Page 53 -no_share[_info] -[no_]nthlinks -[no_]archatt -vss [fallback] -async BACKUP_SPECIFICATION_OPTIONS -select SelectList -mode {Full | Incremental[1-9]} -protect {none | weeks n | days n | until Date | permanent} -preview -disk_only -load {low | medium | high} -crc -no_monitor LIST_OPTIONS -barcmnd Command -protect {none | weeks n | days n | until Date | permanent} -load {low | medium | high} -crc -no_monitor...
Page 54 SapMode= full | incremental SapdbMode= full | diff | trans Oracle8Mode= -full | -incr1 | ... | -incr4 VMwareMode= full | diff | incr SybaseMode= full | trans InformixMode= full | inf_incr1 | inf_incr2 MSSQLMode= full | diff | trans MSSPSMode= full | diff | trans MSExchangeMode= full | incr MSMailboxMode= -full | -incr | -incr1...
Page 55 Backup monitoring When the backup command is executed, it sends a request (specifying the backup objects) to the Session Manager. When the Session Manager (SM) accepts the request, it assigns a unique SessionID to the session. You can use this SessionID to monitor the progress of the session using the xomnimonitor or omnistat commands.
Page 56 -resume SessionID This option is applicable only for the Data Protector Oracle Server integration. It starts a new backup session using the same backup specification as used in the backup session SessionID. The main difference, compared to a standard backup session, is that, before the session is started, Data Protector modifies the RMAN script by adding the clause NOT BACKED UP SINCE Original_session_start_time for each backup command.
Page 57 -msese_list ListName Specifies the name of the Microsoft Exchange Server backup specification file for the backup. The Microsoft Exchange Server backup specification contains the Microsoft Exchange Server objects to be backed up. -mbx_list ListName Specifies the name of the Microsoft Exchange Server single mailbox backup specification file for the backup.
Page 58 is issued. Note: If the Media Allocation Policy is "strict", you must specify a Prealloc list. GENERAL_OPTIONS -preview Checks the backup objects, backup devices and options you selected, without performing the backup. The check includes: backup objects, status of the backup device, available media, and the approximate amount of data which will be backed up.
Page 59 This option is not supported on Novell NetWare. However, it is possible to uncompress files that were compressed with this option using older versions of Data Protector. -encode [aes256] Instructs the General Disk Agent to write data to media in encoded format. If the aes256 option is specified, data is written to media in encrypted format, using the Advanced Encryption Standard (AES) algorithm.
Page 60 without volumes (drives). For example: -tree /usr/temp (UNIX system) or -tree \temp (Windows system). This option is not supported with Data Protector NDMP server integration. -only MatchPattern Specifies that only files that match the MatchPattern will be backed up. This option is not supported with Data Protector NDMP server integration.
Page 61 Specifies the mode for the backup session. Full mode backs up all specified files. Incremental[1-9] backs up only a subset of the specified files, based on whether or not the files were modified since the last Full or lower-level Incremental backup. Default is the Full mode. The level of incremental backup is based on the level number which is specified.
Page 62 -no_share[_info] If this option is specified, share information for directories on Windows systems is not backed up. By default, if a directory was shared on the network when a backup was run, the share information for directory is backed up, unless the -no_share[_info] option is specified.
Page 63 BACKUP_SPECIFICATION_OPTIONS -select SelectList Specifies which objects (of those in the backup specification) to back up. The SelectList is the list of objects to be backed up. -mode{Full | Incremental[1-9]} Specifies the Mode for the backup session. Full mode backs up all specified files.
Page 64 For SAP R/3 objects, the possible modes are full and incremental. The default value for this option is full. -barmode SapdbMode For SAP DB/MaxDB objects, the possible modes are full, diff and trans. The full option triggers a full backup of the SAP DB/MaxDB instance, the diff option triggers a differential backup, and the trans option triggers an archive logs backup.
Page 65 (for example full, copy, incr, diff with Microsoft Exchange Server 2003 writer), others may support only full. See the HP Data Protector integration guide for Microsoft applications: SQL Server, SharePoint Portal Server, Exchange Server, and Volume Shadow Copy Service.
Page 66 The option checks the backup objects, backup devices and options you selected, without doing the backup. The check includes: objects due for backup, status of the backup device, available media, and the approximate amount of data which will be backed up. -disk_only A ZDB related option.
Page 67 -log_dirs If this option is specified, only the directories are logged into the database. By default, the filename and backup history of each backed up file is written to the catalog database. -log_file All detailed information about backed up files and directories (filenames and file versions) is logged to the Data Protector internal database (IDB).
Page 68 RETURN VALUES See the man page omniintro for return values. Additional return values of the omnib command are: There was an error while backing up some files. All agents completed successfully. One or more agents failed, or there was a database error. None of the agents completed the operation;...
Page 69 "test", and write a CRC checksum at the end of every block on the medium, run: omnib -sapdb_list test -barmode diff -crc To perform an encrypted backup of a tree "/usr" of filesystem "alpha.hp.com" with the label "work", using the encode aes256 option, to the backup device "ENC1", run: omnib -filesystem alpha.hp.com:/work -device ENC1 -tree...
Page 71: Omnicc
omnicc handles the Data Protector licensing, reports the number of configured and available Data Protector licenses, installs the licenses, imports and exports Data Protector clients, and manages access to secured clients (this command is available on systems with any Data Protector component installed) omnicc SYNOPSIS omnicc -version | -help...
Page 72 OPTIONS -version Displays the version of the omnicc command. -help Displays the usage synopsis for the omnicc command. -check_licenses[-detail] Reports licensing related information from the cell. If the -detail option is not specified, the command returns information on whether the Data Protector licensing is covered or not. If the -detail option is specified, a detailed report is produced.
Page 73 -port Port Sets the TCP/IP port number for the VLS Device. -user UserName Sets the username that is used by Data Protector to establish the connection to the VLS Device. -passwd Password Sets the password for the above specified username. -import_ndmp ClientName Imports the specified NDMP server into the cell.
Page 74 -secure_client ClientName Specifies the client to be secured. -authorities ClientName [ClientName2...] Specifies systems from which the specified client accepts requests on the Data Protector 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 Data Protector port is allowed to do so.
Page 75 (Windows Server 2008), Data_Protector_home\Config\Server\mom\cell_info (other Windows systems), or /etc/opt/omni/server/mom/cell_info (UNIX systems) under client Cell Manager name. Use this command when switching to CMMDB mode. Omnicc with this option specified has to be executed on the client Cell Manager. -password_info Displays information about installed license passwords. EXAMPLE The following example illustrates how the omnicc command works.
Page 77: Omnicellinfo
omnicellinfo displays configuration information about the Data Protector cell (this command is available on systems with the Data Protector User Interface component installed) omnicellinfo SYNOPSIS omnicellinfo -version | -help omnicellinfo -servers omnicellinfo -group omnicellinfo -object [schedule | no_schedule] -group Group | -db omnicellinfo {-mm | -dev} [-detail] omnicellinfo {-dlinfo [-group Group]} | -cell [brief] {-schinfo [Backup_Specification | -days NumberDays | -group Group]} | {-dlobj...
Page 78 -object[schedule | no_schedule] Displays information about objects (filesystems, databases and disk images) in the cell. The report shows: Object (object type, client name, and mountpoint), Label, and Next Scheduled Backup Date. When you use the schedule option, the report only shows those objects which are scheduled for backup. When you use the -no_schedule option, the report only shows those objects which are not scheduled for backup.
Page 79 displays the next schedule time for each backup specification. If backup specification is specified the command lists all schedules in the next year for the specified backup specification. Option -days can be used to display schedules of all backup specifications for a specified number of days. -dlobj Shows information about all objects in backup specifications.
Page 81: Omniclus
omniclus manages load balancing in a cluster environment in the event of an application (Data Protector or other) failover (this command is available on systems with the Data Protector MS Cluster Support component installed (Windows systems) and on the Data Protector Cell Manager (UNIX systems)) omniclus SYNOPSIS...
Page 82 -help Displays the usage synopsis for the omniclus command. -clus cluster_name Specifies the cluster-aware Cell Manager. -session* | backup_specification 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.
Page 83 backup session manager checks whether the command addresses it and if this is the case it aborts. Abort sessions (all or specific) with application identifications omniclus -clus obvs.hermes.com -session * -abortsess -abortid != 10 Note: On UNIX systems replace the * wildcard with '*'. This way the user can define groups of sessions and abort only the ones that are actually related to the application that failed over.
Page 85: Omnicreatedl
(datalist); or an HP StorageWorks Disk Array XP, HP StorageWorks Virtual Array, or HP StorageWorks Enterprise Virtual Array Microsoft Exchange Server ZDB backup specification file (datalist) (this command is available on systems with the Data Protector User Interface...
Page 86 MICROSOFT EXCHANGE SERVER ZDB BACKUP SPECIFICATION The omnicreatedl command is also used to create an Exchange ZDB backup specification file for the following disk arrays: HP StorageWorks Disk Array XP HP StorageWorks Virtual Array HP StorageWorks Enterprise Virtual Array When creating an Exchange ZDB backup specification file, if the circular logging is...
Page 87 The backup specification file is created on the Cell Manager in the directory Data_Protector_program_data\Config\Server\datalists (Windows Server 2008), Data_Protector_home\Config\Server\datalists (other Windows systems), or /etc/opt/omni/server/datalists (HP-UX or Solaris systems). If this option is not specified, backup specification objects are written to stdout.
Page 88 Cell Manager in the directory Data_Protector_program_data\Config\Server\datalists (Windows Server 2008), Data_Protector_home\Config\Server\datalists (other Windows systems), or /etc/opt/omni/server/datalists (HP-UX or Solaris systems). The corresponding datalist(s) for Microsoft Exchange Server logs for every storage group specified that has the circular logging disabled is/are also created in the same directory with the file name Storage_Group_Name (LOGS) app_sys.
Page 89 Specifies a specific replica or a replica set to be used in the backup session to define a replica set from which the integration, according to the replica set rotation, selects one replica to be used in the backup session. If this option is not specified, the MU# 0 is set.
Page 90 VIRTUAL_ARRAY_OPTIONS -snapshot -va app_sys bck_sys Sets the application system app_sys and the backup system bck_sys and instructs the omnicreatedl command to create an HP StorageWorks Virtual Array snapshot datalist. -instant_recovery Specify this option if you want to perform either a ZDB to disk or a ZDB to disk+tape and leave the replica on a disk array (after the backup session) to use it in future for instant recovery.
Page 91 Specify this option if you want to apply the LUN security to the child LUNs (target volumes or snapshots) that the integration creates. If Secure Manager is activated on HP StorageWorks Virtual Array, you must specify this option and configure passwords correctly, otherwise the backup sessions will fail.
Page 92 Note that this option sets the number of replicas in the replica set for a backup specification. -snapshot_type{standard | vsnap | clone} This option instructs Data Protector to create one of the two types of HP StorageWorks Enterprise Virtual Array snapshots during the backup session. Setting standard creates snapshots with the pre-allocation of disk space.
Page 93 some vsnaps or snapclones of the source volumes already exist in a replica set, the following happens: with the loose option selected, Data Protector creates either vsnaps (if vsnaps already exist) or snapclones (if snapclones already exist) instead of standard snapshots.Note that Data Protector can use only one type of snapshots in the backup session.
Page 94 Microsoft Exchange Server. EXAMPLES The following examples show how the omnicreatedl command works: To create an HP StorageWorks Disk Array XP Microsoft Exchange Server ZDB-to-tape backup specification file named "Exchange_example" for a Microsoft Exchange Server running on client "computer1.company.com" with the backup system "computer2.company.com", to back up all storage groups relating to...
Page 95 To create an HP StorageWorks Disk Array XP Microsoft Exchange Server ZDB-to-tape backup specification file named "Exchange_example" for a Microsoft Exchange Server running on client "computer1.company.com" with the backup system "computer2.company.com", to back up entire First Storage Group and Test Storage Group (both have circular logging disabled), run: omnicreatedl -ex2000 -datalist Exchange_example -storage_group "First Storage Group"...
Page 96 "SRS (LOGS) computer1.company.com" for Site Replication Service log files backup if the circular logging is disabled. To create an HP StorageWorks Enterprise Virtual Array Microsoft Exchange Server ZDB-to-tape backup specification file (datalist) "Exchange_example", to back up Site Replication Service on "dev1" device, using the vsnap type of...
Page 97 After the backup session, the created replica is retained on a disk array and can be used for instant recovery. To create an HP StorageWorks Enterprise Virtual Array Microsoft Exchange Server ZDB-to-disk+tape backup specification file (datalist) "Exchange_example", to back up Site Replication Service on the backup device "dev1", using the...
Page 99: Omnidb
omnidb queries the Data Protector internal database (IDB) (this command is available on systems with the Data Protector User Interface component installed) omnidb SYNOPSIS omnidb -version | -help omnidb -session [-datalist Datalist] [-type {restore | backup | verification}] [-user User] {[[-since Date] [-until Date]] | [-last Number] | [-latest] | [ -wo start duration ]} [-detail] omnidb -filesearch [-n N]Client Directory FileName omnidb Object [-session SessionID] [-copyid CopyID] -listdir Dir-...
Page 100 omnidb Object -session SessionID [-copyid CopyID] -listcopies [{–detail | –encryptioninfo}] omnidb -auditing [-timeframe StartDate EndDate | -since Date [-until Date] | -last NumberOfDays] [–detail] Object [-noexpand] { -filesystem [Client:MountPoint Label]| -winfs [Client:MountPoint Label]| -netware [Client:MountPoint Label]| -omnidb [Client:MountPoint Label]| -rawdisk [Client Label]| -sap [Client:Set]| -sapdb [Client:Set]| -stream [Client:Set]|...
Page 101 • list sessions and their summary reports • list backed up objects and their details (for example: client name, mountpoint, label, object type, object status, backup type, etc.), message logs, and media location • search for all occurrences of a pathname pattern The omnidb command performs basic IDB queries.
Page 102 Lists the sessions that started within a specified timeframe. Start defines the start of the timeframe. Duration is the duration of the timeframe in seconds. -detail Displays detailed information about the selected query, such as backup type, protection, whether or not encrypted. –encryptioninfo Displays detailed encryption information for objects meeting the query criteria.
Page 103 -list_folders Microsoft Exchange Server single mailbox restore only: displays a list of all single mailbox folders (including their subfolders) backed up within a particular session. -mailbox MailboxName Microsoft Exchange Server single mailbox restore only: displays mailbox folders for a particular mailbox only. If the option is not specified, folders of all backed up mailboxes are listed.
Page 104 -winfs[Client:MountPoint Label] Displays information on all Windows filesystem objects (displays the Client:MountPoint Label string for every Windows filesystem object in the IDB). If a Client:MountPoint Label string is specified, the backup sessions containing the object specified by this string are listed. For each backup session, the report shows: the SessionID, start time, session duration, object status, size of object and the number of errors for the session.
Page 105 -stream[Client:Set] Displays information on stream objects (displays the Client:Set string for every stream object in the IDB). If a Client:Set string is specified, the backup sessions containing the object specified by this string are listed. For each backup session, the report shows: the SessionID, start time, session duration, object status, size of object and the number of errors for the session.
Page 106 -mbx[Client:Set] Displays information on Microsoft Exchange Server objects - single mailboxes (displays the Client:Set string for every Microsoft Exchange Server object - single mailboxes in the IDB). If a Client:Set string is specified, the backup sessions containing the object specified by this string are listed. For each backup session, the report shows: the SessionID, start time, session duration, object status, size of object and the number of errors for the session.
Page 107 -noexpand Do not expand client names. Use this option if object was backed up with different client name resolution as when using this option. -strip 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.
Page 108 -catalog Displays the detail catalog of a specified object - session combination. Use an object option (for example -filesystem) to specify the object and use the -session (and sessionID) to specify the session. -purge This option removes the session from the session list. All objects within the session become unprotected.
Page 109 omnidb -filesystem bob:/ -session 2008/07/14-6 -catalog To see details for the Microsoft Exchange Server backup specification "TEST" backup sessions, run: omnidb -session -datalist "MSExchange TEST" -details To list all Microsoft Exchange Server mailbox folders in the mailbox "User 2", backed up in the session "2008/03/16-5", run: omnidb -mbx -list_folders -session 2008/03/16-5 -mailbox "User 2"...
Page 110 1 10...
Page 111: Omnidbsmis
HP StorageWorks SMI-S EVA provider (this command is available on systems with the Data Protector User Interface component installed) omnidbsmis SYNOPSIS omnidbsmis -version | -help omnidbsmis -ompasswd -add hostname [-ssl] [-port port] [-namespace...
Page 112 SETTING THE DISK GROUP PAIRS CONFIGURATION FILE 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.
Page 113 The omnidbsmis options used for querying the SMISDB are: -list, -session, -ir, -datalist, -purge, -show. PURGING THE SMISDB The omnidbsmis command can be used to run the purge operation that checks the SMISDB for the virtual disks with the purge flag and, in case of finding such disks, attempts to delete these objects.
Page 114 Stores the login information for the system with the name hostname, on which SMI-S EVA provider is installed, in the SMISDB. 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.
Page 115 Note that HP StorageWorks SMI-S Agent must be installed on the specified host.
Page 116 Provides the information on the DR groups with the EVA identified by EVA_Name acting as home. The command returns the information on EVA_Name and the DR groups belonging to this EVA. -caconf -check DR_Group_Name Checks if a DR group, identified by DRGroup_name, is part of CA+BC configuration.
Page 117 -list -purge Lists all virtual disks (source or target volumes) that are marked for purging in the SMISDB. -purge Runs SMI-S Agent to perform the SMISDB purge operation that attempts to remove the virtual disks (source or target volumes) that could not be deleted although they should be.
Page 118 Used together with the -force option, the command forces removal of the target volumes marked for deletion even if they are presented to hosts. With the -host hostname option specified, you can choose another system to start the SMISDB synchronizing operation. Use this option if the systems, involved in a backup session, are no longer available, thus allowing redirection to another systems that have the SMI-S Agent installed.
Page 119 d) To upload the "dgrules.txt" file to the server, run: omnidbsmis -dgrules -put c:\tmp\dgrules.txt The command reads the contents of the file, checks its syntax, and copies the file to its location on the Cell Manager. To get the information on the disk group that is the pair of a disk group named original_disk_group configured on EVA storage system with WWN 50001FE15007CA90, run: omnidbsmis -dgrules -check EVA1 original_disk_group...
Page 120 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: omnidbsmis -session 2008/05/13-3 1 1. To delete a backup session with the session ID "2008/05/13-3" on the disk array and from the SMISDB, run: omnidbsmis -delete -session 2008/05/13-3 To run the SMISDB synchronizing operation and force removal of the target...
Page 121: Omnidbva
LUN security information is contained in the VA LUN exclude file. The VA LUN exclude file is used to specify LUNs, within HP StorageWorks Virtual Arrays connected to a Data Protector cell, that are to be excluded from Data Protector operations. The file contains a list of such LUNs grouped according to the world-wide-name of the Virtual Arrays concerned.
Page 122 Password information is held within a series of encrypted password files within VADB. OPTIONS -version Displays the version of the omnidbva command. -help Displays the usage synopsis for the omnidbva command. -exclude -put filename Sets the list of excluded LUNs by reading the contents of the filename, checking its syntax and if the syntax is correct, copying the filename to its position on the Cell Manager.
Page 123 -sampasswd SAM_server_ID user password Sets the HP Allocator access password. If a SAN network is being used, with HP Allocator installed, this password must be supplied using this command. Refer to the HP Allocator documentation for further information.
Page 124 This command reads the contents of the "c:\tmp\filename.txt", checks its syntax and if the syntax is correct copies the file to its position on the Cell Manager. To check whether the LUN number "123" in the virtual array with world_wide-name "Abcde12345" is specified in the VA LUN exclude file, run: omnidbva -exclude -check Abcde12345 123 To list all available ZDB-to-disk and ZDB-to-disk+tape sessions in the VADB, run: omnidbva -session...
Page 125: Omnidbvss
omnidbvss queries the VSS database (VSSDB); browses, lists, saves, removes, and manages the items of the VSSDB (this command is available on systems with the Data Protector User Interface component installed) omnidbvss SYNOPSIS omnidbvss -version | -help omnidbvss -init omnidbvss –list session [-barlist BackupSpecName] omnidbvss –list session_persistent [-barlist BackupSpecName] [-older_than YYYY/MM/DD] omnidbvss –get session {sessionID [SessionID ...] | -barlist...
Page 126 • save backup components and writer metadata documents • remove a specific or all available ZDB-to-disk and ZDB-to-disk+tape sessions, together with theirs replicas, from the VSSDB and from the disk array • remove a reference to a specific or to all available backup sessions from the VSSDB •...
Page 127 By specifying SessionID, the -barlist, or the –all option, information about the backup components and disks about the sessions that match the given criteria will be displayed. –detail displays detailed information (components, disks) about the specified session. -save_metadata saves the backup components document (Backup Components Document.xml) and writer metadata document (writer_name.xml) to the specified directory.
Page 128 — If the target volumes cannot be unmounted because of a lock by some other process. -remove session_persistent {SessionID [SessionID...]|–barlist BackupSpecName [–older_than YYYY/MM/DD]|–all [–older_than YYYY/MM/DD]} Removes the reference information about the specified sessions from the VSSDB (persistent metadata). It does not remove the session's replicas from the disk array.
Page 129 (for example, you have modified the existing source volumes or you have presented new source volumes) — you have added a new storage object (for example, a Microsoft Exchange Server storage group) For more information, see the HP Data Protector zero downtime backup integration guide. Command line interface reference...
Page 130 EXAMPLES To list the instant recovery–enabled sessions (ZDB to disk or ZDB to disk + tape) created using the backup specification "Backup1", run: omnidbvss –list session –barlist Backup1 To get information about the backup components of all backup sessions created before February 1st, 2009, and to save information about the backup components and writer metadata to the directory "C:\metadata", run: omnidbvss –get session_persistent -all older_than...
Page 131: Omnidbxp
2008), Data_Protector_home\db40\xpdb (other Windows systems), or /var/opt/omni/server/db40/xpdb (UNIX systems). The XPDB contains data about the split P-VOL - S-VOL pairs used with the Data Protector HP StorageWorks Disk Array XP integration in a set of XPDB records. The XPDB is written to whenever a pair is split using the Data Protector HP StorageWorks Disk Array XP integration.
Page 132 The HP StorageWorks Disk Array XP command devices are needed by any process that needs access to the HP StorageWorks Disk Array XP. The information about HP StorageWorks Disk Array XP command devices is kept in the XPDB for the purpose of eliminating duplicate instance usage and over-allocation.
Page 133 Specify a particular command device (identified by the HP StorageWorks Disk Array XP serial number and LDEV number) to be used by a particular system. Optionally, an instance number can be assigned too. If the instance number is not specified, Data Protector assigns the lowest not yet assigned instance number.
Page 134 -cm -add serial {CU:LDEV | LDEV} hostname [instance] Adds the command device identified by the serial number of the HP StorageWorks Disk Array XP (serial) and serial number of command device in the hexadecimal or decimal format (CU:LDEV or LDEV) to the XPDB, and assigns it the hostname of the system accessing it (hostname) and optionally the instance number (instance).
Page 135 If only the serial argument is specified, the command removes the information about command devices within a specific HP StorageWorks Disk Array XP identified by the serial number of this HP StorageWorks Disk Array XP (serial) from the XPDB. If the CU:LDEV | LDEV and optionally hostname arguments are specified as...
Page 136 To list all command devices in the XPDB, run: omnidbxp -cm -list To add the command device identified by the HP StorageWorks Disk Array XP serial number "00035371" and command device serial number "103" to the XPDB and assign it to be used on the "computer.company.com" system by the instance number "303", run:...
Page 137: Omnidownload
omnidownload downloads information about a backup device and a library from the Data Protector internal database (IDB) (this command is available on systems with the Data Protector User Interface component installed) omnidownload SYNOPSIS omnidownload -version | -help omnidownload -list_devices [-detail] omnidownload -dev_info omnidownload -device BackupDevice [-file FileName] omnidownload -list_libraries [-detail]...
Page 138 Displays information about the Data Protector backup devices. The report includes the following information for each device: device name, client, device type and pool. -dev_info Same as -list_devices option. Used only for compatibility with old Data Protector releases. -list_libraries Displays information about the Data Protector libraries. The report includes the following information for each device: library name, client and library type.
Page 139: Omniiso
omniiso primarily serves as a pre-exec script to prepare the ISO image file for One Button Disaster Recovery (OBDR); can also be used as a standalone command to automate your backup and disaster recovery process (this command is available on systems with the Data Protector Automatic Disaster Recovery component installed) omniiso SYNOPSIS...
Page 140 If the command is used as a pre-exec script in the OBDR Wizard in Data Protector GUI to prepare the disaster recovery ISO image, you do not have to specify any parameters, because they are obtained from the current environment. OPTIONS -version Displays the version of the omniiso command.
Page 141 This option is available only for Windows Vista and Windows Server 2008. -inject_drivers Driver1Path [Driver2Path ...] Injects additional drivers into the DR OS image. You must specify a full path to the driver. A maximum of 50 paths can be specified. This option is available only for Windows Vista and Windows Server 2008.
Page 142 SEE ALSO omnidr(1M), omniofflr(1M), omnisrdupdate(1M)
Page 143: Omnimcopy
omnimcopy makes a copy of a Data Protector medium using Data Protector backup devices as the source and destination (this command is available on systems with the Data Protector User Interface component installed) omnimcopy SYNOPSIS omnimcopy -version | -help omnimcopy -copy BackupDevice [-slot Slot...] -from BackupDevice [-src_slot Slot...] [BasicOptions] [LabelOptions] omnimcopy -ams [-from VLS_SMART_COPY -src_slot SourceTapeBarcode] [-copy VirtualTapeLibrary] [-slot TargetTapeBarcode] [-pool Pool-...
Page 144 of media using -barcode_as_label, -no_barcode_as_label and MediumLabel options. • Medium ID (system-assigned) • Location The physical devices used for the input and output must be the same device type and have the same block size. This copy functionality allows the user to use multiple tapes in order to implement vaulting with Data Protector.
Page 145 Specifies the output backup device - the device used to create a copy of the medium (target medium). You can specify only one slot. For VLS smart copies, the output backup device is the name of the VTL that will be used for automigration.
Page 146 -permanent This backup protection option provides permanent protection of backup media. This means that the data is permanently protected from being overwritten. -until Date This backup protection option provides protection until a date of your choice. This means that the data on the medium cannot be overwritten until the specified date.
Page 147: Omniminit
omniminit initializes a Data Protector medium (this command is available on systems with the Data Protector User Interface component installed) omniminit SYNOPSIS omniminit -version | -help omniminit -init BackupDevice [MediumLabel] [BasicOptions] [SlotOp- tions] [-no_barcode_as_label] omniminit -init BackupDevice [BasicOptions] [SlotOptions] [-bar- code_as_label] omniminit -init_magazine BackupDevice [MagazineDescription] [Ba- sicOptions]...
Page 148 of media using -barcode_as_label, -no_barcode_as_label and MediumLabel options. • Medium ID (system-assigned) • Location This information is added to the Data Protector internal database (IDB) and the medium is added to a Data Protector media pool. Medium ID is its unique identifier. The Medium Label does not necessarily have to be unique, but it is recommended.
Page 149 process. For best performance, optical disks should be pre-erased before each backup. -force Overrides the initialization safety checks. By default, a medium containing protected data or being in a non-Data Protector format cannot be initialized. -pool PoolName Specifies the name of the media pool to which this medium will be added. If no PoolName is specified, the medium is added to the default pool for the specified backup device.
Page 150 EXAMPLES The following examples illustrate how the omniminit command works. To init slot "4" of backup device "ADIC" with medium label "Label4", in location "Backup Room", run: omniminit -init ADIC Label4 -slot 4 -location "Backup Room" To preerase slot "8" side "A" of MO tape library unit "MO_Changer", run: omniminit -preerase MO_Changer -slot 8 A SEE ALSO omniamo(1), omnidownload(1), omnimcopy(1), omnimlist(1), omnimm(1), omnimnt(1),...
Page 151: Omnimlist
omnimlist lists the contents of a Data Protector medium (this command is available on systems with the Data Protector User Interface component installed) omnimlist SYNOPSIS omnir -version | -help omnimlist -device BackupDevice [-slot SlotID [Side]] [-monitor] [-detail] omnimlist -device BackupDevice [-slot SlotID [Side]] [-header] [-monitor] omnimlist -device BackupDevice -session [-slot SlotID [Side]] [-monitor] [-detail]...
Page 152 Specifies the BackupDevice where the medium is mounted. If no other option is specified the command lists all sessions and all their objects. -slot SlotID [Side] Specifies the SlotID of the library where the medium is mounted. This option is only valid for this backup device type, but must be given for MO devices. To specify the side of the platter in this slot, use the additional Side parameter.
Page 153 Displays detailed information about the selected query. NOTES For the -header option, the following limitation applies: the command displays the header information stored on the medium, ignoring possible updates in the Data Protector internal database (IDB). EXAMPLES The following examples show how the omnimlist command works. To list sessions and corresponding disk agents from device "DAT2", run: omnimlist -device DAT2 -monitor To list sessions on slot "43"...
Page 155: Omnimm
omnimm provides media management for Data Protector (this command is available on systems with the Data Protector User Interface component installed) omnimm SYNOPSIS omnimm -version | -help omnimm -create_pool PoolName MediaType [Policy AgeLimit MaxOver- Writes] [-[no_]alloc_uninit_first] [-[no_]free_pool [FreePoolName]] [-[no_]move_free_media] omnimm -modify_pool PoolName NewPoolName [Policy AgeLimit Max- OverWrites] [-[no_]alloc_uninit_first] [-[no_]free_pool [FreePool- Name]] [-[no_]move_free_media] omnimm -create_free_pool PoolName MediaType [AgeLimit MaxOver-...
Page 156 omnimm -media_info Medium [-detail | –encryptioninfo] omnimm -list_magazines_of_pool PoolName [-detail] omnimm -list_media_magazine MagazineDescription [-detail] omnimm -catalog Medium omnimm -check_protection Medium omnimm -recycle Medium omnimm -recycle_magazine MagazineDescription omnimm -export Medium omnimm -export_magazine MagazineDescription omnimm -copy_to_mcf {Medium1 [Medium2...]} [-output_directory Pathname] omnimm -import LogicalDevice [-slot SlotID [Side]] [-no_log | -log_dirs | -log_file] [-pool PoolName] [-import_as_original] omnimm -import_catalog LogicalDevice [-slot SlotID [Side]] [-no_log | -log_dirs | -log_file]...
Page 157 This means protection of data which are on Data Protector tapes and protection for data which is still on the system and needs to be backed up. For the list of supported media classes, refer to the HP Data Protector product announcements, software notes, and references.
Page 158 Creates a new pool with PoolName for the medium of MediaType with the policy defined by Policy. For the list of supported media classes, refer to the HP Data Protector product announcements, software notes, and references. Supported policies are: Loose, Strict, App+Loose, App+Strict, AppIncr+Loose and AppIncr+Strict.
Page 159 no automatic de-allocation of free media. The default setting is -no_move_free_media. -modify_pool PoolName NewPoolName [Policy AgeLimit MaxOver- Writes] Renames the pool PoolName into NewPoolName. The Policy, AgeLimit and MaxOverWrites can also be changed. Supported policies are: Loose, Strict, App+Loose, App+Strict, AppIncr+Loose and AppIncr+Strict. AgeLimit is set in months.
Page 160 Moves magazine MagazineDescription from the current pool to the pool specified by NewPoolName. -modify_medium Medium NewMediumLabel NewLocation Modifies medium with the specified Medium . Note that you should always enter the medium label NewMediumLabel and location NewLocation in that sequence. -modify_magazine MagDescription NewLocation [NewMagDescription] Changes the location of the magazine MagDescription to NewLocation.
Page 161 -list_media Medium Displays all the objects, their type and their protection status for the medium you specified. -list_appendable_media PoolName Displays all appendable media from the specified media pool. -list_copy Medium List all copies of the given medium. -media_info Medium Displays information on the given medium. -encryptioninfo Displays detailed encryption information for objects on the specified medium.
Page 162 -output_directory Pathname Specifies the directory where MCF files are stored. You must specify a full path to the files. If not specified, the files are by default copied on the Cell Manager in the directory Data_Protector_program_data\Config\Server\export\mcf (Windows Server 2008), Data_Protector_home\Config\Server\export\mcf (other Windows systems), or in /var/opt/omni/server/export/mcf (UNIX systems).
Page 163 Specifies a media pool for import. By default, the -orig_pool option is set. It can be disabled with the -[no_]orig_pool option. -import_as_original Imports a medium copy or a medium-related catalog data copy as original if an original medium does not exist in a database. -disable_lockname LockName Disables devices with the LockName for any operation.
Page 164 Adds slots to the selected library. With ADIC/GRAU DAS or StorageTek ACS libraries, this option adds volsers to the selected library. Make sure you use a format supported by your library. For example, when adding slots to a SCSI library, do not use letters or leading zeros. -remove_slots LibraryName {Slot...
Page 165 Splits the magazine MagazineDescription so that the magazine media become non-magazine media. -reload_serial_number DeviceName Reloads the device serial number and overwrites the serial number stored in the internal database. A physical device can therefore be replaced without changing the logical device properties. RETURN VALUES See the man page omniintro for return values.
Page 166 To copy media catalogs of media "DefaultFile_1" and "MyDLT_35" to the mcf directory on UNIX system, run: omnimm -copy_to_mcf "DefaultFile_1" "MyDLT_35" -output_directory /tmp/mcf To import media-related catalog data copies "2401 1 10a_47d7f516_0aa0_0001.mcf" and "2401 1 10a_47e26bc2_0a74_0002.mcf" from the default MCF directory on Windows Server 2003 into a new media pool with prefix "MCF_"...
Page 167: Omnimnt
omnimnt responds to a Data Protector mount requests for a medium (this command is available on systems with the Data Protector User Interface component installed) omnimnt SYNOPSIS omnimnt -version | -help omnimnt -device BackupDevice -session SessionID [-cancel] DESCRIPTION The omnimnt command satisfies or aborts a Data Protector mount request. A mount request is issued by a backup device once it has filled all the available media.
Page 168 EXAMPLES The following examples illustrate how the omnimnt command works. To satisfy a mount request issued by device "DAT1" in a session with SessionID "R-2008/05/05-275", run: omnimnt -device DAT1 -session R-2008/05/05-275 To cancel device for the backup device "Juke" in the session with SessionID "R-2008/05/25-3", run: omnimnt -device Juke -session R-2008/05/25-3 -cancel SEE ALSO...
Page 169: Omnimver
omnimver verifies data on a medium (this command is available on systems with the Data Protector User Interface component installed) omnimver SYNOPSIS omnimver -version | -help omnimver -device BackupDevice [-slot SlotID [Side]] [-eject] DESCRIPTION The omnimver command is used to verify the contents of a Data Protector backup medium.
Page 170 omnimver -device Spectra60 -slot 32 SEE ALSO omniamo(1), omnidownload(1), omnimcopy(1), omniminit(1), omnimlist(1), omnimm(1), omnimnt(1), omniupload(1), sanconf(1M), uma(1M)
Page 171: Omniobjconsolidate
omniobjconsolidate consolidates Data Protector backup objects into synthetic full backups (this command is available on systems with the Data Protector User Interface component installed) omniobjconsolidate SYNOPSIS omniobjconsolidate -version | -help omniobjconsolidate -consolidationlist ConsolidationSpecifica- tionName -scheduled [GeneralOptions] omniobjconsolidate -consolidationlist ConsolidationSpecifica- tionName -postbackup -session SessionID [GeneralOptions] omniobjconsolidate [GeneralOptions] [Device...]...
Page 172 [-copy CopyID] [-sourcedevice BackupDevice] -consolidationdevice LogicalDevice [-targetdevice LogicalDevice] [-protect {none | weeks n | days n | until Date | permanent}] [-keepcatalog {weeks n | days n | until Date | same_as_data_protec- tion}] [-[no_]log | -log_dirs | -log_file] [-[no_]recycle] OtherOptions Date= [YY]YY/MM/DD (1969 <...
Page 173 Immediately starts a post-backup object consolidation specification specified by the -session SessionID option. -session SessionID If specified with the -postbackup option, provides the session ID for the post-backup object consolidation session. If specified as part of the object definition, selects the point in time for object consolidation.
Page 174 attributes) are logged to the IDB. You can browse directories and files before restoring and in addition look at file attributes. Data Protector can fast position on the tape when restoring a specific file or directory. If the logging level is not specified, the logging level of the source object is used. -no_log Specifies the logging level of the object consolidation session.
Page 175 -no_monitor If this option is used, the command displays only the session ID. By default, the command monitors the session and displays all messages. -filesystem Client:MountPoint Label Selects the filesystem identified with Client:MountPoint Label for object consolidation. -winfs Client:MountPoint Label Selects the Windows filesystem identified with Client:MountPoint Label for object consolidation.
Page 176 Data Protector re-calculates the CRC during a restore and compares it to the CRC on the medium. It is also used while verifying and copying the media. -encrypt If this option is used, the Backup Media Agent enables hardware encryption on the device.
Page 177 EXAMPLES To start an objectconsolidation session that consolidates the WinFS object versions for "OBJECT1" on the host "system1.company.com" to the point in time defined with the session ID "2008/09/06- 1 ", using the device "LTO3" as the source device and the file library "FILEDEV1" as the consolidation device, and writes the consolidated objects to the device "LTO4", use: omniobjconsolidate -winfs system1.company.com:/C 'OBJECT1' -session 2008/09/06-1 -sourcedevice 'LTO3'...
Page 179: Omniobjcopy
omniobjcopy creates additional copies of objects backed up with Data Protector on a different media set (this command is available on systems with the Data Protector User Interface component installed) omniobjcopy SYNOPSIS omniobjcopy -version | -help omniobjcopy -copylist CopySpecificationName -scheduled [General- Options] omniobjcopy -copylist CopySpecificationName -postbackup -session SessionID [GeneralOptions]...
Page 180 Object {-filesystem | -winfs | -netware | -omnidb} Client:MountPoint Label -session SessionID [-copyid N [-fixedcopy...]] [-sourcedevice LogicalDevice] [-targetdevice LogicalDevice] [-targetprotect {none | weeks n | days n | until Date | permanent}] [-keepcatalog {weeks n | days n | until Date | same_as_data_protec- tion}] [[-no_]log | -log_dirs | -log_file] [-sourceprotect {none | weeks n | days n | until Date | permanent |...
Page 181 DESCRIPTION The omniobjcopy command creates additional copies of objects backed up using Data Protector. You can use the omniobjcopy command to copy objects such as filesystems (UNIX or Windows), very big file systems, disk image sections, NetWare objects, and Data Protector internal database (IDB) to an additional media set. The command can be also used for copying the integration objects (SAP R/3, Oracle, Informix Server, VMware Virtual Infrastructure, Microsoft Exchange Server, Microsoft Exchange Server single mailboxes, Microsoft SQL Server, Lotus, Sybase, DB2,...
Page 182 Specifies how many devices are locked prior to starting a session. Devices that are specified per object through the -targetdevice option are locked in any case. The max value is increased by Data Protector if the number of statically assigned devices is higher than the specified max value. Min specifies the minimum number of available devices (devices that are not being used by another Data Protector session and have the license to be started) required for starting the session.
Page 183 -log_dirs Specifies the logging level of the object copy session. If this option is specified, only the directories are logged into the database. By default, the filename and backup history of each backed up file is written to the catalog database. -log_file Specifies the logging level of the object copy session.
Page 184 -concurrency ConcurrencyNumber Specifies the number of Restore Media Agents that can send data to a device concurrently. The maximum concurrency value is 32. -crc The CRC check is an enhanced checksum function. When this option is selected, cyclic redundancy check sums (CRC) are written to the media during an object copy.
Page 185 If -fixedcopy option is not specified, Data Protector selects the needed media set automatically. If several copies of the same object exist in one session as a result of the object copy or object mirror operation, this option is obligatory. -sourcedevice LogicalDevice Specifies a logical device different from the one used for the backup to be used for reading backed up objects from the source media.
Page 186 -db2 Client:Set Selects the DB2 object identified by Client:Set for object copying. -sybase Client:Set Selects the Sybase object identified by Client:Set for object copying. -mssps Client:Set Selects the Microsoft SharePoint Portal Server object identified by Client:Set for object copying. -vmware Client:Set Selects the VMware Virtual Infrastructure object identified by Client:Set for object copying.
Page 187 'Label42'" from the session "2008/07/01-2", using the device "DEV1" to read the source objects and the device "DEV2" copy the objects, run: omniobjcopy -filesystem system1.company.com:/ 'Label42' -session 2008/07/01-2 -sourcedevice 'DEV1' -targetdevice 'DEV2' -full To immediately start a post-backup object copy specification named "post_BU1" for the session "2008/08/03- 1 ", use: omniobjcopy -copylist post_BU1 -postbackup -session 2008/08/03-1...
Page 189: Omniobjverify
omniobjverify verifies Data Protector backup objects, either interactively or using pre-configured post-backup, or scheduled verification specifications (this command is available on systems with the Data Protector User Interface component installed) omniobjverify SYNOPSIS omniobjverify -version | -help omniobjverify -verificationlist VerificationSpecificationName -scheduled [GeneralOptions] omniobjverify -verificationlist VerificationSpecificationName -postbackup -session SessionID [GeneralOptions] omniobjverify [GeneralOptions] Object[[Object]...]...
Page 190 DESCRIPTION The omniobjverify command verifies backup objects that have been created by Data Protector backup, object copy, or object consolidation sessions. You can use the omniobjverify command to verify objects such as filesystems (UNIX or Windows), very big file systems, disk image sections, NetWare objects, and the Data Protector Internal Database (IDB).
Page 191 Specifies the original backup object source host as the host on which the object verification process will be performed. –verify_on_mahost Specifies the media agent host as the host on which the object verification process will be performed. –verify_on_host hostname Specifies the host identified by hostname as the host on which the object verification process will be performed.
Page 192 -copyid N [-fixedcopy] Selects the specified copy of an object version as a source for object verification. If -fixedcopy option is not specified, Data Protector selects the needed media set automatically. If several copies of the same object version exist in one session as a result of the object copy or object mirror operation, this option is obligatory.
Page 193 -sybase Client:ObjectName Selects the Sybase object identified by Client:ObjectName for object verification. -mssps Client:ObjectName Selects the Microsoft SharePoint Portal Server object identified by Client:ObjectName for object verification. -vmware Client:ObjectName Selects the VMware Virtual Infrastructure object identified by Client:ObjectName for object verification. RETURN VALUES See the man page omniintro for return values.
Page 194 To immediately start a post-backup verification specification named "post_bu_verify1" for the session "2009/01/03- 1 ", run: omniobjverify -verificationlist post_bu_verify1 -postbackup -session 2009/01/03-1 To immediately start a scheduled verification specification named "sched_verify1", run: omniobjverify -verificationlist sched_verify1 -scheduled SEE ALSO omnib(1), omnidb(1), omnikeymigrate(1M), omnikeytool(1M), omniobjconsolidate(1), omniobjcopy(1), omnir(1)
Page 195: Omnir
omnir restores filesystems, disk images, the Data Protector database (IDB), Microsoft Exchange Server single mailboxes and Public Folders, Microsoft Exchange Server, Microsoft SQL Server, Microsoft SharePoint Portal Server (SPS), SAP R/3, SAP DB/MaxDB, Informix Server, VMware Virtual Infrastructure (VMware), Lotus, IBM DB2 UDB, NetWare objects, and NDMP objects backed up with Data Protector.
Page 196 Object {-filesystem | -winfs | -netware}Client:MountPoint Label -omit_deleted_files [-session SessionID [-copyid CopyID] ] -overwrite -tree TreeName... [DATA_OPTIONS] [FILESYSTEM_OPTIONS] [SPLIT_MIRROR_OPTIONS] [GENERAL_OPTIONS] Object {-filesystem | -winfs | -netware} Client:MountPoint Label -tree TreeName... MEDIUM_OPTIONS [DATA_OPTIONS] [FILESYSTEM_OPTIONS] [GENERAL_OPTIONS] Object -host Clientname -session SessionID [-full | -omit_deleted_files -overwrite ] [FILESYSTEM_OPTIONS] [GENERAL_OPTIONS] INTERNAL DATABASE RESTORE...
Page 197 RAW DISK RESTORE Object -rawdisk Host Label -session SessionID [-copyid CopyID] -section [ToSection=]Section [SPLIT_MIRROR_OPTIONS] [GENERAL_OPTIONS] Object -rawdisk Host Label -section [ToSection=] Section MEDIUM_OPTIONS [GENERAL_OPTIONS] INSTANT RECOVERY omnir -host ClientName -session SessionID -instant_restore [DISK_ARRAY_XP_OPTIONS | VIRTUAL_ARRAY_OPTIONS | ENTERPRISE_VIR- TUAL_ARRAY_OPTIONS] [ORACLE_SPECIFIC_OPTIONS] [SAP_SPECIFIC_OPTIONS] DISK_ARRAY_XP_OPTIONS -keep_version -check_config...
Page 198 -user UserName -group GroupName -recover {now | time MM/DD/YY hh:mm:ss | logseq LogSeqNum thread ThreadNum | SCN Number} [-open [-resetlogs] ] -appname ApplicationDatabaseName -parallelism Number NDMP RESTORE Object -filesystem Host:MountPoint Label -full [-session SessionID] -treeTreeName... [NDMP_DATA_OPTIONS] [NDMP_GENERAL_OPTIONS] Object -filesystem Host:MountPoint Label -session sessionID [-full] -tree TreeName...
Page 199 VMWARE VIRTUAL INFRASTRUCTURE RESTORE RESTORE OF VIRTUAL MACHINES omnir -vmware -barhost OriginalVMwareManagementClient -instance OriginalDatacenter -method {Snapshot | Suspend | VCBimage} [-session SessionID] VirtualMachines [-disk Disk [-disk Disk ...]] [VirtualMachines [-disk Disk [-disk Disk ]] ...] [-destination RestoreClient] [-newinstance TargetDatacenter] [-consolidate] [-memory] [-register] [-poweron]...
Page 200 [-newinstance DestinationInstanceName] [-session SessionID] [-recover [-endlogs | -time: YYYY-MM-DD.hh.mm.ss] [-from_disk]] [-nochain] INFORMIX SERVER RESTORE omnir -informix -barhost ClientName -barcmnd PathName -user User:Group -appname ApplicationDatabaseName -bararg OnBarRestoreArguments [SESSION_OPTIONS] [GENERAL_OPTIONS] SESSION_OPTIONS -report {warning | minor | major | critical} -load {low | medium | high} -no_monitor MICROSOFT EXCHANGE SERVER RESTORE omnir -msese...
Page 201 PUBLIC_FOLDERS_OPTIONS -folder FolderName -exclude FolderName -originalfolder {-keep_msg | -overwrite_msg} -chain MICROSOFT SQL SERVER RESTORE omnir -mssql -barhost ClientName [-destination ClientName] [-instance SourceInstanceName] [-destinstance DestinationInstanceName] { -base DBName [-session SessionID] [MSSQL_OPTIONS]... | -base DBName -datafile GroupName/DataFileName -session SessionID [DATAFILE_OP- TIONS]...} [GENERAL_OPTIONS] MSSQL_OPTIONS -asbase NewDBName {-file LogicalFileName1 PhysicalFileName1 [-file LogicalFileName2 PhysicalFileName2]...}...
Page 202 [-tohost Client] [-instance Instance] [-as NewDBName] Index_Options -session SessionID [-tohost Client] [-todir Directory] SiteDBS_Options -session SessionID [-tohost Client] [-instance Instance] LOTUS RESTORE omnir -lotus -barhost ClientName [-user User:Group] [-destination ClientName] [-parallelism n] -domino_server srv_name -appname -db db1 [-db db2...] [-NSF] [-NTF] [-BOX] [-ALL] [-direx direx1 [-direx direx2]...] [-r_dest restore_dir] [ -recover | recovery_time yyy/mm/dd.hh:mm:ss]...
Page 203 [-use_vds | VSS_ENTERPRISE_VIRTUAL_ARRAY_OPTIONS | VSS_DISK_AR- RAY_XP_OPTIONS] VSS_ENTERPRISE_VIRTUAL_ARRAY_OPTIONS [—no_copy_back | -copy_back [ -diskarray_wait Minutes [-delete_rep- lica] | -no_diskarray_wait]] [-no_retain_source] VSS_DISK_ARRAY_XP_OPTIONS -copy_back -no_retain_source [-no_diskarray_wait] VSS_EXCHANGE_SPECIFIC_OPTIONS [-exch_check [-exch_throttle Value]] VSS_EXCHANGE_2007_SPECIFIC_OPTIONS [-appsrv ClientName] [[-target_tree TargetStoreName | –exch_RSG LinkedStoreName] -target_dir Directory] DB2 RESTORE omnir -db2 -barhost ClientName -instance InstName {[-dbname DBName [-session SessionID] [-newdbname NewDBName...]]...
Page 204 [-slot SlotID [Side]] FILESYSTEM_OPTIONS -touch -lock -no_protection -[no_]overwrite | -merge -catalog -sparse -move_busy -vsr_only -trustee -no_share[_info] -omit_unrequired_object_versions -[no_]resumable GENERAL_OPTIONS -device BackupDevice -no_auto_device_selection -server ServerName -target Client -profile -load {low | medium | high} -pre_exec PathName -post_exec PathName -variable VariableName VariableValue -no_monitor SPLIT_MIRROR_OPTIONS -sse | -symmetrix...
Page 205 DESCRIPTION The omnir command restores objects backed up using Data Protector. You can use the omnir command to restore filesystems (UNIX, Windows), very big file systems, disk image sections, NetWare objects, NDMP objects and Data Protector internal database (IDB) to their original (or a new) location. The command can be also used for restoring Integration objects (SAP R/3, Microsoft Exchange Server, Microsoft Exchange Server single mailboxes, Microsoft SQL Server, Microsoft SharePoint Portal Server, Lotus, Informix Server, DB2 and SAP DB/MaxDB) or to start the instant recovery...
Page 206 To restore objects from a medium that is not in IDB, use the -medium MediumID option, instead of the SessionID . NOTE: The -medium option is not possible when performing a parallel restore. To get the MediumID and DiskAgentID from the medium, use the omnimlist command to read the medium.
Page 207 Specifies the file, component, or tree to restore. Note that when specifying trees on UNIX systems, complete trees must be specified including the mount points, whereas on Windows systems, trees must be specified without volumes (drives). For example: -tree /usr/temp (UNIX system) and -tree /temp/Filesytem/E (Windows system).
Page 208 not specified), Data Protector selects the media set to restore from automatically. When using this option, it is necessary to specify both the object and the session. -tree TreeName Specifies the file, component, or tree to restore. Note that when specifying trees on UNIX systems, complete trees must be specified including the mount points, whereas on Windows systems, trees must be specified without volumes (drives).
Page 209 For example: -tree /usr/temp (UNIX system) and -tree /temp/Filesytem/E (Windows system). -into Pathname Restores the selected fileset into the given directory. -ndmp_user UserName Sets the username that is used by Data Protector to establish the connection to the NDMP server. -ndmp_passwd Password Sets the password for the username that is used by Data Protector to establish the connection to the NDMP server.
Page 210 The value of the barcmnd option has to be set to ob2onbar.pl. The command should reside in /opt/omni/bin directory on HP-UX systems and in Data_Protector_home\bin directory on Windows systems. -user UserName:GroupName Specifies Username and GroupName that started the script specified by the -barcmnd option.
Page 211 This option must be set for every -base option specified. -logpath path Specifying this option, you set the temporary directory for the Microsoft Exchange Server log files. Data Protector restores the log files to this directory. Using this directory, the Microsoft Exchange Server then recovers the database - this operation is referred to as hard recovery.
Page 212 -folder FolderName Specifies folders to be restored. Note that the subfolders are also restored. If this option is not specified, all backed up folders are restored. -exclude FolderName Specifies the folders to be excluded from restore. -originalfolder{-keep_msg | -overwrite_msg} If this option is selected, Data Protector restores Exchange Server items to the same folders in which they were when the backup was performed.
Page 213 Specifies the Lotus Notes/Domino Server client from which the data was backed -destination ClientName Specifies the target client for restore. Use this option only when you restore to some other instance than the one that was backed up. -parallelism n Sets the number of restore streams, running in parallel.
Page 214 Specifies the session to be used for restore. When restoring objects that have copies, do not use the object copy session ID, but the object's BackupID, which equals the object's backup session ID. DB2 RESTORE -db2 Selects the IBM DB2 UDB object to restore. -barhost ClientName Specifies the IBM DB2 UDB client from which the data was backed up.
Page 215 Sets the name of the DB2 instance from which you want to restore the data. VSS RESTORE -vss Selects the VSS object for restore. -barhost ClientName Specifies the system where the VSS agent or application agent is run. -session SessionID Specifies the session to be used for restore.
Page 216 (VSSDB). Does not use a ZDB array specific options or agents. On HP StorageWorks Disk Array XP, this option must be used after the backup created with the XP provider in the VSS compliant mode.
Page 217 VSS_DISK_ARRAY_XP_OPTIONS -copy_back Performs resynchronization of the disk pair, copying data from the target volume (backup disk) to the source volume. This option must be specified if the data was backed up with VSS provider in the resync mode. -no_retain_source Deletes the source volume during restore. This option must be specified if the data was backed up with VSS provider in the resync mode since there is no possibility to retain the source during re-synchronization of replica and source disk.
Page 218 TreeName and its TargetStoreName pair must always be fully expanded subcomponents representing an Exchange store or logs. See also the Exchange 2007 examples. To get a list of available targets on a specific host, run the command: vssbar -appsrv:HostName -perfom:browse -all Potential targets can be identified by the string "RESTOREMODE = 1".
Page 219 -newinstance DestinationInstanceName Performs a restore to the SAP DB/MaxDB instance with the instance name DestinationInstanceName. This option is to be used only when a restore to an instance other than the one that was backed up is to be performed. Note that the specified instance must already exist and must be configured for use with Data Protector.
Page 220 -from_disk Specify this option to apply the existing archive logs on the SAP DB Server to SAP DB Server redo logs. If this option is not specified, the backed up archive logs on backup media are applied to the redo logs (if trans backup session is restored), or the redo logs are left intact together with the existing archive logs on the SAP DB Server (if full or diff backup session is restored).
Page 221 When restoring objects that have copies, do not use the object copy session ID, but the object's BackupID, which equals the object's backup session ID. -datafile GroupName/DataFileName Specifies an SQL Server data file for restore. GroupName is the name of the group the data file belongs to.
Page 222 Specifies the VMware management client that was used during backup. -instance OriginalDatacenter Specifies the datacenter from which the virtual machines were backed up. -method Method Specifies the method that was used for backup. -session SessionID Specifies the backup session to be used for restore. –all Restores all the virtual machines from the specified backup session.
Page 223 –newinstance TargetDatacenter Specifies the datacenter that the virtual machines are restored to. By default, the virtual machines are restored to the original datacenter. Use this option in the case of a disaster recovery when the new datacenter does not have the same name as the original one.
Page 224 -mssps Selects the Microsoft SharePoint Portal Server object for restore. -barhost ClientName Specifies the front-end Web server system that was used during backup. -changemaster Applicable only if the Microsoft SharePoint Portal Server farm is centralized (having the master and child portals). If you are restoring the master portal and you specify this option, the current master portal becomes a child of the restored master portal.
Page 225 -host ClientName Restores all objects of the specified client that were backed up in the specified session. -session SessionID Specifies the session to be used for restore. ENTERPRISE_VIRTUAL_ARRAY_OPTIONS -check_config If this option is set, the current volume group configuration of the volume groups involved in the instant recovery session is compared with the volume group configuration during the ZDB-to-disk or ZDB-to-disk+tape session kept in the ZDB database (EVADB or SMISDB).
Page 226 from the volume group configuration kept in the VADB. In such a case the VADB 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.
Page 227 Selects the SAP R/3 options for instant recovery. -recover {now | time Time | logseq LogSeqNum thread ThreadNum | SCN Number} Selects the point in time to which the database is recovered. The following options are available: All existing archive logs are applied. time MM/DD/YY hh:mm:ss Specifies an incomplete recovery.
Page 228 Selects the parallelism for the restore of archive logs and restore from incremental backups. DATA_OPTIONS -exclude TreeName Excludes the specified tree from the restore. This option is not supported with the Data Protector NDMP server integration. -skip MatchPattern Excludes files matching MatchPattern from restore. This option is not supported with Data Protector NDMP server integration.
Page 229 in this slot, use the additional Side parameter. Slot Side must be specified for MO devices. Values for side are A or B. -id DiskAgentID Specifies the ID of the disk agent which should be used for restore. FILESYSTEM_OPTIONS -touch Updates the access date/time of the file during the restore.
Page 230 If you have changed the default using the global option ResumableRestoreDefault, specify the option -resumable if you want checkpoint files to be created. SPLIT_MIRROR_OPTIONS -sse Selects the HP StorageWorks Disk Array XP split mirror restore. -symmetrix Selects the EMC Symmetrix split mirror restore.
Page 231 Data Protector Symmetrix database on both the application and backup systems. Its functionality is the same as that of the Data Protector Syma -init command. (Refer to the HP Data Protector zero downtime backup administrator's guide).
Page 232 -restore_links_after_restore With this option enabled, the HP StorageWorks Disk Array XP agent incrementally restores links for LDEVs that were successfully restored by Data Protector to the backup system. The HP StorageWorks Disk Array XP agent also incrementally re-establishes links for LDEVs that were not successfully restored by Data Protector to the backup system.
Page 233 -load{low | medium | high} Specifies the level of network traffic generated by a session during a time period. High level generates as much traffic as allowed by the network, resulting in a faster restore. A low level has less impact on network performance, but results in a slower restore.
Page 234 -keep_version To perform an instant recovery of filesystem backup data on HP StorageWorks Disk Array XP or HP StorageWorks Virtual Array to the system named "computer" from the backup session "2008/01/02- 1 ", keeping the replica on the backup system disk, run:...
Page 235 To perform an instant recovery on HP StorageWorks Enterprise Virtual Array to the system named "computer" from the backup session "2008/01/08- 1 " and to perform volume group configuration check, run: omnir -host computer -session 2008/01/08-1 -instant_restore -check_config To perform a point in time recovery of the database "dbase.nsf" and all Lotus Notes/Domino Server NTF files of the Lotus Notes/Domino Server "BLUE"...
Page 236 want to ensure that the newly restored virtual machines are put online when the session completes. Run: omnir -vmware -barhost Virtualcenter.company.com –instance /MyDatacenter -method Suspend –session 2006/2/7-31 –vm /vm/MachineA –vm /vm/MachineB -disk scsi0:0 –disk scsi0:1 –memory –poweron VMware Virtual Infrastructure restore: Suppose the virtual machines "/MyVirtualMachines/machineA"...
Page 237 To restore all messages from the "Inbox" folder (and all subfolders) from the "User 1" mailbox residing on the Microsoft Exchange Server system called "exchange.hp.com", into the original location, using the backup made in the session "2007/03/10- 1 8", without overwriting the messages, run: omnir -mbx -barhost exchange.hp.com -mailbox "User 1"...
Page 238 -rawdisk system "Raw" -section /dev/rdsk/c201d6s0 -session 2007/07/23-12 -copyid 132123 To start instant recovery of data on the HP StorageWorks Enterprise Virtual Array on the system named "system1" from the VSS backup session "2007/08/08- 1 4" which copies the data from the replica to the source disk group overwriting the source volume, execute the following command: omnir —vss —barhost system1 -session 2007/08/08-14...
Page 239 omnir -vss –instant_restore –use_vds –barhost exch2007.company.com -appsrv server2 -session 2007/04/08-9 -tree "/Microsoft Exchange Writer(Exchange Information Store)/Microsoft Information Store/First Storage Group/StoreOne" -target_dir "c:\mnt" -tree "/Microsoft Exchange Writer(Exchange Information Store)/Microsoft Information Store/First Storage Group/Logs" -target_dir "C:\Omni_Mnt" Exchange 2007 VSS restore to a non-Exchange location and creating RSG: To restore the Exchange 2007 Writer store "Store One"...
Page 241: Omnirpt
omnirpt generates various reports about the Data Protector environment, for example, about backup, object copy, object consolidation, and object verification sessions in a specific time frame, session specifications, media, Data Protector configuration, and single sessions (this command is available on systems with the Data Protector User Interface component installed) omnirpt SYNOPSIS...
Page 242 obj_copies | obj_lastbackup | obj_avesize | fs_not_conf | dl_info | dl_sched | db_size | db_purge | db_purge_preview | db_system | cell_info | hosts_unused | dev_unused | lookup_sch | hosts_not_conf | licensing | host | media_list | media_list_extended | media_statistics | pool_list | single_session | session_objects |...
Page 243 -[no_]library Library ... ProtectionOption -[no_]protection NoOfDays MediaClassOption -class MediaClass MediaStatusOption -status MediaStatus SpecificationOptions -datalist BackupSpecificationName ... -copylist_sch ScheduledCopySpecificationName ... -copylist_post PostbackupCopySpecificationName ... -verificationlist_sch ScheduledVerificationSpecificationName -verificationlist_post PostbackupVerificationSpecificationName -conslist_sch ScheduledConsolidationSpecificationName ... -conslist_post PostbackupConsolidationSpecificationName ... -no_datalist -no_copylist -no_verificationlist -no_conslist BackupSpecificationGroupOption -group BackupSpecificationGroup LookupSchedulesOption -schedule NoOfdays NetworkOption -network Network_IP_Adress ...
Page 244 -level Level ObjectCopiesOption -num_copies {less | equal | more} NumberOfCopies TimeframeOption -timeframe {Start Duration | Day Hour Day Hour} LatestObjectOption -days NoOfdays Level: {warning | minor | major | critical} Day: [YY]YY/MM/DD Hour:: HH:MM DESCRIPTION The omnirpt command generates various reports about Data Protector environment: reports about backup, object copy, object consolidation, and object verification sessions in a specific time frame, about backup, object copy, object consolidation, and object verification specifications, media, Data Protector configuration and single...
Page 245 • Extended Report on Used Media (used_media_extended) • Client Statistics (host_statistics) • Session Statistics (session_statistics) • Session Errors (session_errors) • Object Copies Report (obj_copies) Session Specifications "Session Specifications" reports provide different configuration reports which are based on backup, object copy, object consolidation, and object verification specifications.
Page 246 • Clients not Configured for Data Protector (hosts_not_conf) • Licensing report (licensing) • Client Backup Report (host) Pools and Media "Pools and Media" reports provide four reports that search through Data Protector pools for media that match the search criteria. The default is to list all media or pools and each report option can then limit the search to a certain set of media.
Page 247 -multicell This option is only used with Manager-of-Managers. If this option is specified, the report will be generated for all Cell Managers configured in the MoM environment (multi-cell report). -[no_]multiple This option is only used for enterprise reports (multi-cell) and for Session per Client reports.
Page 248 sessions matching search criteria is shown. By default, the report is generated for all session specifications. Use the report filtering options to generate a report only for a specific backup, object copy, object consolidation, or object verification specification. Report options are: -timeframe {Start Duration | Day Hour Day Hour} [-datalist BackupSpecificationName ...] [-group BackupSpecificationGroup]...
Page 249 [-conslist_sch ScheduledConsolidationSpecificationName ...] [-conslist_post PostbackupConsolidationSpecificationName ...] Report filtering options are: [-no_datalist ] [-no_copylist ] [-no_conslist ] used_media Lists destination media that have been used by backup, object copy, and object consolidation sessions in the specific time frame together with their statistics. By default, the report is generated for all session specifications.
Page 250 [-copylist_post PostbackupCopySpecificationName ...] [-conslist_sch ScheduledConsolidationSpecificationName ...] [-conslist_post PostbackupConsolidationSpecificationName ...] Report filtering options are: [-no_datalist ] [-no_copylist ] [-no_conslist ] host_statistics Lists of clients and their backup status - only clients that were used by the backup sessions matching the search criteria are displayed. Additionally, clients can be limited also with hosts report option.
Page 251 Shows list of messages that occur during backup, object copy, and object consolidation sessions in the specified time frame for selected session specifications. The messages are grouped by clients (for all selected clients). By default, the report is generated for all session specifications. Use the report filtering options to generate a report only for a specific backup, object copy, or object consolidation specification.
Page 252 [-no_datalist ] [-no_copylist ] [-no_conslist ] dl_trees Lists all trees in the specified backup specification. It also shows names of drives and the name of a tree. Report options are: [-datalist BackupSpecificationName ...] [-group BackupSpecificationGroup] obj_nobackup Lists all objects, specified for backup in selected backup specifications, which do not have a valid backup.
Page 253 – Filesystem objects that do not match the condition in the object creation time filter are listed anyway. However, in this case, the object creation time fields remain empty. – If you clear certain filesystem objects from a backup specification, these filesystem objects will not be included in the report even if the objects exist in the IDB.
Page 254 [-copylist_post PostbackupCopySpecificationName ...] [-verificationlist_sch ScheduledVerificationSpecificationName ...] [-verificationlist_post PostbackupVerificationSpecificationName ...] [-conslist_sch ScheduledConsolidationSpecificationName ...] [-conslist_post PostbackupConsolidationSpecificationName ...] Report filtering options are: [-no_datalist ] [-no_copylist ] [-no_verificationlist ] [-no_conslist ] dl_sched Shows information about all selected backup, object copy, object consolidation, and object verification specifications and their next scheduled time up to one year in advance (type, session type, session specification name, group, next execution, and backup operation time).
Page 255 db_size Lists a table that contains information about the MMDB, CDB, IDB extension files, statistics for DCBF, SMBF and SIBF, and low IDB disk space. The Used columns in this report show the percentage of used records. This figure is calculated as current amount of used records divided by the amount of records allocated in the IDB in percents.
Page 256 List of configured clients that are not used for backup and do not have any device configured. dev_unused List of configured destination devices that are not used for backup, object copy, or object consolidation at all. lookup_sch List of backup, object copy, and object consolidation specifications that are scheduled to start in the next n number of days up to one year in advance (where n is the number of days specified by user).
Page 257 [-[no_]protection NoOfDays] [-timeframe {Start Duration | Day Hour Day Hour}] [-[no_]library Library ...] media_list_extended List of all media matching the search criteria. The following information is provided for each medium: ID, label, location, status, protection, used and total MB, the time when media was last used, the media pool and media type, session specifications that have used this medium for backup, object copy, or object consolidation, as well as the session type and subtype.
Page 258 Report options are: [-label Label] [-location Location ...] [-pool PoolName ...] [-class MediaClass] [-status MediaStatus] [-[no_]protection NoOfDays] [-timeframe {Start Duration | Day Hour Day Hour}] [-[no_]library Library ...] pool_list Lists all pools matching a specified search criteria. For each pool the following information is provided: pool name, description, media type, total number of media, number of full and appendable media containing protected data, number of free media containing no protected data, number of poor, fair and good...
Page 259 Provides information for each client that took part in the selected backup session: statistics about backup status for the client, list of objects and their related information for the client, error messages for the client. All information is grouped for each client separately. Using the -multiple option, this report can be split into smaller reports, one for each client (see section Notifications for details).
Page 260 server must be accessible from the Cell Manager system, but does not need to be part of the Data Protector cell. -snmp Hostname Report is send as an SNMP (Simple Network Mailing Protocol) trap. -broadcast Hostname Report is broadcasted to the selected machine. Note: Only Windows machines can be specified as broadcast destination.
Page 261 This option is used to specify the media status report option. It can have one of the following values: poor, fair, or good. -datalist BackupSpecificationName ... This option is used to specify the backup specifications for the report. Note that you can specify more than one backup specification.
Page 262 This option is used to specify report option, which defines the number of days for which to display the schedule information. -network Network_IP_Adress ... This option specifies one or more network IP addresses. Network IP address is represented by the first three numbers in the IP address, for example 123.44.5. You can specify more that one network IP address using spaces in between.
Page 263 Report Formats Specifies report format: ASCII -ascii Specifies report format: HTML -html Specifies report format: TAB -tab Specifies report format: SHORT -short EXAMPLES To list all backup sessions that have started in the last 24 hours and display the report in the default ASCII format, run: omnirpt -report list_sessions -timeframe 24 24 -no_copylist -no_conslist -no_verificationlist To list all objects from session "2009/03/16- 1 "...
Page 264 To list all the media used only for object copy and object consolidation sessions, run: omnirpt -report media_list_extended -no_datalist To list all object versions created in the last 72 hours that have less than 5 valid copies, run: omnirpt -report obj_copies —timeframe 72 72 —num_copies less 5 To list all destination media that were used only for scheduled object copy specification named "Alpha"...
Page 265: Omnistat
omnistat displays the status of active Data Protector backup and restore sessions (this command is available on systems with the Data Protector User Interface component installed) omnistat SYNOPSIS omnistat -version | -help omnistat -session SessionID [-status_only | -monitor | -detail] omnistat [-user Username] [-mount] [-error] [-detail] omnistat -previous [-user Username] [{-since Date | -until Date} | -last Number] [-failed]...
Page 266 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)" -mount Displays all active sessions with mount requests pending.
Page 267 To see only the status of session with this SessionID, run: omnistat -status_only -session 2 To monitor the session with the SessionID "R-2008/05/13-8", run: omnistat -session R-8 -monitor SEE ALSO omniabort(1) Command line interface reference...
Page 269: Omniupload
omniupload uploads information about a backup device from an ASCII file to the Data Protector internal database (IDB) (this command is available on systems with the Data Protector User Interface component installed) omniupload SYNOPSIS omniupload -version | -help omniupload -create_device FileName omniupload -modify_device BackupDevice [-file FileName] omniupload -remove_device BackupDevice omniupload -create_library FileName...
Page 270 the current directory for a file with the same name as the BackupDevice. Note that the media class may not be changed. -file FileName Specifies the ASCII file that will be parsed for information about the backup device (library). This option is used to modify an existing backup device (library). If - is specified as FileName then data is read from stdin.
Page 271: Omniusers
omniusers adds or removes Data Protector users to or from an existing Data Protector user group, or lists the configured Data Protector users. It enables you to use all GUI functionality on a Cell Manager platform on which the GUI is not supported, using a GUI installed on another system.
Page 272 <Any> in the Data Protector GUI. Note that in some shells, backslash and asterisk (\*) must be used instead of *. Note that domain names of Windows GUI clients that are used with an HP-UX Cell Manager must be in capital letters.
Page 273 The omniusers command is designed to be used in Data Protector cells where the Cell Manager is running on a platform on which the Data Protector GUI is not supported. For details on supported operating systems, see the HP Data Protector product announcements, software notes, and references.
Page 274 omniusers -add -type U -name root -usergroup admin -group \* -client client.company.com To display the Data Protector users in all configured Data Protector user groups, run: omniusers -list SEE ALSO ob2install(1M), omnigui(5), omniintro(9), omnimigrate.pl(1M), omnisetup.sh(1M), upgrade_cm_from_evaa(1M), winomnimigrate.pl(1M)
Page 275: Syb_Tool
syb_tool a utility used to get ISQL command needed to restore a Sybase database that was backed up by Data Protector (this command is available on systems with the Data Protector Sybase Integration component installed) syb_tool SYNOPSIS syb_tool dbname servername -date YYYY/MM/DD.hh:mm:ss [-new_db dbname] [-new_server servername]...
Page 276 When restoring the objects, add the -i file_name -J utf8 options to the isql command, where file_name is the file with the load command. For details, see HP Data Protector integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server.
Page 277 "server", saving the ISQL statement to file "/tmp/stat.isql", and getting the list of media IDs needed for restore, run: syb_tool database1 server -date -file /tmp/stat.isql -media To start the restore, start the ISQL command, specifying the input file "/tmp/stat.isql" in the following way: isql -Usa -P -Sserver -i /tmp/stat.isql Command line interface reference...
Page 279 Section 1M: Administrative Commands Command line interface reference...
Page 280 Section 1M: Administrative Commands...
Page 281: Cjutil
cjutil starts, stops, and queries the Change Journal (this command is available on systems with the Data Protector Disk Agent component installed) cjutil SYNOPSIS cjutil -volume vol {-start [-maxsize max -delta del] | -stop [-wait] | -query} DESCRIPTION The cjutil command is used to control and administer the Change Journal. It is located in the Data_Protector_home\bin directory on a Windows client.
Page 282 NOTES If the -start option is specified and the Change Journal is already active, the Change Journal is adjusted to the value of the maximum size and delta. Note that these values can only be adjusted to increase. When starting the Change Journal, if you not specify -maxsize and -delta, or specify 0 for these parameters, the system chooses a default value based on the volume size.
Page 283: Nnmpost.ovpl
NNMpost.ovpl a script with no arguments that resumes the eight processes paused by NNMpre.ovpl (this command is available on systems with the Data Protector HP Network Node Manager Integration component installed) NNMpost.ovpl SYNOPSIS NNMpost.ovpl DESCRIPTION A script with no arguments that resumes the eight processes paused by NNMpre.ovpl.
Page 285: Nnmpre.ovpl
NNMpre.ovpl starts NNM embedded database backup (this command is available on systems with the Data Protector HP Network Node Manager Integration component installed) NNMpre.ovpl SYNOPSIS NNMpre.ovpl DESCRIPTION The NNMpre.ovpl script starts the NNM embedded database backup. The embedded database makes a direct copy of itself to a location specified in the solid.ini file.
Page 287: Nnmscript.exe
NNMScript.exe finds the location of the NNM Perl compiler and the NNMpre.ovpl and NNMpost.ovpl scripts and starts the two scripts (this command is available on systems with the Data Protector HP Network Node Manager Integration component installed) NNMScript.exe SYNOPSIS NNMScript.exe -pre | -post DESCRIPTION The NNMScript.exe finds the location of the NNM Perl compiler and the...
Page 288 SEE ALSO NNMpost.ovpl(1M), NNMpre.ovpl(1M)
Page 289: Ob2Install
ob2install runs remote client installation, uninstallation, upgrade, or check of a client from the selected Installation Server (this command is available on the Data Protector Installation Server) 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.
Page 290 HP StorageWorks VA Agent software component informix installs the Informix Integration software component ov installs the HP Network Node Manager Integration software component lotus installs the Lotus Integration software component db2 installs the DB2 Integration software component...
Page 291 InstallPath Specifies the path for installation — the Data Protector home directory. The parameter must be enclosed in double quotes. For UNIX remote client installation this path is ignored and a placeholder ("-") can be used. UserName Specifies the user name that is used during the remote client installation. If not specified, the default value "root"...
Page 292 To start a remote client installation from the Installation Server "computer1.company.com" to the client "computer2.company.com" belonging to the Cell Manager "computer3.company.com", where the input file is named "infile.txt" and the selected components are Disk Agent, General Media Agent and Cell Console, run the following command on the Cell Manager: ob2install -server computer1.company.com -input infile.txt The input file "infile.txt"...
Page 293: Omnicheck
omnicheck performs a DNS connections check within a Data Protector cell and lists Data Protector patches installed on Data Protector clients (this command is available on systems with any Data Protector component installed) omnicheck SYNOPSIS omnicheck -version | -help omnicheck -dns [-host Client | -full] [-verbose] omnicheck -patches -host Client DESCRIPTION The following tasks can be performed using the omnicheck command:...
Page 294 OPTIONS -version Displays the version of the omnicheck command -help Displays the usage synopsis for the omnicheck command. -dns Checks that the Cell Manager and every Media Agent resolve DNS connections to every Data Protector client in the same cell properly and vice versa. This option performs the same as running the omnicheck -dns -host cell_manager and omnicheck -dns -host media_agent_1 ...
Page 295 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. Additional return values of the omnicheck command used to list the Data Protector patches are: List of patches found on host client Patch level Patch description...
Page 296 SEE ALSO omnicc(1), omnicellinfo(1), omnidlc(1M), omniinstlic(1M), omnisv(1M)
Page 297: Omnicjutil
omnicjutil starts, stops, and queries the Change Journal on Windows clients (this command is available on the Data Protector Cell Manager) omnicjutil SYNOPSIS omnicjutil -help omnicjutil -version omnicjutil -file filename omnicjutil -host hostname -volume vol {-start [-maxsize max -delta del] | -stop [-wait] | -query} DESCRIPTION The omnicjutil command is used to remotely control and administer the Change Journal on Windows clients.
Page 298 The -maxsize max option sets the maximum size of the Change Journal in bytes. The highest possible value is 4 GB (4294967296 bytes). Any specified value greater than 4 GB will be rounded down to 4 GB. Note that a reasonable size for a 100 GB drive is an 85 MB Change Journal.
Page 299 SEE ALSO cjutil(1M) Command line interface reference...
Page 301: Omnidbcheck
omnidbcheck checks the consistency of the Data Protector internal database (IDB) (this command is available on the Data Protector Cell Manager) omnidbcheck SYNOPSIS omnidbcheck -version | -help omnidbcheck [-quick | -extended] omnidbcheck -core [-summary] omnidbcheck -filenames [-summary] omnidbcheck -bf [-summary] omnidbcheck -sibf [-detail | dumpmedia] [-summary] omnidbcheck -smbf [-detail | dumpmessages] [-summary] omnidbcheck -keystore [-summary]...
Page 302 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. -quick Checks the core, CDB filenames, presence and size of DCBF parts of the IDB, and displays the summary of the check by executing the omnidbcheck -core...
Page 303 -smbf Checks the presence of the SMBF. This check takes approximately 5 - 10 minutes. Note that if you have removed a SMBF in any way (e.g. using Data Protector GUI or CLI or deleted the file manually), then this option will report the removed session message as missing.
Page 304 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.
Page 305: Omnidbinit
The IDB directory structure has to exist in order to initialize the IDB successfully. You can re-create the IDB directory structure by copying it from the directory Data_Protector_program_data\NewConfig\ (Windows Server 2008), Data_Protector_home\NewConfig\ (other Windows systems), or /opt/omni/newconfig/ (HP-UX or Solaris system) on the Cell Manager. OPTIONS -version Displays the version of the omnidbinit command...
Page 307: Omnidbrestore
omnidbrestore performs the restores of the Data Protector internal database (IDB) (this command is available on the Data Protector Cell Manager) omnidbrestore SYNOPSIS omnidbrestore -version | -help omnidbrestore -autorecover [AutorecoverOptions] [General Options] omnidbrestore -read OptionFile [GeneralOptions] omnidbrestore RMA_Options VRDA_Options MediaOptions [GeneralOp- tions] RMA_Options (Restore Media Agent options) -mahost DeviceHostname...
Page 308 -session sessionID -save OptionFile -logview -optview -replay_only -firstlog FirstTransactionLog DESCRIPTION The omnidbrestore command is used to restore the Data Protector internal database (IDB) without using the IDB, as opposed to the omnir - omnidb command which uses the IDB to retrieve the information needed for the IDB restore. If the IDB was installed on symbolic links, these symbolic links have to be created as they existed before running the omnidbrestore command.
Page 309 options (Volume Restore Disk Agent options) and arguments needed for the restore. When the options and arguments are retrieved, the restore of the IDB is performed using the retrieved options and arguments to the original location overwriting the current files. The obrindex.dat file resides on the Cell Manager in the directory Data_Protector_program_data\db40\logfiles\rlog (Windows Server 2008), Data_Protector_home\db40\logfiles\rlog (other Windows systems),...
Page 310 3 (Stacker), 5 (Jukebox), 6 (external control), 8 (Grau DAS exchanger library), 9 (STK Silo medium library) or 10 (SCSI Library). -type DeviceType Specifies the media type. Media type numbers are specified in the HP Data Protector product announcements, software notes, and references. -dev PhysicalDevice Physical device path.
Page 311 -remhost RoboticsHostname Use the -remhost option to specify the client with the attached library device, if the library device is connected to a system other than mahost (Media Agent host) VRDA_Options -daid DAID Disk Agent ID of the database backup. -overwrite | -no_overwrite By default, or if the -overwrite option is specified, the already existent files on the disk are overwritten by the restored files.
Page 312 If this file does not exist, enter a full path to theIDB-ClientName-key.csv file that resides on the Cell Manager in the directory Data_Protector_program_data\Config\Server\export\keys (Windows Server 2008), Data_Protector_home\Config\Server\export\keys (other Windows systems), or /var/opt/omni/server/export/keys (UNIX systems). Autorecover Options -session sessionID Instead of selecting the last valid backup of the database, the backup from the specified session is selected.
Page 313 -autorecover -session 2008/04/12-1 To start the IDB restore in the autorecover mode of the client system "pollux.hp.com" using encrypted backed up files from a specific session and the corresponding decryption keys from the "IDB-pollux.hp.com-key.csv" file, run: omnidbrestore -autorecover -session 2008/03/16-8 -keyfile IDB-pollux.hp.com-key.csv...
Page 315: Omnidbupgrade
omnidbupgrade converts filenames in the IDB to the new internal character encoding used in Data Protector A.06.1 1 and thus enables the correct handling of non-ASCII characters in filenames in the Data Protector GUI (this command is available on the Data Protector Cell Manager) omnidbupgrade SYNOPSIS omnidbupgrade -version | -help...
Page 316 NOTES The omnidbupgrade command is available on Windows systems only. Backup will not log files or directories for the client that is being converted while his backup is running. It is recommended to back up the IDB before converting it using omnidbupgrade.
Page 317: Omnidbutil
omnidbutil handles various Data Protector internal database (IDB) maintenance tasks (this command is available on the Data Protector Cell Manager) omnidbutil SYNOPSIS omnidbutil -help omnidbutil -version omnidbutil -list_dcdirs omnidbutil -add_dcdir Pathname [-maxsize Size_MB] [-maxfiles Num- berOfFiles] [-spacelowSize_MB] [-seqNumber] omnidbutil -modify_dcdir Pathname [-maxsize Size_MB] [-maxfiles NumberOfFiles] [-spacelowSize_MB] [-seqNumber] omnidbutil -remove_dcdir Pathname omnidbutil -remap_dcdir...
Page 318 omnidbutil -upgrade_info omnidbutil -show_db_files omnidbutil -free_pool_update omnidbutil -list_large_directories MinNumberOfFiles [-top Nu- mOfTopDirectories] [-detail] [-csv CSVFile] omnidbutil -list_large_mpos MinNumberOfMpos [-top NumOfTopMedia] [-detail] [-csv CSVFile] omnidbutil -list_mpos_without_overs [-csv CSVFile] omnidbutil -free_cell_resources DESCRIPTION The omnidbutil command is used for Data Protector internal database (IDB) maintenance tasks.
Page 319 The contents of MMDB and CDB can be exported to and re-created from text files. Text files are in the ASCII format on UNIX systems and in the UNICODE format on Windows systems. The omnidbutil options used for exporting and re-creating the contents of MMDB and CDB are: -readdb and -writedb.
Page 320 The omnidbutil options used for this group of tasks are: -changebdev, -extendfnames, -extendtblspace, -extendinfo, -purge, -purge_stop, -info, -clear, -change_cell_name, -show_cell_name, -set_session_counter, -upgrade_info, -show_db_files, -free_pool_update, -list_large_directories, -list_large_mpos, -list_mpos_without_overs, -top, and -csv. The following options, -purge –filenames, -fixmpos, and -purge_failed_copies 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.
Page 321 The -seq option sets the sequence number for the new DCBF directory. Each DCBF directory has a certain position which determines when DCBF will be created in the DCBF directory. The first DCBF directory to be used for DCBF has the lowest sequence number.
Page 322 Removes (unregisters) the given DCBF directory. The directory must not hold any DCBF and will not be removed. -remap_dcdir Locates DCBF across all DCBF directories and updates DCBF locations in the IDB if they had been moved manually (using the mv command or similar) between DCBF directories.
Page 323 PhyLocation | Serial_LDEV | WWN_LUN] Unlocks a specified device, target volume, medium or slot, where DevName is the device, Serial_LDEV is the target volume where Serial is the HP StorageWorks Disk Array XP serial number and LDEV is the HP StorageWorks...
Page 324 you can disable the local MMDB on the remote Cell Manager by removing (and possibly copying to a safe place) the directory Data_Protector_program_data\db40\datafiles\mmdb (Windows Server 2008), Data_Protector_home\db40\datafiles\mmdb (other Windows systems), or /var/opt/omni/server/db40/datafiles/mmdb (UNIX systems). All duplicated items (stores, media pools, devices) will have "_N"...
Page 325 The -days option removes media management sessions, restore sessions, and obsolete backup sessions (backup sessions without backed up data) older than NumberOfDays. The -messages option removes session messages for all sessions older than NumberOfDays. The -dcbf option removes DCBF for all media with expired catalog protection. The -mpos option removes all the object versions and media position records for the overwritten tapes.
Page 326 Adjusts the maximum size of database files (dirs.dat, fnames.dat, fn?.ext, and their extension files) to 2 GB. This command should be used only on HP-UX 1 1.23 and 1 1.31 (Itanium) and Linux x86–64 systems, after an upgrade to Data Protector A.06.1 1 if the IDB files exceed 2 GB.
Page 327 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.
Page 328 -free_locked_devs machine omnidbutil -free_locked_devs 0a1106452:5a45add9:2548:0007 omnidbutil -free_locked_devs libraryName phyLocation To unlock a target volume with the HP StorageWorks Disk Array XP serial number of "30658" and the HP StorageWorks Disk Array XP volume number of "288", run: omnidbutil -free_locked_devs 30658_288...
Page 329 To manually change the maximum size for DC directory "dcbf16" in the "C:\Program Files\OmniBack\db40" directory to 48 GB and modify the free disk space needed for a DCBF binary file (10 to 15% of the maximum size is recommended), run: omnidbutil -modify_dcdir C:\Program Files\OmniBack\db40\dcbf16 -maxsize 49152 -spacelow 7372 To save the IDB without detail catalogs (DC binary files and filenames) as ASCII...
Page 331: Omnidlc
Data_Protector_program_data\tmp (Windows Vista, Windows Server 2008), Data_Protector_home\tmp (other Windows systems),/tmp (UNIX systems), and OMNI$ROOT:[TMP] (HP OpenVMS). To collect debugs also from other directories, use the -debug_loc option. Using the command, it is possible to collect Data Protector debug, log and getinfo files from selected clients in the Data Protector cell.
Page 332 Manager, where all collected files with the .gz extension are, by default (if the -depot option is not specified), packed and saved in the current directory as the dlc.pck file. The file includes a generated directory structure that includes the hostnames, paths and the (compressed) collected files of the clients involved.
Page 333 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.
Page 334 All collected files are, by default (if this option is not specified), packed and saved in the current directory as the dlc.pck file. If this option is specified, the collected files are packed and saved in the specified file in the current directory on the Cell Manager.
Page 335 Includes debugs not only from the default debug files directory but also from other directories, dir1, dir2,..Note that the subdirectories are excluded from the search. If a specified directory does not exist on a particular client, the directory is ignored. This option is valid only if the -no_debugs option is not specified.
Page 336 Deletes ctrace.log files containing the information where (on which clients) debug logs are generated and which debug prefixes are used. If the -hosts list option is specified, the command deletes ctrace.log files on specified clients only. Otherwise, ctrace.log files on all clients in a cell are deleted. NOTES The omnidlc command cannot be used to collect the Data Protector installation execution traces.
Page 337 omnidlc -hosts client1.company.com client2.company.com -debug_loc C:\tmp /tmp/debugs To delete all debug log files for the session with the ID "2007/08/27-9", run: omnidlc -session 2007/08/27-9 -delete_dbg To display disk space needed on the Cell Manager for the uncompressed debug files with the debugID "2351" from the client "client.company.com", run: omnidlc -did 2351 -hosts client.company.com -space -no_getinfo -no_logs -no_compress To pack the additional file located in the oc:\debug directory on the client...
Page 339: Omnidr
omnidr a general purpose Data Protector disaster recovery command. Based on its input, it decides on what type of restore to perform (online restore using omnir or offline restore using omniofflr), as well as how to perform the restore (whether or not to use live OS features).
Page 340 Note that omnidr always requires a valid SRD file with updated object information. By default it searches the working directory for recovery.srd. If it is not found, an error is reported. The option -srd overrides the default name recovery.srd -temp[os] Specifies whether the restore process will run in a temporary OS installation.
Page 341 • if the Minimal Recovery option has been selected during EADR or OBDR, meaning that only boot and system disks would be recovered. When omnidr is used on a dual-boot machine, it is strongly recommended to use the -no_cleanup option. -msclusdb If this option is specified, omnidr restores the Microsoft Cluster database.
Page 342 EXAMPLES The following examples illustrate how the omnidr command works. To use the SRD file stored on a floppy drive for the restore, run: omnidr -srd "A:\recovery.srd" To use the local backup device, run: omnidr -local SEE ALSO omniiso(1), omniofflr(1M), omnisrdupdate(1M)
Page 343: Omnihealthcheck
omnihealthcheck checks the status of Data Protector services, the consistency of the Data Protector internal database (IDB), and if at least one backup of the IDB exists (this command is available on the Data Protector Cell Manager) omnihealthcheck SYNOPSIS omnihealthcheck -version | -help omnihealthcheck [-config ConfigFile] DESCRIPTION The omnihealthcheck command reads the specified configuration file where each...
Page 344 The final health check exit code is 0 (OK) only if all executed commands from the configuration file completed successfully (exit codes of all executed individual commands from the configuration file are 0). Output of the omnihealthcheck command is saved on the Cell Manager in the file Data_Protector_program_data\log\server\HealthCheck.log (Windows Server 2008), Data_Protector_home\log\server\HealthCheck.log (other Windows...
Page 345: Omniinetpasswd
omniinetpasswd manages the local Data Protector Inet configuration on Windows systems where the Inet process must be run under a specific user account, and sets a user account to be used by the Installation Server during remote installation (this command is available on systems with any Data Protector component installed) omniinetpasswd SYNOPSIS omniinetpasswd -version | -help...
Page 346 Adds the specified user account from the local Inet configuration. Omniinetpasswd prompts for the password if not specified in the command line. -delete {User@Domain | Domain\User} Removes the specified user account from the local Inet configuration. Omniinetpasswd prompts for the password if not specified in the command line.
Page 347 omniinetpasswd —inst_srv_user User1@CompanyDomain Command line interface reference...
Page 349: Omniinstlic
[-sync] DESCRIPTION If the command is run without options, the licensing data in HP AutoPass is synchronized with the licensing data in Data Protector, and then the HP AutoPass utility is started. If the -sync option is used, it only synchronizes the Data Protector licenses between Data Protector and HP AutoPass, the HP AutoPass utility is not started.
Page 350 EXAMPLE To start the HP AutoPass utility, run: omniinstlic SEE ALSO omnicc(1), omnicellinfo(1), omnicheck(1M), omnidlc(1M), omnisv(1M)
Page 351: Omniintconfig.pl
omniintconfig.pl configures, updates configuration parameters, and checks the configuration of one or multiple Oracle databases (this command is available on systems with the Data Protector User Interface component installed) omniintconfig.pl SYNOPSIS omniintconfig.pl -version | -help omniintconfig.pl [-encode] [-chkconf] [-force] {-passwordfile FileName | Param=Value [Param=Value...]} Param CellManager Client...
Page 352 -help Displays the usage synopsis for the omniintconfig.pl command. -encode Encodes passwords before they are saved to Data Protector Oracle database specific configuration files. Omit this option if the provided passwords are already encoded. -chkconf Performs a configuration check for specified Oracle databases. Provided parameter values are saved to corresponding Data Protector Oracle database configuration files, regardless of whether the check succeeds or not.
Page 353 Target database service(s). If there is more than one service, separate them with a semicolon (service1;service2...). RCUser, RCPasswd Login information for the recovery catalog database (username and password). RCService Recovery catalog database service. ORACLE_HOME Oracle Server home directory. ClusterNodes Cluster nodes (applicable in cluster environments). The user OSUSER, OSGROUP will be automatically added to the Data Protector admin user group for each cluster node listed here.
Page 354 Suppose you are logged in to a UNIX client. To check the configuration of the Oracle database "IN2", run: omniintconfig.pl -chkconf CellManager=galaxy Client=star Instance=IN2 SEE ALSO omnicreatedl(1), util_cmd(1M), util_oracle8.pl(1M), util_vmware.exe(1M)
Page 355: Omnikeymigrate
omnikeymigrate helps you migrate your existing keystore file from the Data Protector A.06.00 client system and imports it into the central keystore file on the Data Protector A.06.1 1 Cell Manager (this command is available on the Data Protector Cell Manager) omnikeymigrate SYNOPSIS omnikeymigrate -version | -help...
Page 356 Migrates only the specified keystore file. Note that after using this option, you need to run the omnikeytool -activate EntityName -keyid KeyID StoreID command to activate the encryption key from Data Protector A.06.00. -datalist ClientName Migrates all encoded backup specifications from the specified client system and enables the AES encryption.
Page 357: Omnikeytool
omnikeytool manages keys used for encryption (this command is available on the Data Protector Cell Manager) omnikeytool SYNOPSIS omnikeytool -version | -help omnikeytool -create EntityName [-description Description] omnikeytool -activate EntityName -keyid KeyID StoreID omnikeytool -deactivate EntityName omnikeytool -export CSVFile ExportOptions omnikeytool -import CSVFile omnikeytool -modify -keyid KeyID StoreID -description Descrip- tion...
Page 358 -create EntityName [-description Description] Creates a new encryption key for the specified EntityName. EntityName is a ClientName for the specified filesystem, rawdisk, or the IDB, an AppType:DatabaseID or AppType:ClientName:AppName for the specified application integration, and a MediumID if you use drive-based encryption.
Page 359 If the -active option is specified, the command just lists currently active keys and the entity names associated with them. If the -unused option is specified, the command lists all encryption keys which are present in the keystore file on the Cell Manager, but have never been used for encryption.
Page 360 To export the active encryption key "10B53673B8232747A806000001000000 5B9381955B 9381955B9381955B938321" to a comma-separated values (CSV) file "a.csv", run: omnikeytool -export a.csv -keyid 10B53673B8232747A806000001000000 5B9381955B 9381955B9381955B938321 To list all encryption keys which are present in the keystore file on the Cell Manager, but have never been used for encryption, run: omnikeytool -list -unused SEE ALSO omnib(1), omnikeymigrate (1M), omniobjconsolidate(1), omniobjcopy(1),...
Page 361: Omnimigrate.pl
Cell Manager from a PA-RISC architecture based HP-UX 1 1.x system to an HP-UX 1 1.23 system for the Intel Itanium 2 (IA-64) architecture (this command is available on the Data Protector Cell Manager) omnimigrate.pl...
Page 362 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. 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.
Page 363 Error parsing options. NOTES The omnimigrate.pl command is available on HP-UX systems only. EXAMPLES 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...
Page 365: Omniofflr
omniofflr enables restore of any type of Data Protector backup object in the absence of a working Data Protector internal database (IDB) (this command is available on systems with the Data Protector User Interface component installed) omniofflr SYNOPSIS omniofflr -version | -help omniofflr DeviceOptions MediaOptions1 [MediaOptions2 ...] Object- Options1 [ObjectOptions2 ...] [GeneralOptions] DeviceOptions...
Page 366 -verbose -preview -report -target TargetHostName -[no]ok[mediumlist] DESCRIPTION The omniofflr command can be used as a standalone utility or - on Windows systems - by a higher level utility omnidr, which automatically generates restore object command line options for the omniofflr command, based on the SRD file information.
Page 367 11 (RSM exchanger) -type LogicalDeviceType Specifies the media type for the media in the device specified by the -device option. Media type numbers are defined in the HP Data Protector product announcements, software notes, and references. -description DeviceDescription This is an optional parameter that specifies the logical device description.
Page 368 -position segment1:offset1 Specifies the segment and offset position of the restore object data on the medium; for example 67:20. If the position is not specified, the position 1:0 is assumed, thus prolonging the restore time. Note that the sequence has to match the sequence in the list created using the -maid option.
Page 369 By default, or if the -overwrite option is specified, the already existent files on the disk are overwritten by the restored files. -no_overwrite If the -no_overwrite option is specified, only the files that do not exist on the disk are restored. -move_busy This option is used with the -omit_deleted_files or -overwrite option.
Page 370 Specifies the starting root directory of data restore. Note that this starting directory is also restored. TreeOptions -exclude TreeName Specifies trees excluded from the restore. -as NewTreeName This is an optional parameter that restores the selected fileset as the specified tree.
Page 371 The following example illustrates how the omniofflr command works. To restore the "c:/temp" directory of the computer "computer.company.com" without the "c:/temp/vnc" directory, which was backed up using an HP Ultrium standalone device on a STK Ultrium drive medium, attached to the Cell Manager "cm.company.com", into the "c:/test/temp directory",run:...
Page 373: Omniresolve
omniresolve resolves a filesystem object or a list of filesystem objects and writes the results to the standard output or to a Unicode file (this command is available on systems with any Data Protector integration component installed) omniresolve SYNOPSIS omniresolve -version | -help omniresolve {-files filename [filename2 ...] | -inputfile datafile} [-verbose] [-unicodefile outfile] DESCRIPTION...
Page 374 Note that on Windows systems, if datafile is in the Unicode format, the output is by default written to the file uniout.dat. You can redirect the output to a different file by using the -unicode option. -verbose Provides a more detailed report (displaying details such as WWNs, LUNs, or LDEVs) using SCSI inquiry on physical disks.
Page 375: Omnirsh
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 (this command is available on the Data Protector Cell Manager) omnirsh SYNOPSIS omnirsh -version | -help omnirsh cluster_hostname {INFO_CLUS | INFO}...
Page 376 Manager in the directory Data_Protector_program_data\Config\Server\cell (Windows Server 2008), Data_Protector_home\Config\Server\cell (other Windows systems), or /etc/opt/omni/server/cell (UNIX systems). SEE ALSO omniclus(1M)
Page 377: Omnisetup.sh
= Sybase Integration ssea = HP StorageWorks XP Agent snapa = HP StorageWorks VA Agent informix = Informix Integration ov = HP Network Node Manager Integration lotus = Lotus Integration db2 = DB2 Integration smisa = HP StorageWorks EVA SMI-S Agent...
Page 378 HP AutoPass utility (unless the -autopass option is specified — if it is, the HP AutoPass utility is installed or upgraded without issuing a prompt). If AutoPass is already installed on the system, it is automatically...
Page 379 HP AutoPass utility is neither unregistered nor uninstalled. It must be uninstalled using UNIX utilities, for example sd. If the HP AutoPass utility is installed in a cluster environment, it must be installed on every node in the cluster.
Page 380 Data Protector cell is upgraded. -autopass If this option is specified, the HP AutoPass utility is automatically installed. If AutoPass is already installed on the system, it is automatically upgraded. This option is to be used only on the Cell Manager.
Page 381 omnisetup.sh -CM -IS -autopass SEE ALSO ob2install(1M), omnigui(5), omniintro(9), omnimigrate.pl(1M), omniusers(1), upgrade_cm_from_evaa(1M), winomnimigrate.pl(1M) Command line interface reference...
Page 383: Omnisrdupdate
omnisrdupdate updates the System Recovery Data (SRD) file (this command is available on systems with the Data Protector User Interface component installed) omnisrdupdate SYNOPSIS omnisrdupdate -version | -help omnisrdupdate [-session sessionID] [-cell name] [-host ClientName] [ -location path1 [-location path2 ...]] [-asr] DESCRIPTION The omnisrdupdate command is used to update System Recovery Data (SRD).
Page 384 Specifies the session ID of the backup session with the backup object information which an existing SRD file will be updated with. This option must be specified when omnisrdupdate is run interactively, and must be omitted when omnisrdupdate is run from a post-exec script. In the latter case, Data Protector automatically obtains the required information from the current environment.
Page 385 If specified, the ASR archive file (a collection of files required for proper reconfiguration of the replacement disk packed in a single archive file) is downloaded from the Cell Manager and ASR files are extracted and stored to all destinations, specified by the -location option. At least one -location option must be specified otherwise the -asr option is ignored.
Page 387: Omnistoreapputil
omnistoreapputil acts as a user interface to Storage Appliances, such as VLS (this command is available on the Data Protector Cell Manager) omnistoreapputil SYNOPSIS omnistoreapputil -version | -help omnistoreapputil [-check_connection] -hostname HostName -port PortNumber -user UserName -password Password -certificate_name CertificateName -check_vls omnistoreapputil [-download_certificate] -hostname HostName -port PortNumber -user UserName -password Password -certificate_name CertificateName...
Page 388 -password Password Sets the password for the above specified username. -check_vls Specifies that the connection to the VLS Device needs to be checked. -client ClientHostNameorIPAddress Specifies the name or the IP address of the client imported into the Data Protector cell.
Page 389: Omnisv
Data Protector daemons (HP-UX, Solaris, or Linux systems) or services (Windows systems) (this command is available on the Data Protector Cell Manager) omnisv SYNOPSIS omnisv -version | -help omnisv {-start | -stop | -status | -start_mon}...
Page 390 On Windows systems, only the users in the Data Protector admin group can execute this command. On HP-UX and Solaris systems, only the root user can execute this command. It is not possible to start or stop services on a cluster using this command.
Page 391: Omnitrig
omnitrig triggers Data Protector scheduled backups (this command is available on the Data Protector Cell Manager) omnitrig 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...
Page 392 Start checks for the following Data Protector notifications: IDB Space Low, IDB Tablespace Space Low, Not Enough Free Media, Health Check Failed, User Check Failed, Unexpected Events, License Warning, License Will Expire, and IDB Purge Needed. 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.
Page 393: Sanconf
The sanconf command can be run on the Data Protector Cell Manager or on Data Protector clients. It resides in the Data_Protector_home\bin directory on Windows and in the /opt/omni/lbin directory on HP-UX and Solaris clients. You can perform the following tasks using the sanconf command: •...
Page 394 Remove drives on all or the specified clients from a library. All sanconf sessions are logged to the file Data_Protector_program_data\log\sanconf.log (Windows Vista, Windows Server 2008), Data_Protector_home\log\sanconf.log (other Windows systems), or /var/opt/omni/log/sanconf.log (HP-UX or Solaris systems). OPTIONS -version Displays the version of the sanconf command.
Page 395 For multipath devices, the path order is determined by the order in the given list or file. [-mom]-configure [ListFileName] This option scans, lists, configures, or reconfigures the specified library. Only one library can be configured with each invocation of the command line. If the ListFileName option is not specified, the sanconf command will dynamically scan, list, and configure the library.
Page 396 case that the RoboticControlHostName and the Hosts have the specified library installed. In case that you try to configure a library with a robotic control host on a client which does not have a library installed, the configuration will not be successful (parameter –hosts is used).
Page 397 3480 RDSK REGFILE 9840 TAPE 3590 SDLT 9940 SAIT 3592 When drives in the library are not of the same type as specified, an error is reported. -drive_template DriveTemplateFileName This option alters the default configuration of each tape device added to the library.
Page 398 This parameter corresponds to the Rescan option in the Data Protector GUI. SANSTABLEADDRESSING This parameter corresponds to the Automatically discover changed SCSI address option in the Data Protector GUI. -library_template LibraryTemplateFileName This option alters the default configuration of the library. You can alter the default configuration of the library only at the initial configuration.
Page 399 -no_multipath and -multipath options. Note: No rescanning is required for this operation. NOTES The sanconf command is available on Windows, HP-UX, Solaris, and Linux systems only. All drives created with the sanconf command are named automatically. Drive names must not be changed manually because the reconfiguration will not work.
Page 400 EXAMPLES The following examples illustrate how the sanconf command works. To scan host(s) for robotic control(s) and tape device(s) and create a file that will be used by sanconf -configure, run: sanconf -list device.list This will display the serial number for any library discovered in the SUMMARY REPORT.
Page 401 To configure a tape library with the default tape device and library settings using the "device.list" file created by the example above, run: sanconf -configure device.list -library MPC0220423 myLib1 To configure a library with a specific drive type, run: sanconf -configure -library MPC0100013 SAN_STORE host33 ".9840"...
Page 402 sanconf -configure -library US9LS01033 mylib2 -hosts myhost This will scan and configure only the new host. In a MoM environment, to reconfigure an already configured library on "host02" after adding a new host "myhost" to a Data Protector cell, run: sanconf -mom -configure -library US9LS01033 mylib2 host02 -hosts myhost This will add drives from the host "myhost"...
Page 403 controls the robotics of SCSI compliant autochangers (this command is available on systems with the Data Protector General Media Agent or NDMP Media Agent component installed) SYNOPSIS uma -version | -help uma [-policy LogicalDevicePolicy] -ioctl deviceFile [-interface {0 | 1}] [-tty] [-barcode] [ -device deviceFile_1 [deviceFile_n] -type DeviceType ] [-ddt NDMP_server_name NDMP_port_number backup_type username password] [-vls_address VLSAddress] [-vls_port VLSPort] [-vls_username VLSUsername] [-vls_password VLSPassword]...
Page 404 Data Protector NLS message catalog. On HP-UX and Solaris systems, uma is located in /opt/omni/lbin/ directory, and the Data Protector NLS message catalog is located in the /opt/omni/lib/nls/C/ directory.
Page 405 -type DeviceType Specifies the media type for the media in the device specified by the -device option. Media type numbers are defined in the HP Data Protector product announcements, software notes, and references. The media type number for VLS is 0.
Page 406 Sets the username for the specified user, who has sufficient privileges to read attributes and trigger operations on the VLS. -vls_password VLSPassword Sets the password for the specified user. Uma command line interface commands: help Displays the usage synopsis for the uma command. Performs a SCSI Inquiry operation on the device file/SCSI address specified with the -ioctl option.
Page 407 Read the device's sense data and dump them in a hex- dump format. pos slot Positions the autochanger transport mechanism in front of the specified slot. This operation is only meaningful if the specified slot refers to an import/export, data drive or repository element.
Page 408 (except for backup devices with library robotics connected to an NDMP Server) is the pathname of the device file which controls the robotics of the target autochthons: AMA -octal /Dave/spot/sctl0 *** PROGRAM: UMA VERSION: HP Data Protector A.06.11...
Page 409 *** Copyright (C) 1999 Hewlett-Packard Company *** License is restricted for use with licensed *** HP Data Protector products. /dev/spt/sctl0> exit To start uma for a backup device with the library robotics connected to the NDMP Server with the robotics SCSI address "mc2", the NDMP Server hostname "ndmpserver", the port number used by Data Protector to connect to the NDMP...
Page 410 SEE ALSO omniamo(1), omnidownload(1), omnimcopy(1), omniminit(1), omnimlist(1), omnimm(1), omnimnt(1), omnimver(1), omniupload(1), sanconf(1M)
Page 411: Upgrade_Cm_From_Evaa
EVADB entries created by the HP StorageWorks EVA Agent (legacy) to the SMISDB entries created by the HP StorageWorks EVA SMI-S Agent (this command is available on the Data Protector Cell Manager) upgrade_cm_from_evaa SYNOPSIS upgrade_cm_from_evaa -version | -help...
Page 412 To preview what happens when the upgrade from the EVA Agent (legacy) to the EVA SMI-S Agent is run on the Cell Manager, run: upgrade_cm_from_evaa -preview This command displays a list of actions that will be taken when the upgrade is run but it does not update the EVADB entries.
Page 413: Util_Cmd
util_cmd sets, retrieves, or lists the parameters stored in the Data Protector Oracle, SAP R/3, SAP DB/MaxDB, Informix, Sybase, and VMware Virtual Infrastructure configuration files. In addition, it encodes passwords. (this command is available on systems with any Data Protector component installed) util_cmd SYNOPSIS util_cmd -version | -help...
Page 414 The parameters stored in the target database configuration file are: — Oracle home directory — encoded connection strings to the target database, recovery catalog, and standby database — variables, which are exported when you start a session using the Data Protector GUI or CLI OB2_RMAN_COMMAND_TIMEOUT (environmental variable) This variable is applicable when Data Protector tries to connect to a target...
Page 415 ORA_NLS_CHARACTERSET After upgrading a Data Protector A.05.50 SAP R/3 client to Data Protector A.06.1 1, set this variable to the encoding used by the Oracle database. OB2_MIRROR_COMP This variable is applicable for ZDB sessions that use the SPLITINT functionality (-t {online_mirror | offline_mirror}). Set this variable to 1 if you want BRBACKUP to be started on the backup system and not on the application system.
Page 416 • name of the Sybase SYBASE_OCS directory (Sybase 12.x only) • environment variables VMWARE VIRTUAL INFRASTRUCTURE For each configured VMware datacenter, Data Protector creates the following configuration files: • Global configuration file Name: VMwareManagementClient%_OB2_GLOBAL Example: vcvirtual.company.com%_OB2_GLOBAL • Virtual machines configuration file Name: VMwareManagementClient%DatacenterPath Example: vcvirtual.company.com%%2FMyFolder1%2FDatacenter1 As seen in the example, the datacenter path (/MyFolder1/Datacenter1) is...
Page 417 The Data Protector configuration parameters for an integration are normally written to the Data Protector configuration files: • during the configuration of the integration • during the creation of a backup specification if the configuration parameters are changed • when the configuration parameters are changed All sublist configuration parameters in the configuration files are optional.
Page 418 Retrieves the parameter (specified by the option_name) and its value from one of Data Protector configuration files and writes it to the standard output, unless the -local option is specified. -putopt[ion] [integration instance] option_name [option_value] Sets the specified parameter (specified by the option_name) and (optionally) its value to the Data Protector configuration files, unless the -local option is used.
Page 419 util_cmd -putopt SAP ICE BR_TRACE "'10'" -sublist Environment To list the Data Protector configuration file parameters for the Oracle instance "ICE", run: util_cmd -getconf Oracle8 ICE To list the parameters from the VMware Virtual Infrastructure configuration file vcvirtual.company.com%_OB2_GLOBAL, run: util_cmd -getconf vmware _OB2_GLOBAL To list the parameters from the VMware Virtual Infrastructure configuration file vcvirtual.company.com%%2FMyFolder1%2FDatacenter1, run: util_cmd -getconf vmware /MyFolder1/Datacenter1...
Page 421: Util_Oracle8.Pl
util_oracle8.pl configures an Oracle database and prepares the environment for backup, and checks the configuration of an Oracle database (this command is available on systems with the Data Protector Oracle Integration component installed) util_oracle8.pl SYNOPSIS util_oracle8.pl -version | -help util_oracle8.pl -chkconf -dbname DB_NAME [-client CLIENT_NAME] util_oracle8.pl -chkconf_smb -dbname DB_NAME [-bkphost BACKUP_SYSTEM] [-clientCLIENT_NAME] util_oracle8.pl -chkconf_ir -dbname DB_NAME [-clientCLIENT_NAME]...
Page 422 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.
Page 423 Checks the configuration of an Oracle database. -chkconf_smb Checks if an Oracle database is properly configured for ZDB. -chkconf_ir Checks if an Oracle configuration is suitable for instant recovery. -bkphost BACKUP_SYSTEM Name of the backup system. -prmuser PRIMARY_USERNAME Username for login to the target or primary database. Note that the user must have been granted the SYSDBA privilege.
Page 424 PFILE (and not SPFILE). NOTES • On HP OpenVMS, to invoke the Data Protector CLI, run: $@OMNI$ROOT: [BIN] OMNI$CLI_SETUP.COM • BACKUP_CONTROL_FILE_COPY_LOCATION: This parameter is optional and if not specified, ob2rman.pl will copy the copy of the control file from the application system to the backup system when it is needed.
Page 425 • backup system name: bcksys The following example illustrates the configuration on HP-UX or Solaris of an Oracle database and its recovery catalog in an Oracle Data Guard environment and using the Oracle backup set ZDB method. The location of the parameter file is also specified: /opt/omni/lbin/util_oracle8.pl -config -dbname oracl...
Page 426 The following example illustrates the configuration on HP-UX or Solaris of an Oracle database and its recovery catalog in an Oracle backup set ZDB environment. The location of the parameter file is also specified: /opt/omni/lbin/util_oracle8.pl -config -dbname oracl -orahome app10g/oracle10g/product/10.1.0 -prmuser system...
Page 427: Util_Vmware.exe
util_vmware.exe configures a VMware datacenter, checks the configuration of a VMware datacenter, and lists all configured VMware datacenters (this command is available on systems with the Data Protector VMware Integration component installed) util_vmware.exe SYNOPSIS util_vmware.exe -version | -help util_vmware.exe -config -security 1 | -security 0 LOGIN_OPTIONS [-instance DatacenterPath -vm VMpath VM_OPTIONS [-vm VMpath VM_OPTIONS...]]...
Page 428 Displays the usage synopsis for the util_vmware.exe command. -chkconf Checks the connection to the VMware management client. The same check is performed regardless of whether or not you specify the –instance option. -app Lists all configured VMware datacenters. -config Configures a VMware datacenter. -security Specifies security type (0 –...
Page 429 Applicable for standard security. Specifies the web service entry point URI. Default: /sdk -port Applicable for standard security. Specifies the TCP port number of the Virtual Infrastructure web service server. Default: 443 (SSL–encrypted HTTP), 80 (unencrypted HTTP). By default, HTTP/S (SSL–encrypted HTTP) is used. To switch to unencrypted HTTP, configure the VMware management client to allow HTTP connections and set the Data Protector omnirc variable OB2_VMWARE_HTTP to 1.
Page 430 EXAMPLES The following environment is used to illustrate the examples: Datacenter: /Mydatacenters/Datacenter1 VirtualCenter Server virtualcenter2.company.com system: Username: Administrator Password: vmfdjkljy8767 Backup proxy: proxy2.company.com Virtual machines: /vm/myfolder/myvm1, /vm/myfolder/myvm2 To specify Standard security for connection to the VirtualCenter Server system, log in to the VirtualCenter Server system and run: util_vmware.exe –config –security 0 —username Administrator —password vmfdjkljy8767 To configure the virtual machine /vm/myfolder/myvm1 to use the Single...
Page 431 SEE ALSO omnicreatedl(1), omniintconfig.pl(1M), util_cmd(1M), util_oracle8.pl(1M) Command line interface reference...
Page 433: Winomnimigrate.pl
Manager and install Data Protector A.06.1 1 Cell Manager. Finally, run the winomnimigrate.pl command again on the new Cell Manager. For a detailed procedure, see the HP Data Protector installation and licensing guide. On Windows systems, you must use the perl command to run winomnimigrate.pl.
Page 434 This option should be used only on the old Cell Manager. -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. -keep_dcdirs If this option is specified, winomnimigrate.pl preserves references to additional DCBF directories in the migrated IDB, even if these additional DCBF directories do not exist on the new Cell Manager system.
Page 435 ERRORS A generic error occurred. Migration of IDB catalogs failed. Configuration error (Cell Manager configuration error or an error during the import of clients) occurred. Error parsing options. NOTES The winomnimigrate.pl command is available on Windows systems only. EXAMPLES Run the following command on the old Cell Manager to add the new Cell Manager with the client name "computer.company.com"...
Page 437 Section 5: Miscellaneous Command line interface reference...
Page 438 Section 5: Miscellaneous...
Page 439: Omnigui
Cell Manager on any other system on which the Data Protector GUI has been installed. For details, see the omniusers reference page. For details on supported operating system versions or releases for the user interface, see the HP Data Protector product announcements, software notes, and references.
Page 440 On UNIX systems, the xomni and xomnimom commands will directly start the Data Protector Java GUI. For more information on local language support and the usage of non-ASCII characters in file names, see the online Help. COMMANDS WINDOWS COMMANDS: manager Starts the Data Protector GUI with all Data Protector contexts activated, or, when additional options are specified, starts only the specified Data Protector contexts.
Page 441 Starts the Data Protector Java GUI with the Clients, Users, Reporting, and Internal Database contexts activated. xomnibackup Starts the Data Protector Java GUI with the Backup context activated. xomnicellmon Starts the Data Protector Java GUI with the MoM cell monitoring context activated. xomnicopy Starts the Data Protector Java GUI with the Object Operations context activated.
Page 442 -instrec Starts the Data Protector GUI with the Instant Recovery context activated. -monitor Starts the Data Protector GUI with the Monitor context activated. -report Starts the Data Protector GUI with the Reporting context activated. -restore Starts the Data Protector GUI with the Restore context activated. -users Starts the Data Protector GUI with the Users context activated.

HP Data Protector A.06.11 Command Line Interface Manual

Publication History

About this Guide

1 I Section 9: Introduction

2 Section 1: User Commands

3 Section 1M: Administrative Commands

4 Section 5: Miscellaneous

Quick Links

Related Manuals for HP Data Protector A.06.11

Summary of Contents for HP Data Protector A.06.11

Table of Contents