Duty3G/Duty3G 5.1 Release Notes

From Documentation

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 abackup 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 than2 gigabytes
  • cpio backup methods do not backup files larger than 2 gigabytes (see “Hardware and OS Dependencies”)
  • 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 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 restore of 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.6 are:

• backup any size file using the CPIO format
• mark a drive as offline

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