HP Data Protector A.06.11 User Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. Data Protector A.06.11
  6. User manual
HP Data Protector A.06.11 User Manual

HP Data Protector A.06.11 User Manual

Media operations
Hide thumbs Also See for Data Protector A.06.11:
Table of Contents

Advertisement

Quick Links

Download this manual
HP Data Protector Media Operations
A.06.11
User guide
B6960-90170
Part number: B6960–90170
First edition: September 2009

Advertisement

Table of Contents
loading

Related Manuals for HP Data Protector A.06.11

Summary of Contents for HP Data Protector A.06.11

  • Page 1 HP Data Protector Media Operations A.06.11 User guide B6960-90170 Part number: B6960–90170 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

    Intended audience ..................... 13 Related documentation ..................13 Document conventions and symbols ..............14 General Information ................... 15 HP technical support ..................15 Subscription service ................... 15 HP websites ...................... 16 Documentation feedback ..................16 1 Media Operations overview ..........17 In this chapter ....................
  • Page 4 Upgrading Media Operations Server and Manager to A.06.11 ....... 36 Upgrading Media Operations XML Gateway to A.06.11 ......... 37 Upgrading on Windows ................ 37 Upgrading on HP-UX ................37 Upgrading on Solaris: ................38 Upgrading on Linux ................38 Licensing Media Operations ................38 Viewing licenses ..................
  • Page 5 Editing a backup manager ..............75 Deleting backup manager objects ............78 Media Operations database backup ............. 79 Tuning backup objects ..................80 Refining physical locations ................80 Refining media compressions ................ 80 Adding and modifying media types .............. 81 Defining media policies ..................
  • Page 6 Multiple sites .................... 107 Scratch media jobs ..................107 Listing scratch jobs ..................108 Confirming scratch bin jobs ................ 109 Containers ..................110 Multiple users ..................111 Multiple sites ..................111 Initializing scratch media ................111 Media order jobs ..................113 Checkout requests (CORs) ................
  • Page 7 Premount metrics ................136 Vaulting metrics .................. 137 Scratch metrics ................... 137 Remote metrics ................... 137 Vendor metrics ................... 137 Vault metrics ..................137 Location metrics ................. 137 Location audits ....................137 View ....................... 140 Query ....................140 Print ....................141 Reset audit flags .................
  • Page 8 Threading ....................159 Polling ..................... 160 Logs ......................160 Log levels ..................161 Kernel tuning for XML Gateway on HP-UX ............ 161 Data management communications ..............161 Service logs ..................... 162 Changing the logging level ..............162 Log file locations ................163 Changing communications port numbers .............
  • Page 9 Figures Media lifecycle ................19 Components ................... 20 Media Operations GUI ..............22 Indexes ..................30 AutoPass license key ................ 39 AutoPass report licenses ..............40 Creating default vaulting policy ............44 Vaulting cycle ................. 45 Vaulting cycle action ................ 45 Vendor account definition - Media Operations vendor ......
  • Page 10 Setting scheduling options ..............73 XML Gateway ................. 74 Backup managers ................75 Backup manager - info ..............76 Backup manager - sites ..............77 Backup manager - polling ..............78 Server parameters - info ..............89 Job status indicators ................. 97 Scratch media movement ..............
  • Page 11 SLA threshold configuration ............126 Alert history - global ..............129 Backup media - history ..............130 Server parameters - notifications ............131 Notifications ................. 133 Alert notification - add/edit ............133 Media location summary (daily average) .......... 135 Open job summary ................ 136 Media location audit ..............
  • Page 12 Tables Document conventions ..............14 Platform support ................24 Supported languages ............... 26 Supported languages—intersite transfers ..........27 Application matrix ................. 165...

  • Page 13: About This Guide

    PDF format. The PDF files are installed during the Media Operations setup procedure on Windows. Once installed, the manuals reside in the Media_Operations_home\ docs directory on Windows. You can also 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 14: Document Conventions And Symbols

    HP Data Protector Media Operations product announcements, software notes, • and references—containing a list of resolved issues, late breaking news and other information Document conventions and symbols Table 1 Document conventions Convention Element Blue text: Table 1 on page 14...

  • Page 15: 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 16: Hp Websites

    For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/support/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. About this guide...

  • Page 17: Media Operations Overview

    • Integration with Backup Applications Media Operations integrates with leading backup applications, including HP Data Protector and Symantec NetBackup. • Cost-efficiency...

  • Page 18: Media Lifecycle

    Media Operations eliminates the cost of supporting homegrown tools for less than 3% of your total media bill. • Automated Operation Media Operations enforces data retention and media recycling policies. Through it, you can control removable backup devices for tape loads and ejects. Additionally, it automates data exchange with backup applications, offsite vaulting services, and removable media suppliers.

  • Page 19: Components

    • XML Gateway—providing integration between Media Operations and Backup Managers. For details of versions of HP Data Protector and Symantec NetBackup supported by Media Operations A.06.11, see User guide...

  • Page 20: Integration With Backup Manager

    Backup Managers not currently supported by XML Gateway. • Backup Manager—such as HP Data Protector, controlling backup functions. Media Operations interacts with Backup Managers to track and provide medium use. After installing Media Operations on Media Operations Server, you can track media from a variety of Backup Managers.

  • Page 21: Logging On To Media Operations

    Logging on to Media Operations Connecting to a server To launch the Media Operations Manager, double-click the Media Operations Manager icon that is now on your desktop. The 4D Server Connection window appears, containing the following tabs: Recent Tab • Lists all Media Operations Servers used recently.

  • Page 22: Using Media Operations Graphical User Interface

    Once this tab assigns a server, click OK to connect to the server. The server is then listed under the Recent tab. Using Media Operations graphical user interface Media Operations provides GUIs available from the client system (Windows client) and from the internet (web client). Windows client Windows GUI allows you to administer the complete media lifecycle environment from a single system.

  • Page 23: Web Client

    NOTE: If you are running Media Operations in “demo” mode and you have media configured, an alert tells you how many days are left before the product switches to “expired” mode (see “Licensing Media Operations” on page 38). Web client The web-based GUI provides operator functions only.

  • Page 24: Environmental Requirements

    Windows XP Media Operations Internet Explorer v5.x and above x86, x86_64, Itanium Web Client Mozilla Firefox 2.0 and above Netscape Navigator v7.0 and above XML Gateway PA-RISC HP/UX v11.11 , v11.23 and v11.31 Itanium HP/UX v11.23 and v11.31 Media Operations overview...

  • Page 25: Barcode Scanner Support

    32-bit Windows operating systems. Includes support for Windows 2003 R2. HP-UX 11.11 is HP-UX 11i version 1.0, HP-UX 11.23 is HP-UX 11i version 2.0, HP-UX 11.31 is HP-UX 11i version 3.0. Includes support for Windows Server 2003 R2, Windows Storage Server 2003 R2 and Windows Unified Data Storage Server where applicable.

  • Page 26: Barcode Printer Support

    Manager. Media Operations Server supports the following tape libraries for use with the barcode labels it prints: • HP SureStore 2/20, 4/40, 6/60, 10/100, 6/140, 10/180, and 20/700 lib- raries • HP StorageWorks SSL, MSL, and ESL libraries “Defining barcode labeling policies”...

  • Page 27: Supported Languages-Intersite Transfers

    Client Locale Server Locale Western/US Western/US The following matrix applies to intersite transfers between two Media Operations Servers where one server acts as an offsite location to the other server Table 4 Supported languages—intersite transfers Client Locale Server Locale Shift JIS (Japanese) Shift JIS (Japanese) EUC-KR (Korean) EUC-KR (Korean)
  • Page 28 Media Operations overview...

  • Page 29: Installing And Licensing

    2 Installing and licensing Installing Media Operations This chapter tells you how to install the following Media Operations components manually from the installation DVD or CD: • Media Operations Server • XML Gateway • Media Operations Manager (optional) Prerequisites • Minimum requirements for the Media Operations Server: 500 MHz Pentium III CPU (or above), 256 MB RAM, and 500 MB free disk capacity.

  • Page 30: Installing Media Operations Server

    Media Operations installation using that character set. This means Japanese clients must link to Japanese servers, Korean to Korean, and so on. See the HP Data Protector Media Operations product announcements, software notes, and references for more information.

  • Page 31: Installing Xml Gateway

    Operations Server. Installing XML Gateway There are standalone installation packages that support installing XML Gateway on Microsoft Windows, HP-UX, Linux, and Solaris. Media Operations A.06.11 XML Gateway integrates with the following supported Backup Managers: • HP Data Protector A.06.11, A.06.10, and A.06.00 •...

  • Page 32: Installing Xml Gateway On Windows

    Installing XML Gateway on Windows NOTE: If you are installing the XML Gateway after installing a Media Operations server, to avoid having to restart, stop the DMComms in between the installations. To install XML Gateway: Insert the installation DVD or CD and run setup.exe from the \xmlgw\ windows directory.
  • Page 33 Using the standard swinstall procedure, type the path, for example: swinstall -s taz:/cdrom/xmlgw/hpux/HPMedOps.depot HPMedOps Check the max_thread_proc parameter of the HP-UX kernel is set to at least 512 (the maximum number of threads allowed per process). For more details, “Kernel tuning”...

  • Page 34: Stopping Gateway Services On Unix

    Stopping Gateway Services on UNIX To stop Gateway Services on UNIX, run the following commands: /opt/hpdmcomms/sbin/stop_hpdmcomms nl /opt/hpdpxmlgw/sbin/ stop_hpdpxmlgw Uninstalling XML Gateway To remove the XML Gateway: HP-UX: type swremove HPMedOps. Solaris: type pkgrm HPdpxmlgw. Linux: type rpm -e HPMedOps. Installing and licensing...

  • Page 35: Installing Media Operations Manager (Optional)

    Media Operations 6.10 to Media Operations 6.11 Before upgrading an existing product version to Media Operations release A.06.11, consider the following: Refer to the HP Data Protector Media Operations product announcements, software • notes, and references for information about supported and discontinued platforms and versions.

  • Page 36: Upgrading Media Operations Server And Manager To A.06.11

    • After the upgrade, the Media Operations Server and all XML Gateways must have Media Operations version A.06.11 installed. • If you have a permanent license for Media Operations A.05.50, A.06.00, or A.06.10, you can use it with Media Operations A.06.11. For details about licensing, see “Licensing Media Operations”...

  • Page 37: Upgrading Media Operations Xml Gateway To A.06.11

    XML Gateway installation. The upgrade process stops the running XML Gateway on the system and copies the new files onto the existing ones. After a successful upgrade, the XML Gateway services start up. Upgrading on HP-UX NOTE: You must have root permission to perform the upgrade.

  • Page 38: Upgrading On Solaris

    Upgrading on Solaris: On Solaris, you need to remove the older version of the XML Gateway before installing a new version. NOTE: You must have root permission to perform the upgrade. Remove the older version of the XML Gateway, using the command: pkgrm HPdpxmlgw Install the new version: pkgadd –d...

  • Page 39: Autopass License Key

    The product is fully usable until the 60 days expire. After that, the product switches to “expired” mode; you cannot run any daily media movement jobs, except checkout request jobs, and the web GUI is disabled. Every time you log in, an error dialog prompts you to install the appropriate number of licenses.

  • Page 40: Viewing Licenses

    When a new license key is entered using this option, it is checked to ensure that it is different from any existing license key, and that it is a valid Media Operations license key. If the new key is unique and valid, the media license is extended by either 2000, 10,000, or unlimited media depending on the key.

  • Page 41: Configuring Media Operations

    3 Configuring Media Operations In this chapter This chapter includes information on the following: • “Site management” on page 41 • “Security management” on page 61 • “Configuring backup processes and objects” on page 63 • “Tuning backup objects” on page 80 •...
  • Page 42 You can edit vaults from the Site Configuration window provided you have per- missions to edit sites. If you delete a vault, all media in the vault are moved to the holding bin for the deleted vault site. Vaulting Policy Vaulting policies are rules defining what happens to the medium after the backup.
  • Page 43 ample, for data recovery). For more information about electronic link interfaces, “External interfaces” on page 143. Three offsite vendor types are: • Media Operations This is used when your offsite storage location is another Media Operations Server. An electronic link between the two servers automatically creates jobs on the offsite server for outgoing and returning media, and provides status information on the offsite jobs.

  • Page 44: Adding A New Site

    • When adding or editing a site definition (see “Bulk configuration file import” on page 154) Adding a new site You can add sites from Global Configuration Options -> Site Management provided you have top-level administrator permissions. If you have no sites configured, you are automatically taken to Add Site Wizard when you log in: Type a site name, site address, and primary contact.

  • Page 45: Vaulting Cycle

    Edit the vaulting cycles as instructed to ensure you have the correct destination site selected and the destination site has vaults configured. Figure 8 Vaulting cycle To edit the location type and location destination, double-click Location Type or Location Destination, or click Edit. NOTE: Clicking Next without editing vaulting cycles produces an alert message.
  • Page 46 In the Offsite Storage Vendor Definition page, specify the vendor name and type, and enter the vendor description. See “Site management” on page 41 for information about vendor types. Click Add to create accounts in the new offsite vendor. You are taken to Vendor Account Definition.

  • Page 47: Vendor Account Definition - Media Operations Vendor

    Which Vendor Account Definition window is displayed depends on the offsite vendor type you have selected: • Media Operations Vendor Enter: • Unique vendor account ID • Hostname of the system on which the offsite Media Operations system resides • Password Account ID and password must match a remote account on the offsite Media Operations Server.

  • Page 48: Vendor Account Definition-Iron Mountain Vendor

    Figure 11 Vendor account definition—Iron Mountain vendor Configuring Media Operations...

  • Page 49: Vendor Account Definition-Generic Vendor

    • Generic Vendor Enter: • Unique account ID • If the offsite vendor has the proprietary electronic link interface, specify optional configuration settings Figure 12 Vendor account definition—generic vendor When configuring offsite accounts for a Generic vendor, you can create scripts to take the information from Media Operations and convert it to the offsite vendors electronic link protocol.
  • Page 50 When you have configured your offsite vendor account, click OKto return to the Offsite Storage Vendor Definition window. Click OK to save the new offsite vendor and its accounts and return to Vaulting Cycle Action. Specify the destination offsite vendor and its account. Click OK to save the vaulting policy cycle.

  • Page 51: Onsite Vault Management-Layout

    In the Onsite Vault Management window (theInfo tab), type a vault name as well as other required information. Click the Layout tab to define the vault configuration and capacity. Figure 13 Onsite vault management—layout Adding cabinets You now need to create cabinets manually by clicking Add Cabinets or automatically by clicking Auto-Create Layout.

  • Page 52: Editing An Existing Site

    Editing an existing site When you have added a site, you can modify the physical layout of its devices and the available onsite and offsite vault locations from: • Global Configuration Options -> Site Management (top-level administrators) Global Configuration Options -> Server Parameters under the Sites tab (top- •...

  • Page 53: Dns

    The DNS tab allows you to associate the site with a set of DNS suffixes (such as *.fc.hp.com). The system objects added to the Media Operations configuration are automatically assigned to the appropriate sites based on their DNS name. Click Edit to view or edit an existing DNS suffix, or Add to create a new one.

  • Page 54: Data Centers

    Figure 16 Onsite vault management—info Under the Info tab of the Add New Onsite Vault wizard, enter the vault name, as well as other required information. Under the Layout tab, define the vault configuration and capacity. You can add cabinets manually by clicking Add Cabinets, or automatically by clicking Auto-Create Layout.

  • Page 55: Vaulting Policies

    Type a unique name for the data center and its description. Figure 17 Data center definition Data center grids define the data center physical layout and the grid walk-through order. You can assign locations to systems and devices in that data center to optimize the walk-through order of devices during premount jobs.

  • Page 56: Offsite Vendors

    Enter a name for a new vaulting policy. Select a template, and type the minimum number of protection days. Figure 18 Vaulting cycle implementation—info Click the Policy tab. Click Add to add a new or Edit to edit an existing vaulting cycle.
  • Page 57 Use Vaulting Days check boxes to define the days the vendor will accept offsite shipments. Vaulting days on this screen takes precedence over vaulting days set in vaulting policies (see “Vaulting policies” on page 55). Then, depending on the vendor type you selected, proceed as follows: Media Operations Vendor Enter: •...

  • Page 58: Vendor Account Definition-Generic Vendor

    Figure 19 Vendor account definition—generic vendor When configuring offsite accounts for a Generic vendor type, you can create scripts to take information from Media Operations and convert it to the offsite vendors electronic link protocol. • Select the Enabled check box for Outgoing/Return Media command line script if the vendor supports an interface to manage outgoing and returning media.

  • Page 59: Users

    Users The Users window defines site-level users. Top-level administrators are not listed as they have full access to every site. To edit or view an existing user, click Edit. To add a new user, click Add and perform these steps: Type the username, login name, and password for the new user.

  • Page 60: Remote Accounts

    Remote accounts The Remote Accounts window defines accounts used by other Media Operations Servers that can store the media in this site. These accounts must match the vendor account records on remote Server. To view or edit an existing account, double-click it or click Edit. To add a new remote account, click Add or Add Many.

  • Page 61: Deleting A Site

    For field values for importing different information types, and for importing examples, “Bulk configuration file import” on page 154. Deleting a site If you delete a site, you also delete vaults, offsite vendor accounts, data centers, and site-level user roles associated with that site. Any manually added backup objects created within the site are deleted as well.

  • Page 62: Product Administrators And Operators

    dows, you can view or create top-level administrators. You can also edit the initial top-level administrator defined during the installation. • The Users/Remote Accounts tabs of the Site Configuration window give you site- level access to users for the current site. You cannot view or add top-level admin- istrators from these tabs.

  • Page 63: Remote Accounts

    • reassigning systems/devices between data centers in the same site. Super operator-level administrators have read-only access to some site-level in- formation but not to site-specific configuration options. • Operator-level administrators, who can: • perform site-level daily operations, including premount jobs, vaulting jobs, scratch bin maintenance, checkout requests, exception list actions, and mount requests, •...

  • Page 64: Automatic Backup

    Backup Managers that support copy operation. NOTE: Currently, the XML Gateway supports copy operation available on HP Data Protector A.06.00, A.06.10, and A.06.11, and the Inline copy feature of Symantec NetBackup 6.0.

  • Page 65: Media Operations Deployment Options With Data Protector

    Figure 23 Media Operations deployment options with Data Protector NOTE: Communication between XML Gateway and Data Protector does not normally pass through firewalls, so XML Gateway running on the Media Operations Server or another server can only communicate with a Backup Manager within the same firewall zone.

  • Page 66: Manual Backup

    • Through the XML file import interface, allowing integration with other types of Backup Servers not supported by XML Gateway. This file-import interface uses files formatted in HTTP/XML protocol, such as: • Backup/Restore Device Information • Media Pool Information • Backup Specification Information •...

  • Page 67: Implementing The Backup Process

    Configure a backup: Create the system (if the system has not been created by a Backup Manager) using Global Objects -> Systems (top-level administrators) or the site-level Systems list (site-level administrators). Specify characteristics of the system, such as data center and grid location (in the site to which the system is assigned).

  • Page 68: Backup Managers

    65 for a representation of deployment options. XML Gateway can be installed on a variety of server platforms, such as Windows, HP-UX, Linux, or Solaris. For optimal Media Operations performance, install XML Gateway on each Backup Manager System. If this causes Backup Manager performance issues, put XML Gateway on other, preferably dedicated, servers.

  • Page 69: Server Parameters - Xml Gateways

    Monitoring XML Gateway When you add a Backup Manager, a baseline synchronization runs, during which any communications problems between XML Gateway and the Backup Manager are noted on screen and/or in the log. NOTE: Errors occurring while parsing the XML received from XML Gateway are written to alert logs.
  • Page 70 Add/Edit Backup Manager window or the XML Gateways tab on Global Parameters -> Server Parameters. NOTE: Add several XML Gateways to a group to activate load balancing and failover. Media Operations can communicate with the XML Gateway group using proxy settings defined for that group.

  • Page 71: Xml File Import Directory

    • Device Scan scanning the media contents of all devices on the Backup Server. It performs library barcode scans for every barcode-capable tape library on the Backup Server and media scans on all standalone tape drives, library slots (except cleaning slots) in non-barcode capable libraries, and slots containing “blank” or “unknown”...

  • Page 72: Adding Backup Managers

    Adding backup managers Launch Add Backup Manager Wizard from either the Add Site Wizard window or Global Configuration Options -> Backup Managers, and proceed as follows: Select the Backup Manager type. Type the network name of the Backup Manager system. If this is different from the primary network name of its host system (for example, if the host system has multiple network interfaces), select the host system primary network name from a list of current systems in Media Operations by clicking the Backup Manager...

  • Page 73: Setting Scheduling Options

    Set scheduling options by checking the appropriate boxes. Figure 25 Setting scheduling options Scheduled events keep Media Operations in sync with the Backup Manager: • Config Report collects clients on the Backup Manager, MMDB configuration, media pools, devices, and backup specifications. •...

  • Page 74: Xml Gateway

    “Manager-of-Managers configuration” on page 164 for more information. If a user is using HP Data Protector as the backup manager and it runs in a locale other than English, you must install the gateway on a system for which the default encoding is same as the backup manager system.

  • Page 75: Editing A Backup Manager

    • Add additional vaulting policies to the site and apply them to pools, backup specifications, or systems if you want a different policy from the default site-level policy. • Edit media pools and set the correct media compression. For example, an LTO pool can contain LTO1 or LTO2 media.

  • Page 76: Backup Manager - Info

    Figure 28 Backup manager - info If your Backup Manager is supported by XML Gateway, either install XML Gateway onto the tape Backup Manager system or use the XML Gateway group to communicate with the Backup Manager. NOTE: NetBackup gateway must always be present on the Master server. Click Add to add a new XML Gateway group.

  • Page 77: Backup Manager - Sites

    Sites The Sites tab shows the sites containing objects from a Backup Manager. Each Backup Manager has a home site where its media and pools are located and where its systems, devices, and backup specifications are placed by default if there is other appropriate site to locate them (if the sites have DNS suffixes defined).

  • Page 78: Deleting Backup Manager Objects

    Figure 30 Backup manager - polling To synchronize configuration information from the Backup Manager (pools, media devices, systems, and backup specifications) immediately, click Manually Synchronize. Scheduled events are used to keep Media Operations in sync with the Backup Manager: • Config Report collects the clients on the Backup Manager, MMDB configuration, media pools, devices, and backup specifications.

  • Page 79: Media Operations Database Backup

    Use the Media Operations Server console to configure and schedule backups of the server database. See the server online help for instructions. IMPORTANT: The server backup process creates a copy of the server database files. HP strongly recommended you include server backup files in your tape backup scheme. User guide...

  • Page 80: Tuning Backup Objects

    Tuning backup objects This section discusses methods of optimizing backup objects performance. Refining physical locations Configuring data centers helps you optimize premount jobs. Premount jobs are faster and more efficient if the premount walk-through is grouped in a logical order by physical location (to use the shortest/quickest path from device to device).

  • Page 81: Adding And Modifying Media Types

    To modify compressions for devices, go to Global Objects -> Backup/Restore Devices or Backup/Restore Devices at the site level. You can not modify the compression of a device if it belongs to any backup manager. Adding and modifying media types Media Operations contains a set of predefined media types and compressions for most current tape technologies., which you may add to or modify.

  • Page 82: Media Vaulting Policy Hierarchy

    Media vaulting policy hierarchy • Default Site-Wide Vaulting Policy. When creating a new site, configure a default vaulting policy for all new media pools created in that site using the Site Config- uration window. • Create onsite vaults or offsite vendor locations for use in the site-wide vaulting policy before you apply this policy.

  • Page 83: Basic Vaulting Policy Concepts

    • Vaulting Policies for Consolidation Media. For any media belonging to Backup Managers that support consolidation operations (such as Data Protector A.06.11), you can define different vaulting policies (at site, pool, backup specification, and system levels of the policy hierarchy).

  • Page 84: Active Vaulting Policies

    Medium Recovery Access, Medium Media Security: Medium is not retained in the • device. It is kept in an onsite vault for seven days and in an offsite vault until it expires. • Slow Recovery Access, High Media Security: Medium is not retained in the device nor in an onsite vault.
  • Page 85 Edit the vaulting cycles to complete their configuration: If the vaulting policy destination is an offsite vendor, choose the offsite vendor and offsite vendor accounts. If the vaulting policy destination is a vault, leave it at the default destination or specify another site on your Media Operations Server. Optionally, alter Day Number, representing the number of days before you move your policy to destination in this vaulting cycle.

  • Page 86: Defining Barcode Labeling Policies

    Selecting a Policy IMPORTANT: If multiple vaulting policies are applied at the same level (such as backupspec, or system), the recently created vaulting policy is applied to the qualified media. After adding the policy, select it from the Vaulting Policy list for the object to which the policy needs to be applied.

  • Page 87: Configuring Scratch Media Policies

    Printing barcodes If you have a supported barcode printer attached to the Media Operations Manager, you can print a range of barcodes from Barcode Policies and reprint a single barcode from Edit Media. Additionally, you can save the list of barcodes to a file (from Barcode Policy) for easy export to the third-party barcode label printing software.

  • Page 88: Tuning Scratch Media Levels

    NOTE: Media Operations does not support manually created backup specifications in premount jobs. You can either mark manual media as used or scratched through Edit Media, or use reactive mount jobs. Premount jobs manage scratch premount processes for every backup/copy/consolidation specification assigned to them. Premount processes are arranged around backup/copy/consolidation specification objects (rather than devices), because a backup/copy/consolidation job can use multiple tape libraries or standalone drives that need the appropriate scratch media loaded before the job...

  • Page 89: Reactive Mount Requests

    Reactive mount requests An ad hoc mount request is triggered by a Media Operations utility (using a command-line program). These jobs react to an unforeseen demand for backup media by loading scratch media into a specified drive. See “External interfaces” on page 143 for details.
  • Page 90 Disable check box: In this and the next three parameters, check the disable boxes to prevents jobs starting by default. Default Premount Job Start—the time when the premount job is performed (when • the contents of the days premounts is calculated). Default Scratch Job Start—the time when the scratch job is performed.

  • Page 91: Vaulting Jobs

    Vaulting jobs The vaulting job start time defines when vaulting jobs are created across all sites in the Media Operations Server. This is also the start time on which SLA measurements are based. Scratch bin maintenance The scratch bin start time defines when scratch bin and scratch initialization jobs are created across all sites in the Media Operations Server.

  • Page 92: Setting Up The Receiving Server

    Setting up the receiving server Create a new site on server A. For the vaulting policy template, select Onsite Vaulting, Medium Security. Edit the first policy cycle entry on the vaulting cycle and click the Add Vault button. Type a name for the vault. Select the Layout tab and click Auto-Create Layout.
  • Page 93 After the polling is done for the backup server, open the Server Parameters window. This should trigger communication between the two servers. The vaulting job will show up on the receiving server and should work in a similar fashion to onsite vaulting jobs.
  • Page 94 Configuring Media Operations...

  • Page 95: Performing Daily Media Operations

    4 Performing daily Media Operations Overview NOTE: To perform daily Media Operations for a particular site, you must have appropriate user rights. This chapter describes the following: • “Running jobs through the CLI” on page 95 • “Job status indicators” on page 97 •...
  • Page 96 Premount Scratch DailyMetrics Example: startjob server.india.hp.com foobar foobar Vault NOTE: The startjob utility only triggers the command to start the job. The actual starting of the job depends completely on the policy set for individual jobs on the Media Operations Server.

  • Page 97: Job Status Indicators

    Job status indicators Status indicators show the overall vaulting status (green - OK, yellow - warning, red - critical) and the status for each job category based on SLA status settings for each active job in that category. For example, if one job in a category are red while all others are green, the whole category is marked red.

  • Page 98: Viewing Premount Jobs

    Figure 33 Scratch media movement Viewing Premount Jobs: To view a list of active premount jobs, double-click Premount Jobs on the Daily Operations menu on the shortcut bar. Double-click a job or click Edit to get the premount job properties. Scratch Listing tab Displays the total number of media required from each scratch bin to complete the mount process.

  • Page 99: Silo-Type Libraries

    Confirmation tab Assigns scratch media to the specified device in the grid ordering for the data center. The process also confirms that the media entered are scratch and of good quality. To verify the medium, either barcode scan or type a medium description, and click Verify.

  • Page 100: Free/Scratch Pool Handling

    When performing load/eject operations for silo-type libraries (such as ACSLS or DAS), consider the following: • When you click Run Mount Cycle for the first time , silo libraries eject all media listed on Premount Job - Dismount Listing during this first cycle (on non-silo librar- ies, it only ejects one CAP’s worth of media).

  • Page 101: Vaulting Jobs

    Vaulting jobs NOTE: Media Operations does not support daily vaulting jobs on file devices, RISS device, Virtual Tape Library (VTL) and file libraries. Vaulting jobs consist of: • Listing the job • Confirming it Figure 35 Vaulting jobs media movement Listing vaulting jobs Vaulting jobs listings display live/protected media you need to vault or transport to a new location.

  • Page 102: Confirming Vaulting Jobs

    To view a list of active vaulting jobs, double-click Vaulting Jobs on the site Daily Operations menu. Figure 36 Vaulting job listing In this window, you can click: • Add COR to create checkout requests for removing media for restore, DRP sessions, special projects, and so on.

  • Page 103: Media Vaulting Confirmation

    Figure 37 Media vaulting confirmation To confirm a job: Retrieve the required media from their current locations. Media locations are displayed on the Pending Media list. • If media come from multiple source locations, you can view them on a source- by-source basis by clicking View Sources.

  • Page 104: Library Unload Tab

    Verify the requested media were found. After the media are retrieved from their current locations, you can either: • Barcode scan each medium by typing the number and clicking Verify Piece, • Select the medium in the Pending Media list and click >>. If the medium is prematurely verified, select it in the Verified Media list and click <<...

  • Page 105: Verifying Media

    Figure 38 Media vaulting confirmation - library unload Select one or more library devices and click Unload to eject media to be vaulted into the library CAP/mail slot (multiple cycles may be required depending on the CAP size). Verifying media After the media are ejected, you can verify the ejected media under Required and Optional tabs.

  • Page 106: Multiple Users

    Lockable Containers: Use if your vaulting job moves the media to an offsite vendor • and the vaulting policy specifies that media must be sent in a lockable container. Consider the following: • all media must have the same vaulting policy, •...

  • Page 107: Multiple Sites

    Multiple sites If you have multiple sites configured on your Media Operations Server, a vaulting job can appear on the job list for multiple sites (depending on your vaulting policy). The behavior for the vaulting job depends on the site type: Home Site is defined as the site that owns the media.

  • Page 108: Listing Scratch Jobs

    Figure 39 Scratch media movement Listing scratch jobs To view an active list of scratch jobs, double-click Scratch Bin Jobs on the shortcut bar under the Daily Operations menu. Figure 40 Scratch bin jobs In this window, click: • Edit to view job details and process requested media movements. •...

  • Page 109: Confirming Scratch Bin Jobs

    • Add Init to manually create a new scratch initialization job (type the number of media to initialize and select the pool). • Add Media Order to manually create a new media order job (type the number of media and media type). Appears only if Blank Bin Tracking is enabled. Confirming scratch bin jobs If you edited a scratch bin job, the following window appears: Figure 41 Scratch bin confirmation...

  • Page 110: Containers

    Retrieve the required media listed under Pending Media from their current location. Consider the following: • If the media come from multiple source locations, click View Sources to view the required media on a source-by-source basis. From here, you can print a list of required media from any source and see the status of the media movement from each source location.

  • Page 111: Multiple Users

    verified media to a container, select media in the Verified Media list and click Change Container. NOTE: Container columns on pending and verified lists identify the container to which the media belong. Multiple users Multiple operators can work on the same job confirmation at the same time. The first user opening Premount Job - Confirmation (Windows GUI) is the primary owner of the job;...

  • Page 112: Scratch Init Job Confirmation

    Figure 42 Scratch init job confirmation There are two ways to initialize media: • Initializing a standalone drive Select a standalone drive from a list of initialization devices and define the label range of media to be initialized. Click Set Label Range to reserve a barcode label range for the media, and then click Initialize.

  • Page 113: Media Order Jobs

    Select the medium you want to initialize and click Initialize Highlighted Media. Media Operations automatically initializes selected medium using the barcode label for the media label. Enable Force Initialize if a medium contains data. Max Drives Used determines how many drives inside the library can be used for initialization.

  • Page 114: Site Definition - Blank Bins

    Click the Blank Bin tab on the Site Definition window and select Enable Blank Bin Tracking. Figure 43 Site definition - blank bins Configuration This predicts the amount of media needed for upcoming scratch initialization jobs based on the criteria set when adding a new blank bin.

  • Page 115: Media Order

    In the Media Order window, the ID, start date and time of the job are displayed, together with: • Media type description, starting with the amount of required media, • Type of media being ordered, • The number of media being ordered, •...

  • Page 116: Checkout Requests (Cors)

    Checkout requests (CORs) Submitting checkout requests In the Checkout Request window: • Type either the tracking ID from the initiator (OpenView Solutions ID, Remedy ID) or NONE. • Type the name of the person who placed the request, select the priority, and type a job description.

  • Page 117: Listing Checkout Requests

    Using the Media Selection Wizard, query for media meeting the selected filters. This allows you to move a group of media into the COR quickly. Type the desired date range and select the appropriate filters (Backup Manager, Media Pool, Backup Specification, and System). After each date/filter selection, the media list is updated.

  • Page 118: Confirming Checkout Requests

    Manual Vaulting to move media into/out of scratch bins in mass. You can also • remove media from a section of the available medium locations and place them into the holding bin or vault. See “Manual vaulting jobs” on page 121 for details. •...

  • Page 119: Containers

    Containers If your scratch job is moving media to another site, you can select a transit container for transporting the media. Assign media to a transport container by typing the container ID into the Container ID field before verifying a medium. To assign or reassign verified media manually to a container, select media in the Verified Media list and click Change Container.

  • Page 120: Mount Requests

    Figure 47 Vaulting exceptions Mount requests An asynchronous mount request mounts one medium at a time using the Interactive Mount Request window. A reactive mount request is an ad hoc mount request that reacts to unforeseen demand for backup media by loading scratch media into a specified drive. The Java-based command-line utility allows you to submit reactive mount requests from any client system into the Media Operations Server.

  • Page 121: Confirming Mount Request Jobs

    • Manual Vaulting to move media into/out of scratch bins in mass. You can also remove media from a section of the available media locations and place them into the holding bin or vault. See “Manual vaulting jobs” on page 121 for details. •...

  • Page 122: Viewing Job History

    the holding bin into the vault. You can remove media from a section of the vault and place them into the holding or scratch bin. Figure 50 Manual media vaulting Select the destination site and location. Select media from Available Media and click >> to include them into this movement job.

  • Page 123: Web Interface

    Figure 51 Media vaulting - history Double-click a job or click View to view job details. Vaulting, scratch bin, checkout request, manual vaulting, and mount request details are displayed, together with a list of media that were due to be moved by that job, their origin and destination. Media marked as exceptions are shown in the status column.
  • Page 124 Performing daily Media Operations...

  • Page 125: Status And Reporting Interfaces

    5 Status and reporting interfaces Overview This chapter describes service level agreements (SLA) status and reporting options. It is organized as follows: • “Viewing current SLA status” on page 125 • “SLA status configuration” on page 126 • “Viewing alerts” on page 128 •...

  • Page 126: Sla Status Configuration

    Figure 53 Site SLA status The summary list shows how many jobs were overdue in the main job types for a selected site. To list all overdue jobs for a selected category, click a required job type. Detailed job information is displayed. SLA status configuration Use Global Configuration Options ->...
  • Page 127 status when the percentage of successful jobs over the last 30 days falls below 99%. To edit settings, click Edit or double- click the item. In the Manage System Threshold window, make changes and click OK. Vaulting tab Warning and overdue times for vaulting, scratch, and checkout request jobs.

  • Page 128: Resetting Current Sla Status

    Resetting current SLA status Media Operations 6.1 provides an option to reset the SLA status at both global and site level. Resetting the SLA resets the SLA status for all jobs and restarts the SLA calculation to start from the reset date and time. The Reset SLA Status button (as shown in “Figure 53”...

  • Page 129: Reports

    Figure 55 Alert history - global To list pending alerts for all sites, click the Current Alerts for All Sites tab in the SLA Status/Reporting window. To view/resolve an alert, double-click it and click View. To select multiple alerts and resolve them all at once, click Resolve Highlighted.

  • Page 130: Additional Reports

    to decide whether to initialize new or remove existing media), and the number of scratch media used by backups in the last 24 hours. This report is also available from the Media Operations web site. • Media Movement—shows the last 24 hours of activity for all media movements caused by vaulting policies, scratch bin maintenance, and checkout requests on a specific site.

  • Page 131: Notifications

    Two types of notification interfaces are: • E-mail • HP Operations Manager E-mail interface configuration Configure the following e-mail interface options to enable e-mail notification: • E-mail “From” Address—shown in the From field in all messages sent by the no- tification system.

  • Page 132: Operations Manager Interface Configuration

    E-mail “Reply To” Address—used if anyone replies to an e-mail sent by the noti- • fication system. • E-mail SMTP Gateways—a list of one or more SMTP Gateway Servers with their network addresses. At least one gateway is required, because it forwards e-mails from Media Operations to defined users.

  • Page 133: Configuring Notification Triggers

    Configuring notification triggers You can configure notification triggers at global or site level by double-clicking Notification under SLA Status/Reporting. At site level, you can only add or edit notification triggers specific to that site. Figure 58 Notifications Alerts Sends events logged to the alert log via e-mail or Operations Man- ager.
  • Page 134 Sends alerts via e-mail or Operations Manager when an SLA is in warning or violation. Click Add to add a new SLA, or double-click an existing notification to view/edit. Choose SLA measures for notification and select the site (select All Sites for global SLAs).

  • Page 135: Metric Report Description

    Metric report description The durations are: • Daily Detail (one day with media pool breakdown) • Daily Summary (multiple days totals only) • Weekly Detail • Weekly Summary • Monthly Detail • Monthly Summary Media location summary The Media Location Summary is the total on a daily report and the average for the number of metric days for weekly and monthly reports.

  • Page 136: Job Metrics

    Figure 61 Open job summary Job metrics Job metrics are: • Job Summary (Daily Average)—the average number of each job typed during the specified period. • Job Period Totals—the total number of each job type during the period. Pool health metrics Pool health metrics are: •...

  • Page 137: Vaulting Metrics

    Vaulting metrics Vaulting metrics are: • Protected Media Summary (Daily Average)—the average number of tapes, how many are written, and how many vaulted. • Protected Media Period Totals—the total number written and the total number vaulted. Scratch metrics Scratch metrics are: •...

  • Page 138: Media Location Audit

    NOTE: Poor quality media cannot be used. To start a location audit: Go to Utilities -> Location Audit. Figure 62 Media location audit NOTE: The bottom six buttons are only displayed for top-level administrators. Select a site and location. The following locations are available: •...

  • Page 139: Media Location Audit - Device/Vault Screen

    For Device/Vault only: The following window is displayed: Figure 63 Media location audit - device/vault screen Select one of the following: • Scan by Slot—verifies the exact location of the media using the walk- through order of the vault/data center. •...

  • Page 140: View

    View You can view the following: • Audit Pending • Audit Problems All Media • Clicking any of these buttons displays media details for selected sites. Figure 65 Media location audit - view Query Reloads the media list using the following filters: •...

  • Page 141: Print

    Example: If you want to query the media, not audited but vaulted since 10/6/03, leave Name Contains blank and select Not Audited radio button. Select the Verified on Job since: check box and type 10/6/2003. Figure 66 Filter media Print Click Print to produce an audit report describing medium characteristics, such as medium number, current location and status, time stamp, and the person who audited the medium.

  • Page 142: Export Remote Account Report

    AB1285 You can type in each number, scan them to notepad, and so on. Export/import for remote accounts/OSVs requires a special XML file, so it is currently only used for Media Operations-to-Media Operations accounts. Export remote account report This produces an XML file for a remote account managed by the Media Operations Server.

  • Page 143: A External Interfaces

    A External interfaces Overview This appendix describes the following external interfaces: • “XML file import interface” on page 143 • “XML offsite vendor interface” on page 145 • “Bulk configuration file import” on page 154 XML file import interface For Backup Managers not supported by XML Gateway, Media Operations Server supports a file-import interface that allows an external backup application to post HTTP/XML formatted files to a directory on the Media Operations Server.

  • Page 144: Usage

    When creating files, you must: • Provide scripts to convert information from your Backup Server (not supported by XML Gateway) into incoming files containing Backup Manager, pool, device, backup specification, and media information. • Ensure the files are copied into the file-import directory defined for that Backup Server.

  • Page 145: Xml Offsite Vendor Interface

    • Media pool information (MediaPool.dtd) • Backup specification data (BackupSpecs.dtd) • Media information request (MediaInfo.dtd) • Media usage within a specified time period (MediaUpdate.dtd) • Backup Manager errors (ErrorReport.dtd) • Device contents updates (RepositoryList.dtd) See the DTDs on the installation media under docs\xml for a guide to creating valid Media Operations XML.

  • Page 146: Media Transit Requests

    3 - Request audit 4 - Send audit • Parameter 2: XML parameters file Filename of the XML parameters file, delimited by quotation marks. Media Oper- ations creates this file before calling the script. Parameter 3: Results filename • Filename passed into the script by Media Operations, delimited by quotation marks.

  • Page 147: Request And Receive Audit Requests

    1 - Job/request successful 3 - Error parsing XML parameters file 5 - Bad account or password Request and receive audit requests Receive audit sends a request to an offsite vendor to verify that the list of media sent in the request matches media for your account currently in the offsite vendor’s possession.

  • Page 148: Xml Offsite Vendor File Format

    NOTE: An additional Disable Electronic Link Check is added to the Generic offsite vendor account definition. This option allows you to disable the check for an electronic link interface to an offsite vendor. XML offsite vendor file format See the following DTDs and examples on the installation media under docs\xml, for a guide to creating valid Media Operations XML: •...
  • Page 149 You must have Java (v1.2 or higher) installed on the system on which you want to run the utility. Syntax <java exe> -cp <full path to reactivemount.jar file> com.hp.ov.dm.reactivemount.DoReactiveMount <param list...> Parameters Mandatory parameters: Name of the Media Operations Server name to which to send the reactive mount request.
  • Page 150 Session ID for the mount request on the backup manager Return Codes Return codes for the utility are: Success Invalid user Invalid backup specification Invalid device Invalid Backup Manager Invalid media Media not in pool Duplicate media encountered Media is manual and still in protected state Unrecognized parameter Required parameter not found Connection failed...
  • Page 151 Media Operations Server will allow the operator to select from a list of valid scratch media. Example 1 An example of the utility being executed on Windows: java.exe -cp "C:\ProgramFiles\Hewlett-Packard\DataMgt\MediaOps\Client \reactivemount.jar" com.hp.ov.dm.reactivemount.DoReactiveMount -m server1.xyx.com -c bkpmgr1.abc.com -s backup_spec_1 -d tape_drive_1 -u mediaops_login_1 -p mediaops_login_1_password...
  • Page 152 REM This session is a backup session, so create a reactive mount request in MediaOps server % MOSERVER % %JAVA_EXEC% -cp %RCTMOUNT_JAR% com.hp.ov.dm.reactivemount .DoReactiveMount -m %MOSERVER% -c %CELLSERVER% -mp %POOLNAME% -d %DEVNAME% -u <MO Server username> -p <MO Server password>...

  • Page 153: User Guide

    UNIX: mount.sh #!/sbin/sh THIS=${0}USER=${1} # unix login of user who started the backup GROUP=${2} # unix group of user who started the backup HOSTNAME=${3} # host where the backup was started STARTPID=${4} # pid of the backup process DEVNAME=${5} # logical device that generated mount request DEVHOST=${6} # host to which the device is attached DEVFILE=${7}...

  • Page 154: Bulk Configuration File Import

    This mail has been sent by the script $THIS, run by Data Protector. " | mailx -s 'Data Protector Mount Request' $USER@$HOSTNAME $JAVACMD -cp $RCTMOUNT_JAR com.hp.ov.dm.reactivemount.DoReactiveMount -m "$MOSERVER" -c "$CELLSERVER" -u "$MOUSER" -p "$MOPWD" -d "$DEVNAME" -mp "$POOLNAME" -id "$SESSIONID"...
  • Page 155 You can import the following information types: • Data Center Grid Information Example: Site,Data Center,Grid,Order Key London #1,North,B16,25 • System Grid Locations Example: System,Site,Data Center,Grid boi1036.boi.hp.com,junk,Brad's DataCenter,A6 boi1037.boi.hp.com,junk,Brad's DataCenter,A7 boi1038.boi.hp.com,junk,Brad's DataCenter,A8 • Media Locations Example: Media,Location,Site,Vault,Slot,Vendor, AccountAB0001,Vault,Akron BLD 3,closet,, 1AB0002,Vault,Akron BLD 3,closet,, 1AB0003,Offsite,Akron BLD 3,,Vendor1,1000...
  • Page 156 container does not already exist in Media Operations, it is created automatically. The following is an example with the Container value: Media,Location,Site,Vault,Slot,Vendor,Account,Container AB0003,Offsite,Akron BLD3,,,Vendor1,10,Cont1 • Device Definitions Example: System,Device,Type,Media Type,Compressions lc1036.abc.xy.com,L0,Library,LTO-Ultrium,LTO2 slc1036.abc.xy.com,L1,Library,LTO-Ultrium,LTO2 slc1036.abc.xy.com,L2,Library,LTO-Ultrium,LTO2 • Import Manual Media (media, not associated with any Backup Manager, such as legacy media already stored in offsite or vault locations).

  • Page 157: B Diagnostics And Tuning

    • “Manager-of-Managers configuration” on page 164 Media Operations logs Media Operations logs include the following: • Media Operations Server logs located in <Install_Location>\DBServer\ log\... Example: C:\ProgramFiles\HP\DataMgt\MediaOps\DBServer\log\ log.0.txt. • Media Operations Manager logs located in <Install_Location>\Client\ log\... Example: C:\ProgramFiles\HP\DataMgt\MediaOps\Client\log\ log.0.txt. Logging level is adjustable under the Log Level tab on the Server Parameters window under Global Configuration Options.

  • Page 158: Xml Gateway Configuration, Logs, And Tuning

    XML Gateway configuration, logs, and tuning This section discusses the XML Gateways configuration, logging, and considerations for tuning the gateway. Configuration Depending on the system that hosts XML Gateway, you can adjust the settings that affect: • performance • logging for XML Gateway •...

  • Page 159: File Locations

    If the Media Operations Server has problems retrieving the reports before they are removed, due to load, adjust the cleanup. In the example configuration file above, cleanUpMin ="15" indicates the frequency (in minutes) of cleanup, and keep FilesMin ="15" specifies the minimum age of files to be removed.

  • Page 160: Polling

    the Backup Manager does not respond to the request every few minutes at least, as defined by the actionTimeoutMin, the action is considered “locked,” the Backup Manager is told to terminate the job, and an error is reported. If actions on your libraries or devices take longer than actionTimeoutMin, increase the value.

  • Page 161: Log Levels

    It causes large log files. Kernel tuning for XML Gateway on HP-UX If you installed XML Gateway on HP-UX, you may need to adjust one of the HP-UX kernel tunable parameters to ensure reliable operation of XML Gateway. Without this tuning, any requests to Backup Managers via this XML Gateway can fail with network connection errors, such as error codes -8 or -2002.

  • Page 162: Service Logs

    Changing the logging level Open the communications configuration file on the DMComms host: • Windows: <DMComms_Install_Location>\DMComms\config\bbc_config • HP-UX, Linux and Solaris: /etc/opt/hpdmcomms/config/bbc_config Change the LOG_LEVEL in the [com.hp.ov.ipcserver] section. Valid settings are: [com.hp.ov.ipcserver] SERVER_PORT = 25556 SECURE_COMM = SSL SSL_PROVIDER = JSSE SSL_CA_CERTIFICATE_FILENAME = /opt/hpdmcomms/certs/ca.jks...

  • Page 163: Log File Locations

    DMComms). The default installation location is: • Windows: C:\Program. • HP-UX, Linux and Solaris: /etc/opt/hpdmcomms/config. Edit the bbc_config file to change the port settings. There are two port numbers, one for HTTP-based RPC communications, the other for HTTP-based data transfer communications.

  • Page 164: Holiday List Configuration

    UNIX only: When changing the port numbers, reflect the change in the /etc/ services file. By default, Media Operations adds entries in this file for its communications settings: hpdmcomms 25555 # HP DMComms port number hpdmcomms 25556 # HP DMComms port number Holiday list configuration Holiday Lists prevent Media Operations from starting jobs on holidays.

  • Page 165: C Application Managers

    C Application managers Overview Media Operations supports the following Application Managers: • HP Data Protector A.06.00, A.06.10 and A.06.11 • Symantec NetBackup Enterprise Server and Server v6.0 The following matrix provides an overview of functionality supported by Application Managers. Table 5 Application matrix...
  • Page 166 Depending on which Backup Manager you are using, consider the following: • With HP Data Protector, when performing load/eject operations for all silo-type library devices (such as ACSLS or DAS), the cartridge access port (CAP) must be set manually.
  • Page 167 group that has permissions. An NT user is acceptable, in which case enter a domain for that user in place of a group. • Initialization: In libraries, NetBackup does not support media initialization on demand. It moves media from a blank (default) pool to a target pool. Library—does not support on-demand initialization.
  • Page 168 Application managers...

  • Page 169: Glossary

    Glossary access rights Permissions to perform specific tasks. Users have the access rights of the user class to which they belong. automatically Media used for backups controlled by the Backup Manager. created media backup device A device configured for use with a Backup Manager that can write data to storage media.
  • Page 170 date entered The date that you entered the request (automatically entered). device A physical unit which contains either just a drive or a more complex unit, such as a library. disaster recovery A process that restores a client’s main system disk to a state close to the time when a (full) backup was performed.
  • Page 171 drives by a robotic mechanism, allowing random access to the media. The library can contain multiple drives. log retention time The length of time the media audit logs are saved on the server. Manager of Several cells can be grouped together and managed from a Managers (MoM) central cell.
  • Page 172 transmission begins. Contrast with an interrupt-driven system, in which the terminal generates a signal when it has data to send. (2) A technique that continually interrogates a peripheral device to see if it has data to transfer. For example, a mouse button was pressed or data is available at a communications port.
  • Page 173 time entered The time that you entered the request (automatically entered). user rights See access rights. vault An onsite or offsite storage location for removable media. vaulting job Performs daily Media Operations related to moving media between onsite and offsite locations to meet the vaulting policies for that site.

  • Page 175: Index

    Index barcodes, labeling policies, bulk configuration file imports, adding backup managers, media types, alerts, checkout requests, audience, job listing, audits CLI, running jobs, history, communications port number, importing, compression, refining, location, configuration files, bulk import, pending, configuration report, problems, configuring, requests, automatic backup, auto pass license key,...
  • Page 176 DMComms, DNS suffixes, document importing conventions, audit list, related documentation, bulk configuration files, documentation data, HP website, offsite vendor file, providing feedback, installing Media Operations Manager, Media Operations server, XML Gateway, 31, e-mail interface, integrating backup managers, 20, editing interfaces...
  • Page 177 metrics, location, languages supported, pool health, license key, premount, licenses, viewing, remote, licensing, report, lifecycle, media, scratch media, lights-out operation, vault, listing vaulting, checkout request jobs, vendor, mount requests, modifying media types, scratch jobs, monitoring, location mount requests, audits, reactive, metrics, multiple sites, 107, 111, locations, refining,...
  • Page 178 GUI, Windows, metrics, jobs through CLI, pool media, startjob, systems media, status checking requests, requests, reactive mount, status indicators, reserving slots, Subscriber's Choice, HP, supported languages, Symantec Netbackup, systems media list, scans, schedules, scratch bin, scratch bin jobs, technical support maintenance,...
  • Page 179 XML offsite vendor manual jobs, file format, metrics, interface, templates, vaulting policies, active, basic concepts, creating, vaults, metrics, priorities, vendor metrics, viewing licenses, web user interface, websites HP Subscriber's Choice for Business, product manuals, XML file import directory, format, interface, User guide...

Table of Contents