Data Protection for Progress OpenEdge 4GL. Using IBM Tivoli Storage Manager Version 4.0.2

Transcription

1 Data Protection for Progress OpenEdge 4GL Using IBM Tivoli Storage Manager Version

2 Summary of changes This section summarizes changes made to the Data Protection for Progress product and this publication. Changes to the text since the version are indicated by vertical lines ( ) in the margin to the left of the change. Technical changes for Version report of de-duplication information report of compression information report of encryption information size estimate is taken from the databases update of capacity in the filespace is taken from the size estimate of the database update of occupancy in the filespace is taken from the backup transfer man pages added to UNIX and Linux performance information reported in MB/s updatelicense tool added to mange licenses 2

3 About this guide The subject of this publication is Data Protection for Progress OpenEdge 4GL, a product provided by repostor. Data Protection for Progress OpenEdge 4GL performs online backups of Progress OpenEdge 4GL databases to Tivoli Storage Manager storage. Tivoli Storage Manager is a client-server licensed product that provides storage management services in a multi-platform computer environment. Who should read this guide The target audience for this publication are system installers, system users, Progress OpenEdge 4GL database administrators, Tivoli Storage Manager administrators, and system administrators. In this book, it is assumed that you have an understanding of the following applications: Progress Server Tivoli Storage Manager server Tivoli Storage Manager backup-archive client Tivoli Storage Manager Application Program Interface It is also assumed that you have an understanding of one of the following operating systems: AIX HP-UX Linux Solaris Operating Environment (hereinafter referred to as Solaris) 3

4 Publications This section lists related repostor publications. It also describes how to access repostor publications online. repostor.com 4

5 Support information If you have a problem with your software, you want to resolve it quickly. repostor provides the following ways for you to obtain the support you need: Progress Search for known Progress problems, workarounds, technotes, and other information. IBM Tivoli Storage Manager Search for known API errors, or other related TSM problems Workarounds, and other information Obtaing API fixes: You can locate the latest fixes that are already available for your product. Repostor Search for known Data Protector related problems, Obtaining fixes: You can locate the latest fixes that are already available for your product. Contacting repostor Software Support: If you still cannot solve your problem, and you need to work with someone from repostor, you can use a variety of ways to contact repostor Software Support. For more information about these three ways of resolving problems, see Appendix C. Support information. Repostor Data Protection Web site Technical support information and publications are available at the following address: By accessing the repostor home page, you can access subjects that interest you. You can also keep up-to-date with the newest repostor Data Protections product information. Repostor Data Protection for Progress OpenEdge 4GL Web site The repostor Data Protection for Progress OpenEdge 4GL Web site contains a knowledge base of articles and information related to backup and restore issues. Access this information at: 5

6 Conventions used in this book This guide uses several conventions for special terms and actions, operating systemdependent commands and paths. Typeface conventions This guide uses the following typeface conventions: Bold Commands, keywords, authorization roles, or other information that you must use. Example: Log on to the server as root user. italics Values or variables that you must provide. Emphasized words and phrases. Example: The node name of the production node and backup node must not be the same. bold italics Options and parameters. Example: Specify the value for the compression option. monospace Directories, parameters, URLs, and output examples. Example: The product is installed in the /usr/tivoli/tsm/client/ba/bin directory. UPPER CASE Environment variables associated with Tivoli Storage Manager, operating systems, or Progress Server. Example: Make sure the DSM_DIR environment variable is set correctly. 6

7 Reading syntax diagrams This section describes how to read the syntax diagrams used in this book. To read a syntax diagram, follow the path of the line. Read from left to right, and top to bottom. * The >>--- symbol indicates the beginning of a syntax diagram. * The ---> symbol at the end of a line indicates the syntax diagram continues on the next line. * The >--- symbol at the beginning of a line indicates a syntax diagram continues from the previous line. * The --->< symbol indicates the end of a syntax diagram. Syntax items, such as a keyword or variable, can be: * On the line (required element) * Above the line (default element) * Below the line (optional element). Syntax Diagram Description Abbreviations: Example Uppercase letters denote the shortest acceptable truncation. If an item appears entirely in uppercase letters, it cannot be truncated. You can type the item in any combination of uppercase or lowercase letters. In this example, you can enter KEYWO, KEYWORD, or KEYWOrd. Read syntax diagramskip visual syntax diagram>>-keyword >< Symbols: Enter these symbols exactly as they appear in the syntax diagram. * Asterisk { } Braces : Colon, Comma = Equal Sign - Hyphen () Parentheses. Period Space 7

8 Variables: Italicized lowercase items (var_name) denote variables. In this example, you can specify a var_name when you enter the KEYWORD command. Read syntax diagramskip visual syntax diagram>>-keyword--var_name >< Repetition: An arrow returning to the left means you can repeat the item. A character or space within the arrow means you must separate repeated items with that character or space. A footnote by the arrow references the number of times you can repeat the item. Read syntax diagramskip visual syntax diagram V >>---repeat >< Read syntax diagramskip visual syntax diagram V >>---repeat >< Read syntax diagramskip visual syntax diagram V (1) >>---repeat >< Notes: 1. Specify repeat as many as 5 times. Required Choices: When two or more items are in a stack and one of them is on the line, you must specify one item. In this example, you must choose A, B, or C. Read syntax diagramskip visual syntax diagram>>-+-a >< +-B-+ '-C-' Optional Choice: 8

