Duty3G/Duty3G 5.1 Release Notes
From Documentation
(Difference between revisions)
| Revision as of 08:26, 20 September 2006 Moff (Talk | contribs) ← Previous diff |
Revision as of 09:08, 20 September 2006 Moff (Talk | contribs) (→Features) Next diff → |
||
| Line 1: | Line 1: | ||
| - | == Features == | + | == Overview and 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. | + | ==== Duty3G ==== |
| - | They are: | + | Duty3G V5.1 is a job control and batch job scheduling application that provides network-wide job execution with comprehensive inter-task dependencies. It can manage the entire production control of your Data Center. You use COStask to:•submit or schedule pre-defined jobs•manage running jobs (hold/release/kill etc.)•monitor job output•handle and recover from error conditions. |
| - | *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|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 | + | |
| + | <br> | ||
| + | ==== New features in Duty3G V5.1 ==== | ||
| - | The major new features in version 3.2.6 are: | + | Key features of the new release are: |
| - | *backup any size file using the CPIO format | + | |
| - | *mark a drive as offline | + | |
| + | '''Enhanced operations''' | ||
| - | The major new features in version 3.2.3 are: | + | *Enhanced schedules, for example, a Weekday schedule can now exclude public holidays. |
| - | *improved error recovery during restore if a media error occurs | + | *You can now assign duties to a class/folder, so the duty name no longer needs to be prefixed with a Class or Category. Now it is much easier to locate that ‘XYZ’ duty. |
| - | *scanning multi-volume media sets | + | *You can now order duties in the order they should be performed, so the duty name no longer needs to be prefixed with a Sequence number |
| + | *You can now force the user to re-authenticate before running certain duties giving added security. | ||
| + | *Duties can now be auto disabled and/or auto re-enabled on given dates. This is useful during system rollouts or migration projects. | ||
| + | *Duties are now run asynchronously, meaning if you have a long running duty it no longer stops you from running another duty. | ||
| + | *As a duty is performed, that duty is now “locked” so no other user can run the same duty with possible undesirable results. | ||
| + | *End user's can set their own start-up view (at-request or outstanding duties) and start-up Class, along with a reminder period before duties become overdue. | ||
| + | *End user’s can now view upcoming scheduled duties for a selected day or date in the future – “What has to be done on Friday?”. This is also useful for Administrators to check that duties have been scheduled correctly, for example, making sure certain duties are not scheduled for Christmas Day. | ||
| + | *You can now filter your view of duties: | ||
| + | :*for a selected class | ||
| + | :*that run on a selected host | ||
| + | :*for a selected users' role | ||
| + | '''Improved auditing''' | ||
| - | The major new features in version 3.2.2 are: | + | *Filtering has been added to make viewing the Duty audit trail more meaningful: |
| - | *media copy can be run from at end command of backup job, COSbackup interface, and command line | + | :*by selected time period |
| - | *multi-part file backup on 32 bit architecture was restricted to file sizes up to 1 gigabyte for image backups | + | :*that have ended in error |
| + | :*for selected duty | ||
| + | :*for selected user | ||
| + | :*for selected mode | ||
| + | *Duty audit trail entries are now colour coded to make it easier to spot abnormal entries. | ||
| + | *New duty compliance reports are generated daily and can be viewed at any time. These reports highlight failed, missed and skipped duties – exceptions that affect operations compliance. | ||
| + | |||
| + | '''Documentation''' | ||
| + | |||
| + | *An HTML or text document can now be associated with a duty, so end users can see what Policies and Procedures the duty is supporting. | ||
| + | *You can now link directly to online help (user guide), release notes and other documentation, and even report a bug via duty3G | ||
| <br> | <br> | ||
| + | == Installation Requirements == | ||
| + | |||
| + | ==== Software prerequisites ==== | ||
| + | |||
| + | To install and run Duty3G V5.1 on a host, you must have: | ||
| + | |||
| + | *COSmanager V4.2.5 or later already installed on the host (see the [[COSmanager/User Guide | COSmanager User Guide]] for instructions) | ||
| + | *a [http://downloads.fs.com.au/index.php?prod=DTY duty3G 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 ==== | ||
| + | |||
| + | Running Remote Tasks on Windows/NTThe current COStask release supports running remote tasks on NT hosts which have the EBC (Enterprise Backup Client) V2.1 installed. This product may be purchased separately. Functional Software is likely to release an NT agent specially for COStask in the near future. | ||
Revision as of 09:08, 20 September 2006
Contents |
Overview and Features
Duty3G
Duty3G V5.1 is a job control and batch job scheduling application that provides network-wide job execution with comprehensive inter-task dependencies. It can manage the entire production control of your Data Center. You use COStask to:•submit or schedule pre-defined jobs•manage running jobs (hold/release/kill etc.)•monitor job output•handle and recover from error conditions.
New features in Duty3G V5.1
Key features of the new release are:
Enhanced operations
- Enhanced schedules, for example, a Weekday schedule can now exclude public holidays.
- You can now assign duties to a class/folder, so the duty name no longer needs to be prefixed with a Class or Category. Now it is much easier to locate that ‘XYZ’ duty.
- You can now order duties in the order they should be performed, so the duty name no longer needs to be prefixed with a Sequence number
- You can now force the user to re-authenticate before running certain duties giving added security.
- Duties can now be auto disabled and/or auto re-enabled on given dates. This is useful during system rollouts or migration projects.
- Duties are now run asynchronously, meaning if you have a long running duty it no longer stops you from running another duty.
- As a duty is performed, that duty is now “locked” so no other user can run the same duty with possible undesirable results.
- End user's can set their own start-up view (at-request or outstanding duties) and start-up Class, along with a reminder period before duties become overdue.
- End user’s can now view upcoming scheduled duties for a selected day or date in the future – “What has to be done on Friday?”. This is also useful for Administrators to check that duties have been scheduled correctly, for example, making sure certain duties are not scheduled for Christmas Day.
- You can now filter your view of duties:
- for a selected class
- that run on a selected host
- for a selected users' role
Improved auditing
- Filtering has been added to make viewing the Duty audit trail more meaningful:
- by selected time period
- that have ended in error
- for selected duty
- for selected user
- for selected mode
- Duty audit trail entries are now colour coded to make it easier to spot abnormal entries.
- New duty compliance reports are generated daily and can be viewed at any time. These reports highlight failed, missed and skipped duties – exceptions that affect operations compliance.
Documentation
- An HTML or text document can now be associated with a duty, so end users can see what Policies and Procedures the duty is supporting.
- You can now link directly to online help (user guide), release notes and other documentation, and even report a bug via duty3G
Installation Requirements
Software prerequisites
To install and run Duty3G V5.1 on a host, you must have:
- COSmanager V4.2.5 or later already installed on the host (see the COSmanager User Guide for instructions)
- a duty3G 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
Running Remote Tasks on Windows/NTThe current COStask release supports running remote tasks on NT hosts which have the EBC (Enterprise Backup Client) V2.1 installed. This product may be purchased separately. Functional Software is likely to release an NT agent specially for COStask in the near future.