Backup3G/COSbackup 3.2.3 Release Notes
From Documentation
(Difference between revisions)
| Revision as of 02:10, 4 May 2006 Daniels (Talk | contribs) ← Previous diff |
Revision as of 02:28, 4 May 2006 Daniels (Talk | contribs) Next diff → |
||
| Line 1: | Line 1: | ||
| - | Release Notes for COSbackup 3.2.3 (Patch)—November 1999 Page 1 | + | == Features == |
| - | Release Notes for COSbackup 3.2.3 (Patch) | + | Implementation of the Patch applies fixes according to solutions described in the attached table - please refer for full details. |
| - | Features | + | |
| - | Implementation of the Patch applies fixes according to solutions described in the attached table - | + | Fixes included in this Patch are cumulative including prior patches. |
| - | please refer for full details. Fixes included in this Patch are cumulative including prior patches. | + | |
| They are: | They are: | ||
| - | • expiring media may leave unused contents files in the COSbackup media database | + | *expiring media may leave unused contents files in the COSbackup media database |
| - | • print error when media catalogue is printed from at-end command | + | *print error when media catalogue is printed from at-end command |
| - | • unable to restore files bigger than 2 gigabytes on Dynix/ptx when using TAR or DUMP | + | *unable to restore files bigger than 2 gigabytes on Dynix/ptx when using TAR or DUMPmethods |
| - | methods | + | *multi-volume scan may only scan a subset of the tape files |
| - | • multi-volume scan may only scan a subset of the tape files | + | *waiting for drive during a media copy may time out even though drive is available |
| - | • waiting for drive during a media copy may time out even though drive is available | + | *during a multi-step, multi-part restore a read error occurs, repositioning on media for restoreof subsequent step may be incorrect |
| - | • during a multi-step, multi-part restore a read error occurs, repositioning on media for restore | + | *all fixes in COSbackup 3.2.2 patch |
| - | of subsequent step may be incorrect | + | **unclear details logged or displayed in monitor about media duplication |
| - | • all fixes in COSbackup 3.2.2 patch | + | **media copy hangs if using drivepools |
| - | • unclear details logged or displayed in monitor about media duplication | + | **media copy does not wait for target drive to become available |
| - | • media copy hangs if using drivepools | + | **retention for duplicated media same as source |
| - | • media copy does not wait for target drive to become available | + | **auto job acknowledgement implies auto unload |
| - | • retention for duplicated media same as source | + | **log file title displayed as “db_lock: waiting for the drive” |
| - | • auto job acknowledgement implies auto unload | + | **FSdump backup method uses “dump” command instead of “vdump” on Digital Unix |
| - | • log file title displayed as “db_lock: waiting for the drive” | + | **recovery cannot be pre-configured |
| - | • FSdump backup method uses “dump” command instead of “vdump” on Digital Unix | + | **searching media indexes slow |
| - | • recovery cannot be pre-configured | + | **media contents incorrect when appending backup job killed |
| - | • searching media indexes slow | + | **incremental tar backup method backs up the list of files rather than the files |
| - | • media contents incorrect when appending backup job killed | + | **a not yet started backup job can be acknowledged |
| - | • incremental tar backup method backs up the list of files rather than the files | + | **loading class not displayed when changing drive details |
| - | • a not yet started backup job can be acknowledged | + | *all fixes in COSbackup 3.2.1 patch |
| - | • loading class not displayed when changing drive details | + | **wrong flags in FScpio |
| - | • all fixes in COSbackup 3.2.1 patch | + | **typo in offsite program |
| - | • wrong flags in FScpio | + | **disable appending backup “ready mode” |
| - | Copyright © Functional Software 1999. | + | **rewind after a backup using Rewind_op |
| - | All trademarks and registered trademarks of products mentioned herein are | + | **“unload” not run during auto-acknowledgement |
| - | recognized by Functional Software. | + | **unload failing should not stop acknowledgement |
| - | Release Notes for COSbackup 3.2.3 (Patch)—November 1999 Page 2 | + | **messages from auto-acknowledgement and unload not going into logfile |
| - | • typo in offsite program | + | **symbolic links creacted by config task are imcomplete |
| - | • disable appending backup “ready mode” | + | |
| - | • rewind after a backup using Rewind_op | + | |
| - | • “unload” not run during auto-acknowledgement | + | |
| - | • unload failing should not stop acknowledgement | + | |
| - | • messages from auto-acknowledgement and unload not going into logfile | + | |
| - | • symbolic links creacted by config task are imcomplete | + | |
| The major new features in version 3.2.3 are: | The major new features in version 3.2.3 are: | ||
| - | • improved error recovery during restore if a media error occurs | + | *improved error recovery during restore if a media error occurs |
| - | • scanning multi-volume media sets | + | *scanning multi-volume media sets |
| + | |||
| The major new features in version 3.2.2 are: | The major new features in version 3.2.2 are: | ||
| - | • media copy can be run from at end command of backup job, COSbackup interface, and | + | *media copy can be run from at end command of backup job, COSbackup interface, and command line |
| - | command line | + | *multi-part file backup on 32 bit architecture was restricted to file sizes up to 1 gigabyte for image backups |
| - | • multi-part file backup on 32 bit architecture was restricted to file sizes up to 1 gigabyte for | + | |
| - | image backups | + | == Environment == |
| - | Environment | + | Software Prerequisites: Before you can install COSbackup 3.2.3 (patch), COSMOS 3.2.1 (or newer) and COSbackup 3.2, 3.2.1 or 3.2.2 must already be installed on the same host. |
| - | Software Prerequisites: Before you can install COSbackup 3.2.3 (patch), COSMOS 3.2.1 (or | + | |
| - | newer) and COSbackup 3.2, 3.2.1 or 3.2.2 must already be installed on the same host. | + | == Notes == |
| - | Notes | + | ===Patch applied after COSbackup 3.2 has been configured: === |
| - | Patch applied after COSbackup 3.2 has been configured: If you are using, or choose to use | + | If you are using, or choose to use appending backups, you must change the label type for each media type used from “COSstdtape” |
| - | appending backups, you must change the label type for each media type used from “COSstdtape” | + | |
| to “COSstdindx”. | to “COSstdindx”. | ||
| + | |||
| To change media type: | To change media type: | ||
| - | 1. Select Media from the COSbackup button bar. | + | #Select Media from the COSbackup button bar. |
| - | 2. Select Maintain > Media type. | + | #Select Maintain > Media type. |
| - | 3. Select a media type to change, then select Maintain > Change. | + | #Select a media type to change, then select Maintain > Change. |
| - | 4. Change label type from “COSstdtape” to “COSstdindx”. | + | #Change label type from “COSstdtape” to “COSstdindx”. |
| - | /DEHO#W\SH 7KLV#GHWHUPLQHV#ZKDW#ODEHO#IRUPDW#DQG#PHWKRG#ZLOO#EH#XVHG#WR#HOHFWURQLFDOO\#ODEHO# | + | something in here |
| - | YROXPHV= | + | |
| - | &26VWGWDSH ZULWHV#D#VKRUW#ILOH#FRQWDLQLQJ#WKH#PHGLD#QXPEHU#DQG#¶GDWH#ODVW#ZULWWHQ·#WR#WKH#VWDUW#RI# | + | |
| - | Release Notes for COSbackup 3.2.3 (Patch)—November 1999 Page 3 | + | |
| - | WKH#WDSH/#EXW#GRHV#QRW#ZULWH#DQ#HQG0RI0GDWD#PDUNHU1 | + | |
| - | &26VWGLQG[ ZULWHV#WKH#ODEHO#WR#WKH#VWDUW#RI#D#WDSH/#DQG#DQ#HQG0RI0GDWD#PDUNHU#DIWHU#WKH#ODVW#ILOH1 | + | |
| - | HQGBODEHO ZULWHV#WKH#ODEHO#WR#WKH#ODVW#EORFN#RI#D#GLVNHWWH1 | + | |
| - | V9B ILOHV\V 6\VWHP#9#ILOHV\VWHP#ODEHO#XVLQJ#WKH#labelit#FRPPDQG1 | + | |
| - | EODQN YROXPHV#ZLOO#QRW#EH#ODEHOHG1 | + | |
| Press Accept to save this media type information. | Press Accept to save this media type information. | ||
| - | If any of your media types have a label type of “COSstdBOT”, please call the Functional Support | + | |
| - | Line. | + | If any of your media types have a label type of “COSstdBOT”, please call the Functional Support Line. |
| - | Patch applied after COSbackup 3.2.1 patch applied: No further action required. | + | |
| - | Patch applied after COSbackup 3.2.2 patch applied: No further action required. | + | === Patch applied after COSbackup 3.2.1 patch applied === No further action required. |
| - | Patch applied after local customising to COSbackup 3.2/3.2.1/3.2.2: The patch is not applied to | + | === Patch applied after COSbackup 3.2.2 patch applied === No further action required. |
| - | customised files. If any files listed in the attached table have been modified, then the patch will | + | === Patch applied after local customising to COSbackup 3.2/3.2.1/3.2.2 === |
| - | need to be applied to these local modifications. Please contact the Functional Support Line for | + | The patch is not applied to customised files. If any files listed in the attached table have been modified, then the patch will |
| - | assistance. | + | need to be applied to these local modifications. Please contact the Functional Support Line for assistance. |
| - | Patch installed same time as COSbackup 3.2: No further action required. | + | === Patch installed same time as COSbackup 3.2 === No further action required. |
| - | Release Notes for COSbackup 3.2.3 (Patch)—November 1999 Page 4 | + | |
| - | Technical Notes: Using COSbackup V3.2.3 | + | == Technical Notes: Using COSbackup V3.2.3 == |
| - | This section contains some technical notes, tips, and troubleshooting information to help you when | + | This section contains some technical notes, tips, and troubleshooting information to help you when installing or upgrading to COSbackup V3.2.3. Detailed information on setting up and using COSbackup can be found in the COS/Backup User Guide V3.2. |
| - | installing or upgrading to COSbackup V3.2.3. Detailed information on setting up and using | + | |
| - | COSbackup can be found in the COS/Backup User Guide V3.2. | + | |
| Media scan now default to multi-volume | Media scan now default to multi-volume | ||
| - | The scan method now defaults to multi-volume media scan, where the scan proceeds from the last | + | |
| - | tape in the set to the first. | + | 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: | To manually scan a single volume from the command line, you can still use the command: | ||
| - | FSdrive <drivename> scan | + | FSdrive <drivename> scan |
| + | |||
| Media copy now run from ‘At-end command’, COSbackup interface or command line | Media copy now run from ‘At-end command’, COSbackup interface or command line | ||
| - | 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. | + | 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. |
| - | 1. From the At-end command as defined for a backup job: | + | #From the At-end command as defined for a backup job: |
| - | FScopy <target drive> | + | #:;FScopy <target drive> |
| - | This will copy the media set used for the current backup to a new media set in the target drive. The | + | #: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 cannot be overridden. |
| - | expiry date of the duplicate set is set to the same date as that of the backup job. This cannot be | + | #: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. |
| - | overridden. | + | #Via COSbackup interface, from the COSbackup button bar: |
| - | If the target drive is likely to be busy when needed for creating a duplicate media set, a timeout | + | #:;Media > select media set > Maintain > Copy |
| - | parameter may be added to the above command, “-T <minutes>”. If this parameter is omitted and | + | #: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. |
| - | the target drive is busy, the media copy will fail. | + | #: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: |
| - | 2. Via COSbackup interface, from the COSbackup button bar: | + | #:;Drive > select target drive > Operations > Load scratch |
| - | Media > select media set > Maintain > Copy | + | #From the command line, as would be used by COStask or COSduty, or a 3rd party batch processing product: |
| - | You will be prompted for the run mode, the source drive and the target drive. The retention | + | #:; FScopy -b [-u] [-U] [-T <minutes>] [-r <retention>] -s <media number> <source drive> <target drive> |
| - | defaults to that of the selected media set, but may be overridden. | + | #: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”. |
| - | 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 | + | |
| - | Release Notes for COSbackup 3.2.3 (Patch)—November 1999 Page 5 | + | |
| - | 3. 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>] -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”. | + | |
| - | See FScopy(1) man page for further detail. | + | |
| Restore steps may now be pre-configured | 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: | + | 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>] |
| - | 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. | If any parameters are missing a prompt will be displayed requesting the missing values. | ||
| - | Warnings | + | |
| + | == Warnings == | ||
| None known. | None known. | ||
| - | Hardware and OS Dependencies | + | |
| + | == Hardware and OS Dependencies == | ||
| + | |||
| See Release Notes for COS/Backup V3.2. | See Release Notes for COS/Backup V3.2. | ||
| - | Further Information | ||
| - | Contact the Functional Support Line at: | ||
| - | support@fs.com.au | ||
| - | Tel: +61 2 9869 0240 | ||
| - | Fax: +61 2 9869 0280 | ||
| - | Visit our website for the latest patch distributions and related documentation at: | ||
| - | http://www.fs.com.au/support | ||
Revision as of 02:28, 4 May 2006
Contents |
Features
Implementation of the Patch applies fixes according to solutions described in the attached table - please refer for full details.
Fixes included in this Patch are cumulative including prior patches.
They are:
- expiring media may leave unused contents files in the COSbackup media database
- print error when media catalogue is printed from at-end command
- unable to restore files bigger than 2 gigabytes on Dynix/ptx when using TAR or DUMPmethods
- multi-volume scan may only scan a subset of the tape files
- waiting for drive during a media copy may time out even though drive is available
- during a multi-step, multi-part restore a read error occurs, repositioning on media for restoreof subsequent step may be incorrect
- all fixes in COSbackup 3.2.2 patch
- unclear details logged or displayed in monitor about media duplication
- media copy hangs if using drivepools
- media copy does not wait for target drive to become available
- retention for duplicated media same as source
- auto job acknowledgement implies auto unload
- log file title displayed as “db_lock: waiting for the drive”
- FSdump backup method uses “dump” command instead of “vdump” on Digital Unix
- recovery cannot be pre-configured
- searching media indexes slow
- media contents incorrect when appending backup job killed
- incremental tar backup method backs up the list of files rather than the files
- a not yet started backup job can be acknowledged
- loading class not displayed when changing drive details
- all fixes in COSbackup 3.2.1 patch
- wrong flags in FScpio
- typo in offsite program
- disable appending backup “ready mode”
- rewind after a backup using Rewind_op
- “unload” not run during auto-acknowledgement
- unload failing should not stop acknowledgement
- messages from auto-acknowledgement and unload not going into logfile
- symbolic links creacted by config task are imcomplete
The major new features in version 3.2.3 are:
- improved error recovery during restore if a media error occurs
- scanning multi-volume media sets
The major new features in version 3.2.2 are:
- media copy can be run from at end command of backup job, COSbackup interface, and command line
- multi-part file backup on 32 bit architecture was restricted to file sizes up to 1 gigabyte for image backups
Environment
Software Prerequisites: Before you can install COSbackup 3.2.3 (patch), COSMOS 3.2.1 (or newer) and COSbackup 3.2, 3.2.1 or 3.2.2 must already be installed on the same host.
Notes
Patch applied after COSbackup 3.2 has been configured:
If you are using, or choose to use appending backups, you must change the label type for each media type used from “COSstdtape” to “COSstdindx”.
To change media type:
- Select Media from the COSbackup button bar.
- Select Maintain > Media type.
- Select a media type to change, then select Maintain > Change.
- Change label type from “COSstdtape” to “COSstdindx”.
something in here
Press Accept to save this media type information.
If any of your media types have a label type of “COSstdBOT”, please call the Functional Support Line.
Patch applied after COSbackup 3.2.1 patch applied
No further action required.Patch applied after COSbackup 3.2.2 patch applied
No further action required.Patch applied after local customising to COSbackup 3.2/3.2.1/3.2.2
The patch is not applied to customised files. If any files listed in the attached table have been modified, then the patch will need to be applied to these local modifications. Please contact the Functional Support Line for assistance.
Patch installed same time as COSbackup 3.2
No further action required.Technical Notes: Using COSbackup V3.2.3
This section contains some technical notes, tips, and troubleshooting information to help you when installing or upgrading to COSbackup V3.2.3. Detailed information on setting up and using COSbackup can be found in the COS/Backup User Guide V3.2.
Media scan now default to multi-volume
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 run from ‘At-end command’, COSbackup interface or command line
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 <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 cannot be overridden.
- 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>] -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
None known.
Hardware and OS Dependencies
See Release Notes for COS/Backup V3.2.