Backup3G/Backup3G 5.1 Release Notes
From Documentation
| Revision as of 00:47, 17 August 2007 Moff (Talk | contribs) (→Running Remote Backups on Windows) ← Previous diff |
Revision as of 00:49, 17 August 2007 Moff (Talk | contribs) (→Notes) Next diff → |
||
| Line 74: | Line 74: | ||
| <br> | <br> | ||
| - | == Notes == | + | == Upgrading COSbackup 3.2.1 - 3.2.6 == |
| <br> | <br> | ||
Revision as of 00:49, 17 August 2007
Contents |
Overview and Features
Backup3G
Backup3G 5.1 ...
New features in backup3G
Simpler Job Configuration
- backup any size file using the CPIO format
- mark a drive as offline
Improved Auditing
Documentation
- A HTML or text document can be associated with a backup job, so end users can see what Policies and Procedures the backup is supporting.
- The user guide, release notes and other documentation can be viewed via your favourite browser.
Installation Requirements
Software prerequisites
To install and run backup3G 5.1 on a host, you must have:
- COSmanager 4.2.5 or newer already installed on the host (see the COSmanager User Guide for instructions)
- a backup3G distribution
- a valid license key for this host (see your COSmanager distributor if you don’t have a valid license key)
- sufficient disk space
- COSmanager Manager access, or equivalent
- the ability to open a root shell
Disk space required
| Software | Approximately 1.5 MB in the backup3G home directory. |
|---|---|
| Temporary Files | While installing backup3G: less than 1.5 MB, to hold a copy of the software distribution. While backup3G is running: less than 5 MB in /tmp. |
| Audit Trails | For the backup3G audit trail, about 10 - 50 MB in the system spool area. The actual amount will depend on the activity on your system (e.g. how many backups are run), and how often you archive and delete the log files. |
| For the operations audit trail, about 10 - 50 MB in the system spool area. The actual amount will depend on the activity on your system. | |
| For the configuration audit trail, about 10 - 50 MB in the system spool area. The actual amount will depend on the configuration activity on your system. | |
| Backup and Restore Logs | For the backup3g backup and restore logs, up to 200 MB for a small backup environments, or up to 1 GB for medium to enterprise backup environments in the system spool area. |
Running Remote Backups on Windows
The current backup3G release supports running remote backups and restores on Windows hosts which have the EWC (Enterprise Windows Client) 3.1.1 installed. This product may be purchased separately.
Related Software
The release of backup3G 5.1 coincides with the release of stacker3G 5.1 (module), VTL3G (module), DA_Oracle 5.1 (module) and duty3G 5.1 (application).
Upgrading COSbackup 3.2.1 - 3.2.6
Technical Notes: Using Backup3G 5.1
This section contains some technical notes, tips, and troubleshooting information to help you when installing or upgrading to Backup3G 5.1. Detailed information on setting up and using Backup3G can be found in the Backup3G User Guide V3.2.
Arbitrary commands can easily be run as part of a backup job
The scan method now defaults to multi-volume media scan, where the scan proceeds from the last tape in the set to the first.
To manually scan a single volume from the command line, you can still use the command:
FSdrive <drivename> scan
Media scan method removed
The scan method now defaults to multi-volume media scan, where the scan proceeds from the last tape in the set to the first.
To manually scan a single volume from the command line, you can still use the command:
FSdrive <drivename> scan
Media copy now configured as part of the backup job
There are now three ways to produce a duplicate set of a backup media volume set. In all cases the target drive must be of the same media type as the source drive.
- From the At-end command as defined for a backup job:
FScopy [-u] [-U] [-T <minutes>] [-r <retention>|-r <days>] <target drive>
This will copy the media set used for the current backup to a new media set in the target drive. The expiry date of the duplicate set is set to the same date as that of the backup job. This can be overridden by specifying “-r <retention>” or “-r <days>”.
If the target drive is likely to be busy when needed for creating a duplicate media set, a timeout parameter may be added to the above command, “-T <minutes>”. If this parameter is omitted and the target drive is busy, the media copy will fail.
- Via COSbackup interface, from the COSbackup button bar:
Media > select media set > Maintain > Copy
You will be prompted for the run mode, the source drive and the target drive. The retention defaults to that of the selected media set, but may be overridden.
When using manually loaded drives, unless the output media volume is preloaded in the target drive, a “Change media” will appear on the backup job monitor. To preload a scratch media volume, from the COSbackup button bar:
Drive > select target drive > Operations > Load scratch
- From the command line, as would be used by COStask or COSduty, or a 3rd party batch processing product:
FScopy -b [-u] [-U] [-T <minutes>] [-r <retention>|-r <days>] -s <media number> <source drive> <target drive>
The retention period must be defined in the retention table. If it is not, the retention of the duplicate set will be set to “forever”.
Restore steps may now be pre-configured
You may now initiate a restore via the command line. This may be used by COStask or COSduy to preconfigure specific application restores. The command is:
FSrestore -i|-b [-D <to directory>] [-h <to hostname>] [-v <drive>] [-M <method>] [-f <files>] [-d <directories>] [<media number>]
If any parameters are missing a prompt will be displayed requesting the missing values.
Warnings
- Scan and rewind steps must be removed.
Hardware and OS Dependencies
AIX 4:
TX
Appears:
Suggested actions:
Linux:
X
Appears:
Suggested actions:
Solaris:
X
Appears: “
Suggested actions:
Copyright © 1990-2007 Functional Software. All rights reserved.