Computer Associates International, Inc. |
2.0 Operating System Support
2.1 Base Product
2.2 Disk Staging Option
3.0 System Requirements
3.1 Base Product
3.2 Disk Staging Option
4.0 Installation Considerations
10.0 BrightStor ARCserve Backup for Mainframe Linux r11.5 Readme
D01226-1E
12.0 Operating System Support for BrightStor ARCserve Backup r11.5
12.1 Hardware Support
13.0 System Requirements for BrightStor ARCserve Backup r11.5
13.1 Advantage Ingres Database
13.2 Device Driver Support
13.3 Browser Support
13.4 Client Agent for Mainframe Linux
14.0 Installation Considerations for BrightStor ARCserve Backup r11.5
15.0 General Considerations for BrightStor ARCserve Backup r11.5
15.1 Advantage Ingres Database
16.0 Known Issues for BrightStor ARCserve Backup r11.5
17.0 Documentation Changes for BrightStor ARCserve Backup r11.5
Welcome to BrightStor® ARCserve® Backup for Mainframe Linux r11.5 SP1. This Readme file contains important information to help you with your implementation of the product, including installation considerations, operating system information, known issues, and how to contact Computer Associates Customer Support.
This service pack is cumulative, as is this readme. Information related specifically to this service pack has been identified separately from information originally included in the release of BrightStor ARCserve Backup for Mainframe Linux r11.5. For information included in the release of BrightStor ARCserve Backup for Mainframe Linux r11.5, see the sections following the BrightStor ARCserve Backup for Mainframe Linux r11.5 Readme section.
The following sections provide information about operating systems support added for this release.
Note: For information released with BrightStor ARCserve Backup for Mainframe Linux r11.5, see the section Operating System Support for BrightStor ARCserve Backup r11.5.
You can run BrightStor ARCserve Backup for Mainframe Linux on the following operating systems:
You can run the BrightStor® ARCserve® Backup Disk Staging Option on the following operating systems:
The following sections provide information about the minimum system requirements for BrightStor ARCserve Backup components added for this release.
Note: For information released with BrightStor ARCserve Backup for Mainframe Linux r11.5, see the section System Requirements for BrightStor ARCserve Backup r11.5.
You must have a minimum of 150 MB free disk space on the / file system and 450 MB free disk space on the BrightStor ARCserve Backup installation file system to install BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1.
The following sections provide the minimum system requirements for the BrightStor ARCserve Backup Disk Staging Option:
The following sections provide information to consider when installing BrightStor ARCserve Backup.
For information originally released with BrightStor ARCserve Backup for Mainframe Linux r11.5 and included in this release of BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1, see the section Installation Considerations for BrightStor ARCserve Backup r11.5.
If the disk becomes full in the volume, increase the amount of free disk space as soon as possible.
Note: For information released with BrightStor ARCserve Backup for Mainframe Linux r11.5, see the section General Considerations for BrightStor ARCserve Backup r11.5.
The following section provides information about issues known to exist in this release of BrightStor ARCserve Backup.
Note: For information released with BrightStor ARCserve Backup for Mainframe Linux r11.5, see the section Known Issues for BrightStor ARCserve Backup r11.5.
For information about changes to the documentation for BrightStor ARCserve Backup for Mainframe Linux r11.5, see the section Documentation Changes for BrightStor ARCserve Backup r11.5.
The following section provides information about items that have not yet been changed in the product documentation for BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1, but that affect the information in that documentation:
"For example: sqlingres <maintain_script.sql>"
This should be changed to the following:
"For example: sqlingres <maintain_script.sql"
Each guide in the documentation set has a unique Document Identification (DID) designation that appears on the title page of the guide. The DID consists of six characters that identify the guide, followed by a hyphen, followed by two characters that identify its edition and the language in which it is written. For example, D01223-2E identifies the second edition of the English version of the BrightStor ARCserve Backup for Mainframe Linux 11.5 Release Summary. If a third edition of this guide is published, the DID is incremented to D01223-3E.
The DID appears on the title page of PDF files. The DID without the hyphen also serves as the eight-character file name for PDF files on the product media and on SupportConnect. The DIDs and file names of the BrightStor ARCserve Backup guides are:
Guide Name | DID | filename |
---|---|---|
BrightStor ARCserve Backup for Mainframe Linux Release Summary | D01223-2E | D012232E.PDF |
BrightStor ARCserve Backup for Mainframe Linux Getting Started | D01224-2E | D012242E.PDF |
BrightStor ARCserve Backup for Mainframe Linux Administrator Guide | D01225-2E | D012252E.PDF |
Advantage Ingres Embedded Edition Administrator Guide | A00229-1E | A002291E.PDF |
BrightStor ARCserve Backup Client Agents Guide | D01165-2E | D011652E.PDF |
The DID for this readme file appears on a separate line under the readme title. The DID without the hyphen also serves as the readme file name on SupportConnect.
Note: For information about the documentation released with BrightStor ARCserve Backup for Mainframe Linux r11.5, see the section Documentation for BrightStor ARCserve Backup r11.5.
For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Customer Support at http://ca.com/support.
The following sections provide information originally released with BrightStor ARCserve Backup for Mainframe Linux r11.5 and included in this release of BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1.
Note: For information added to BrightStor ARCserve Backup for Mainframe Linux r11.5 and released with BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1, see the section Operating System Support.
You can run BrightStor ARCserve Backup on the following operating systems:
BrightStor ARCserve Backup supports the following processors in the Linux distribution:
BrightStor ARCserve Backup supports the following tape devices:
You can install the BrightStor® ARCserve® Backup Client Agent for Mainframe Linux on the following platforms:
Note: For information added to BrightStor ARCserve Backup for Mainframe Linux r11.5 and released with BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1, see the section System Requirements.
The following sections provide the minimum system requirements for BrightStor ARCserve Backup and its agents:
In addition, you must have the following installed on your machine:
Most Linux systems automatically install an Apache Web Server package. If an Apache Web Server package is not installed, the BrightStor ARCserve Backup for Mainframe Linux installation script prompts you to install it.
Some Linux systems install the C++ backward compatible library package by default. If the library package is not installed, the BrightStor ARCserve Backup for Mainframe Linux installation script prompts you to install it.
The Advantage™ Ingres® Database requires, at minimum, 1,700 MB total free disk space for all Linux platforms, if you install the following on the same file system:
The BrightStor ARCserve Backup for Mainframe Linux installation script provided on the installation media lets you provide an alternate temporary space if /tmp does not have sufficient space.
BrightStor ARCserve Backup supports z/OS device drivers. The device driver must satisfy the following requirements:
To use the z/OS Device driver, a TCP/IP connection is required.
nnnn TCP jobname NODELAYACKS
where nnnn is the port number dedicated to the OS/390 Tape Device driver and jobname is the name of the job or started task that is the OS/390 Tape Device driver, as in the following example of a port defined in the TCP/IP profile:
PORT 0001 TCP testone 0002 TCP testtwo 0101 TCP oneohone 0601 TCP BAB NODELAYACKS
BrightStor ARCserve Backup supports, at minimum, the following browsers:
The following are the minimum requirements for the Client Agent for Mainframe Linux:
The following section provides information to consider when installing BrightStor ARCserve Backup.
Note: For information to be considered when installing BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1, see the section Installation Considerations.
compat-libstdc++-295-2.95.3-81.s390.rpm
The following sections provide general information to consider when using BrightStor ARCserve Backup.
Note: For information to be considered when using BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1, see the section General Considerations.
The following sections provide general information relating to the Advantage Ingres database used by BrightStor ARCserve Backup.
You can extend the BrightStor ARCserve Backup internal database to multiple directory locations to allow for growth, if the underlying file system does not support large files (larger than 2 GB) or does not have enough space. Additionally, you can spread the directory locations across multiple disks to improve performance.
Note: If you use Advantage Ingres Version 2.0, you might need to extend the database to circumvent the 2 GB table size limitation. BrightStor ARCserve Backup uses Advantage Ingres Version 2.6, which does not have this limitation.
You can extend the BrightStor ARCserve Backup database during installation or at a later time. The extend_db utility, located in the $BAB_HOME/bin directory, is called automatically by the setup script or manually by the root user if performed after installation. The amount of information in the database dictates the time required by the utility to run.
At the time of the database upgrade, cadbd must be down and Advantage Ingres must be running.
If you are using Advantage Ingres Version 2.0, you must perform additional steps to complete the database extension. If you extend the database during setup, perform this procedure after installation:
To enter a command in the interface, press the ESC key. To move up, press Ctrl+K; to move down, press Ctrl+J.
Repeat this step until you have assigned all of the extended directories.
You must complete these steps before you can run extend_db again.
To recover the BrightStor ARCserve Backup Advantage Ingres database when Advantage Ingres has stopped working entirely, complete the following steps to reinstall Advantage Ingres and restore the latest data available.
Note: If only the BrightStor ARCserve Backup database stored in Advantage Ingres (cadbase) is affected, see the section Recovering cadbase While Advantage Ingres is Running.
# rm -rf /disc2/ingresii/ingres
Note: You can obtain Advantage Ingres home information from the INGRES_HOME_PATH variable in $BAB_HOME/config/cadbd.cfg or through the symbolic link $BAB_HOME/dbase/ingres. You can obtain any extended location from $BAB_HOME/dbase/extend_db.log.
$BAB_HOME/bin/cadbase_setup
access_db
Ensure that you have enough space. Create these directories on the file system that originally contained the Advantage Ingres database to reduce the chances of running out of disk space.
If you have multiple extended locations, check BrightStor.log and databaseBackup.log to obtain the correct session numbers and restore to the correct directory. This may not be in the order you expect, but the correct order is very important for successful recovery.
$BAB_HOME/sbin/stopingres
# cd /disc1/cadb-restore/s6/ingres/dmp # cp –r * /disc1/ingresii/ingres/dmp/
# cd /disc1/ingresii/ingres/data/default/iidbdb # rm –r *
# cd /disc1/ingresii/ingres/dmp/default/iidbdb # cp aaaaaaaa.cnf /disc1/ingresii/ingres/data/default/iidbdb
Important! If you do not perform this step, you receive an error when you run the cadbutil utility.
# cd /disc1/ingresii/ingres/dmp/default/cadbase # cp aaaaaaaa.cnf /disc1/ingresii/ingres/data/default/cadbase
$BAB_HOME/sbin/startingres
Note: If you start Advantage Ingres at this point, some processes do not start and generate error messages. These messages are normal at this point and you can safely ignore them. Press the Enter key or Ctrl+C to exit the error messages.
cadbutil –r iidbdb –c
/disc1/cadb-restore/s3/iidbdb/
cadbutil –r cadbase –c
/disc1/cadb-restore/s4/cadbase/
You have successfully recovered the Advantage Ingres database.
If only cadbase (the BrightStor ARCserve Backup database stored in Advantage Ingres) was lost or corrupted and if Advantage Ingres is still running, you do not need to reinstall Advantage Ingres. The following procedure restores the cadbase database:
# destroydb cadbase –ucadbase
If the destruction of cadbase is unsuccessful, manually remove all cadbase directories from the Advantage Ingres home and all extended locations and run destroydb again. It should be successful.
Note: You can obtain Advantage Ingres home information from the INGRES_HOME_PATH variable in $BAB_HOME/config/cadbd.cfg, or through the symbolic link $BAB_HOME/dbase/ingres. You can obtain any extended locations from $BAB_HOME/dbase/extend_db.log.
If, in the previous step, the initial attempt to destroy cadbase was unsuccessful, answer Yes, and use the same directory and locations as the extended locations.
# cd /disc1/cadb-restore/s6/ingres/dmp/default # cp –r cadbase /disc1/ingresii/ingres/dmp/default
# cd /disc1/ingresii/ingres/dmp/default/cadbase # cp aaaaaaaa.cnf /disc1/ingresii/ingres/data/default/cadbase
cadbutil –r cadbase –c
/disc1/cadb-restore/s4/cadbase/
You have successfully restored the BrightStor ARCserve Backup database.
To increase the performance of the FIND operation in the Restore Manager, use the optimizeingres utility. The optimizeingres utility calls the Advantage Ingres optimizedb utility on the more critical tables of the database.
WARNING: If the tables contain large amounts of data, the execution of the optimizeingres utility can take a considerable amount of time.
We strongly recommend that you run a minimum of two backups of all client machines for which the BrightStor ARCserve Backup server is responsible before executing the optimizeingres utility for the first time. This gives Advantage Ingres a basis for the type of data you will normally store in the database and allows the utility to update its own statistics about those tables. You should also use the utility whenever a large number of changes in the database have occurred. Changes that occur in the database include, for example, adding new hosts as clients or expiring tapes. There are no arguments to the optimizeingres utility. For example:
$BAB_HOME/bin/optimizeingres
During the installation or configuration of the Advantage Ingres database, you are asked for the size of the transaction log file. The following general guidelines help you decide what size is best for your environment:
If the database table's size is larger than 2 GB, ensure that your system's Allow Large File setting is enabled.
The following section provides information about issues known to exist in this release of BrightStor ARCserve Backup.
Note: For information about issues known to exist in BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1, see the section Known Issues.
http://HostName or IP Address:6060
where 6060 is the default web server port number assigned during csetup (use the host name or IP address of the system that you want to manage).
# ./setmaxconningres
For the new value to take effect after running this script, run stopingres to stop Advantage Ingres and run startingres to restart Advantage Ingres. You must be an Advantage Ingres user to run these two utilities.
export LC_CTYPE=en_US.8859-1
Updated guides will be available at http://ca.com/support.
Note: For information about changes to the BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1 documentation, see the section Documentation Changes.
The following section provides information about items that have not yet been changed in the product documentation, but that affect the information in that documentation:
-regenerate <adapter #> <scsi ID> <lun> <tape name> [ <random ID> <mm/dd/yyyy> ]
This option is for use with file system devices. It lets you regenerate a new volume header with a new name that you specify.
After you generate a new volume header, you can merge all of the sessions on the file system device into the BrightStor ARCserve Backup database. This capability lets you initiate restore operations from the file system device using the merged session data.
If you know the original tape name (<tapename>) and its random ID (<randomID>), you can reuse them such that the session records in the BrightStor ARCserve Backup database can reconnect to the volume without having to merge the session records again.
Use the <mm/dd/yyyy> parameter to specify the last backup date of SnapLocked data on the volume.
Restore by Tree-Restores a specific directory or drive from a display of files and directories that were backed up with BrightStor ARCserve Backup. Use this method when you do not know which media contains the data you need, but you know the machine from which the back up originated.
The Restore by Tree view displays only the last instance of a backup. To view and access all other instances, select the object that you want to restore and click the Version History button. If there are multiple partial backups of the same drive, the Restore by Tree view displays only the last backup. However, if there is a full volume backup of the drive available, the last full backup is displayed, instead of the last partial backup.
For example, if a drive contains two directories that were backed up on April 21 and April 28, and if a full backup of the drive was performed on April 1, only the April 1 backup appears in the Restore Manager.
To restore the April 28 instance of one of the directories, select the directory in the Restore by Tree view and click Version History. From the Version History dialog, select the April 28 instance and click Select.
The Restore by Tree view uses the BrightStor ARCserve Backup database; if the database engine is stopped, this method is not available.
Each guide in the documentation set has a unique Document Identification (DID) designation that appears on the title page of the guide. The DID consists of six characters that identify the guide, followed by a hyphen, followed by two characters that identify its edition and the language in which it is written. For example, D01223-1E identifies the first edition of the English version of the BrightStor ARCserve Backup for Mainframe Linux 11.5 Release Summary. When the second edition of this guide is published, the DID is incremented to D01223-2E.
The DID appears on the title page of PDF files. The DID without the hyphen also serves as the eight-character file name for PDF files on the product media and on SupportConnect. The DIDs and file names of the BrightStor ARCserve Backup guides are:
Guide Name | DID | filename |
---|---|---|
BrightStor ARCserve Backup for Mainframe Linux Release Summary | D01223-1E | D012231E.PDF |
BrightStor ARCserve Backup for Mainframe Linux Getting Started | D01224-1E | D012241E.PDF |
BrightStor ARCserve Backup for Mainframe Linux Administrator Guide | D01225-1E | D012251E.PDF |
Advantage Ingres Embedded Edition Administrator Guide | A00229-1E | A002291E.PDF |
BrightStor ARCserve Backup Client Agents Guide | D01165-1E | D011651E.PDF |
The DID for this readme file appears on a separate line under the readme title. The DID without the hyphen also serves as the readme file name on SupportConnect.
Note: For information about the documentation released with BrightStor ARCserve Backup for Mainframe Linux r11.5 SP1, see the section Documentation.
For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Customer Support at http://ca.com/support.