9 When an item is below the line, that item is optional. In the first example, you can choose A or nothing at all. When two or more items are in a stack below the line, all of them are optional. In the second example, you can choose A, B, C, or nothing at all. Read syntax diagramskip visual syntax diagram>> >< '-A-' Read syntax diagramskip visual syntax diagram>> >< +-A-+ +-B-+ '-C-' Defaults: Defaults are above the line. The default is selected unless you override it. You can override the default by including an option from the stack below the line. In this example, A is the default. You can override A by choosing B or C. You can also specify the default explicitly. Read syntax diagramskip visual syntax diagram.-a-. >> >< +-B-+ '-C-' Repeatable Choices: A stack of items followed by an arrow returning to the left means you can select more than one item or, in some cases, repeat a single item. In this example, you can choose any combination of A, B, or C. Read syntax diagramskip visual syntax diagram V >>---+-A >< +-B-+ '-C-' Syntax Fragments: Some diagrams, because of their length, must fragment the syntax. The fragment name appears between vertical bars in the diagram. The expanded fragment appears between vertical bars in the diagram after a heading with the same fragment name. Read syntax diagramskip visual syntax diagram>>- The fragment name >< 9

10 The fragment name:.-a B-+ '-C-' 10

11 Chapter 1. Introducing Data Protection for Progress Overview of Data Protection for Progress OpenEdge 4GL Data Protection for Progress OpenEdge 4GL currently supports Progress OpenEdge 4GL databases with the Progress (probkup). See Chapter 2. Installing Data Protection for Progress OpenEdge 4GL for specific levels of supported Progress databases. 11

12 Chapter 2. Installing Data Protection for Progress OpenEdge 4GL AIX environment (64-bit) This section contains operating system, hardware, software, and communication requirements for installing Data Protection for Progress OpenEdge 4GL in an AIX 5/6/7L environment. Operating system requirements One of the following AIX operating systems: AIX 6.1 AIX 7.1 Hardware requirements Any RS/6000, pseries or IBM System p, iseries or IBM System i, or compatible workstation as supported by AIX Disk space: 8 MB Memory: 64 MB (128 MB or more recommended) Software requirements Tivoli Storage Manager API Version (or later) One of the following levels of Progress Server: Progress 11+ (64-bit or 32bit) Java 1.7 must be installed for GUI Communication methods TCP/IP Shared memory Note: Data Protection for Progress OpenEdge 4GL and the Tivoli Storage Manager server must be installed on the same machine in order for shared memory to work. TCP/IP must also be installed on the machine. Installing Data Protection for Progress OpenEdge 4GL on AIX 64-bit The installation uses standard AIX installation routines. Please refer to AIX installation guide for a complete guide. Prerequisite: Tivoli Storage Manager API must be installed Progress must be installed Environment DLC has to be set to point out the location of installation directory File $DLC/properties/conmgr.properties has to be configured in order to find all database instances "probkup","rfutil","proutil","prorest" and "sqlexp" has to be in search PATH Download: Get the latest version of the binaries from repostor. 12

13 Installation: 2. Log in as the root user. 3. Enter smitty install at the command prompt. 4. Select Install and Update Software. Press Enter. 5. Select Install and Update from ALL Available Software. Press Enter. 6. Enter. in the Entry Field for INPUT device / directory for software. Press Enter. 7. Highlight the SOFTWARE to install option. Press F4 to list available software. 8. Select the installable packages by performing the following: 1. Highlight the Data Protection for Progress package (rdp4progress) and press F7. 2. Highlight the Electronic License Agreement (rdp4progress.ela) and press F7. 1. Make sure you set ACCEPT new license agreements? to Yes. (The default is No). You can also specify the -Y option with the installp command. 2. Set Preview new license agreements? to No (the default value) for the installation to proceed. 3. If Preview new license agreements? is set to Yes, the installation will enter preview mode but Data Protection for Progress does not install. Preview new license agreements? must be set to No for Data Protection for Progress to install. After all five packages are selected, press Enter. 9. When the Install and Update from LATEST Available Software window displays, press Enter. 10. A window displays and prompts you with this message: ARE YOU SURE? Press Enter to continue the installation procedure. 11. After successfully installing Data Protection for Progress, press F10 to exit the smitty install environment. You can view the Summary for more information regarding the installation. 13

14 Linux x86 environment (64bit) This section contains operating system, hardware, software, and communication requirements for installing Data Protection for Progress OpenEdge 4GL in a Linux on Intel x86 64-bit environment. Operating system requirements One of the following levels of Linux 64-bit operating system: Red Hat Enterprise Linux 5 (64-bit) Red Hat Enterprise Linux 6 (64-bit) SuSE Linux Enterprise Server 10 (64-bit) SuSE Linux Enterprise Server 11 (64-bit) SuSE Linux Enterprise Server 12 (64-bit) Hardware requirements Any Intel x86 (or compatible) 64-bit workstation Disk space: 8 MB Memory: 64 MB (128 MB or more recommended) Software requirements Tivoli Storage Manager API Version (or later) Java 1.7 (or later) is required to run the gui program. One of the following levels of Progress Server: o Progress 11+ Communication methods TCP/IP Prerequisite: Tivoli Storage Manager API must be installed Progress must be installed Environment DLC has to be set to point out the location of installation directory File $DLC/properties/conmgr.properties has to be configured in order to find all database instances "probkup","rfutil","proutil","prorest" and "sqlexp" has to be in search PATH Installing Data Protection for Progress OpenEdge 4GL on Linux x86 This installation procedure is designed to install directly from the Data Protection for Progress OpenEdge file: 1. Log in as the root user. 2. Install the product using rpm $ rpm i rdp4progress-x.x.x-1.i586.rpm 14

