BackBox® H4.00 User Manual HP Part Number: 748415-002 Published: March 2014 Edition: G06.24, H06.06 or J06.
Legal Notice © Copyright 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents Preface ..................................................................................... 6 SUMMARY OF CHANGES ....................................................................................... 7 Product Description .................................................................. 8 BACKBOX COMPONENTS ...................................................................................... 9 PRODUCT REQUIREMENTS ......................................................................
ENTITIES CONFIGURED IN A DOMAIN ..................................................................... 35 Domain ................................................................................................... 36 VTCs and Virtual Devices ........................................................................... 36 Data Stores ............................................................................................. 36 Volume Groups.......................................................................
Configuration data on each VT Controller ..................................................... 63 Images of virtual volumes kept in Data Store(s) ........................................... 63 Operations.............................................................................. 65 VTC STARTUP ................................................................................................ 65 VTC SHUT DOWN ...........................................................................................
MS-Windows Start button in VTC .............................................................. 115 User interface ....................................................................... 117 SIGN IN ..................................................................................................... 120 Session timeout...................................................................................... 120 DOMAIN ADDRESS CONFIGURATION ....................................................................
APPENDIX B – EXTERNAL TAPE DEVICES INSTALLATION .............................................. 196 Physical tape device attachment ............................................................... 197 Attachment to another Virtual Tape System ............................................... 198 VTC configuration ........................................................................................................................................... 198 Configuration in the BackPak Domain ....................
Preface Preface This User Manual contains a product presentation and reference information for the configuration and operation of a BackBox subsystem connected to a NonStop server. BackBox is part of the BackPak product family that also contains BackLib, a library management for NonStop attached tape libraries. BackBox and BackLib share the software components running on the NonStop host and the user interface This present manual is dedicated to the BackBox versions Hxx.xx that are distributed by HP.
Preface Summary of Changes Version 4.00 – January 2013 No functional changes. The release 2014-JAN-29 contains only bug fixes. 7 BackBox H4.
Product Description Product Description BackBox is the ETI-NET virtual tape solution to connect the NonStop Guardian tape subsystem to external storage facilities. BackBox is part of the BackPak ETI-NET family of backup related products: • BackBox provides NonStop virtual tape capability storing the virtual volumes in various Enterprise storage infrastructures.
Product Description BackBox Components The BackBox is made up of the following components: the Virtual Tape Controller (VTC) unit, the Data Store, the Domain Manager and the Event Extractor. A graphical user interface to BackBox runs on the operator workstation. The Domain Manager, Event Extractor and UI Client are common BackPak components shared with BackLib, the ETI-NET tape library management. BackBox virtual tapes and BackLib library tapes can be managed in the same BackPak Domain.
Product Description VTC functions are controlled through TCP/IP. The VTC is built on a dedicated Windows Server 2008 R2 server platform. It stores virtual tape images through the Windows file system of the VTC. The disks are generally shares in a StoreOnce NAS, but could use any disks compatible with the Windows file systems, including internal disks in the VTC. The number of possible physical connections per VTC depends on the model. See in Product Requirements below.
Product Description Product requirements VTCs The VTCs are delivered with the required hardware and software.
Product Description For automatic sessions such as the processing of mount requests, the account to authorize is SUPER.SUPER, and the utilities are MEDIACOM, MEDIASRV and TMFSERVE. This basic security schema can be adjusted, see NonStop Access Authorizations. Additional software Tape catalog: DSM/TC is recommended for tape catalog, with optimal BackPak integration; Other tape catalog products are supported, partial but essential integration is provided for QTOS.
Product Description Basic Functions Basic BackBox functionalities allow: Creation of virtual volumes, Completion of tape mounts requests in Guardian, Emulation of a tape drive connected to a NonStop host Safeguard of virtual volumes and their data. Import/export of virtual volumes through a physical tape drive attached to the VTC (virtualization / materialization) Encryption of virtual volumes (see the separate manual BackBox Tape Encryption Option).
Product Description Virtual volume mounts A virtual volume can be manually “mounted” using the Web user interface, but this process is normally automated by the BackBox EMS Extractor. The EMS Extractor listens for mount requests and sends the required command to the Domain Manager that will forward the request via IP to a selected VTC. Volumes are normally unloaded by the tape application after use. Unused volumes kept loaded for unexpected reasons are automatically unloaded, as documented below.
Product Description • Not configured as a device reserved for explicit allocation (with an explicit only attribute), and • Not configured as a device reserved for a volume class that is not the class of the volume to mount. Once those mandatory criteria are met, the devices are dynamically assigned to distribute the workload across available SCSI/FC ports and VTCs. The preference criteria are listed below, beginning by the most important one: 1. Rank of the Data Store route. All drives of a route (i.e.
Product Description by the VTC to the Domain Manager to register the volume statistics and new idle state. Automatic unload occurs when the MEDIACOM REJECT command is issued, or the tape application is canceled before the load completes. Automatic unload is also initiated by the daily cleanup (BB017_FREE_EXPIRED macro) if the volume was abnormally left in LOAD state after its use by the NSK tape system.
Product Description Compression Software compression is available for Windows File System Data Stores, through a well-known algorithm that can be enabled in the Volume Group. • ZLIB – better compression, that adds to the VTC CPU load • The End-Of-Tape (EOT) indication is sent to the Guardian tape process when the size of the compressed data reaches the maximum volume size defined in the Volume Group. • VTCs add metadata to the User data received from SCSI commands.
Product Description The data is encrypted using IEEE 1619.1 (tape) industry standard algorithms before it is sent to the Data Store. The encryption algorithm uses a 256 bit encryption key stored in an external Key Management Server. Encryption by BackBox software can be used with an HP Enterprise Security Key Manager (ESKM) and can optionally be fully integrated with the NonStop Volume Level Encryption (VLE) product.
Product Description 3) Using the BackPak GUI, Volume tab, the operator initiates the materialization of a volume (Volume Materialization) or a batch of virtualizations (Virtualize Volume), monitors the status of these tasks, and eventually, if needed, cancels them. Details about the physical tape attachment are provided in Appendix B – External tape devices installation. General guidelines for migration to BackBox are provided in Appendix C – Migration to the BackBox product.
Product Description Creation of virtual volumes The virtual volumes in each set of created volumes are spread evenly across the Data Paths on disks that contain enough free space to contain the maximum volume size of one of these volumes. For a Volume Group configured as AUTOSCRATCH and associated to a NonStop tape catalog such as DSM/TC or TMF, the two files .IND and .DAT corresponding to each empty volume are not actually created as disk files in storage while the volume’s catalog status is SCRATCH.
Product Description A virtual volume just written is unloaded by the NonStop server (new Windows files to backup) A virtual volume must be loaded for the NonStop server and a corresponding Windows file is missing (Windows file to restore) Scripting facilities Scripts are identified in the Data Store advanced configuration page. User parameters can also be defined and their value set in the same page. There are two sets of scripts.
Product Description • Delete backed up files after a certain number of days has elapsed since their backup, allowing for the immediate retrieve of recent backups and freeing of disk space associated to old backups (BB023_DEL_BACKEDUP) • Delete restored files after a certain number of days have elapsed since their restore, allowing several executions of the NonStop RESTORE program after a single execution of the restore script (BB023_DEL_BACKEDUP).
Product Description The replication of virtual volumes from a ‘Storage pool’ to a ‘Copy pool’ must be set before a ‘Copy pool’ can be used. The replication of can be provided by any disk replication tool, by replication included in storage provider such as Data Domain, by MS-Windows replication tool, or by a backup script specified in the BackBox Data Store configuration. 23 BackBox H4.
Product Description TSM Data Store In a Tivoli Storage Manager server, a virtual volume is materialized by a series of TSM objects of a certain size. A BackBox server can either be a TSM client and can even host the TSM server when the BackBox is set up as a storage appliance. Tivoli Storage Manager Software The TSM Windows client API runtime module is required in VTCs accessing TSM servers. An enterprise TSM server might be shared, or a dedicated TSM server can be installed for the BackBox clients.
Product Description Integrity check when a volume is written When a volume just re-written is unloaded, the TSM data base is queried to verify the list of TSM objects containing the virtual volume. If an anomaly is detected, the message #6005 or #6006 is issued in EMS, the backup should be re-executed, and ETI-NET support contacted. Notes: • The NSK backup or TMF dump will most of the time finish without any NSK error condition. • The number of TSM objects can be seen in the Volume detail web page.
Product Description When processing these mounts requests, the Domain Manager knows the characteristics of the Guardian TAPECATALOG DEFINE that initiated the mount request and can determine if the volume is scratch or not. The auto-scratch mechanism is never active for manual loads initiated through the Volume Detail page of the Web user interface.
Product Description Delete Expired Volumes The free-up of the storage occupied by expired volume is enabled by checking “Delete Expired Volumes” in the Volume Group configuration. The cleanup is triggered by the TACL macro BB017_FREE_EXPIRED in the daily batch OBB017. The automatic free-up of storage for volumes that become SCRATCH is available only for DSM/TC, TMF and QTOS catalogs.
Product Description For operations initiated through the Web interface the Guardian login information (Domain Manager node and user-id) entered to access the Web interface is used. Authorization specification Each of the three authorizations, Read, Write and Control, specifies how the user accessing the volume should compare to the volume owner.
Product Description SET DEFINE USE OUT ADD DEFINE =TAPE1 Un-cataloged volumes Restricting the access to volumes that are not cataloged has constraints. There is no volume status in Guardian that allows recognizing a SCRATCH volume before accessing it and so the authorization check is not bypassed. The user must plan to avoid a denied access to SCRATCH/expired volumes.
Product Description To use pre-load with multi-volume backup set: • Be sure there are two virtual devices available for each NonStop restore tape process. • Enable Pre-load in the Volume Group configuration. BackBox detects and registers the multi-volumes backup sets (BACKUP, BRCOM or TMF dumps)). When a load for input is executed and the volume is part of a multi-volume set: 1. The restore script for the first volume is run. 2.
Product Description To set up a Restricted Data Store in an alternate domain: In the domain configuration, a Data Store is defined with RESTRICTED domain access. The Data Store id and Volume Group ids are ideally be the same as in the original domain; if different, the original ids must be specified in ‘Primary Data Store ID’ and ‘Primary Volume Group ID’. These primary ids become visible in the configuration pages only when the Data Store access is set to RESTRICTED.
Product Description The volume timestamp check is not available. The control of access to volume data is different from a PRIMARY Data Store: In regular PRIMARY Data Stores, the access to a volume is controlled by the security settings (volume owner and access authorizations) stored in the domain catalog. In an alternate domain with RESTRICTED access to a Data Store, the Read access is the only possible access.
Product Description A RESTRICTED Data Store promoted to PRIMARY replaces the original owner, in a site or environment recovery. When a RESTRICTED Data Store is promoted to PRIMARY domain access, the volumes of the Data Store will progressively migrate to the full Primary domain access state, as they are rewritten for backup by the new Owner domain.
Product Description The replication of the only BackPak catalog brings several benefits, the most important: • The timestamp of the last backup on the volume is written, and will be verified against the volume in storage at restore time in the secondary site, securing the identification of the version of the volume data.
Configuration Configuration This chapter provides explanations and guidelines to complement: • The following chapter “User Interface” that documents the actual UI pages. • The distinct manual “BackBox installation Guide” that describes the overall procedure to install the product. The chapter is organized in the following sections. Entities configured in a Domain briefly presents the main entities defined in a Domain configuration.
Configuration • The VT Controller (or VTC) defines the virtual devices, TCPIP and SCSI/FC connections to the NonStop are specified. • The Data Store describes where the virtual volume images are stored. • The Volume Groups set volume attributes such as the maximum volume size, the type volume and corresponding NonStop catalog and pool. Domain A domain is the definition of an operational environment for tape applications.
Configuration • Data Store name. • Maximum size of a virtual volume. • BackBox compression • Catalog type and name Not all attributes in a Volume Group definition can be changed once volumes have been created in this Volume Group. Maximum volume size, volume class, compression and encryption will take effect only on volumes loaded for output. To change un-modifiable Volume Group attribute, the volume must be recreated and the included volumes deleted and recreated under the new Volume Group.
Configuration Options for BACKUP, BRCOM and TMF These options should be revised taking into consideration the differences between physical and virtual tape media. Some options apply to real media but not necessarily to virtual media For example, the value of the tape feature VERIFYTAPE can be reconsidered when the data is actually written to a disk file. Ensure to always use the maximum BLOCKSIZE. Use 52 K in BACKUP and TMFCOM DUMP FILES commands.
Configuration Number of virtual volumes It is a good idea to avoid defining a lot more volumes than needed. Smaller catalogs are easier to manage. In addition, the free-up of expired storage is not possible in some environments; for example because the tape catalog is not supported by BackPak, or because it was not possible to write a delete script to free-up the back-end copy of an expired volume in the Enterprise Backup infrastructure.
Configuration Domain Network BackBox network topology 40 BackBox H4.
Configuration BackBox TCPIP ports Considerations about the Scope of a Domain Number of NonStop nodes per BackPak Domain A Domain has: − A main node that hosts the Domain Manager, the configuration and catalog of virtual volumes. This node runs the Domain daily batch OBB017. − Optional peripheral nodes that host only the EMS Extractor. The GUI requires a distinct sign-on to each domain. A GUI instance shows only the configuration and operation of a domain.
Configuration It is possible to operate concurrently several BackPak Domains on the same NonStop node; each domain must have its own and separate: − Domain Manager (distinct TCP/IP port) − Domain Installation configuration) − EMS Extractors (BBEXT processes) − Data Stores (Disk for Windows Data Store, Storage pool for TSM Data Store) sub-volume (programs, catalog and Number of VTCs per domain For fail-over reasons, two or more VTCs are attached to the NonStop node(s).
Configuration TCP/IP traffic port configurations Client Server Standard Port Workstation (UI Client) NonStop ( Domain Manager) 4561 Workstation (Windows Desktop client) VTC (Windows Remote Desktop Server) 3389 VTC (emulator and administrative services) VTC (TSM Data Store data service) 1501 Workstation (Web browser) VTC (TSM Data Store Administrative service) 1580 Nonstop (Domain Manager) VTC (FC emulator services) 8764 Nonstop (Domain Manager) VTC (administrative service) 8766 If Win
Configuration Installation with QTOS The virtual volumes are defined in both QTOS and BackBox. To register the volumes in the BackPak Domain: - Have them first created in the QTOS data base - Use the BackPak GUI, Volume tab, “Import from Tape Catalog” page, to populate BackPak according the QTOS data base QTOS must be set for SILO. QTOS vault must be set for Vault location "V" and Silo "S". A BackBox Volume Group must be configured for each QTOS vault. They will contain the same set of tape volumes.
Configuration On the NonStop platform, the BackPak application is used to configure BackPak, to automate the tape operations and to provide a GUI to manually operate and support tape operations. Operator actions on the NonStop tape system (TMFCOM, MEDIACOM, SCF) require a user-id in the SUPER group, for example to add a TAPEVOLUME in DSM/TC or to reject a MOUNT REQUEST. In a regular security setup: • SUPER.
Configuration SUPER.SUPER. In this AUTOMATION context, only actions pre-defined in the configuration are executed, for example: • Volume load sent by the EMS Extractor • Cleanup of expired storage initiated by BB017_FREE_EXPIRED macro • Log message coming from a VTC server forwarded to EMS Access to the NSK files in the BackPak installation sub volume The basic Guardian security set by the INSTALL configuration macro will allow remote access and update to the SUPER group.
Configuration File Content Access SCF, TACL, CLIMCMD Guardian utilities BBSV processes for GUI need to run these programs when configuring Access to the NSK utilities BackPak starts SPI processes with MEDIASRV, TMFSERVE and MEDIACOM to access the Guardian tape system and catalogs during the configuration and the regular operations. The MEDIASRV & TMFSERVE action commands are reserved to the SUPER group. During the configuration through the BackPak UI, the programs TACL, CLIMCMD, SCF are also run.
Configuration In some enterprise contexts, the regular Guardian security pattern is not directly applicable; especially when operators cannot be given a Guardian user-id in the SUPER group. Then giving the PROGID attribute to BBSV can be a bypass; if BBSV is owned by a SUPER group member, it will start as if logged-in the SUPER group. By default, the result of the PROGID attribute on interactive processes running for the GUI will be overridden by the Sign on initiated by the GUI.
Configuration Windows Files Data Stores In this kind of Data Store, a virtual volume is implemented in two disk files stored in a Windows compatible file-system. Several storage technologies are supported, such as HP StoreOnce NAS, with specific BackBox code to maximize the storage features such as the de-duplication. File servers / NAS considerations Hardware requirements To write/read virtual tape images on a remote file server requires high performance network and file servers.
Configuration • Spare Pool: (if licensed) emergency pool of paths in case of unavailability of all paths in the Storage Pool. • Copy Pool: (if licensed) direct access to a copy of the ‘Storage pool’, allowing to restore from a copied virtual volume without executing any restore script fetching back the copy to the regular ‘Storage pool’.
Configuration • Make sure the moved files will allow full access to the account specified in the Data Store configuration When a path is added to the pool: • This path is immediately active and will be considered as candidate for the next file creation, move and restore operation. Distribution of files among the paths of a pool When a file is re-created to satisfy a mount for output request (i.e.
Configuration TSM Data Stores This chapter assumes that minimally: The IBM TSM client has been installed in each VTC, including: The API run-time The command-line backup client The GUI backup client The connectivity between the VTC and the TSM environment has been tested outside the BackPak software, by using: A TSM backup client provided by IBM The TSM client node-id / password that will be used by the VTC. The TSM management class to be used by the VTC meets the BackBox requirements.
Configuration The expiration of the tape volumes is managed by the Guardian tape catalogs and storage corresponding to expired volumes is explicitly released by the BB017_PURGE daily job. Consequently, the TSM server should keep the BackBox archives forever and the Archive Copy Group must be set accordingly. When defining an Archive Copy Group for the VT Controller, the parameters below are important. Other parameters usually do not apply to the BackBox application.
Configuration Edit, Preference, General, Node Name: specify the node name registered for the VTC (this is often not the machine name) Edit, Preference, General, Authorization, Password Access: choose “Password prompt” Edit, Preference, Communication: specify TCP/IP method and TSM server address Do a connect (File, Logon ..) and an archive For each VTC: Create the same directory name to contain the DSM.OPT file for the VTC. Copy the DSM.
Configuration Only PASSWORD ACCESS GENERATE allows the TSM API to manage the automatic TSM password renewal in when NODENAME/PASSWORD is specified in DSM.OPT. In the configuration of the TSM Data Store of BackPak, the TSM user-id and password must be omitted in when NODENAME/PASSWORD is specified in DSM.OPT. Compression/ encryption Compression and encryption by the TSM API are supported. However be aware that performance may be degraded if backup encounter a bad disk sector and must issue a back-space.
Configuration TSM Setting TSM Client Configuration VTC Domain configuration, Data Store. Fields Node, Password. Client node and password Or (LAN-free case): DSM.OPT file. Keywords PASSWORDAccess , NODename, ASNODEName, PASsword Maximum object size Management classes File Space names VTC Domain configuration, Volume Group. Fields Max Object Size. VTC Domain configuration, Volume Group. Field Management Class. VTC Domain configuration, Data Store. Fields File Space 56 BackBox H4.
Configuration EMS Extractors configuration Each Guardian node where a BackBox virtual device is operating must run the EMS Extractor program BBEXT as a permanent process. BBEXT reads tape mounts messages from EMS events; forward them to the Domain Manager. It also retries pending mount requests. It regularly checks the MEDIACOM list of pending mounts to detect any new mount missed if, for example, BBEXT was not running. This periodic check is executed every failsafe-retry-interval.
Configuration Tag definitions : Maximum wait time, in seconds, for response from the Domain Manager. : Maximum number of times a volume load is retried when no virtual device is free. Value 0 to suppress any retry. Value -1 to get infinite retries. : Delay, in seconds, between two retries to load a volume on a busy virtual device(s).
Configuration RUN BBEXT /IN BBEXTCFG, NOWAIT, NAME $BBEXT/ Automatically Start BBEXT BBEXT can be started automatically by the Guardian system at each system boot. Below is a sample SCF command to register BBEXT and initially start it. ADD PROCESS $ZZKRN.#BBOXEXT, & PROGRAM $DATA05.BBOX.BBEXT, & NAME $BBEXT, & AUTORESTART 3, CPU FIRST, & & HOMETERM $ZHOME, & INFILE $DATA05.BBOX.BBEXTCFG, & STARTMODE APPLICATION, & USERID SUPER.OPER START PROCESS $ZZKRN.#BBOXEXT 59 BackBox H4.
Configuration Set Up for Recovery This section suggests backup procedures for the BackBox environment. The recovery procedures are detailed in the Operation Chapter. When planning for recovery of a BackPak environment in the event of a site disaster or a simple file loss, three groups of BackBox data must be considered: 1. The metadata on NonStop server(s): the BackPak Domain Manager configuration, its catalog and one or more EMS Extractor configurations. 2.
Configuration OPER Cache for temporary status information (no need to protect) STATE TSM API passwords (not used for WINDISK / StoreOnce) VOLUME Catalogue of virtual volumes VOLUME0 Index for the previous file BackBox configuration The BackBox configuration, as created/updated by the BackBox web application, is stored on the NonStop server in the installation sub-volume of the Domain Manager. The configuration file name is BBSVCFG.
Configuration • This is the location of the two Windows files the last time the volume was re-written by a NonStop tape application. • At NonStop restore time, this location is not used to retrieve the virtual image in the online disk pool(s). It is only used to retrieve the Windows files from a back-end Enterprise Backup software: this “Last Update Index Path” makes up the fully qualified original file name in the restore command.
Configuration Basic protection of NonStop DSM/TC catalogs • This applies when the BackPak Catalog Sync Option is not available. Refer to the HP documentation, such as: o "Disaster/Recovery of DSMTC catalogs" (Id: gcsc10456) o "How to move a VOLCAT or FILECAT to another system" (Id: 1.0.1593289.2189680) o “How to recover/restore the DSM/TC database to the original node using TMF." (Id: 100.0.40060491.
Configuration Windows File Data Stores Protection tools for the Windows file system such as disk replication are used independently of the BackBox software. The BackBox VTC scripting helps to integrate in Enterprise Backup infrastructures. 64 BackBox H4.
Operations Operations Basic BackBox operational procedures are presented below. VTC Startup 1. Stop the virtual tape devices emulated by the VTC with the Guardian SCF command: TACL> SCF STOP TAPE $vtname 2. Power on the VTC. 3. Wait for the following two EMS messages to be displayed on the Guardian node where the Domain Manager is installed: BBOX-I103 Service started (VTC Admin) BBOX-I103 Service started (VTC Virtual Tape Devices) 4.
Operations If the EMS Extractor is registered in the Kernel subsystem, restart through SCF. If #BBOXEXT was the registered name: TACL> SCF START PROCESS $ZZKRN.#BBOXEXT Manual Load and Unload Unless operational needs require the pre-mount of a tape volume, the preferred method of operation is detailed below. The processing of a manual load requires the Domain Manager running on a NonStop server.
Operations In the BackPak environment, the user must identify each unlabeled volume by a pseudo-label. This pseudo-label is then used by the BackBox software to catalog and locate the image of the unlabeled volume. To Create an Unlabeled Volume 1. Create the virtual volumes with the label type Unlabeled. Assign a six-character label, along with a descriptive comment, to each unlabeled volume. The labels assigned to unlabeled volumes are usually different from those of labeled volumes in manual operations.
Operations OBB017 list: COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT cOMMENT COMMENT COMMENT COMMENT COMMENT COMMENT *********************************************************************** * BackBox Data Store cleanup * * * * 1- BB017_FREE_EXPIRED in all Data Stores, free storage allocated * * to volumes expired in DSMTC and TMF catalogs * * * * 2- BB023_DEL_BACKEDUP in "Windows files" Data Stores, delete backed* * up files according to the Volume Group config* * * * 3- BB022_CHECK_SPACE in "Wi
Operations Syntax BB017_FREE_EXPIRED [SCRIPT_TIMEOUT minutes] [,PROCESS NEW | ALL], [,MIN_SIZE size] [,OUT filename] Parameters [SCRIPT_TIMEOUT minutes] maximum number of minutes allowed to the Delete script. Default value is 5. [PROCESS NEW | ALL] NEW: process only the new SCRATCH volumes ALL : process all SCRATCH volumes or backup software Default value is NEW. [MIN_SIZE size] minimum number of KB of data in the tape volume, to allow the free up executed. Default value is 0.
Operations I3173 BackBox storage space purge of expired tape volumes. 51 volumes in catalog, 3 volumes purged. BBOX-BB017 ends at 2006-02-05 23:16 BB023_DEL_BACKEDUP The BB023_DEL_BACKEDUP command will initiate a Windows process that will scan all configured paths in PRIMARY WINDISK Data Stores, and according to the Volume Group configuration associated with each volume, delete the Windows files that have been saved to an enterprise backup server.
Operations value 1: replace '_' characters by space value 2: replace '+' characters by space. Default value is 0. [START_TIME HH:MN] Specific to StoreOnce. See after the Sample regular report. Minimum start time in the day. If the macro is run before, nothing will be executed. From 00:00 to 23:59. Default value is 00:00. START_TIME and END_TIME must be both specified or both omitted. [END_TIME HH:MN] Specific to StoreOnce. See after the Sample regular report.
Operations Data Store total 6 volumes for which Windows files have been deleted 12 Windows files deleted 185 MB deleted LSD3-BB023 Delete backed up Windows files 2007-08-21 10:38:36 Data Store: WIN2 Label ----- Last update ---------------- Last accsss ---------------- Size (MB) ----------- Path: D:\LSAL\LSD3\WIN2 This path is not available Data Store total 0 volumes for which Windows files have been deleted 0 Windows files deleted 0 MB deleted Grand total 6 volumes for which Windows files have been
Operations Sample report for a StoreOnce: QCBLADE-BB023 Delete backed up Windows files Execution window from: 2013-09-10 13:44:18 to: , max duration: 00:03 Store id to clean up: WINETI1 Processing will be interrupted on: 2013-09-10 13:47:00 Data Store: WINETI1 DATASTORE WINDOWS Label ----- Last update ---------------- Last access ---------------- Clean job was submitted for data store WINETI1.
Operations E3034 No available route to Data Store CR1 W3218 Disk path D:\LSAL\LSD3\WIN2 in Store WIN2 is not accessible W3313 Only 30% of SCRATCH volumes available in Volume Group DSMTC_ETINIUM. Volume Group has reached the warning level of 80%. 3 volumes are SCRATCH out of 10 volumes in the Volume Group.
Operations f 10 volumes in the Volume Group. DSMTC_ETINIUM 10 344 3.80 3 5 0.01 1.12 n/a 30% 119 QTOS Data Store : WIN2 Volume group -----BACKDSK n/a n/a (Type WINDISK) Nbr of volumes ------- Uncompressed data size(MB) ------------- 2 1 Compr.
Operations Macro syntax: LOAD /KEEP 1/ BBOX.BBSETUP BBOX.MACROS BB020_RESERVE [DRIVE [\node.]$name-pattern, , CLASS name | (name, name...) | NONE ] [, LIST ] LIST shows all current reservation. To modify reservations, the keywords DRIVE and CLASS must be entered. Note that the modified reservations are always listed. DRIVE Specifies the drive whose reservation will be altered. Only a single specification is allowed but wild-cards can be used in the device name. The current node is the default drive node.
Operations Recover the BackPak Catalog For the replication provided by BackPak, refer to the separate manual BackPak Catalog Sync Option. This chapter shows manual alternatives to the BackPak Catalog Sync Option. To recover the VOLUME* files, the Domain Manager should not be running. To that end the EMS Extractor process BBEXT must be stopped. To recover a version of VOLUME* from TMF dumps: Run TMF RECOVER.
Operations Manager, the security setting of volumes may not have been done correctly for disaster recovery and read access is denied Use the BackPak user interface to edit volumes settings that were written since the backup of BackPak catalog and that may need to be restored or to fix volume load problems: 1. Adjust the volume owner and security setting if required. 2. Disable the Check volume timestamp at volume or Data Store level.
Operations Note that a virtual volume must be known by the Domain Manager to be automatically loaded by BackPak. An up-to-date catalog is required to make all BackPak features available. TMF and DSM/TC catalogs are not required to run restores from virtual volumes. These NonStop catalogs must be restored according to the procedure recommended by HP.
Operations 2. If VOLUME* files were not replicated, RESTORE them from the latest backup of the BackPak installation sub-volume. 3. Recover the TMF and DSMTC catalogs using the procedures documented by HP. Eventually use the BackPak Catalog Sync option for the DSM/TC catalog. The BackPak environment is now ready to process all mount requests.
Support Tools Tools Guardian tools The following TACL and obey files programs are provided as support tools for various reports, testing the performance of virtual drives, and for looking at traces etc.. Features that are essential parts of the operation are described in the previous Operations chapter; especially see the section Daily cleanup (OBB017). A reset procedure for the NonStop tape subsystem is documented in the BackPak Troubleshooting and Messages Manual.
Support Tools Notes: • When a disk file pattern is entered, different subsets of disk files might be present in different tape files (different backups), but the RECOVER DISKFILE will execute only from a single tape file. • Predefined standard restore options are set in the macro. It is possible to change them by editing BBREST. Search for: #SET restore^opt LISTALL, OPEN, and #SET outfile $S.#DSMTC.
Support Tools Default tape file generation is the latest generation. Optional tape file generation (ALL/nn): ALL **** excuting MEDIACOM query Disk file(s) name / pattern: OBWIN1 Tape file name / pattern: Tape file generation : ALL Detail report, Summary, or Quit (D/S/Q): (1) File Catalog Tape File Generation Version Time Archived D \ETINIUM.TAPECAT LSBBE-OBTSM1 6 0 10May11 15:20 File Name Code EOF --------------- -----------------------\ETINIUM.$DATA15.
Support Tools Logical Copy Time Archived Tape File Mode Catalog Files Tape Name 1 10 MAY 2011, 15:20:57 FILEMODE BACKUP YES LSTS06 Total count of valid matching disk files: 0000000001 Do you want to see the matching disk files ? (y/n) Y File Name Code Last Modified ---------------------------------------- ------------\ETINIUM.$DATA15.LSBBE.OBWIN1 00101 14MAR11 Do you want RESTORE to be started? (y/n) Y Starting RESTORE...
Support Tools About to execute: RECOVER DISKFILE OBWIN1, TAPEFILE LSBBE-OBTSM1, GEN 6 , MAP NAMES (OBWIN1 TO $DATA06.LSREST8.*), OUT $S.#BPAK.REST1, LISTALL, OPEN, TAPEDATE, AUDITED Confirm execution (Y/N): Y **** executing MEDIACOM recovery MEDIACOM - T6028H01 (24JAN2011) (C) Copyright 1993-2002, 2004 Hewlett-Packard Development Company, L.P.
Support Tools - generates in a temporary files a command for each selected media - runs TMFCOM giving the generated file as input file - deletes the temporary file - requires to run in BackPak macro and program are run. the BackPak environment: Syntax LOAD /KEEP 1/ MACROS BBSETUP TMFC2 [PEEK | NOPEEK,] [FILE file-name,] TMFCOM-command Parameters [PEEK | NOPEEK,] allows to preview the commands to execute. Default value is NOPEEK.
Support Tools NTMF03 tape assigned TMF 4> INFO MEDIA NTMF04 Media Name Media Type Media Status -----------------------------------NTMF04 tape assigned TMF 5> INFO MEDIA NTMF05 Media Name Media Type Media Status -----------------------------------NTMF05 tape assigned TMF 6> INFO MEDIA NTMF06 Media Name Media Type Media Status -----------------------------------NTMF06 tape assigned TMF 7> INFO MEDIA NTMF07 Media Name Media Type Media Status -----------------------------------NTMF07 tape released TMF 8> INFO M
Support Tools (C)2005 TMF 1> TMF 2> TMF 3> Hewlett-Packard Development Company, L.P. ALTER MEDIA NTMF07 ,status SCRATCH ALTER MEDIA NTMF08 ,status SCRATCH ALTER MEDIA NTMF09 ,status SCRATCH BB000_COLLECT – Gather information for support BB000_COLLECT is a TACL macro that produces files to send to the product support to document a problem or to provide general information about a working environment.
Support Tools [LISTALL yes|no] LISTALL YES produces the detailed PAK output (i.e. send the LISTALL parameter to the BACKUP program). no is used as default value. Sample $DATA05 BPAK 330> BB000_COLLECT TARGET BPAKTRC ... creating \ETINIUM.$DATA05.BPAKTRC.COL222* files for node number 222 WARNING - $DATA05.BPAKTRC.COL222*: ERR 11 0 FILES PURGED 1 RECORDS TRANSFERRED CREATED - $DATA05.BPAKTRC.ETINIUM MEDIACOM - T6028H01 (24JAN2011) (C) Copyright 1993-2002, 2004 Hewlett-Packard Development Company, L.P.
Support Tools BB010 - Extracts virtual volume records BB010 extracts virtual volumes records to the VOLEXT file for further reporting by BB011 or BB012. Syntax: RUN BB010 label-pattern [REPORT] [REPORT] will generate a simple report of volumes that match label-pattern. The VOLEXT file will be its content will be overwritten if it already exists.
Support Tools - the QTOS catalogues referred by Volume groups configured in the BackPak domain Syntax: RUN BB044 [BPAK_REPORT {y|n}] [, CATALOG_REPORT {y|n}] [, MERGED_REPORT {y|n}] Parameters: BPAK_REPORT {y|n} If Y or Yes, the report BB044-1 will be produced. It lists the virtual volumes of BackPak and their Volume Group name. Default value is No. BPAK_REPORT {y|n} If Y or Yes, the report BB044-2 will be produced.
Support Tools *** end of report BB044-1 *** BB044-2 Labels in catalogs seen from system \ETINIUM and from domain BPAK Labels Number of from to volumes ----------000100-000150 51 0D7F15-0D7F15 1 123456-123456 1 52284A-522853 10 AAAAAA-AAAAAA 1 ACB01 -ACB04 4 EDQ001-EDQ005 5 Label type ------BACKUP BACKUP IBM BACKUP ANSI TMF BACKUP Media type ----LTO3 LTO3 CART3480 CART3480 LTO3 EFS301-EFS351 51 BACKUP LTO3 EFS401-EFS442 42 BACKUP LTO3 LSDEP1-LSDEP9 LSE01 -LSE24 LSLSXX-LSLSXX LSMM01-LSMM10 LSQ001
Support Tools VT0005-VT0019 W8D00 -W8D99 15 BACKUP 100 BACKUP BBOX_WIN1, \MONT.VERYLONGVOLUMECATALOG CATALOGED_VOLUMES BBOX_WIN1, TAPECAT (unknown in BackPak) PRODBKP, ETINET_PROD *** end of report BB044-3 *** OBB011 - List of volumes in Windows files Data Stores OBB011 List the virtual volumes stored in Data Stores of type Windows files, sorted by Windows disk path.
Support Tools Sample: $DATA15 BFERHG19 47> run obb012 LS* BB012 List of virtual volumes 01/09/05 Volume Label Tapecat Tapecat label type Last load node status ------ ------ ------------------- -------- -------Store id: TSM2 LSBT09 BACKUP LSBT10 BACKUP LSBT11 BACKUP Author.
Support Tools COMMENT COMMENT COMMENT COMMENT * RELATIVE-START-DAY number * * choose the starting 24 hour period relatively to today* * default value is 0 (current period) * ***************************************************************** CLEAR ALL COMMENT PARAM CUTOFF-TIME 00:00:00 COMMENT PARAM RELATIVE-START-DAY -1 BB018_DEFAULTS COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT **************************************************************
Support Tools -------- -------Start date: 14:38:20 14:38:25 14:38:25 14:38:35 14:55:03 14:55:22 14:55:04 14:55:16 -------- 2011-04-07 LOAD W BACKUP W LOAD R RESTORE R ------ ----------- ------ -- -------------------OBCD09 OBCD09 OBCD09 OBCD09 2 2 2 2 1.0 0.2 0.5 0.
Support Tools Syntax: OBEY OBB019 Content of OBB019: COMMENT ***************************************************************** COMMENT * * COMMENT * BB019: List the script controller activity * COMMENT * from the statistic files * COMMENT * * COMMENT ***************************************************************** LOAD /KEEP 1/ $DATA05.BPAK.BBSETUP $DATA05.BPAK.
Support Tools COMMENT ***************************************************************** ENFORM /IN BB019 / Sample: $DATA15 LSBBOX 14> OBEY OBB019 BPAK-BB030 - Extraction of statistic files 2010-03-16 13:12 Stats file names : $DATA05.BPAK.STAT%YY%%MM% Extract file : STATEXT Selection from: 2010-03-15 14:00:00 to: 2010-03-16 14:00:00 Existing statistic files Records read Records extracted ----------------------------------- ----------------\MONT.$DATA21.LSBBOX.STAT0912 5526 0 \MONT.$DATA21.LSBBOX.
Support Tools E – severe error occurred for one or all the files processed by the script OBB021 – Emulation statistics report OBB021 List the tape emulation activity only: data size and throughput per volume loaded. Rates printed in BB021 exclude the initial wait time. This excludes all starting activity, including the tape label recognition by $ZSVR, until the tape application begins to write or read data blocks.
Support Tools COMMENT * Activity is selected from FROM-DATE & CUTOFF-TIME (included)* COMMENT * to TO-DATE & CUTOFF-TIME (excluded) * COMMENT ***************************************************************** BB030_EXTRACT_STATS EXTRACT_FILE STATEXT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT ***************************************************************** * STEP 3: Produce report * * from the file specified in ASSIGN STATS-FILE-REC * * * * Input PARAM's
Support Tools Volume label Virtual volume label Data size Data size written or read by the NSK tape application Rate Transfer rate computed from the time the 1st data block is written/read (excluding tape headers processing), up to the unload time. Compr. ratio Compression ratio = user data size / storage size. En-cryp Encryption indication = space or “Encr”.
Support Tools ------ ---------- -------- -------------------------------------------------Key manager id Client type : KM-ESKM : 1-VTC ONLY VE1001 2011/10/27 ASSIGNED BBOX_21F5BD27VE1001D68095D44B400008_111027202410 VE1015 2011/10/27 ASSIGNED BBOX_767FE574VE1015D5C6642F4B230008_111024144520 2 printed volumes for Key manager KM-ESKM End of report BB038 Report elements: Volume label Label of the virtual tape volume Last write date Last date the volume was written by a tape application.
Support Tools COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT COMMENT * from the statistic files matching the pattern * * configured in the BackPak Domain configuration. * * Set an ASSIGN STATS-FILE-REC to the extract file.
Support Tools Compr. ratio Compression ratio = user data size / storage size in the BackBox Data Store. En-cryp Encryption indication = space, “Decr” or “Encr”.
Support Tools The user must ensure the BackPak macros are loaded in the TACL session, from the installation sub-volume of the domain to extract statistics from. VOLUME domain-subvol LOAD /KEEP 1/ BBSETUP MACROS The period to extract must be set by TACL PARAMs: PARAM CUTOFF-TIME hh:mn:ss PARAM FROM-DATE yyyy-mm-dd PARAM TO-DATE yyyy-mm-dd This will select activity from FROM-DATE to TO-DATE & CUTOFF-TIME (excluded).
Support Tools Download the file to the workstation The written NonStop file is an Enscribe Entry Sequenced file that must be downloaded as a text file. ftp nonstop1 quote site nocrlf on get $data21.temp.mystat stats.csv bye Usage in the workstation tool Specify the file as comma delimited, declared containing field names in 1st line if extracted with the FIELD_NAMES YES parameter.
Support Tools o • These records are not associated to a specific tape volumes, as sub-scripts are submitted for a set of volumes, several columns are blank. Operation_cat LIBR is for tape library specific Operation’s: MOVE-IN/-OUT are media moves from/to the IE slots. INVENTORY-IN/-OUT are changes beside regular BackLib operations. LABEL detected in the inventory, are for labelling a new media. All elapsed times are specified in seconds.
Support Tools Field name Description Sample value for EMUL LOAD Sample value for SCRIPT BACKUP Operation EMUL: LOAD, EXPORT, IMPORT SCRIPT:BACKUP, RESTORE, DELETE STORAGE ADMIN:MOVE SCRIPT (script controller): BACKBATCH, REST-BATCH LIBR (libraries): LABEL, LOAD, MOVE-IN, MOVEOUT, INVENTORY-IN, INVENTORY-OUT, EXPORT, IMPORT LOAD DELETE Severity “I” when there is no error. “W”, “E” and “F” are possible.
Support Tools Field name Description Sample value for EMUL LOAD Sample value for SCRIPT BACKUP Init_time Elapsed time - from the time VTC is ready to report the tape drive ONLINE, - to the time VTC detects the 1st data block (i.e. after the processing of tape labels). 0000013 000000000 Data_time Elapsed time of data blocks transfer (This is the base of throughput computation in OBB018) 0000001 000000132 Post_unload_time Elapsed time in after the unload.
Support Tools Field name Description Sample value for EMUL LOAD Store_type Data Store type (WINDISK or TSM) Volume_class Volume class as defined in the Volume Group VTC VTC id in the domain configuration VTC85 NSK_node NonStop node where the tape device is attached \MONT NSK_device NonStop tape device $VT8501 NSK_access_nod e NonStop node running the tape application (note 1) \MONT NSK_dui NonStop user id running the tape application (note 1) 255.
Support Tools Field name Description Sample value for EMUL LOAD Encrypt_algo. Encryption method: 0 – none 1 – NSK CLIM VLE 0 Media_type DSM/TC media type: CART3480, LTO 3, LTO 4 etc.. LTO 3 Compr_algo Compression algorithm: NONE ZLIB TSM NONE Sample value for SCRIPT BACKUP OEMS - EMS messages extraction TACL Obey file to extract EMS events related to tapes and BackBox. Update this obey file before submitting.
Support Tools Content of OEMS2: ?TACL routine [#CASE [#EXCEPTION] |_CALL| |_ERROR| == #PUSH errtxt #ERRORTEXT /CAPTURE errtxt/ #OUTPUTV errtxt #POP errtxt #RETURN |_BREAK| #OUTPUT Break key pressed, stopping [#PROCESS] stop #RETURN |ABORT| #RETURN ] == END CASE #FRAME #PUSH #INFORMAT #FILTER _BREAK #SET #INFORMAT TACL emsdist /name / type printing, filter $DATA05.BPAK.
Support Tools maxRecordLenInBytes Maximum record length. Optional PARAMs below should not be used without consulting ETI-NET support. PARAM UNLOAD ON|OFF OFF: avoid the volume unload at the end PARAM MAXNOWAIT number Maximum number of pending IO’s PARAM BUFFERMODE ON|OFF OFF: avoid the execution of SETMODE 99 PARAM BACKBOXVOL ON|OFF ON: verify ‘SizeToWriteInMB’ against the BackPak configuration, and possibly reduce it to limit the size to a single volume.
Support Tools Blocklen Specifies the length of data blocks to read. Sample: ADD DEFINE =TAPE1, CLASS TAPE, VOLUME TST001, & LABELS ANSI, BLOCKLEN 56000, FILEID testfile, USE IN RUN TAPERD =TAPE1 56000 Trace macros The domain traces are enabled and disabled and the location of the trace files is specified by modifying the domain configuration page of the BackPak user interface (domain page).
Support Tools MS-Windows Start button in VTC In Remote Sessions on a VTC server, the “All Programs” of the MS-Windows Start button shows the group “BackPak”. “BackPak UI Client” allows starting the User Interface. “Virtual Tape Controller” is a sub-menu specific to VTCs, as shown below. 115 BackBox H4.
Support Tools “Collecting ticket information” gathers logs and configuration files in a zip file to send to the product support. See more in BackPak Troubleshooting and Messages Manual “Default Folder of Ticket Files” usually contains the result of the previous function. “VTC Configuration” starts Windows Explorer in the directory containing all configuration files. “VTC Configuration” starts Windows Explorer in the directory containing all log files. 116 BackBox H4.
User Interface User interface Standard Page Elements Each Window of the user interface contains the page elements listed below: Window title: contains the logged-in BackPak Domain id. Window menu: access the main entry-points Window Button bar: access to a subset of main entry-points. Names of tabbed Windows: a few Tabbed Windows can be opened by actions such as Domain Address, Sign On, Node Status.
User Interface The menus above are usually not used after the BackPak UI installation, actual functionality is available through the buttons row. Note that the Preferences, Session can modify the session timeout, see more in manual “BackPak UI Client Installation”. Buttons row The three first buttons are BackPak specific, remaining buttons are standard Windows buttons. Buttons other than Sign In and Back are rarely used.
User Interface Navigation Bar The navigation bar is located on the left hand side of the page. It allows access to and navigation through, the main functions of the BackPak user interface. The current location is highlighted as shown below: Tabbed Pages When a page has more than one section, tabs across the top of the main page provide easy navigation between subsections. Each tab is highlighted when selected. Data Grids In Configuration mode, many of the data is displayed in data grids.
User Interface Sign In A successful sign in to the Domain Manager is required before accessing the regular BackPak functionality. By the “Sign In” page, the user identifies the BackPak Domain and enters a NonStop Guardian user id and password. A successful NonStop logon will return the main Status page. Page elements Domain: The Domain Name and the Domain Manager selected for the session. Domain addresses are managed using the Domain Address Configuration page.
User Interface In VTCs, all domains allowed to access the VTC must be registered in this list. The Domain Address page allows the user to create, edit, or delete a domain address. See more details in the Client UI Installation manual. Stand Alone Load The Stand Alone Load is reserved for cases where the Domain Manager is not available and a virtual volume must be loaded: When a NonStop server is cold loaded from a SIT virtual tape.
User Interface Stand Alone Load – Common elements Common page elements Port Type: FC is the only possible value Port Number: configuration. Identifies the port number connector in the VTC internal SCSI Lun: SCSI LUN ID assigned to the Guardian tape device by SCF (FC connections). Volume Label: volume label to load. Label Type: Label type of the volume. Data Store Type: TSM or Windows. This choice will change the fields presented to the user.
User Interface Stand Alone Load - Windows Data Store Page elements User Account: user account used to access the Windows disk pool remote paths. Password: account password. Use Restore Script: check to enable the execution of the restore script if a Windows disk file was archived and purged. If this box is checked, the user will have to enter additional elements. Fully Qualified Path of the Index File: Name of the path containing the index file (*.IND file) of the virtual volume.
User Interface Stand Alone Load - Windows File Data Store with Scripting Page elements Original Path of the Index File: If the index file (*.IND file) must be restored, the user must enter the path of the file when it was backed up. If this path cannot be used for restoring the index file (or the data file), the user must specify an Alternate Restore Path. Scripting: Fully qualified file name of the restore script to execute.
User Interface Alternate Restore Path: Used if the original path of the index file cannot be used for the restore of a file. Optional Script Parameters: up to 10 parameters, name (do not enter the % characters) and value, to pass to the script. They should normally be equal to the scripting parameters entered for the Data Store in the Domain configuration. Status pages The Home link opens with Status Summary page. This page displays the list of NonStop nodes, and a summary status of current operations.
User Interface Pending: Total number of pending mount requests. Assigned: Number of mount requests assigned to a device where the volume is being or already loaded, but still pending in MEDIACOM. In error: Number of mount requests for which the latest load attempt failed. VTC / Library name Identifier of the BackBox VTC where devices are attached. Devices Numbers about virtual devices. Devices: number of devices defined in this BackPak Domain.
User Interface In this case above the EMS Extractor is not running, there is no mount automation. Page elements Mount Requests Mount requests appear only if there are pending mounts in $ZSVR or if there is any BackBox generated pre-loads that are still unsatisfied. All pending mount requests are shown, including requests for tape volumes that are unknown in BackPak, such as requests for physical tape media. NonStop View The left part of a row shows the attributes of the mount request seen by MEDIACOM.
User Interface BackPak View The right part of a displayed row shows the attributes of a mount request managed by the BackPak Domain Manager. Volume in Domain: tells if the volume label is known in the BackPak domain. Request Type: $ZSVR for regular mount requests seen in MEDIACOM, PRELOAD for requests generated internally by BackBox. PRELOAD is a special BackBox feature for optimizing multi-volume restores, rarely used.
User Interface Port: Port type and port number (ex: SCSI-2, FC-0). TID/Lun: For SCSI or BRIDGE port: Target Id Device. For FC port: Lun. Volume: Virtual volume id, equal to the volume label for labeled volumes. Device State: Internal device state set by the VTC. NOT CONFIGURED – not configured by the internal VTC configuration ACTIVATED – initial communication received from the NonStop, but not yet the sequence produced by a SCF START TAPE command.
User Interface Mount Request detail This page shows all the details about a tape mount request, from both the NonStop view and the BackBox internal view. Buttons offer the possible actions on a mount request: Reject A MEDIACOM REJECT command is issued. The tape application will fail. Alter A MEDIACOM ALTER command is issued. DSM/TC or TMF will search for another SCRATCH volume. Load The load of the volume will be immediately attempted in BackBox. Close The window is closed without any action.
User Interface DSM/TC POOL: POOL assigned by the TAPECATALOG DEFINE. BackPak View The right part of a displayed row shows the attributes of a mount request managed by the BackPak Domain Manager. Request Type: $ZSVR for regular mount requests seen in MEDIACOM, PRELOAD for requests generated internally by BackBox, for multi-volumes restore when Preload is enabled in the Volume Group. Load attempts: Already executed load attempts. BackPak Mount Status: Internal status of the request.
User Interface Domain The Domain page allows changes to the Domain Manager and trace configuration. Page elements Domain ID: Unique name of the domain. It must match the Domain name entered in the VT Controller manager through the Domain Address tab. Location: Read-only element showing the NonStop disk subvolume where the BackPak Domain was installed. 132 BackBox H4.
User Interface Version: Read-only element showing the version of the BackPak NonStop component, that can be retrieved in a different format by the TACL command VPROC BBSV. The major version 04 and minor version 00 are split in the VPROC: Version procedure: T9999V04_16DEC2013_BPAKETI_00 Release: Read-only element showing the release date of the BackPak NonStop component, also visible in the VPROC output. EMS Collector: Guardian process name for the destination of the EMS log messages.
User Interface %DD% will be replaced by the day number %MM% will be replaced by the month number %YY% will be replaced by the year (two digits) %YYYY% will be replaced by the year (four digits) The statistic file is listed by the OBB018 obey file. The default file name at installation is STAT%YY%%MM% in the installation subvolume. Stats Retention: Number of months the statistics are kept.
User Interface To modify the Domain 1. Click the Domain tab. 2. In Domain ID and other fields, type the changes. 3. Click Update Domain. 4. Click Save Configuration to activate your changes. Alerts Setup To ease the automated monitoring of critical events, some EMS messages generated by BackPak can be duplicated by an Alert message that has a unique event number. For example, if this message is issued: “W3373 Mount-id \MONT.2243.
User Interface “W3171 Alert triggered by message ‘W3373 Mount-id \MONT.2243. Volume VRT15 is still not loaded after 60 minutes’” Alert can be enabled for some pre-defined events or group of events. It can also be enabled for a few user entered EMS event numbers, only BackPak generated EMS events can be selected.
User Interface VT Controller The VT Controller tabbed page contains the VTC configuration. The essential configuration of a VTC entity is: - Its TCPIP address that allows to reach it to send commands - The definition of operational tape drives, obtained by connecting the definitions known in the VTC and the definitions known in the NonStop host by SCF and CLIMCMD queries.
User Interface Page elements Top section: List of all VTCs configured on the current Domain, displayed even when no VT Controller is selected. Virtual Tape Controller Information section: Displays the attributes of the selected VTC. Click the Update button after any change to this section. VTC ports: List all physical ports prepared for BackPak operations inside the VTC. Nothing can be entered in this section.
User Interface Notes Some data comes from queries to the VTC: − General information such as Host name, OS and Version, version of BackBox software − VTC ports: List all physical ports prepared for BackPak operations inside the VTC, and their internal status. − Virtual Devices: List the virtual drives already configured in the domain, and their internal status.
User Interface ATTENTION: if above information change, you must click on the Update button to confirm change before saving the configuration. If not, change will be discards. Page elements coming from the license key This sub-section shows the limitations associated to this VTC, according the license key entered in the Domain page. SCSI ports: Maximum number of SCSI ports allowed to concurrently load tape volumes. More ports can be configured and associated tape devices started for fail-over purpose.
User Interface FC is for a Fibre Channel attachment BRIDGE is for a FC physical attachment on the VTC, up to a Bridge router that converts FC to two SCSI cables to be attached to NonStop legacy SCSI ports. For a BRIDGE, there are two VTC internal ports for the physical FC port (CH1 and CH2), each corresponding to a SCSI cable. RELAY is a special port where the VTC is just a pass-through between a NonStop host and other tape drives attached to the VTC.
User Interface For a SCSI or BRIDGE connection the user will also have to select the Guardian Port to fully identify the host port. The Node will be queried and all tape drives defined in SCF can be added (if Guardian Device is set to All available devices), or can add individual Guardian Device chose from the list. The GUI will automatically match the SCF and VTC definitions by the LUN and Target Ids.
User Interface 5. Virtual tapes can be updated or deleted individually in the list of Virtual drives. Attributes updatable: “Node”, “Guardian Device”, “Port”, “Target” or “LUN”, “VLE”, “Explicit Only” and “Reserved for”. Virtual Device Information Node: Guardian Node name of the NonStop server connected to the port. Guardian Device: Guardian tape device name defined in SCF.
User Interface VT Controller device reservations The Volume Class List page is opened when the "Reserved for" link of the VT Controller page is clicked. This page lists the Volume classes configured in Volume Groups and permits device reservation for one or several Volume classes. Page elements Device: Identifies the device for which reservations are entered. Volume class: identifies the possible volume classes. Check the classes for which the device must be reserved.
User Interface VT Controller Advanced properties Page elements Top section: List of all VTCs configured on the current Domain, displayed even when no VT Controller is selected. Advanced properties: Advanced properties of the selected VTC. Click the Update button after any change to the advanced properties. Advanced properties SSL Proxy ports The TCPIP ports for VTC services might have to be modified if a VTC is reached through the HP SSL proxy.
User Interface The TCPIP ports for VTC services might have to be modified if VTC is reached through the HP SSL proxy. This is the case when several VTCs are in the domain: all VTCs are configured with the same address of local proxy (127.0.0.1). To reach different VTCs, all port numbers configured in the local proxy clients must be different. Admin TCP port: Port for the Admin service. 8766 is required if VTC is not reached through HP SSL proxy.
User Interface Device Protocol: Reports if the tape drive is a Standard device handled by a regular Windows driver, or if the tape drive is an old Legacy drive without Windows driver. Operation of legacy drives requires a license option. Data Store The Data Store page contains information regarding the storage configuration for the virtual tape volumes. The initial view shows the list of existing Data Stores.
User Interface Page sections These sections will be documented in sequence. Data Store Information: Common properties of the selected Data Store. Windows Details, Windows Pool: regular properties of Windows File Data Stores Storage Route: For the selected Data Store, list of the VTCs that can access the storage, and therefore can be a route for a NonStop tape application to the virtual volumes. 148 BackBox H4.
User Interface Data Store Information Store ID: Identifies the Data Store. Must be unique and cannot be modified after it is added. If the Domain access (see below) is RESTRICTED or SECONDARY, this ID must be equal to the corresponding Data Store ID in the owner domain. Store Type: Indicates the type of Data Store and cannot be modified after it is added. Refer to the related section in the Configuration chapter for more details.
User Interface Administrative link: Optional URL of an administrative client for the Data Store. This Link will be available in the Storage Admin page. Data Store - Tivoli Storage Manager (TSM) Tivoli Storage Manager Detail section Node: TSM node name used by the VT Controller to log-in to the TSM Server. This node must be created manually by a TSM administrator. If omitted, the TSM client configuration file (dsm.opt) must contain node name and password. Password: Password associated with the TSM node.
User Interface TSM client Option File: Name of the DSM.OPT file the VTC will use as local TSM configuration for accessing a TSM Data Store. Must be a local file (C:\…) to allow a VTC operations when another VTC is down. This local file must be in the same location in all VTCs, for a given Data Store.
User Interface If the account is unqualified, ex: USER1, the VTC will execute a local Windows login. The account must exist in each VTC with the same password. Password: Password for the account above. Disk Space Warning Threshold (%): This parameter is used by the NonStop TACL macro BB022_CHECK_SPACE to check the total free space available in all Windows Data Stores. When the space occupied on disk is higher than this threshold, the EMS message 3217 is issued in the daily batch OBB017.
User Interface Storage Routes This section defines the routes to data, i.e. it lists the VTCs that are connected to the storage. Rank: Indicates the route priority. The highest priority is 1. See “Virtual volume mounts”, "Assign a tape device” section for description. VT Controller ID: Identifies the VTC connected to the selected Data Store.
User Interface request. Only local disks will be considerate as candidate as destination path. Load request is rejected if there is not enough space on local path – even if there is enough space on remote path. Scripting: Optionally specify a Windows command files to be executed following specific tape events. Refer to the section Scripting/Background Migration on Tapes Backup script: Command file to be executed after a volume unload.
User Interface The page layout varies, page sections are displayed depending on the type of Data Store and the type of tape catalog. The various page layouts are showed first, the page elements are then documented by page section. The sample above is for a group associated to a DSM/TC pool and a Primary Data Store The Advanced properties are common to all Volume Groups and documented at the end of this section.
User Interface Layout for Windows files – no tape catalog (or CA catalogs) See description of elements in “Page sections” after layouts. Layout for Windows files – DSM/TC catalog See description of elements in “Page sections” after layouts. 156 BackBox H4.
User Interface Layout for Windows files – QTOS catalog See description of elements in “Page sections” after layouts. Layout for Windows files – TMF catalog See description of elements in “Page sections” after layouts. 157 BackBox H4.
User Interface Layout for TSM – DSM/TC catalog See description of elements in “Page sections” after layouts. Page sections The sections are documented in the sequence below.
User Interface Data Store ID: Specifies in which Data Store the virtual volumes will be created. This value applies to new virtual volumes created in this group. It cannot be modified to change the location of volumes previously created. Primary Volume Group ID: Specify the corresponding Volume Group ID in the primary site, when its ID is different. This parameter is applicable only for SECONDARY Data Stores. Tape Catalog: Specify the volume catalog type (None, DSM/TC, TMF, QTOS or CA).
User Interface In progress Migration of historical backups from a legacy storage system to BackBox has started but is not completed. Tape applications access some tape volumes of the group in the legacy system, others volumes in BackBox. Being prepared Virtualizations are executed to copy the historical backups to the BackBox storage, but all NonStop backups and restores are still executed in the legacy storage system.
User Interface Guardian Node: Indicates the Guardian Node where TMF is running. (ex: \NODE1). Delete Backed up Files Delete Backed up files must be used with caution, especially when using Tivoli Storage Manager (TSM) with backup objects, see the manual BackBox VTC Scripting.. • Enables and controls the deletion of virtual volume Windows files that have been backed up by an Enterprise Backup software. A file is recognized as backed up if it’s archive bit is reset.
User Interface Compression algorithm: For Windows files Data Stores only, enables the software compression. Possible values: ZLIB –compression, higher CPU usage. None –no compression When the file server is a Data Domain appliance, refer to the Data Domain considerations in the Configuration chapter. TMF Audit Dump Class: This BackPak class will be assigned to volumes of this group. Max Volume Size (MB): Indicates the maximum capacity (compressed data in megabytes) of the virtual volumes.
User Interface Volume Group Advanced properties There is a single page layout for advanced properties of all Volume Groups. Advanced properties Pre Load: Pre-Load enabling. Enabling Pre-Load can be useful for the NonStop restore/recover of multi-volumes tape files, when a restore script must be executed before the volume can be read by the NonStop.
User Interface A Same node, any user-id G Same node, same group number O Same node, same user-id ? Use authorizations that were set at backup time . Disabled access ‘?’ is a special value that cannot be entered, but is displayed by the BackPak GUI for volumes that were created in a RESTRICTED Data Store.
User Interface Create Volume: Create and label new virtual volumes and add them to the domain catalog. Virtualize Volume: Copy the image of an external tape to a BackBox virtual volume, and add it to the domain catalog. Import from Tape Catalog: Register in the domain catalog volumes that are already known in a NonStop tape catalog such as DSM/TC. This does not move any volume data.
User Interface Volume List Use the Volume List page to list the domain virtual volumes. Output is limited to a “page size”, defined as a maximum number of returned volumes. Next and Previous buttons allow scrolling the complete list of volumes. The list can be filtered according selection criteria. Page elements Filter section: Used to select the volumes to list. List section: The list of volumes shows when the Display button is pressed.
User Interface Label Type: Filters volumes based on the label type. Current Operation: Current operation on the volume. Data Store: Filters volumes based on their Data Store. Volume Group: Filters volumes based on the Volume Group. Page size: Maximum number of volumes to return in the reply page. The user can browse a large list by ‘Previous’ and ‘Next’ buttons. Volume List The Volume List section displays the virtual volume list that matches the specified filter.
User Interface Volume Operations The Volume Operations tabbed page allows the user to identify a virtual volume and directly access the Volume Detail page. Page elements Label prefix: Indicates whether the volume is labeled or not. Volume Label: Volume label. Get Details button: Link to the Volume Detail page. 168 BackBox H4.
User Interface Volume Details The Volume details page displays the data available in the BackPak catalog for a virtual volume and allows requesting operations on it. Page elements Load button: Links to the Load page. Materialize button: Links to the Volume Materialization page. Edit button: Links to the Edit volume page. 169 BackBox H4.
User Interface Delete button: Deletes the virtual volume. Run Backup script link: Not shown if the script option is not licensed or the script is not configured. Click to run the backup script to backup this volume. Refresh link: Refreshes the data displayed. Volume Label: Identifies the virtual volume. Label Type: Label type, NL, ANSI, IBM, BACKUP or TMF.Data Store: Identifies the Data Store and its type. (WINDISK or TSM). Domain Access to Volume: PRIMARY: This is the usual value.
User Interface Last Load for Output section: Timestamp of the last load for output. Tape application process that requested the volume. Last Operation section: Timestamp of the last load. Tape application process that requested the volume. Operation type: LOAD, VIRTUALIZE, MOVE.. Pre load: Indicates if the volume was pre-loaded.
User Interface Until the first load, the owner is the user who created the volume in the domain catalog. When the Data Store is RESTRICTED, the owner kept in domain is used only for authorizing Control access. The access to data is controlled by the ownership copied along the volume data in the Data Store at backup time. Authorized Access: Authorizations set when the volume was created, last time the volume was loaded for output.
User Interface Volume Load The Volume load page allows to “manually” load a virtual volume on a NonStop tape drive outside the context of a mount request. IMPORTANT: the manual loading is normally initiated through the Home page and the Status for NonStop node page where the pending mounts are listed. The load will then execute in the context of the associated mount request. In this case, the Volume load page below is skipped because all parameters are provided by the mount request in $ZSVR.
User Interface The physical media capacity must be able to contain the whole virtual volume, check the volume detail page, “Data size” item. Page elements Status: Link to a Status page that will show all virtualizations and materializations on all VTCs that have configured physical/external tape drives. Volume label: Volume label to export.
User Interface Volume Details Update Page elements Volume Label: Volume label to update. Last Update: Date and time of the last update. Domain Access to Volume: Domain access to this specific volume. PRIMARY: Volume owned and regularly operated by the domain. SECONDARY: Volume replicated from a PRIMARY side. RESTRICTED: Volume owned by another domain.
User Interface Automatic Mount: Enable automatic mount if requested by Mediacom. Current Operation, Reset: Applicable if the volume is currently known as “in use”. Check to reset the current operation of the volume to . To be used as bypass, when the end of operation event was not registered by the BackPak domain. The current operation status (such as LOAD or MATERIALIZE) is set when an operation starts and is reset when the VT Controller returns feedback and statistics to the Domain Manager.
User Interface Create Volume The Create Volume page is used to create new volumes, label them, add them to the library and catalog them in an external catalog (i.e. DSM/TC or TMF) if needed. Page elements Volume Label: Specifies the label of the first volume to create. To create more than a single volume, the end of the label must be coherent with the “Quantity” and “Increment Base” below. Ex: 3 numeric digits are required to create 100 volumes in base 10. Label Type: Indicates the volume label type.
User Interface Tape Creation – Progress The Tape Creation - Progress page appears when the volume creation is in progress. A message is displayed when the process is complete. Virtualize Volume The Volume Virtualize page is used to clone physical or other legacy media to a BackBox virtual volume.
User Interface For a Non-Labeled volume, the BackPak name for this volume must be entered, and the virtualization is submitted for a single volume. For Labeled volumes, the label will be read from the physical media, and cannot be changed. The maximum volume size configured in Volume Groups must be able to contain the whole data of a physical media. The NonStop tape catalogs associated to the Volume Groups (TMF, DSM/TC or QTOS) are not updated.
User Interface VT Controller ID: VTC where physical tape devices are attached for reading the tape volumes. Tape Device: Select a device among physical tape devices configured in the VT Controller Advanced properties, or select “All tape devices”. Idle time out: Maximum time the VTC will wait for the first media and for a new media be loaded by the auto-loader or by a manual load before ending the Virtualization session.
User Interface Page layout, when Catalog searching is not enabled Labeled / Non-Labeled Volume: Type of media to virtualize. If Non-Labeled, the BackPak name for this volume will be requested. Feed-back The GUI will show this kind of message: I3385 Virtualization initiated on 1 devices in VTC VTC85. EMS will report the starting and the ending of the Virtualization session, and the processing of each volume. 15:03 \ETINIUM.
User Interface Virtualization / Materialization Status This page can be accessed by a link in the Materialization and the Virtualization pages. It shows all VTCs that have configured physical tape drives (or drives directly connected to a tier-party Virtual Tape System). For each listed VTC, the materialization / virtualization tasks that are running are listed. Page layout Page elements VTC name (Show/Hide Details…) The external devices are listed by VTC names.
User Interface Import from Tape Catalog This page is used to register in the BackPak catalog, volumes that are already known in a tape catalog on the NonStop: DSM/TC, TMF or QTOS. This is normally used in the first steps of a migration from a legacy storage system to BackBox, in which case only SCRATCH volumes will be registered. For a migration, the registration of ASSIGN volumes must be done by the other function “Virtualize Volume” that will both transfer data and register the volume.
User Interface I3447 Process $Z50C initiated to import scratch & released volumes from the catalogue DSM/TC volcat: \ETINIUM.TAPECAT, pool: BBOX_WIN1 (Volume group BBOX_WIN1). EMS messages are issued in batch to report the starting and the completion of the process. 11:23 29AUG13 222,01,207 BPAK-I3447 Process $Z50C initiated to import scratch & released volumes from the catalogue DSM/TC volcat: \ETINIUM.TAPECAT, pool: BBOX_WIN1 (Volume group BBOX_WIN1).
User Interface Storage Size: The total size of storage allocated for the volumes of the current Volume Group. This is the compressed size, for both WINDISK and TSM Data Stores. Average Compression ratio: (User Data Size) divided by (Storage Size). Number of Scratch Volumes: Only for Volume Groups associated to DSM/TC or TMF catalog. This is the number of SCRATCH volumes in this group.
User Interface Data Store Administration The Data Store Administration page displays a list of the configured Data Stores. Page elements Data Store: Data Store name. This is a link to the actual management of WINDISK Data Stores. TSM is managed through a IBM TSM administrative client. Type: Data Store type: WINDISK or TSM. Status: Activation status configured for the Data Store. Domain access: Domain access configured for the Data Store.
User Interface 2. The volumes entries are then “de-registered” from the original domain by a Catalog Detach. 3. Finally the domain access of the Data Store in the new domain is promoted from SECONDARY (or from RESTRICTESD) to PRIMARY to allow regular operations including backups. Page sections Report Location: Destination of the control report that will list the detached volumes. It can be a disk file name or a spooler specification such as $S.#BPAK.DETACH.
User Interface Page sections Storage route: choice of the VTC that will gather the information. The “1st available VTC” or a specific VTC can be chosen in the selection list Reply from: actual VTC that provided the data Summary: The sum of all files in all paths configured for the Data Store Detail Report: The sum of files distributed by: Path: List of paths configured in the Data Store (initial view).
User Interface The backup script is normally automated after each backup and if enabled, the script controller will automatically retry failed backups. Files marked as not backed up are usually either still being backed up or in the script controller input queue. This button is for re-submitting manually the backup scripts that have failed for reason unrelated to the software like communication or power failures.
User Interface Backup does not know the file; although a copy produced from the Spare pool by the backup script is present in the Enterprise Backup. Page elements for Detail Report by Path Pool: “Storage”, “Spare” or “Copy”. Disk #: Number of the physical disk, from 0 to n, in the Data Store. Paths in the same physical disk are listed together. The disk # is displayed only for the first path of a group of paths on the same disk..
User Interface Number of Non-Backed-Up Files: Number of files that have the archive bit set. This is not shown for StoreOnce NAS. Size of Non-Backed-Up Files (MB): Total size of Windows files with the archive bit set. This is not shown for StoreOnce NAS. Page elements for Detail Report by Volume Group Volume Group: Volume Group name of the volume stored on disks. Number of Files: Number of Windows files in all paths of the Data Store. Space used (MB): Total size of Windows files.
Appendix A – Encryption of BackBox TCP/IP control paths Appendixes Appendix A – Encryption of BackBox TCP/IP control paths SSL can be implemented on the BackBox TCP/IP control paths by use of HP NonStop SSL that provides an SSL tunnel through proxy processes on NonStop and Windows servers. The support of this software should be assessed from HP and/or ComForte in the context of its usage for BackBox. On older NonStop releases, this SSL software is available as the SecureCS product from ComForte company.
Appendix A – Encryption of BackBox TCP/IP control paths Sample SSL setup for BackBox Configuration of each connection (1) The NonStop TCPIP LISTNER configuration associates port 4561 to a specific BackPak Domain Manager (PORTCONF file). (2) In the NonStop, the SSL proxy server forwards incoming sessions from local port 14561 to address 127.0.0.1 port 4561 (3) In the GUI running on the workstation, 127.0.0.1 port 4561 is entered in the Domain Address Configuration.
Appendix A – Encryption of BackBox TCP/IP control paths (10) In VTC1, the SSL proxy server forwards incoming sessions from ports 18764-18766 to address 127.0.0.1 ports 8764-8766 In VTC2, the SSL proxy server forwards incoming sessions from ports 18764-18766 to address 127.0.0.1 ports 8764-8766 (11) In the NonStop, the SSL proxy client forwards incoming sessions from ports 18764-18766 to address 192.168.3.101 ports 18764-18766 from ports 28764-28766 to address 192.168.3.
Appendix A – Encryption of BackBox TCP/IP control paths RUN SWAP /NAME $SSLC/ PROXYS; CONFIG $DATA15.SSL.CFGSRV $DATA15.SSL.CFGCLI extract: PORT TARGETHOST TARGETPORT 18764 ,18765 ,18766, 28764 ,28765 ,28766 192.168.3.101, 192.168.3.101, 192.168.3.101, 192.168.3.102, 192.168.3.102, 192.168.3.102 18764 ,18765 ,18766, 18764 ,18765 ,18766 $DATA15.SSL.CFGSRV extract: PORT TARGETHOST TARGETPORT 14561 127.0.0.1 456 195 BackBox H4.
Appendix B – External tape devices installation Appendix B – External tape devices installation For materialization and virtualization, physical tape devices must be installed in a VTC and configured in the Windows operating system as regular tape devices. For virtualization, a second kind of external tape device can be installed, as direct connection between the BackBox VTC and another Virtual Tape System. See below how to install these two kinds of external tapes.
Appendix B – External tape devices installation Physical tape device attachment The tape drive must be physically connected to the VTC, and the appropriate Windows tape driver must be installed. If there is no Windows driver for the tape drive, the VTC is able to access the legacy drives in raw mode. A BackPak license option is required to access legacy drives. Auto-loaders are supported. The Windows Media Manager that existed in Windows-2003 Server must be uninstalled. 197 BackBox H4.
Appendix B – External tape devices installation Attachment to another Virtual Tape System Images of virtual tape volumes can be exchanged directly with a tier party Virtual tape unit. The transfer is possible only from the tier-party to the BackBox system, i.e. for virtualizations. Like the BackBox, other Virtual tape systems are able to materialize/virtualize. In addition the BackBox VTC is able to provide to the other system a device that appears as a physical tape drive.
Appendix B – External tape devices installation Controller). That will open a Windows Explorer dialog that will give you access to VTC configuration files. • The tape drives emulated for Virtualization are defined as tape drives emulated for a NonStop host. • The only difference in tape drives for virtualization is the mandatory keyword AUTOLOADER as type of the FiberPort identify as port connected to the external Virtual Tape System. • Use the LTO 4 tape devices emulation.
Appendix B – External tape devices installation LTO3 LTO3 LTO3 LTO3 LTO3 LTO3 LTO3 LTO3 Configuration in the BackPak Domain For both physical devices and devices emulated by the VTC for another Virtual Tape Syste
Appendix C – Migration to the BackBox product Appendix C – Migration to the BackBox product This appendix gathers general guidelines for migrating legacy tape storage to the BackBox product, with a focus on the tape volumes, their content and their registration in catalogues.
Appendix C – Migration to the BackBox product In these two cases, the media type of the volume catalogued in DSM/TC or CA must be modified when the volume is moved in the new environment. This change of media type is automatically done by BackPak, in DSM/TC only – not in CA, as part of the three migration functions (“Virtualization”, “Import from Tape Catalogue” and the Volume group “auto-import” feature).
Appendix C – Migration to the BackBox product Automatic load legacy system in the Can be kept running for the restores Must be stopped. Mount requests to execute manually in the legacy system Available functionality to migrate volumes to BackBox Migration of ASSIGNED volumes The data of these volumes must be converted to the BackBox format to be available for restore through BackBox.
Appendix C – Migration to the BackBox product In the Volume tab, the page “Import from Tape Catalog” allows to select the tape volumes that are SCRATCH in a tape catalogue and populate the BackPak own catalogue of virtual volumes. The imported volumes are ready for new backups. As the migration can lasts several months, it can happen that legacy volumes that were not SCRATCH initially expire before they are visualized. The “Auto-import” below will pick up these volumes.
Appendix C – Migration to the BackBox product When there is a migration, the “Migration to BackBox” is usually set to “In Progress”, corresponding to this sequence of stages: 1. Start-up: switch the writing of new backups to BackBox 2. Data of assigned volumes is acquired by BackBox. During this period, BackBox executes new backups, and restores from recent backups written by BackBox. For restoring from volumes not yet migrated, the legacy system must still be able to load volumes.
Appendix C – Migration to the BackBox product Initial status The BackPak configuration is assumed completed. The VTCs, the Data store and the Volume group paired to the DSM/TC, QTOS or TMF catalogue are configured. Be sure the Volume group is set for ‘Auto-import’, so volumes expired during the migration period and requested for a new backup will automatically be registered in BackPak and processed by BackPak.
Appendix C – Migration to the BackBox product "Automatically importing the SCRATCH volume %s requested by a backup, and found in the NonStop catalogue %s, (volume group: %s). Step-3: Stop using the legacy tape system − Register in the BackPak domain, the latest legacy volumes that have expired. BackPak GUI, Volume tab, choose the “Import from Tape Catalog” page, select the Volume group and ask for registering only SCRATCH volumes − Verify all the legacy volumes are now in the BackBox system.
Appendix D - VTC Services and internal configuration Appendix D - VTC Services and internal configuration On VTC server, several services are installed to provide BackBox functionalities. Here is a quick overview of them.
Appendix D - VTC Services and internal configuration The internal VTC configuration is stored in text files. To access these files, open the Start menu and expand up to reach the VTC Configuration folder (All Programs – BackPak – Virtual Tape Controller). That will open a Windows Explorer dialog that will give you access to VTC configuration files. 209 BackBox H4.
Appendix D - VTC Services and internal configuration These files should not be changed before communicating with the ETI-NET support, except BBFcEmulPortCfg.xml. File BBAdminAppCfg.xml Description Parameters for the service VTC Admin Changes are used only when the service is restarted. BBFcEmulAppCfg.xml Application parameters VTC Emulator (FC) for the service Changes are used only when the service is restarted. The service must be restarted only when the NonStop tape devices are stopped.
Appendix D - VTC Services and internal configuration BBAdminAppCfg.xml Sample Elements syntax ConfigApp Enumerate all available options. This element should not edit Option Represent an application option. Each Option element can be customized as following: name: this attribute is use to identify the option see the table to exhaustive list Element value depends of the option.
Appendix D - VTC Services and internal configuration BBFcEmulAppCfg.xml Sample Elements syntax ConfigApp Enumerate all available options. This element should not edit Option Represent an application option. Each Option element can be customized as following: name: this attribute is use to identify the option see the table to exhaustive list Element value depends of the option.
Appendix D - VTC Services and internal configuration BBSL.OPT Keyword COMPRESSION_LEVEL Description 0 to 9 Default 6 Parameter for ZLIB compression. 0 = disable compression 1 = best speed 9 = best compression.
Appendix D - VTC Services and internal configuration Keyword TRACING Description Value 0, 1, 4, 8, 12 or 16 Default 0 When active will create a file for each Virtual Volume loaded. The volume name will be used as file name. No trace will be activating in the VtLog.log file.
