Backup3G/COSbackup 3.2.5 Release Notes
This page was last modified 01:18, 5 September 2007.From Documentation
< Backup3G(Difference between revisions)
| Revision as of 01:56, 4 May 2006 Daniels (Talk | contribs) (→Media copy now run from ‘At-end command’, COSbackup interface or command line) ← Previous diff |
Current revision Moff (Talk | contribs) (→Solaris: cpio backup methods do not backup files greater than 2 gigabyte) |
||
| Line 39: | Line 39: | ||
| **symbolic links creacted by config task are imcomplete | **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 command line | *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 | *multi-part file backup on 32 bit architecture was restricted to file sizes up to 1 gigabyte for image backups | ||
| + | <br> | ||
| == Environment == | == Environment == | ||
| Software Prerequisites: Before you can install [[COSbackup]] 3.2.5 (application) on Solaris 8 or 9, [[COSmanager]] 4.1 (or newer) must already be installed on the same host. Before you can install COSbackup 3.2.5 (application) on earlier Solaris releases, COSmanager 3.2.1 (or newer) must already be installed on the same host. | Software Prerequisites: Before you can install [[COSbackup]] 3.2.5 (application) on Solaris 8 or 9, [[COSmanager]] 4.1 (or newer) must already be installed on the same host. Before you can install COSbackup 3.2.5 (application) on earlier Solaris releases, COSmanager 3.2.1 (or newer) must already be installed on the same host. | ||
| Line 52: | Line 55: | ||
| Before you can install COSbackup 3.2.5 (application) on all other operating systems, COSmanager 3.2.1 (or newer) must already be installed on the same host. | Before you can install COSbackup 3.2.5 (application) on all other operating systems, COSmanager 3.2.1 (or newer) must already be installed on the same host. | ||
| + | <br> | ||
| == Notes (only applies to patch) == | == Notes (only applies to patch) == | ||
| - | === 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 appending backups, you must change the label type for each media type used from “COSstdtape” to “COSstdindx”. |
| - | + | ||
| - | 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: | To change media type: | ||
| Line 63: | Line 65: | ||
| #Change label type from “COSstdtape” to “COSstdindx”. | #Change label type from “COSstdtape” to “COSstdindx”. | ||
| #;Label type: This determines what label format and method will be used to electronically label volumes: | #;Label type: This determines what label format and method will be used to electronically label volumes: | ||
| - | ##;COSstdtape: writes a short file containing the media number and ‘date last written’ to the start of the tape, but does not write an end-of-data marker. | + | #:;''COSstdtape'': writes a short file containing the media number and ‘date last written’ to the start of the tape, but does not write an end-of-data marker. |
| - | ##;COSstdindx: writes the label to the start of a tape, and an end-of-data marker after the last file. | + | #:;''COSstdindx'': writes the label to the start of a tape, and an end-of-data marker after the last file. |
| - | ##;end_label: writes the label to the last block of a diskette. | + | #:;''end_label'': writes the label to the last block of a diskette. |
| - | ##;sV_ filesys: System V filesystem label using the labelit command. | + | #:;''sV_ filesys'': System V filesystem label using the labelit command. |
| - | ##;blank: volumes will not be labeled. | + | #:;''blank'': volumes will not be labeled. |
| - | 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.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.3 patch applied: === | + | '''Patch applied after COSbackup 3.2.2 patch applied:''' No further action required. |
| - | No further action required. | + | |
| - | === Patch applied after local customising to COSbackup 3.2/3.2.1/3.2.2/3.2.3: === | ||
| - | 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 applied after COSbackup 3.2.3 patch applied:''' No further action required. |
| - | === Patch installed same time as COSbackup 3.2: === | ||
| - | No further action required. | ||
| + | '''Patch applied after local customising to COSbackup 3.2/3.2.1/3.2.2/3.2.3:''' 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. | ||
| + | |||
| + | <br> | ||
| == Technical Notes: Using COSbackup V3.2.5 == | == Technical Notes: Using COSbackup V3.2.5 == | ||
| - | This section contains some technical notes, tips, and troubleshooting information to help you when installing or upgrading to COSbackup V3.2.5. Detailed information on setting up and using COSbackup can be found in the COS/Backup User Guide V3.2. | + | This section contains some technical notes, tips, and troubleshooting information to help you when installing or upgrading to COSbackup V3.2.5. Detailed information on setting up and using COSbackup can be found in the [[Backup3G/User_Guide|Backup3G User Guide V3.2]]. |
| - | === Media scan now default to multi-volume === | + | <br> |
| + | === 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. | 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 | ||
| + | <br> | ||
| + | === 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 | FSdrive <drivename> scan | ||
| + | <br> | ||
| === 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''. |
| - | #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”. | + | |
| + | #'''From the At-end command as defined for a backup job:'''<br><code>FScopy [-u] [-U] [-T <minutes>] [-r <retention>|-r <days>] <target drive></code><br>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 “<tt>-r <retention></tt>” or “<tt>-r <days></tt>”.<br><br>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, “<tt>-T <minutes></tt>”. If this parameter is omitted and the ''target drive'' is busy, the media copy will fail.<br><br> | ||
| + | #'''Via COSbackup interface, from the COSbackup button bar:'''<br>Media > select media set > Maintain > Copy<br><br>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.<br><br>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:<br>Drive > select target drive > Operations > Load scratch<br><br> | ||
| + | #'''From the command line, as would be used by COStask or COSduty, or a 3rd party batch processing product:'''<br><code>FScopy -b [-u] [-U] [-T <minutes>] [-r <retention>|-r <days>] -s <media number> <source drive> <target drive></code><br>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”. | ||
| + | |||
| + | <br> | ||
| === 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. | ||
| + | |||
| + | <br> | ||
| == Warnings == | == Warnings == | ||
| None known. | None known. | ||
| + | |||
| + | <br> | ||
| == Hardware and OS Dependencies == | == Hardware and OS Dependencies == | ||
| + | |||
| === AIX 4: cpio backup methods do not backup files greater than 2 gigabytes === | === AIX 4: cpio backup methods do not backup files greater than 2 gigabytes === | ||
| - | The /usr/bin/cpio program, as used by COSbackup, cannot backup files that are greater than 2 gigabytes in size. The standard cpio header uses a 32 bit signed type to store the file size. this limits the file size to 2 gigabytes minus 1 byte. | + | The <tt>/usr/bin/cpio</tt> program, as used by COSbackup, cannot backup files that are greater than 2 gigabytes in size. The standard cpio header uses a 32 bit signed type to store the file size. this limits the file size to 2 gigabytes minus 1 byte. |
| + | |||
| + | Appears: “<tt>< filename > ?</tt>” is displayed in the backup log, when attempting to backup a file greater than 2 gigabytes in size. | ||
| - | Appears: “< filename > ?” is displayed in the backup log, when attempting to backup a file greater than 2 gigabytes in size. | ||
| Suggested actions: | Suggested actions: | ||
| - | *Use a backup format other than cpio for directories containing files greater than 2 gigabytes in size. For example, backup the individual large files using the image backup method. | + | *Use a backup format other than cpio for directories containing files greater than 2 gigabytes in size. For example, backup the individual large files using the image backup method. |
| - | *Alternately, upgrade to AIX 5.1 or later with the System V Affinity package. If installed, COSbackup will use /usr/sysv/bin/cpio instead, that can backup and restore files of any size. /usr/sysv/bin/cpio is backward compatable with /usr/bin/cpio. | + | *Alternately, upgrade to AIX 5.1 or later with the System V Affinity package. If installed, COSbackup will use <tt>/usr/sysv/bin/cpio</tt> instead, that can backup and restore files of any size. <tt>/usr/sysv/bin/cpio</tt> is backward compatable with <tt>/usr/bin/cpio</tt>. |
| + | <br> | ||
| === Linux: cpio backup methods do not backup files greater than 2 gigabytes === | === Linux: cpio backup methods do not backup files greater than 2 gigabytes === | ||
| - | The /usr/bin/cpio program, as used by COSbackup, cannot backup files that are g reater than 2 gigabytes in size. The standard cpio header uses a 32 bit signed type to store the file size. this limits the file size to 2 gigabytes minus 1 byte. | ||
| - | Appears: “filename is too large to archive in current mode” is displayed in the backup log, when attempting to backup a file greater than 2 gigabytes in size. | + | The <tt>/usr/bin/cpio</tt> program, as used by COSbackup, cannot backup files that are greater than 2 gigabytes in size. The standard cpio header uses a 32 bit signed type to store the file size. this limits the file size to 2 gigabytes minus 1 byte. |
| + | |||
| + | Appears: “<tt>filename is too large to archive in current mode</tt>” is displayed in the backup log, when attempting to backup a file greater than 2 gigabytes in size. | ||
| Suggested actions: | Suggested actions: | ||
| - | *Use a backup format other than cpio for directories containing files greater than 2 gigabytes in size. For example, backup the individual large files using the image backup method. | + | *Use a backup format other than cpio for directories containing files greater than 2 gigabytes in size. For example, backup the individual large files using the image backup method. |
| - | === Solaris: cpio backup methods do not backup files greater than 2 gigabytes === | + | <br> |
| - | The /usr/bin/cpio program, as used by COSbackup, cannot backup files that are greater than 2 gigabytes in size. The standard cpio header uses a 32 bit signed type to store the file size. this limits the file size to 2 gigabytes minus 1 byte. | + | === Solaris: cpio backup methods do not backup files greater than 2 gigabyte === |
| - | Appears: “filename is too large to archive in current mode” is displayed in the backup log, when attempting to backup a file greater than 2 gigabytes in size. | + | The <tt>/usr/bin/cpio</tt> program, as used by COSbackup, cannot backup files that are greater than 2 gigabytes in size. The standard cpio header uses a 32 bit signed type to store the file size. this limits the file size to 2 gigabytes minus 1 byte. |
| + | |||
| + | Appears: “<tt>filename is too large to archive in current mode</tt>” is displayed in the backup log, when attempting to backup a file greater than 2 gigabytes in size. | ||
| Suggested actions: | Suggested actions: | ||
| - | *Specify “-p” in the Options field of the Backup Item. This will allow for the backup of files up to 8 gigabytes minus 1 byte in size. Files larger than 8 gigabytes minus 1 byte will display an error in the backup log. Using the “-p” option will display an error message in the backup log when backing up /devices files and limit the file path length to 256 characters long (instead of the normal 1024 characters). | + | *Specify “<tt>-p</tt>” in the Options field of the Backup Item. This will allow for the backup of files up to 8 gigabytes minus 1 byte in size. Files larger than 8 gigabytes minus 1 byte will display an error in the backup log. Using the “<tt>-p</tt>” option will display an error message in the backup log when backing up <tt>/devices</tt> files and limit the file path length to 256 characters long (instead of the normal 1024 characters). |
| *Use a backup format other than cpio for directories containing files greater than 2 gigabytes in size. For example, backup the individual large files using the image backup method. | *Use a backup format other than cpio for directories containing files greater than 2 gigabytes in size. For example, backup the individual large files using the image backup method. | ||
| + | |||
| + | <br> | ||
| + | ---- | ||
| + | <div style="float:right;">October 2002</div>Copyright © 1990-{{CURRENTYEAR}} Functional Software. All rights reserved. | ||
Current revision
Contents |
[edit]
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:
- 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
- during a multi-step, multi-part restore a read error occurs, repositioning on media forrestore 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.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
[edit]
Environment
Software Prerequisites: Before you can install COSbackup 3.2.5 (application) on Solaris 8 or 9, COSmanager 4.1 (or newer) must already be installed on the same host. Before you can install COSbackup 3.2.5 (application) on earlier Solaris releases, COSmanager 3.2.1 (or newer) must already be installed on the same host.
Before you can install COSbackup 3.2.5 (application) on all other operating systems, COSmanager 3.2.1 (or newer) must already be installed on the same host.
[edit]
Notes (only applies to patch)
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”.
- Label type
- This determines what label format and method will be used to electronically label volumes:
- COSstdtape
- writes a short file containing the media number and ‘date last written’ to the start of the tape, but does not write an end-of-data marker.
- COSstdindx
- writes the label to the start of a tape, and an end-of-data marker after the last file.
- end_label
- writes the label to the last block of a diskette.
- sV_ filesys
- System V filesystem label using the labelit command.
- blank
- volumes will not be labeled.
- 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 COSbackup 3.2.3 patch applied: No further action required.
Patch applied after local customising to COSbackup 3.2/3.2.1/3.2.2/3.2.3: 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.
[edit]
Technical Notes: Using COSbackup V3.2.5
This section contains some technical notes, tips, and troubleshooting information to help you when installing or upgrading to COSbackup V3.2.5. Detailed information on setting up and using COSbackup can be found in the Backup3G User Guide V3.2.
[edit]
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
[edit]
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
[edit]
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 [-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”.
[edit]
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.
[edit]
Warnings
None known.
[edit]
Hardware and OS Dependencies
[edit]
AIX 4: cpio backup methods do not backup files greater than 2 gigabytes
The /usr/bin/cpio program, as used by COSbackup, cannot backup files that are greater than 2 gigabytes in size. The standard cpio header uses a 32 bit signed type to store the file size. this limits the file size to 2 gigabytes minus 1 byte.
Appears: “< filename > ?” is displayed in the backup log, when attempting to backup a file greater than 2 gigabytes in size.
Suggested actions:
- Use a backup format other than cpio for directories containing files greater than 2 gigabytes in size. For example, backup the individual large files using the image backup method.
- Alternately, upgrade to AIX 5.1 or later with the System V Affinity package. If installed, COSbackup will use /usr/sysv/bin/cpio instead, that can backup and restore files of any size. /usr/sysv/bin/cpio is backward compatable with /usr/bin/cpio.
[edit]
Linux: cpio backup methods do not backup files greater than 2 gigabytes
The /usr/bin/cpio program, as used by COSbackup, cannot backup files that are greater than 2 gigabytes in size. The standard cpio header uses a 32 bit signed type to store the file size. this limits the file size to 2 gigabytes minus 1 byte.
Appears: “filename is too large to archive in current mode” is displayed in the backup log, when attempting to backup a file greater than 2 gigabytes in size.
Suggested actions:
- Use a backup format other than cpio for directories containing files greater than 2 gigabytes in size. For example, backup the individual large files using the image backup method.
[edit]
Solaris: cpio backup methods do not backup files greater than 2 gigabyte
The /usr/bin/cpio program, as used by COSbackup, cannot backup files that are greater than 2 gigabytes in size. The standard cpio header uses a 32 bit signed type to store the file size. this limits the file size to 2 gigabytes minus 1 byte.
Appears: “filename is too large to archive in current mode” is displayed in the backup log, when attempting to backup a file greater than 2 gigabytes in size.
Suggested actions:
- Specify “-p” in the Options field of the Backup Item. This will allow for the backup of files up to 8 gigabytes minus 1 byte in size. Files larger than 8 gigabytes minus 1 byte will display an error in the backup log. Using the “-p” option will display an error message in the backup log when backing up /devices files and limit the file path length to 256 characters long (instead of the normal 1024 characters).
- Use a backup format other than cpio for directories containing files greater than 2 gigabytes in size. For example, backup the individual large files using the image backup method.
October 2002
Copyright © 1990-2024 Functional Software. All rights reserved.