15 HP-UX x86 environment (64bit) This section contains operating system, hardware, software, and communication requirements for installing Data Protection for Progress OpenEdge 4GL in a HP-UX on IA 64-bit environment. Operating system requirements One of the following levels of HP-UX 64-bit operating system: HP-UX (64-bit) HP-UX (64-bit) Hardware requirements Disk space: 8 MB Memory: 64 MB (128 MB or more recommended) Software requirements Tivoli Storage Manager API Version (or later) Java 1.7 (or later) is required to run the gui program. One of the following levels of Progress Server: o Progress 11+ Prerequisite: Tivoli Storage Manager API must be installed Progress must be installed Environment DLC has to be set to point out the location of installation directory File $DLC/properties/conmgr.properties has to be configured in order to find all database instances "probkup","rfutil","proutil","prorest" and "sqlexp" has to be in search PATH Communication methods TCP/IP Installing Data Protection for Progress OpenEdge 4GL on HP-UX This installation procedure is designed to install directly from the Data Protection for Progress OpenEdge file: 3. Log in as the root user. 4. Install the product using swinstall $ swinstall -s $(pwd)/rdp4progress-x.x.x 15

16 SUN environment This section contains operating system, hardware, software, and communication requirements for installing Data Protection for Progress OpenEdge 4GL in a SUN environment. Operating system requirements One of the following levels of SUN operating system: SUN Solaris (2.10,2.11) SUN OS (10,11) Hardware requirements Disk space: 8 MB Memory: 64 MB (128 MB or more recommended) Software requirements Tivoli Storage Manager API Version (or later) Java 1.7 (or later) is required to run the gui program. One of the following levels of Progress Server: o Progress 11+ Prerequisite: Tivoli Storage Manager API must be installed Progress must be installed Environment DLC has to be set to point out the location of installation directory File $DLC/properties/conmgr.properties has to be configured in order to find all database instances "probkup","rfutil","proutil","prorest" and "sqlexp" has to be in search PATH Communication methods TCP/IP Installing Data Protection for Progress OpenEdge 4GL on SUN This installation procedure is designed to install directly from the Data Protection for Progress OpenEdge file: 5. Log in as the root user. 6. Install the product using pkgadd $ pkgadd d rdp4progress-x.x.x 16

17 Chapter 3. Configuring Data Protection for Progress OpenEdge 4GL 1. Define the Tivoli Storage Manager options in the dsm.opt and dsm.sys files Log on to the system as root. AIX: # vi /usr/tivoli/tsm/client/api/bin/dsm.opt Linux/SUN/HP-UX: # vi /opt/tivoli/tsm/client/api/bin/dsm.opt Create the default tsm server stanza name SErvername backupserver Create the stanza in the dsm.sys file AIX: # vi /usr/tivoli/tsm/client/api/bin/dsm.sys Linux/SUN/HP-UX: # vi /usr/tivoli/tsm/client/api/bin/dsm.sys SE backupserver TCPSERVERADDRESS backupserver PASSWORDACCESS generate NODENAME hostname_progress 2. Register the Data Protection for Progress OpenEdge 4GL node to a Tivoli Storage Manager server If you have configured your backup server for open registrations, you can do this from the client. If not, you need to logon to the backup server. tsmserv> register node nodename password 17

18 1. Configure Data Protector using GUI Start the GUI # /opt/repostor/rdp4progress/bin/rdpgui Click on Setup Wizard 18

19 2. Add the nodenames and configurations to the list Fill in The TSM Node Name (NodeName) Location of dsm.opt file (OptFileName) The address to the TSM Server (TcpServerAddress) The port to the TSM Server (TcpPort) The location of the dsmerror, and dsmsched log files (LogDir) The retention time for the logfiles (LogRetention) o The username for this schedule service (Os User for service) o The password for this os user (OS Password for service) o The Domain name for this user (OS Domain for service) o (the above is only used in special cases) Click on Add to add this node to the list When added all nodes, click on Next 19

20 3. Add instances to the list Select the nodename from the list, and add all instances associated to this nodename Fill in The environment variable for DLC (the location of progress binary) Click on Add to add this instance, when you have added all instances, click on Next 4. Setup Click on Create opt, to create the dsm.opt file, and add the new stanza in dsm.sys (unix/linux) Create Config, to create the GUI configuration file Install Service, to install the startup programs (rc scripts, services) Authenticate, to authenticate to TSM (register node if openregistration) A status symbol will show the result, and Finnish button will be enabled when all activities has been completed. 20

