FS
Documentation

Backup3G/COSbackup 3.2.6 Release Notes

From Documentation

(Difference between revisions)
Jump to: navigation, search
Revision as of 02:08, 4 May 2006
Daniels (Talk | contribs)
(Backup 3.2.6 Release Notes moved to Backup 3.2.5 Release Notes)
← Previous diff
Revision as of 02:10, 4 May 2006
Daniels (Talk | contribs)

Next diff →
Line 1: Line 1:
-#REDIRECT [[Backup 3.2.5 Release Notes]]+Release Notes for COSbackup 3.2.6 (Patch and
 +Application)
 +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:
 +• cpio backup methods do not backup files larger than 2 gigabytes
 +• index files are removed if backup step completes with non-zero exit status
 +• automatic jobs cannot have complex scheduling
 +• backing up read only filesystems produces error messages
 +• media retention period cannot be overriden when producing a media copy at the end of a
 +backup job
 +• drives cannot easily be marked as “out of action”
 +• all users can schedule any backup and restore data from any media
 +• media indices are not displayed in alphabetical order
 +• restoring data from index may cause drive status information to become corrupt
 +• all fixes in COSbackup 3.2.5 patch
 +• image backup method, as used by the DA-Oracle module, does not backup files larger than
 +2 gigabytes
 +• cpio backup methods do not backup files larger than 2 gigabytes (see “Hardware and OS
 +Dependencies” on page 6)
 +• multi-part backup methods can not stat files larger than 2 gigabytes
 +• all fixes in COSbackup 3.2.3 patch
 +• 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 DUMP
 +methods
 +• 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
 +Copyright © Functional Software 2002.
 +All trademarks and registered trademarks of products mentioned herein are
 +recognized by Functional Software.

Revision as of 02:10, 4 May 2006

Release Notes for COSbackup 3.2.6 (Patch and Application) 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: • cpio backup methods do not backup files larger than 2 gigabytes • index files are removed if backup step completes with non-zero exit status • automatic jobs cannot have complex scheduling • backing up read only filesystems produces error messages • media retention period cannot be overriden when producing a media copy at the end of a backup job • drives cannot easily be marked as “out of action” • all users can schedule any backup and restore data from any media • media indices are not displayed in alphabetical order • restoring data from index may cause drive status information to become corrupt • all fixes in COSbackup 3.2.5 patch • image backup method, as used by the DA-Oracle module, does not backup files larger than 2 gigabytes • cpio backup methods do not backup files larger than 2 gigabytes (see “Hardware and OS Dependencies” on page 6) • multi-part backup methods can not stat files larger than 2 gigabytes • all fixes in COSbackup 3.2.3 patch • 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 DUMP methods • 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 Copyright © Functional Software 2002. All trademarks and registered trademarks of products mentioned herein are recognized by Functional Software.