This Solution is from Symantec Support :Error No.183 Solution
Third party-related issue: Backups
performed with VERITAS NetBackup (tm) exit with status 0 (successful), but show
"ERR - invalid tar header encountered, attempting to continue" during
a restore from a backup that has spanned media on the Sony AIT-4 SDX 900V tape
drives. When this error occurs, the data is not restorable.
Article Type
Technical Solution
Technical Solution
Product(s)
Environment
Languages
Problem
Third party-related
issue: Backups performed with VERITAS NetBackup (tm) exit with status 0
(successful), but show "ERR - invalid tar header encountered, attempting
to continue" during a restore from a backup that has spanned media on the
Sony AIT-4 SDX 900V tape drives. When this error occurs, the data is not
restorable.
Error
ERR - invalid tar
header encountered, attempting to continue
Solution
Vendor: Sony
OS platform: This issue is known to affect Windows 2000 and 2003 platforms that are supported with NetBackup 5.x. The operating system versions known to be affected are listed at the bottom of this TechNote.
Hardware: Sony AIT-4 SDX 900V tape drives
If the issue described in this TechNote is occurring in your environment, please contact Sony Support: 800-801-7927.
Issue: In the above OS/Hardware configuration, VERITAS NetBackup (tm) Enterprise Server 5.x and NetBackup Server 5.x, backups exit with status 0 (successful), but show "ERR - invalid tar header encountered, attempting to continue" in the Restores Progress log. This issue occurs when attempting a restore from a tape that has spanned media. When this error occurs the data is not restorable.
(Important Note: This issue also affects UNIX platforms, however, with UNIX platforms NetBackup exits with a Status Code 84: media write error. Please visit the following TechNote for UNIX platforms: http://support.veritas.com/docs/274292 .)
This issue is known to occur with the Sony AIT-4 SDX 900V tape drives. This happens when the last of block of data that is written at EOM (End of Media) and the image spans media, NetBackup does not know that it gets written. This issue resides within the firmware on the tape drives. Customer's using these tapes drives should contact Sony for further information.
How to tell if affected:
After attempting a restore with NetBackup and the above OS/Hardware configuration, view the Restore Progress log and look for the message that is in bold within the following snippet:
12/16/2004 8:59:25 AM - begin Restore
12/16/2004 8:59:26 AM - 1 images required
12/16/2004 8:59:26 AM - media 000027 required
12/16/2004 8:59:26 AM - media 000024 required
12/16/2004 8:59:29 AM - restoring image hcl-959_1103163163
12/16/2004 8:59:29 AM - connecting
12/16/2004 8:59:30 AM - started process bptm (2708)
12/16/2004 8:59:30 AM - mounting 000027
12/16/2004 8:59:34 AM - connected; connect time: 00:00:05
12/16/2004 9:01:14 AM - mounted; mount time: 00:01:44
12/16/2004 9:01:14 AM - positioning 000027 to file 34
12/16/2004 9:03:57 AM - positioned 000027; position time: 00:02:43
12/16/2004 9:03:57 AM - begin reading
12/16/2004 9:12:05 AM - started process bptm (2708)
12/16/2004 9:12:05 AM - mounting 000024
12/16/2004 9:24:51 AM - mounted; mount time: 00:12:46
12/16/2004 9:24:51 AM - positioning 000024 to file 1
12/16/2004 9:24:51 AM - positioned 000024; position time: 00:00:00
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: ERR - invalid tar header encountered, attempting to continue
12/16/2004 9:24:52 AM - Warning bpbrm(pid=916) from client hcl-959: WRN - unknown file type Q encountered, continuing to process file '' (0)
12/16/2004 9:24:52 AM - Critical bpbrm(pid=916) from client hcl-959: FTL - expected file '/E/TestData/Set05/Dir02/SubDir05/File013064', found file ''
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir05/File013064
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir05/File013065
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir05/File013066
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013067
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013068
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013069
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013070
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013071
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: ERR - more than 10 files not restored, logging will only continue in the progress log
12/16/2004 9:24:57 AM - restored image hcl-959_1103163163 - (media manager - system error occurred(174)); restore time 00:25:28
12/16/2004 9:24:57 AM - Warning bprd(pid=2744) Restore must be resumed prior to first image expiration on 12/29/2004 9:12:43 PM
12/16/2004 9:24:57 AM - end Restore; elapsed time: 00:25:32
the restore failed to recover the requested files(5)
OS platform: This issue is known to affect Windows 2000 and 2003 platforms that are supported with NetBackup 5.x. The operating system versions known to be affected are listed at the bottom of this TechNote.
Hardware: Sony AIT-4 SDX 900V tape drives
If the issue described in this TechNote is occurring in your environment, please contact Sony Support: 800-801-7927.
Issue: In the above OS/Hardware configuration, VERITAS NetBackup (tm) Enterprise Server 5.x and NetBackup Server 5.x, backups exit with status 0 (successful), but show "ERR - invalid tar header encountered, attempting to continue" in the Restores Progress log. This issue occurs when attempting a restore from a tape that has spanned media. When this error occurs the data is not restorable.
(Important Note: This issue also affects UNIX platforms, however, with UNIX platforms NetBackup exits with a Status Code 84: media write error. Please visit the following TechNote for UNIX platforms: http://support.veritas.com/docs/274292 .)
This issue is known to occur with the Sony AIT-4 SDX 900V tape drives. This happens when the last of block of data that is written at EOM (End of Media) and the image spans media, NetBackup does not know that it gets written. This issue resides within the firmware on the tape drives. Customer's using these tapes drives should contact Sony for further information.
How to tell if affected:
After attempting a restore with NetBackup and the above OS/Hardware configuration, view the Restore Progress log and look for the message that is in bold within the following snippet:
12/16/2004 8:59:25 AM - begin Restore
12/16/2004 8:59:26 AM - 1 images required
12/16/2004 8:59:26 AM - media 000027 required
12/16/2004 8:59:26 AM - media 000024 required
12/16/2004 8:59:29 AM - restoring image hcl-959_1103163163
12/16/2004 8:59:29 AM - connecting
12/16/2004 8:59:30 AM - started process bptm (2708)
12/16/2004 8:59:30 AM - mounting 000027
12/16/2004 8:59:34 AM - connected; connect time: 00:00:05
12/16/2004 9:01:14 AM - mounted; mount time: 00:01:44
12/16/2004 9:01:14 AM - positioning 000027 to file 34
12/16/2004 9:03:57 AM - positioned 000027; position time: 00:02:43
12/16/2004 9:03:57 AM - begin reading
12/16/2004 9:12:05 AM - started process bptm (2708)
12/16/2004 9:12:05 AM - mounting 000024
12/16/2004 9:24:51 AM - mounted; mount time: 00:12:46
12/16/2004 9:24:51 AM - positioning 000024 to file 1
12/16/2004 9:24:51 AM - positioned 000024; position time: 00:00:00
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: ERR - invalid tar header encountered, attempting to continue
12/16/2004 9:24:52 AM - Warning bpbrm(pid=916) from client hcl-959: WRN - unknown file type Q encountered, continuing to process file '' (0)
12/16/2004 9:24:52 AM - Critical bpbrm(pid=916) from client hcl-959: FTL - expected file '/E/TestData/Set05/Dir02/SubDir05/File013064', found file ''
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir05/File013064
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir05/File013065
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir05/File013066
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/
12/16/2004 9:24:52 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013067
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013068
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013069
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013070
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: UTF - /E/TestData/Set05/Dir02/SubDir06/File013071
12/16/2004 9:24:53 AM - Error bpbrm(pid=916) from client hcl-959: ERR - more than 10 files not restored, logging will only continue in the progress log
12/16/2004 9:24:57 AM - restored image hcl-959_1103163163 - (media manager - system error occurred(174)); restore time 00:25:28
12/16/2004 9:24:57 AM - Warning bprd(pid=2744) Restore must be resumed prior to first image expiration on 12/29/2004 9:12:43 PM
12/16/2004 9:24:57 AM - end Restore; elapsed time: 00:25:32
the restore failed to recover the requested files(5)
Issue exists at
firmware version: VERITAS
is unable to positively identify or specify firmware version. Please
contact Sony Support to assist you in identifying which firmware version you
have in your environment: 800-801-7927.
Workarounds:
1. Uncheck the box in front of "Allow backups to span media" from the following location: Admin GUI > Host Properties > Master Server properties > Media (Refer to Figure 1). Please note: This option is selected by default.
Figure 1
2. If it is
necessary to span media in your environment, VERITAS recommends that you use an
alternate drive destination.
After either of the
above workarounds are implemented, perform a full backup.
Formal Resolution:
At the time of this
writing, VERITAS and Sony are working together to re-qualify these drives with
updated firmware provided by Sony. Until VERITAS can re-qualify the Sony
AIT-4 SDX 900V tape drives, VERITAS NetBackup 5.x will not support the Sony AIT-4
SDX 900V tape drives. The process to re-qualify the Sony AIT-4 SDX 900V
tape drives is currently in progress. VERITAS strongly recommends
implementing either workaround provided in this TechNote until these drives are
re-qualified. Please contact Sony Support for more information:
800-801-7927.
Sony developed a new
firmware version (ref.# 0101) which fixes this problem. End users must get this
firmware upgrade from Sony, and upgrade their installed drives. Firmware
upgrades are available from:
1. Tech Support Tel#
1-800-801-7927
2. Or Email Support
at Tape.Support@am.sony.com
3. Or by Web @ http://sony.storagesupport.com/ait/sdx900v.htm
For further updates on
this issue, please subscribe to this document by clicking on the following
link: http://maillist.support.veritas.com/notification_services.asp?doc=274864
If you have not
received this TechNote from the VERITAS Email Notification Service for Software
Alerts, please subscribe at the following link:
If you have any
questions or concerns regarding this issue, please contact VERITAS Technical
Services.
NetBackup
status code 183: tar received an invalid archive
|
Article: TECH58657
|
|
|
Created: 2008-01-19
|
|
|
Updated: 2009-01-12
|
|
|
Problem
NetBackup
status code 183: tar received an invalid archive
Solution
Message: tar
received an invalid archive
Explanation: The data that was passed to tar was corrupt.
Recommended action:
If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar debug log directory on the client and rerun the operation.
Explanation: The data that was passed to tar was corrupt.
Recommended action:
If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar debug log directory on the client and rerun the operation.
a Check
the tar debug log file for any error messages that explain the problem.
b Reboot
the client to see if it clears the problem.
c When
you finish with your investigation of the problem, delete the
/usr/openv/netbackup/logs/tar directory on the client.
If the
problem is with a Microsoft Windows, NetWare, or Macintosh client:
a Create
a bpcd debug log directory on the client (on a Macintosh NetBackup creates the
log automatically).
b On a
Windows client, create a tar debug log directory.
c
Increase the debug or log level as explained in the debug log topics in Chapter
3.
d Rerun
the operation and check the resulting debug logs. e Reboot the client to see if
it clears the problem.
NET_BUFFER_SZ,
SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS - how they work and how to configure them
|
Article: TECH1724
|
|
|
Created: 1999-01-15
|
|
|
Updated: 2011-01-01
|
|
|
Article
Type
Technical Solution
Technical Solution
Product(s)
Environment
Subject
Languages
Problem
NET_BUFFER_SZ, SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS - how
they work and how to configure them
Solution
Here is some
information on undocumented features for setting the Network Buffer Size, Data
Buffer Size, and Number of Data Buffers used by NetBackup (tm) on UNIX
platforms.
NOTE: These settings are used to tune the performance of NetBackup.
TCP/IP Network Buffer Size.
/usr/openv/netbackup/NET_BUFFER_SZ is a file containing a number indicating the TCP/IP socket buffer size that should be used for data transfers between the NetBackup media server and its clients. If the file does not exist, the default value used is 32032 bytes.
The default value can be changed by creating the file /usr/openv/netbackup/NET_BUFFER_SZ on the NetBackup media server and client systems.
The /usr/openv/netbackup/NET_BUFFER_SZ file is a text file containing a single line specifying the value of the Network Buffer Size in bytes in decimal format.
For example, a Network Buffer Size of 64KB could be configured and checked like this:
# echo "65536" > /usr/openv/netbackup/NET_BUFFER_SZ
# cat /usr/openv/netbackup/NET_BUFFER_SZ
65536
#
Most networks can handle a NET_BUFFER_SZ of 262144 (256K). In this case to make the changes
to the NetBackup media server and Unix clients, the commands would be:
# echo "262144" > /usr/openv/netbackup/NET_BUFFER_SZ
# cat /usr/openv/netbackup/NET_BUFFER_SZ
262144
#
For Windows clients, the Communications Buffer size setting is modified to 256. See the
Technote reference below for further details.
Specifying a larger value in the NET_BUFFER_SZ file may improve the performance of backups and restores. It is recommended that if NET_BUFFER_SZ is used, the same value should be set on all the NetBackup media servers and clients.
Data Buffer Size and Number of Data Buffers.
The NetBackup media server uses shared memory to buffer data between the network and the tape drive (or between the disk and the tape drive if the NetBackup media server and client are the same system). By default, NetBackup uses a default value of 8 x 32KB shared memory buffers for non-multiplexed backups and 4 x 64KB for a multiplexed backup.
These buffers can be configured by creating the files /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS and/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS on the NetBackup media server. These parameters are meant exclusively for media servers, and should not be used on a pure master server or client.
The SIZE_DATA_BUFFERS file should contain a single line specifying the data buffer size in bytes in decimal format.
The NUMBER_DATA_BUFFERS file should contain a single line specifying the number of data buffers in decimal format.
The value in the SIZE_DATA_BUFFERS file has to be a multiple of 1024B.
It is common to increase SIZE_DATA_BUFFERS to 256KB and NUMBER_DATA_BUFFERS to 16.
IMPORTANT: Because the data buffer size equals the tape I/O size, the value specified in SIZE_DATA_BUFFERS must not exceed the maximum tape I/O size supported by the tape drive or operating system. This is usually 256 KB or 128 KB.
In order to configure NetBackup to use 16 x 256 KB data buffers, specify 262144 (256 x 1024) in SIZE_DATA_BUFFERS and 16 inNUMBER_DATA_BUFFERS:
# echo "262144" > /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
# echo "16" > /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
# cat /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
262144
# cat /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
16
#
Care should be taken when changing these values. For example, increasing the tape buffer size can cause some backups to run slower and there have been cases where there have been restore problems.
IMPORTANT: After making any changes, it is vitally important to verify that the following tests can be completed successfully:
1. Run a backup
2. Restore data from the new backup created in step 1
3. Restore data from a backup created prior to the changes to SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS
The number and size of the data buffers used by the NetBackup media server can be checked by looking in the bptm log file:
12:02:55 [28551] <2> io_init: using 32768 data buffer size
12:02:55 [28551] <2> io_init: CINDEX 0, sched bytes for monitoring = 2000
12:02:55 [28551] <2> io_init: using 8 data buffers
or
15:26:01 [21544] <2> mpx_setup_restore_shm: using 12 data buffers, buffer size is 65536
Increasing the size and number of the data buffers will use up more shared memory, which is a limited system resource. The total amount of shared memory used is: (buffer_size * num_buffers) * drives * MPX.
So, for two tape drives, each configured with an MPX of 4, and with 16 data buffers of 256 KB, the total shared memory usage would be:
(16 * 256k) * 2 * 4 = 32 MB (32768 KB)
Take into consideration the total system resources and the entire network.
The Maximum Transmission Unit (MTU) for the LAN may also have to be changed.
NOTE: For Digital Linear Tape (DLT) drives, the number that seems to give the best performance for SIZE_DATA_BUFFERS is 65536. Further performance improvements can be achieved by increasing the value in the NUMBER_DATA_BUFFERS file.
NOTE: These settings are used to tune the performance of NetBackup.
TCP/IP Network Buffer Size.
/usr/openv/netbackup/NET_BUFFER_SZ is a file containing a number indicating the TCP/IP socket buffer size that should be used for data transfers between the NetBackup media server and its clients. If the file does not exist, the default value used is 32032 bytes.
The default value can be changed by creating the file /usr/openv/netbackup/NET_BUFFER_SZ on the NetBackup media server and client systems.
The /usr/openv/netbackup/NET_BUFFER_SZ file is a text file containing a single line specifying the value of the Network Buffer Size in bytes in decimal format.
For example, a Network Buffer Size of 64KB could be configured and checked like this:
# echo "65536" > /usr/openv/netbackup/NET_BUFFER_SZ
# cat /usr/openv/netbackup/NET_BUFFER_SZ
65536
#
Most networks can handle a NET_BUFFER_SZ of 262144 (256K). In this case to make the changes
to the NetBackup media server and Unix clients, the commands would be:
# echo "262144" > /usr/openv/netbackup/NET_BUFFER_SZ
# cat /usr/openv/netbackup/NET_BUFFER_SZ
262144
#
For Windows clients, the Communications Buffer size setting is modified to 256. See the
Technote reference below for further details.
Specifying a larger value in the NET_BUFFER_SZ file may improve the performance of backups and restores. It is recommended that if NET_BUFFER_SZ is used, the same value should be set on all the NetBackup media servers and clients.
Data Buffer Size and Number of Data Buffers.
The NetBackup media server uses shared memory to buffer data between the network and the tape drive (or between the disk and the tape drive if the NetBackup media server and client are the same system). By default, NetBackup uses a default value of 8 x 32KB shared memory buffers for non-multiplexed backups and 4 x 64KB for a multiplexed backup.
These buffers can be configured by creating the files /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS and/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS on the NetBackup media server. These parameters are meant exclusively for media servers, and should not be used on a pure master server or client.
The SIZE_DATA_BUFFERS file should contain a single line specifying the data buffer size in bytes in decimal format.
The NUMBER_DATA_BUFFERS file should contain a single line specifying the number of data buffers in decimal format.
The value in the SIZE_DATA_BUFFERS file has to be a multiple of 1024B.
It is common to increase SIZE_DATA_BUFFERS to 256KB and NUMBER_DATA_BUFFERS to 16.
IMPORTANT: Because the data buffer size equals the tape I/O size, the value specified in SIZE_DATA_BUFFERS must not exceed the maximum tape I/O size supported by the tape drive or operating system. This is usually 256 KB or 128 KB.
In order to configure NetBackup to use 16 x 256 KB data buffers, specify 262144 (256 x 1024) in SIZE_DATA_BUFFERS and 16 inNUMBER_DATA_BUFFERS:
# echo "262144" > /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
# echo "16" > /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
# cat /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
262144
# cat /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
16
#
Care should be taken when changing these values. For example, increasing the tape buffer size can cause some backups to run slower and there have been cases where there have been restore problems.
IMPORTANT: After making any changes, it is vitally important to verify that the following tests can be completed successfully:
1. Run a backup
2. Restore data from the new backup created in step 1
3. Restore data from a backup created prior to the changes to SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS
The number and size of the data buffers used by the NetBackup media server can be checked by looking in the bptm log file:
12:02:55 [28551] <2> io_init: using 32768 data buffer size
12:02:55 [28551] <2> io_init: CINDEX 0, sched bytes for monitoring = 2000
12:02:55 [28551] <2> io_init: using 8 data buffers
or
15:26:01 [21544] <2> mpx_setup_restore_shm: using 12 data buffers, buffer size is 65536
Increasing the size and number of the data buffers will use up more shared memory, which is a limited system resource. The total amount of shared memory used is: (buffer_size * num_buffers) * drives * MPX.
So, for two tape drives, each configured with an MPX of 4, and with 16 data buffers of 256 KB, the total shared memory usage would be:
(16 * 256k) * 2 * 4 = 32 MB (32768 KB)
Take into consideration the total system resources and the entire network.
The Maximum Transmission Unit (MTU) for the LAN may also have to be changed.
NOTE: For Digital Linear Tape (DLT) drives, the number that seems to give the best performance for SIZE_DATA_BUFFERS is 65536. Further performance improvements can be achieved by increasing the value in the NUMBER_DATA_BUFFERS file.
|
|
No comments:
Post a Comment