21 Required options in the dsm.sys file Specify these options in the Tivoli Storage Manager client system options file (dsm.sys by default) located in the directory where the Tivoli Storage Manager API is installed: passwordaccess Specify whether you want to generate your password automatically or be prompted to enter your password. You can specify one of the following values: prompt You are prompted to enter your password during each session. This is the default value. generate The Tivoli Storage Manager API manages all password actions after the password is created. The Tivoli Storage Manager API stores and manages the password and automatically generates a new password when the current password expires. This method of password management is useful when running unattended scheduled backups because it ensures that the backup never fails due to an expired password. When specifying passwordaccess generate, set the following values in the in the dsm.sys file: passwordaccess generate nodename <node name> servername Specify the name you want to use to identify a stanza that contains the options used for connecting to the Tivoli Storage Manager server. Although the name does not have to be the actual name of a Tivoli Storage Manager server, the name must match the name specified by the servername option in the dsm.opt file. tcpserveraddress Specify the TCP/IP address (in the stanza) for the Tivoli Storage Manager server to be used for Progress backups. When the Tivoli Storage Manager server that is specified with the tcpserveraddress option uses a non-default port for communication, specify the correct port in the stanza with the tcpport option. commmethod Specify the communication method for Data Protection for Progress OpenEdge 4GL to communicate with the Tivoli Storage Manager server. Note that this option requires other Tivoli Storage Manager options, depending on the communication method you specify. Specify this option in the Tivoli Storage Manager client user options file (dsm.opt by default) servername Specify a Tivoli Storage Manager server stanza name that matches the name specified by the servername option in your client system options file (dsm.sys by default) that is used to contact Data Protection for Progress for backup services. 21

22 Other options to consider It is recommended that you specify these options in the Tivoli Storage Manager client system options file, dsm.sys: compression Specify whether the Tivoli Storage Manager API compresses data before sending it to the Tivoli Storage Manager server. You can specify yes or no. The default value is yes. The value of the compression option for Data Protection for Progress OpenEdge 4GL is honored only if the Tivoli Storage Manager administrator leaves the compression decision to the node. Enabling compression affects performance in three ways: CPU utilization is higher on the machine on which Data Protection for Progress OpenEdge 4GL is running. Network bandwidth utilization is lower because fewer bytes are transmitted. Storage usage on the Tivoli Storage Manager server is reduced. Considerations: It is recommended that you specify yes when any of the following conditions exist: The network adapter has a data overload. Communications between Data Protection for Progress OpenEdge 4GL and the Tivoli Storage Manager server are over a low bandwidth connection. There is heavy network traffic. It is recommended that you specify no when any of the following conditions exist: The machine running Data Protection for Progress OpenEdge 4GL has a CPU overload. The added CPU usage (as a result of enabling compression) can impact other applications, including the Progress server. You are not constrained by network bandwidth. In this case, you can achieve the best performance by specifying compression no and enabling hardware compaction on the tape drive, which also reduces storage requirements. Hardware compression is in use for the media where Data Protection for Progress OpenEdge 4GL data resides. After a completed backup operation, view the throughput rate and the compression status for a backup object in the Tivoli Storage Manager server activity log file. Run the Tivoli Storage Manager server QUERY ACTLOG command in the Tivoli Storage Manager server administrative client window. Be aware that the throughput rate and the compression status are not written to the activity log when activity logging is disabled on the Tivoli Storage Manager server. See the SET ACTLOGRETENTION command in the Tivoli Storage Manager Administrator's Reference for complete activity logging information. 22

23 enablelanfree Specify whether you run backup operations in a LAN-free environment if you are equipped to do so. You can specify yes or no. The default value is no. You can avoid network constraints by shifting the movement of data to a storage area network (SAN). After a completed backup operation, view the LAN-free status for a backup object in the Tivoli Storage Manager server activity log file. For more information, see the appropriate Storage Agent User's Guide. include Add an include statement to the dsm.sys file (used by the Progress node) when a management class (other than the default management class) is defined within an existing policy domain. This include statement binds the Progress backup objects to the management class that is defined for managing these objects. The include statement uses the following naming convention: /instance/database/type The default instance name is progress. And on this release you can do full/inc/log backups, type=full, type=inc or type=log. So if you have a database name, test and you want to exclude that from being backuped, you enter: EXCLUDE /progress/test/full The include statement in the dsm.sys file (used by the Progress node) would be as follows: INCLUDE /progress/.../full mgmtclassnamefordbs deduplication When deduplication is set to yes, Data Protector for Progress Open Edge 4GL will be enabled to use client de-duplication in TSM, if also the TSM Server is configured to retrieve client de-duplication information. Enable client deduplication can be done by this command: update node nodename deduplication=clientorserver. This option can be used in combination with compression yes to reduce bandwidth further. Note that the storagepool on the TSM Server has to be configured for deduplication. enableclientencryptkey When enableclientencryptkey is set to yes, Data Protector for Progress OpenEdge 4GL provides 128-bit transparent encryption of Progress databases during backup and restore processing. One random encryption key is generated per session and is stored on the Tivoli Storage Manager server with the object in the server database. Although Tivoli Storage Manager manages the key, a valid database must be available in order to restore an encrypted object. You can specify the databases you want encrypted by adding an include statement with the include.encrypt option in the dsm.sys file. For example, to enable transparent encryption, set the following options in the client system options file, dsm.sys: 1. Specify enableclientencryptkey yes. 2. Specify encryptiontype AES128 (recommended) or DES Specify the objects to encrypt. This example encrypts all data: include.encrypt /progress/.../* 23

24 Thus, the encryption options in this client system options file, dsm.sys would be as follows: enableclientencryptkey yes encryptiontype aes128 include.encrypt /progress/.../* After a completed backup operation, view the encryption status for a backup object in the Tivoli Storage Manager server activity log file. Run the Tivoli Storage Manager server QUERY ACTLOG command in the Tivoli Storage Manager server administrative client window. See IBM Tivoli Storage Manager Using the Application Program Interface for more details regarding the enableclientencryptkey option. 24

25 4. Define Tivoli Storage Manager policy requirements The Data Protector for Progress uses the following format when backup is performed: /instance/database/type Where instance, is the name of the Progress instance. Database, is the database name of the Progress database. Type is always full in current release, next release might have support for incremental, and transaction log backups. All backup objects inserted into the Tivoli Storage Manager backup storage pool have same file names, and uses the same normal mechanism as for standard file system backups. Backup copy group values You should consider Recover Point Objective, Recover Time Objectives before you continue this section. If you want to have 30 days kept for all your databases, and unlimited number of versions. Logon to the Tivoli Storage Manager. tsmserv> define policyset standard tsmserv> define domain Progress standard tsmserv> define managementclass Progress standard default tsmserv> assign defmgmt Progress standard default tsmserv> def co Progress standard default vere=nol verd=nol reto=30 rete=30 dest=backuppool tsmserv> validate policyset Progress standard tsmserv> activate policyset Progress standard After each backup from Data Protector for Progress OpenEdge 4GL the older versions of the backup objects becomes inactive, that object is deleted from the Tivoli Storage Manager server the next time expiration processing occurs. Note that an inactive backup object cannot be restored using the Data Protector for Progress OpenEdge 4GL interface. Notes: Data Protector for Progress OpenEdge 4GL accepts default values for these options. Management class Tivoli Storage Manager uses management classes to manage backups on the Tivoli Storage Manager server. When you back up a database, the default management class for your node is used. Because the policy requirements for Data Protector for Progress OpenEdge 4GL may be different from the desired settings for the regular Tivoli Storage Manager backup-archive clients, you must have a different management class defined for Data Protector for Progress OpenEdge 4GL. It is recommended that you define a separate policy domain where the default management class has the required settings and then register all Data Protector for Progress OpenEdge 4GL nodes to that domain. If you choose to define a new management class within an existing policy domain (not the default management class for that domain), then you must add an include statement to the Data Protector for Progress OpenEdge 4GL options file to bind all objects to that management class. The following steps assign a management class name PRObackup to all Progress backups: 1. Add this inclexcl entry under the server stanza you use in the dsm.sys file: inclexcl /progress/include.def 25

26 2. Add this include entry to the /progress/include.def file: include /progress/.../* PRObackup Note: The file space name in the include/exclude statement must match the instance/database in order to work. All the files backed up are assigned to management class PRObackup. Note: Data Protector for Progress OpenEdge 4GL stores all objects as backup objects on Tivoli Storage Manager storage, so an archive copy group is not required, although it can exist. See your Tivoli Storage Manager administrator or see the Tivoli Storage Manager Administrator's Guide for more information on defining or updating Tivoli Storage Manager policy domains and copy groups. 26

27 Chapter 4. Using progressbackup and progressrestore You can perform full online backups with Data Protector for Progress. Once you identify which database to back up, Progress locates all necessary data and sends them to the Tivoli Storage Manager server through Data Protector for Progress. As a result, Data Protector for Progress provides an interface between Progress (probkup) and Tivoli Storage Manager API routines. Full Backup database empty1 to Tivoli Storage Manager # progressbackup s empty1 f Full Backup of all databases to Tivoli Storage Manager # progressbackup a -f Incremental Backup database empty1 to Tivoli Storage Manager # progressbackup s empty1 -i Transaction log Backup database empty1 to Tivoli Storage Manager # progressbackup s empty1 -l Restore database empty1 from Tivoli Storage Manager # progressrestore -s empty1 Restore database empty1 to :00 from Tivoli Storage Manager # progressrestore s empty1 t :00:00 27

28 Chapter 5. Using the utilities This chapter describes how to use the Data Protector for Progress OpenEdge 4GL utilities (progressquery) from the command line interface. These utilities are located in the directory where Data Protector for Progress OpenEdge 4GL is installed. The progressquery utility is used for query the Tivoli Storage Manager for all existing backups. Query all existing full backup versions from Tivoli Storage Manager for database empty1 # progressquery s empty1 -f 28

29 Command line reference progressbackup Syntax >>-progressbackup s database >< '- -S instance -' '- -a ' - -f - '- -v -' - -i - '- -l -' Optional parameters -S instance Choose the instance name to backup. Default is progress. Note that this is only the namespace used in tsm (/instance/) You have to set the environments to the DLC your self. -s database Choose which database to backup. -a Backup all databases. -f Do a full backup of the chosen database, this is the default. -i Do an incremental backup of the chosen database. -l Do a log backup of the chosen database. Requires enabled AI (After Images). -v Verbose information 29

30 progressrestore Syntax >>-progressrestore s srcdb > '- -S srcinst -' '- -a ' '- -D destinst -' > >< '- -d destdb -' '- -t YYYY-MM-DD.HH:MM:SS -' '- -v -' Optional parameters -S srcinst Choose which instance to restore from. -s srcdb Choose which database to restore from. -D destinst Choose which destination instance to restore to. Note you have to set the DLC environment. -d destdb Choose which database to restore to. -v Verbose information -t YYYY-MM-DD.HH:MM:SS Choose date and time for the restoration. It will pick the latest available full backup version from the date and time specified and restores that version into Progress. And will continue to load the incremental backups into progress (it any). And continue with AI (After Images) / transaction logs into progress (if any) until the time has been reached in progress. To see which versions are available, see the output of the Progressquery command. 30

31 progressquery Syntax >>-progressquery s srcdb >< '- -S srcinst -' '- -a ' - -f - '- -v -' - -i - '- -l -' Optional parameters -S srcinst Select instance to query against TSM -s srcdb Select database to query against TSM. -a Query all databases stored in TSM -f Query only full backup versions -i Query only incremental backup versions -l Query only log backup versions -v Verbose information 31

32 Appendix A. Quick configuration guide This section provides instructions on how to perform a quick configuration of Data Protector for Progress OpenEdge 4GL on an AIX 64-bit machine. This procedure uses default settings and requires minimal configuration tasks. It minimizes set up time and allows you to proceed quickly to a state where you can begin backing up your Progress databases. Note that you must change the installation paths and library extensions documented in this procedure if you are using an operating system other than AIX 64-bit. See page Chapter 3. Configuring Data Protector for Progress for detailed instructions on how to customize Data Protector for Progress for your environment and processing needs. 1. Install Data Protector for Progress. Detailed installation instructions are available on page Chapter 2. Installing Data Protector for Progress OpenEdge 4GL. 2. In /usr/tivoli/tsm/client/api/bin64/,create a dsm.opt file. Edit the dsm.opt file to include the following server stanza: SErvername Progress o More information about this option and the dsm.opt file is available on page 3. Define Tivoli Storage Manager options in the dsm.opt and dsm.sys files. 3. Change to the /usr/tivoli/tsm/client/api/bin64 directory and create a symbolic link to /usr/tivoli/tsm/client/ba/bin/dsm.sys. Edit the dsm.sys file to include another server stanza with the following options: 4. SErvername Progress 5. COMMMethod TCPip 6. TCPServeraddress x.x.x.x 7. PASSWORDAccess generate nodename hostname_progress Replace x.x.x.x with the IP address of the Tivoli Storage Manager server to which Data Protector for Progress will back up data. o More information about the dsm.sys file, these options, and their relationship with Data Protector for Progress is available on page 3. Define Tivoli Storage Manger options in the dsm.opt and dsm.sys files. 8. Register the node to the Tivoli Storage Manager server with the following command: REG NODE hostname_progress password maxnummp=2 Where hostname is the name of the machine where Data Protector for Progress OpenEdge 4GL is installed and password is the password for this node. 9. Make sure the Progress user has the following permissions: o Read (r) permission to the /usr/tivoli/tsm/client/api/bin64 and o /usr/tivoli/tsm/client/api/bin64 directories. Read permission (r-) to the dsm.opt, and dsm.sys files located in the /usr/tivoli/tsm/client/api/bin64 directories. 32

33 33

34 license administration A new tool too administrate licenses has been added. It is recommended to use this tool to add / move licenses. updatelicense Syntax >>-updatelicense--+- PERM key ---+->< +- EXPIRE '- UNLOCK key -' Required parameters PERM key The license key to apply on this machine as received from repostor. Note that the key can only be used on one machine. EXPIRE This is used to move a license from one host to another. You will see a transition key in the backup log when next backup has been performed. Use this transition key to get a new license from repostor. The license will only work for 30 days after this status has been entered. UNLOCK key Use this parameter if you have received an invalid license key, or by mistake entered wrong license key. Note that the license key has to come from repostor on request using a valid support contract. The key can only be used to unlock the host for 7 days. TEMP key is automatically generated when the first backup is executed if no licenses has been used before on the machine. 34

35 Example of use cases. To enter a permanent license # updatelicense PERM xxxxxx To move a license to another machine On source machine: root@srchost# updatelicense EXPIRE Do a backup root@srchost# progressbackup -a Retrieve the TRANSITIONKEY from output of backup job Send a request for a new license according to our routines Include: FROMHOST: source hostname TOHOST: destination hostname TRANSITIONKEY: as output in backup log 35

36 Appendix B. Using the Tivoli Storage Manger scheduler This section describes how to use the Tivoli Storage Manager scheduler with Data Protector for Progress to automate online backups of Progress server databases. The example illustrates the use of the Tivoli Storage Manager Version 5.5 backup-archive client scheduler. Considerations The Tivoli Storage Manager backup archive client must reside on the same machine as Data Protector for Progress OpenEdge 4GL for the Tivoli Storage Manager scheduler to function. After Data Protector for Progress has been registered to a Tivoli Storage Manager server and installed on the Progress server, perform these steps: 1. On the Tivoli Storage Manager server: a. Define a schedule to run an AIX, HP-UX, Linux, or Solaris scheduler backup script (schedbkdb.scr) in the policy domain to which Data Protector for Progress OpenEdge 4GL is registered. b. Associate the Data Protector for Progress OpenEdge 4GL node to the defined schedule. 2. On the machine where Data Protector for Progress OpenEdge 4GL is installed: a. Create a single dsm.sys file from which to associate nodes for your client, Data Protector for Progress OpenEdge 4GL, and scheduled backups. b. Create the scheduler backup script (schedbkdb.scr). This is the script that the Tivoli Storage Manager scheduler invokes directly. c. Create a command script (PROched.scr). This is the script that contains the Progress environment information and invokes the Progressbackup command. d. Start the scheduler. Setting up a schedule For consistency, this procedure uses specific information. However, you can define a command file with any set of commands you choose. This allows you to use the same command file to define schedules on other Tivoli Storage Manager servers. All command information is presented as command-line interface entries. This schedule in this procedure contains the following settings: The Data Protector for Progress node name is NodeA1. The password for node name NodeA1 is PasswordA1. The policy domain to which node name NodeA1 is registered is PolicyA1. The schedule is a daily backup of an online Progress database. The scheduled backup begins between 9:00 and 9:15 PM. 36

37 Part I: On the Tivoli Storage Manager Server 1. Define the following schedule on the Tivoli Storage Manager server. You can enter the command on the Tivoli Storage Manager server console or on an Administrative Client. The Administrative Client does not have to be running on the same system as the Tivoli Storage Manager server. 2. define schedule PolicyA1 daily_probackup description="08daily Online DB Backup" 3. action=command objects="/usr/repostor/rdp4progress/schedbkdb.scr" 4. starttime=21:00 duration=15 durunits=minutes period=1 perunits=day dayofweek=any The following message must display before proceeding to Step 2: ANR2500I Schedule daily_probackup defined in policy domain PolicyA1. 5. Issue the following command to associate the Data Protector for Progress OpenEdge 4GL node to the backup schedule defined in Step 1: define association PolicyA1 daily_probackup NodeA1 The following message must display before proceeding to Part II: ANR2510I Node NodeA1 associated with schedule daily_probackup in policy domain PolicyA1. Summary: o o o o o A backup schedule is now defined on the Tivoli Storage Manager server. The backup schedule will run the scheduler backup script (schedbkdb.scr), which will run the command Progressbackup. The backup is performed once a day around 9:00 PM. The backup schedule can start on any day of the week. You can run the Tivoli Storage Manager query schedule and query association commands to confirm that the schedule and node association are set correctly. Part II: On the client machine (NodeA1) This example assumes: The Tivoli Storage Manager backup-archive client is installed on NodeA1 in the /usr/tivoli/tsm/client/ba/bin directory. Data Protector for Progress OpenEdge 4GL is installed on NodeA1 in the /usr/repostor/rdp4progress/bin directory. An AIX operating system is used. Scheduling Data Protector for Progress OpenEdge 4GL backups with the Tivoli Storage Manager scheduler requires special configuration issues to be addressed. This procedure addresses this issue by creating a dsm.sys file from which to associate nodes for your client, Data Protector for Progress OpenEdge 4GL, and scheduled backups: 37

38 1. Create a dsm.sys file in the /usr/tivoli/tsm/client/ba/bin directory (if one does not already exist) and add the following servername stanzas: a. Add a servername stanza for the file system backups associated with your Tivoli Storage Manager backup-archive client. For example: servername TSMbackup commmethod tcpip tcpserveraddress site.xyzinc.com tcpport 1500 nodename client passwordaccess generate The servername TSMbackup setting must be specified in the dsm.opt file associated with the Tivoli Storage Manager backup-archive client. The default directory location is /usr/tivoli/tsm/client/ba/bin. b. Add a servername stanza for the backups associated with Data Protector for Progress OpenEdge 4GL. For example: servername TSMProgress commmethod tcpip tcpserveraddress site.xyzinc.com tcpport 1500 nodename NodeA1 passwordaccess generate c. Add a servername stanza for the scheduled backups associated with Data Protector for Progress OpenEdge 4GL. For example: servername DPSched commmethod tcpip tcpserveraddress site.xyzinc.com tcpport 1500 nodename NodeA1 passwordaccess generate 2. Make sure there is a symbolic link to this dsm.sys file so that the file is available to the Tivoli Storage Manager API directory (/usr/tivoli/tsm/client/api/bin64). 3. Create the scheduler backup script (schedbkdb.scr) in the /usr/repostor/rdp4progress/bin/ directory. This is the scheduler backup script that was defined for the scheduler in Step 1 in Part I: On the Tivoli Storage Manager server. This scheduler backup script will run the command script (PROched.scr), which will run the Progressbackup command. This is an example of the scheduler backup script (schedbkdb.scr): #!/bin/ksh PATH=$PATH:/opt/repostor/rdp4Progress/bin progressbackup u backup -a 38

39 4. Login as the root user to the machine where Data Protector for Progress OpenEdge 4GL is installed as node name NodeA1. 5. Start the scheduler in the inittab. Use the servername parameter to specify the correct stanza to use in the dsm.sys file: dsmc sched -servername=dpsched Data Protector for Progress OpenEdge 4GL is now enabled for scheduled backups. 39

40 Appendix C. Support information If you have a problem with your repostor software, you want to resolve it quickly. This section describes the following options for obtaining support for repostor software products: What to do when you encounter a problem Searching knowledge bases Obtaining fixes Receiving weekly support updates Contacting repostor Software Support Contacting IBM Software Support What to do when you encounter a problem If you encounter a problem while using Data Protector for Progress or if you cannot start Data Protector for Progress, do the following: 1. Run the progressbackup X v -s empty1 2. If the above command failed, check the dsierror.log files, dsmerror.log files, and the output from the command. The dsierror.log is generated by the Tivoli Storage Manager API when a problem occurs with the Tivoli Storage Manager API setup. 3. If the problem persists, gather the following information: a. A problem description file that includes the command you used and the session output you received when the problem occurred. b. The dsm.opt file c. The dsm.sys file d. The output from the Data Protector for Progress OpenEdge 4GL command The value of the Tivoli Storage Manager API errorlogname option specified in the dsm.sys file. e. The Tivoli Storage Manager API error log file (dsierror.log) in the following location (listed from highest to lowest precedence): The value of the Tivoli Storage Manager API errorlogname option specified in the dsm.sys file. Make sure errorlogname specifies a directory and file name with Read/Write permissions for the Progress user. 40

41 The value of the DSM_LOG environment variable. f. The Tivoli Storage Manager API trace file To generate the Tivoli Storage Manager API trace file, add the following lines in your dsm.opt file: tracefile /home/progress/tsmapi.out traceflag service g. The node information on the Tivoli Storage Manager server. To obtain this information, enter: query node <nodename> format=detail h. The Tivoli Storage Manager server activity log. To obtain this information, enter this Tivoli Storage Manager administrator command: query actlog Note that this command provides one previous hour of activity. Since the activity log should be obtained for the time period immediately prior to the failed operation until a few moments after the failed operation, you can specify the following settings to obtain activity for the exact time of failure: query actlog begindate=mm/dd/yyyy begintime=hh:mm:ss i. The output from the Data Protector for Progress OpenEdge 4GL command To generate the necessary information for Data Protector for Progress OpenEdge 4GL, run: Progressbackup D s master -v 41

42 Obtaining fixes A product fix might be available to resolve your problem. To determine what fixes are available for your repostor software product, follow these steps: TSM API: 1. Go to the IBM Software Support Web site at 2. Click Downloads and drivers in the Support topics section. 3. Select the Software category. 4. Select a product in the Sub-category list. 5. In the Find downloads and drivers by product section, select one software category from the Category list. 6. Select one product from the Sub-category list. 7. Type more search terms in the Search within results if you want to refine your search. 8. Click Search. 9. From the list of downloads returned by your search, click the name of a fix to read the description of the fix and to optionally download the fix. For more information about the types of fixes that are available, see the IBM Software Support Handbook at Data Protector for Progress OpenEdge 4GL: 10. Go to the repostor Software Support Web site at 42

43 Receiving weekly support updates from IBM To receive weekly notifications about fixes and other software support news, follow these steps: 1. Go to the IBM Software Support Web site at 2. Click My support in the upper right corner of the page. 3. If you have already registered for My support, sign in and skip to the next step. If you have not registered, click register now. Complete the registration form using your e- mail address as your IBM ID and click Submit. 4. Click Edit profile. 5. In the Products list, select Software. A second list is displayed. 6. In the second list, select the product segment, Storage Management. A third list is displayed. 7. In the third list, select the product sub-segment, Data Protector. A list of applicable products is displayed. 8. Select the products for which you want to receive updates, for example, IBM Tivoli Storage Manager for Databases. 9. Click Add products. 10. After selecting all products that are of interest to you, click Subscribe to on the Edit profile tab. 11. Select Please send these documents by weekly Update your address as needed. 13. In the Documents list, select Software. 14. Select the types of documents that you want to receive information about. 15. Click Update. If you experience problems with the My support feature, you can obtain help in one of the following ways: Online Send an message to erchelp@ca.ibm.com, describing your problem. By phone Call IBM-4You ( ). 43

44 Contacting IBM Software Support IBM Software Support provides assistance with product defects. Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have: For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational products, as well as DB2 and WebSphere products that run on Windows or UNIX operating systems), enroll in Passport Advantage in one of the following ways: Online Go to the Passport Advantage Web site at Passport_Advantage_Home and click How to Enroll. By phone For the phone number to call in your country, go to the IBM Software Support Web site at and click the name of your geographic region. For customers with Subscription and Support (S & S) contracts, go to the Software Service Request Web site at For customers with IBMLink, CATIA, Linux, OS/390, iseries, pseries, zseries, and other support agreements, go to the IBM Support Line Web site at 44 For IBM eserver software products (including, but not limited to, DB2 and WebSphere products that run in zseries, pseries, and iseries environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eserver software products, go to the IBM Technical Support Advantage Web site at If you are not sure what type of software maintenance contract you need, call IBMSERV ( ) in the United States. From other countries, go to the contacts page of the IBM Software Support Handbook on the Web at and click the name of your geographic region for phone numbers of people who provide support for your location. To contact IBM Software support, follow these steps: 1. Determining the business impact 2. Describing problems and gathering information 3. Submitting problems Contacting repostor Software Support Send mail to support@repostor.com