Feature Pack NB_45_9_F.winnt.intel.exe provides fixes to the VERITAS NetBackup (tm) NT server and clients. It also contains fixes for NetBackup Add-on products and Database Agents.
| Article:TECH44135 | | | Created: 2005-01-04 | | | Updated: 2006-01-12 | | | Article URL http://www.symantec.com/docs/TECH44135 |
Problem
Feature Pack NB_45_9_F.winnt.intel.exe provides fixes to the VERITAS NetBackup (tm) NT server and clients. It also contains fixes for NetBackup Add-on products and Database Agents.
Solution
NB 4.5FP6 Pack NB_45_9_F
README October
4, 2005
================================================================================
This Feature Pack provides fixes to the VERITAS NetBackup (tm) NT server and
clients. It also contains fixes for NetBackup Add-on products and Database
Agents.
Symantec recommends that the backing up of active file systems be avoided,
or the use of snapshot technologies be implemented. The directory structure
reported back from the file system (to NetBackup) may not contain all of the
files available during the time of backup. NetBackup will not report errors
in many cases where the file's existence is not known to NetBackup as reported
by the file system.
================================================================================
=================
PACK DEPENDENCIES
=================
-- 4.5 FP6 must be installed prior to installing this Feature Pack.
-- For the latest robotics support please also download and install the
latest Mappings_4.5.<6 digit number>.zip from the support website:
www.support.veritas.com.
I. DOWNLOAD INSTRUCTIONS
II. INSTALLATION INSTRUCTIONS
III. UNINSTALL INSTRUCTIONS
IV. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_45_8_F
NB_45_7_F
=========================
I. DOWNLOAD INSTRUCTIONS
=========================
This is an update to NetBackup/Media Manager products
with the latest fixes for Windows NT NetBackup servers.
Download instructions:
1) Download the NB_45_9_F.winnt.intel_<6 digit number>.exe file
into a temporary directory.
where <6 digit number> is an internal tracking identifier
2) Extract the NB_45_9_F.winnt.intel_<6 digit number>.exe
by double-clicking on it.
This will create a number of files that include:
README.NT
and
Setup.exe
==============================
II. INSTALLATION INSTRUCTIONS
==============================
NOTE: For Feature Pack installation on Microsoft Cluster Environment:
- Install this Feature Pack on the inactive node(s) of the cluster,
performing Steps 1-4 below.
- Use the MSCS move group command to 'failover' the server to another node.
This should be done when the NetBackup system is quiet, that is, no
backups or restores are running.
- Install this Feature Pack on the newly inactive node of the cluster.
- (Optional) Use the MSCS move group command to 'failover' the server back
to the original node.
--------------------------------------------------------------------------------
Installation steps:
NOTE: If upgrading a NetBackup Windows 4.5 FP8 client to server or
Administration Console, the 4.5 Feature Pack must be uninstalled
prior to upgrading to 4.5 server or Administration Console.
1) Close all NetBackup Windows.
Make sure the NetBackup server system is quiet and has no active backups,
restores, duplications, etc., running. If there are NetBackup activities in
process, the Feature Pack will not install if the file to update is busy.
If a database client is being used, such as Oracle, ensure that the
database services are stopped. Database services can be stopped by
using the Control Panel -> Services tool. Repeat this process until
all databases have been stopped. These services must be restarted
once the patch is successfully installed.
2) Run Setup.exe. (Double-click on the icon from File Manager or Explorer
or run it from the command prompt.)
Setup.exe begins by stopping the appropriate NetBackup Services required
for the Feature Pack installation. Next, it will install the necessary
files into their correct locations. Finally, Setup.exe will restart the
appropriate NetBackup services.
3) Examine the <install_path>.Log file to ensure that no
errors took place during the installation, for example, an error during
Feature Pack installation because of a busy file.
4) Remove the temporary directory created in the download instructions.
============================
III. UNINSTALL INSTRUCTIONS
============================
**Important notice regarding un-installs on Windows**
Only the last Feature Pack installed on a Windows system can be un-installed.
1) Close all NetBackup Windows.
Make sure the NetBackup server system is quiet and has no active backups,
restores, duplications, etc., running.) If there are NetBackup activities
in process, the Feature Pack will not install if the file to update is busy.
If a database client is being used, such as Oracle, ensure that the
database services are stopped. Database services can be stopped by
using the Control Panel -> Services tool. Repeat this process until
all databases have been stopped. These services must be restarted
once the patch is successfully installed.
2) Go to <install dir of NetBackup>_Uninstaller.exe and
double-click on the executable.
(For example, C:Files_Uninstaller.exe)
3) Select the correct Pack to be uninstalled.
4) Click Uninstall.
5) You may review the trace file
(<install dir of NetBackup>_Uninstall.log)
to see what files were replaced.
==================================
IV. DESCRIPTION OF PROBLEMS FIXED
==================================
The following are descriptions of the problems fixed.
Please read the entire document before installing.
README Conventions:
Description
Describes particular problem or feature contained in this Feature Pack.
** Description **
Describes a problem that can lead to potential data loss. Please
read these problem descriptions carefully.
Workaround
Any available workarounds to a problem are also listed. Workarounds
can be used INSTEAD of applying the patch, however, Symantec strongly
recommends the "best practice" of being at the latest patch level.
Additional Notes
Any additional information regarding this problem or feature is included.
=============
Current pack
=============
================================================================================
Description:
Message lines in LTIerrno.h that begin with spaces instead of a tab are not
found by the search program.
Additional Notes:
The list of messages for MMm errors is changed and only effects localized
sights.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In the Windows NetBackup Administration Console, there is a timing issue
that causes the display to show multiple instances of the same physical
drive when there should be one line entry per physical drive in a SSO
environment.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The scheduler is modified to correctly process a status 134 error race
condition in a multiplex backup.
This condition occurs when a multiplex child bpsched starts a backup, but
the storage unit is over committed. A status 134 is sent back to the
multiplex child bpsched, but the child schedule is already adding another
backup to the multiplexed group.
The child schedule attempts to send the new jobs information to bpbrm, but
bpbrm has exited and the connection is defunct. Scheduler was incorrectly
logging the defunct connection in the job progress log. With this change
the scheduler will not log the broken socket, but will correctly read and
process the 134 status from the in-bound connection.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When performing Windows backups on an Itanium server running
Windows 2003, the backups may fail with a 54 and a 41 status.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Executing drfile.exe may generate an application error.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
bpretlevel loops echoing 'What?' when changing retention levels. No input
seems to be a satisfactory response to exit the loop until a ctrl-C is
entered. There does not seem to be any way to change retention levels
with the CLI because of this bug.
The following is the discovered resolution.
An earlier change had changed all occurrences of gets() to fgets(), but
failed to recognize that fgets() WILL return the '', whereas gets()
did not. The subsequent strcmp was not expecting the '', and
always failed. The solution is to strip the [new] trailing '' to
emulate the gets() behavior.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpbrm can hang if a database agent backup fails in a certain way.
The job appears to be running in the Activity Monitor until it is
terminated by the administrator.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
corrected situation where scheduler would lose a backup in the middle of a
catalog backup.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Multiplexed backup jobs would occasionally hang. This would happen if the
bptm or bpdm parent process crashed, or if bptm could not successfully add
the TIR fragment for a TIR backup. It may also happen because of a timing
problem in bpbrm when new jobs are started.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When backing up Lotus Notes databases, some databases were skipped. These
skipped databases were not reported as an error; the backup exited with a
status 0 instead of a status 1.
(All NetBackup Windows Clients Linux2.4 RS6000_433 RS6000_51 SOLARIS)
--------------------------------------------------------------------------------
Description:
If the add_slave_on_clients command is unable to add the media server
entries to one client, it may incorrectly update the media servers on
subsequent clients. Typically, only one media server will be added to the
remaining clients.
Workaround:
Use the Host Properties GUI to update the server list for the clients.
Use the bpsetconfig admincmd to update the server list for the clients.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
After a controlfile autobackup the image verification fails.(ORA-27206:
REQUESTED FILE NOT FOUND IN MEDIA MANAGEMENT CATALOG)
Workaround:
To avoid this issue, add the touch file USEDEFAULTDATERANGE to
/usr/openv/netbackup on UNIX or VERITASon Windows.
(NetBackup Clients: HP Intel-NT Linux2.2 NCR RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris)
--------------------------------------------------------------------------------
Description:
bprd cannot clean up a vault session directory that contains files that are
larger than 2GB .
(All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpimage ¿cleanup process fails with the message, "Too many files open"
when using ASCII catalog and FlashBackup policies.
Workaround:
To avoid this issue, run cleanup for a single client at a time.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup SQL Server agent fails when an attempt is made to back up
more than 255 databases using one batch file. This occurs if the backups
are individually specified in the database or if $ALL is used and there are
more than 255 databases on the SQL Server host.
When this occurs the Automatic backup job fails to terminate.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
During a NetBackup MSSQL scheduled backup, the bpbdb.log shows
a log entry with a severity <16>, however, the backup succeeds.
Receiving this error indicated that the was set incorrectly for an
informational message.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Corrected the display of new the ACS vendor media types: T10000T1,
T10000TS, and T10000CT. Also corrected the allowable type that is the
ACS vendor media type, LTO_400G.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpdbm may crash if it is unable to determine the host name of caller.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A SAP online backup is started and a Tablespace (PSAPES46CI) in the Oracle
database is placed in BACKUP MODE by the agent. However the backup receives
a STATUS 134 error in BPTM & BPBRM. The bpbkar, bptm, and bpbrm processes
exit and clean up after themselves. The SAP agent process remains active,
awaiting the backup to be queued and run again, leaving the Tablespace
(PSAPES46CI) still in BACKUP MODE.
(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
In certain firewall configurations, multi-stream backups from Linux client
may fail with status 25 if the vnetd connect-back is used.
(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
The vmoprcmd -comment <drive_index> <comment_string> command overwrites
the serial number that is specified if the comment_string size is 26.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NDMP restores fail with Hitachi NAS when restoring the entire backup image.
The NDMP log shows the path being sent twice in the NDMP_DATA_START_RECOVER
message.
Workaround:
Restores will work as long as the file system path is not selected (the
path that was initially backed up). If the entire image is needed for
restore, select all the files and directories in the file system path
instead.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
* Description:
NetBackup processes may core dump if an error occurs. The stack from the
core file showed problems with the ndmp_user_scsi() or ndmp_user_tape()
functions.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
On a multimedia type robot, robotic inventory was failing while inserting
media into the volume database. The inventory operation successfully inserts
media of one type but fails while inserting media of another type. It does
not take the media type of existing standalone media into consideration.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added a new ID for the duplicated message.
Changed:
ovgetmsg("DmeBrm0166N", LC_C, sizeof(lmsgl), lmsgl, lc_messages,
sizeof(cmsgl), cmsgl, "cannot create data socket" );
To:
ovgetmsg("DmeBrm0167N", LC_C, sizeof(lmsgl), lmsgl, lc_messages,
sizeof(cmsgl), cmsgl, "cannot create data socket" );
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Vault can physically eject tapes but it does not remove them from media
manager.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
An XBSA application would hang during a shared memory backup (such as, the
client and the media server are the same machine) if a problem occurred
that caused the bptm to exit. The BSASendData() call did not return.
(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
If the bpgetmedia options -h and -M were both specified, the -h argument
would always inherit the -M argument, and the original -h value would be
lost.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When bpbackup is run with the option to wait for the completion of the
backup job, a firewall between bpbackup and bprd can shut down the socket
while bpbackup waits for the completion status. This causes backint to
get stuck in an infinite loop during database backups.
(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
During the alternate client restore, the secondary restore process
was not passed the value for the browse client(source client).
(All NetBackup Windows Clients Linux2.4 RS6000_433 RS6000_51 SOLARIS)
--------------------------------------------------------------------------------
Description:
Updated this release to include the most recent device entries.
Fixed the following:
IBM3583 barcode reader recognition issue with newer library firmware.
Quantum PX720 barcode reader recognition issue.
Added the following:
Diligent VTF Open
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in the following
robotic libraries. The drives are properly configured within the library,
instead of being configured as standalone drives.
- NEC T40A
- HP UHDL
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The ACS robot inventory may timeout when the ACSLS server is
overloaded. Timeouts increased.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When backing up files using VSP to back up open/active files on Windows
clients, files deleted while the backup was running would not be backed up
and could not be restored. This was not the expected behavior because all
files that existed during the time the VSP snapshot creation occurred (at
the beginning of the backup) should have existed when the backup was run
and any file deletions during the course of the backup should have affected
the backup job, because backups using VSP used the VSP snapshots to
enumerate files to be backed up.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
If the forked re-read storage unit process detected a transient error, it
would error, exit, and then remove the scheduler message queues.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When running VSP-enabled backups to back up open/active files, backups would
intermittently hang after the VSP snapshot creation had taken place. The
bpbkar32 logs indicated that snapshots were successfully enabled for the
backup but inexplicably stopped while backing up files. The bpbkar32 back-up
process then stopped processing and appeared to hang until it was explicitly
killed by Windows Task Manager.
(All NetBackup Windows Clients)
================================================================================
=========
NB_45_8_F
=========
Description:
A NetBackup restore that has a path specified to be excluded from the restore,
but that path does not even exist in the backup image, was completing with a
partial success status of 1. Changes have been made so that a backup such as
this completes successfully with a status of 0.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Adjusted a loop used during the deletion of a mpx group. This loop was not
functioning correctly on the W2K platform and resulted in removal of
additional mpx groups.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
"Ghost" backup jobs were appearing in the Activity Monitor.
A deleted backup job could (partially) re-appear. This would only happen
to a deleted job that is one number lower than a multi-copy backup.
Example:
1) Job n finishes.
2) Job n is deleted from the Activity Monitor.
3) Multi-copy job n+1, n+2, n+3 finishes.
4) Activity monitor incorrectly updates jobs n, n+1, n+2.
5) Deleted job n (partially) re-appears.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The interrupt code paths for the Scheduler were simplified to eliminate
scheduler core dumps because the interrupt handlers were too "noisy".
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Corrected potential problems with memory leaks and non-initialized malloc
space.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When the scheduler verbose is set greater than 0, there is the potential for
Jobs to exit with a status 50. This is more likely on systems that experience
connection issues. The situation occurs when the scheduler prints a message
and loses the errno value. Armed with the incorrect errno value, the scheduler
exits (status 50) the current running jobs.
Workaround:
To avoid this issue, set the scheduler verbose to zero.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpplschedrec -deldayomonth command deletes a range of days instead of
the specified day.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A backup is established with the following:
- Multiplexing enabled
- Multi-copy enabled
- Continue backup on copy failure
Excessive failure messages are displayed if one of the copies fails, and
additional backups attempt to join the same multiplex group.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In the Windows client GUI, the "Temporary location for log and patch
files" for Exchange 2000 restores may now contain space characters.
Workaround:
To avoid this issue, do not use space characters in the "Temporary location
for log and patch files" path for Exchange 2000 restores.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Vault jobs fail with "status 23" when run from a vault policy if another
"Program" directory or file resides on the same drive on which NetBackup
is installed.
Workaround:
Run the vault job by using a vltrun command from a command prompt, run the
profile from the shortcut menu, or rename the other "Program" directory or
file on the drive.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When trying to perform a Lotus PIT restore (using PIT) when a secondary
restore is required to restore requested Lotus transaction log extents, the
following error is encountered:
"Invalid start date: 11/15/99" syntax error in bprestore. Only applies to
restoring Transaction Logs function - standard nsf files are ok.
tar debug log shows:
16:32:19 (101307.001) INF - Begin Lotus point in time database recovery to:
06/05/2004 16.29.22 CEDT
16:32:19 (101307.001) INF - Transaction Log:/A1VG3DATA/S0000160.TXN Required
for Recovery
16:32:19 (101307.001) INF - Requesting Restore of
Log:/A1VG3DATA/S0000160.TXN
Id:001c6243c1256e7d-f762d76fa9030000
LogNo:160
16:32:19 (101307.001) Invalid start date: 11/15/99
16:32:19 (101307.001) EXIT STATUS 144: invalid command usage
16:32:19 (101307.001) INF - NBLN_RecoverDb() RecoverErrorCode:0x13E3
DbIndex:0
16:32:19 (101307.001) ERR - /A1VG1DATA/c59admin_domino/testtl.nsf Recovery
Failed!
(0x13E3:Recovery Manager: Error from Logging Subsystem.)
Bprestore demonstrates incorrect syntax:
16:32:19.346 [83270] <2> logparams: -B -w -t 25 -s 11/15/99 -R
/usr/openv/netbackup/logs/user_ops/LN_Restore_Rename_File_87834.chg
/Transaction Logs/S0000160.TXN~001c6243c1256e7d-f762d76fa9030000
16:32:19.361 [83270] <16> process_args: Invalid start date: 11/15/99
16:32:19.361 [83270] <2> bprestore: exit with status = 144
Bplist can also recreate error with the following options;
# bplist -t 25 -l -R -s 11/15/1999
Invalid start date: 11/15/1999
EXIT STATUS 144: invalid command usage
(NetBackup Clients: Intel-NT Linux2.4 RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
Description:
SAP Alternate Client restores may fail. The SAP Agent was unable to read
the output file of the restore_filter script. This failure produced a log
similar to the following:
"14:30:00.381 [7082] <16> backint_restore_filter: cannot open restore
working file:
/oracle/BD1/sapbackup/backint_dir/.backint.filter.1085772595.7082
14:30:00.381 [7082] <16> backint_do_restore: ERROR: running restore filter"
In addition, the restore_filter script was unable to handle a use case
where source client (a backed-up client) did not have soft links to the
actual file paths of the SAP data files. During a restore on the target
client (a new destination client), the agent would not adjust file paths to
match the originally backed-up paths. This issue would produce a log file
similar to the following:
"**************************************************************************
Program: ./backint 5.0GA
Input File: ./in_re
Profile: ./initSAP.utl
Function: RESTORE
***************************************************************************
#NOTFOUND <input file name>
***************************************************************************"
or in the backint log:
"10:56:07.093 [2838] <2> backint_find_master_time: exit status = 2
10:56:07.094 [2838] <4> backint_do_restore: #NOTFOUND /tmp/bd1/file1"
(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
After a failure had occurred, the SAP DB Environment Agent would report a
Success despite the actual failure. This problem only occurred when an
agent is called into the SAP DB environment with the adapter program and
there were previously successful backups and current backup failures. A
problem similar to this would produce a log file similar to the following
example:
"
...
08:16:49.143 [1433628] <16> backint_system: ERROR: executing
command /usr/openv/netbackup/bin/bpbackup -w -t 17 -h pollux_bk -S
frsux071 -c ASV_SAP_A30_online -s Default-Policy -
L /usr/openv/netbackup/logs/user_ops/sap/.backint.log.0.1083392186.1282186 -
08:16:51.208 [1282186] <16> dbc_Wait: ERR - job (1433628) failed status (71)
...
08:16:52.853 [1282186] <4> backint_do_backup: #SAVED
NS1083106428 /home/adasav/A10/NB_puffer1/STAGE3.0
08:16:52.853 [1282186] <4> backint_do_backup: #SAVED
NS1083364604 /home/adasav/A10/NB_puffer1/STAGE1.0"
Note: The example above shows a backup command failed, but the agent
reported that the input files were saved. This happened because agent
saved these files in a previous backup. This might mislead the user into
thinking the backup of SAP on the SAP DB was successful when it actually
failed.
(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
The spin control for the "Number of Parallel Streams" field in the "Backup
Limits" page of the Windows Oracle backup wizard now works correctly.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
An NDMP backup in the ASCII catalog format would fail and produce the
following error in the bptm log.
08:42:17.202 [5704.5624] <2> write_data_ndmp: calling
ndmp_bpfsmap_create
08:42:18.304 [5704.5624] <2> write_data_ndmp: bpfsmap longjmp: setjmp
returned 6; aborting backup
...
08:42:18.764 [5704.5624] <2> write_data: write_data_ndmp() returned -8,
EXIT_Status 6, Kbytes = 1359099
08:42:18.774 [5704.5624] <2> write_backup: write_data() returned,
exit_status = 6, CINDEX = 0, TWIN_INDEX = 0, backup_status = -8
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
A dual stream backup starts only one backup for each Redo Log Group after
the first Redo Log Group is backed up correctly (two backups).
This problem occurs in following configuration:
1. BRARCHIVE is called with -f option
2. SAP Agent configuration file (init<SID>.utl) contains sched_log
parameter.
The sched_log parameter is the value of the second schedule that the SAP
Agent can use to backup archive logs. When this parameter is enabled, two
backups of archive logs will be performed. This enables backing up the same
archive logs to different media. This parameter is processed correctly by
the SAP Agent when BRARCHIVE is called without -f option.
However, when BRARCHIVE was called with the -f option, only the first
group of archive logs were backed up to both schedules. Any subsequent
group of archive logs would be backed up to only one (original) schedule.
(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
The scheduler does not automatically start "bpexpdate -deassignempty" to
deassign media that do not have associated images after "bprecover -l" has
been run.
Workaround:
If a bprecover -l has been executed, remove the following file:
UNIX:
/usr/openv/netbackup/bin/deassign_lock
Windows:
VERITAS_lock
Do not remove this file if a catalog recover (bprecover -r) has been done.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When performing an Intelligent Disaster Recovery and the communications
between the client and server are configured to use vnetd, the submission
of the restore request from the recovery wizard will fail.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When performing full backups of using the UNC naming convention, the
archive bits on some files are not getting cleared.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When performing an IDR restore with a bootable CD created from a Japanese
Windows 2000 SP 3 integrated CD, the setup fails with the following error:
"The following value in the .SIF file used by Setup is corrupted or
missing: Value 0 on the line in section [SourceDisksFiles]. With
key 'sp3.cab' error is received"
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
When performing a VSP-enabled backup, the first attempt at the backup does
not process the VSP excluded drives and crashes.
When a second attempt occurs, the backup acknowledges the VSP excluded
drives and then functions properly.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
In certain cases, a backup job may receive an error, but the job remains
active and must be manually cancelled.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
A loss of multiplexed groups within bpsched.exe resulted in the failure to
cancel multiplexed backups.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The following logging statement in bptm was confusing.
09:37:46.035 [16536] <4> ndmp_internal_open_and_auth: NDMP server DEBUG
suggests protocol version 3
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Attempting to restore from an image that was backed up with the following
setting would result in a failed status 5.
"SET FILES = ( Multiple Files ) "
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Exchange Server shutdowns due to lack of space on the transaction log file
device.
The transaction logs were probably not truncated because the Exchange
backup failed. The original backup may have failed due to networking or
media failures and retry attempts may fail with a status 1.
Investigation of the Error logs would reveal the following error,
"INF - HrESEBackupSetup: Microsoft Information Store = 0xc80001f9"
"ERR - XCHG_BackupRead() FS_ReadObj() Failed! 0xFFFFFE30:FS_COMM_FAILURE".
These errors indicate that the Exchange StorageGroup is already in
backup mode. Close inspection may also reveal that the bpbkar32 from the
original backup attempt is still running.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
You can now view the correct number of files backed up in the Activity
Monitor.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Update ltid such that it does not leave behind defunct processes when it
spawns vmd.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Bprd hits a segmentation fault and core dumps. The issue occurred when the
log-file path for the bprestore log exceeded 58 characters. This only
occurred when the media server involved was not the master server, and when
FQDN names were used.
To resolve this issue, the command buffer size has been increased to
BUFFLEN (4096), and implemented bounds checking on all string buffers,
where practicable, by using V_strlcpy, V_strlcat, and snprintf().
Additional Notes:
While libVcom.so and netbackup.dll contain no changes, they are required
to resolve new entry points introduced in libsfr.so. In addition,
libsfr.so is Solaris only.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A race condition existed when two restore jobs needed the same piece of
media, from the same server, when this media was not already in the media
database. This condition could cause the media to be added twice, and one
of the restores to fail.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Improved VMD debug logging to better enable analysis for slow servers.
Allow control of VMD child timeout, such that slow servers can be
interrupted, before VMD encounters connection timeout's on other
connections.
Add "VMD_CHILD_TIMEOUT = xx", to the vm.conf file. xx is the number of
seconds to wait for a child to release its lock on the volume database.
Allowable time is 60 to 360 seconds, where 360 is the default (a value
used prior to this patch).
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup was not properly examining the SCSI library mailslot status bits;
therefore, during ejects of more than a MAP-full of media, the eject
operation may abort after the first MAP-full is removed.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
While trying to reduce the size of a database, the command "bpimage -
cleanout -client dill-bk" was used. Using the command in this way caused
bpimage to core dump.
Workaround:
To avoid this issue, allow the nightly clean-up process to clean the
catalog.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup for Lotus Notes will successfully backup Domino transaction log
extents, but will NOT truncate them.
Workaround:
Do not specify the TRANSLOG_Path for the Lotus transaction log directory
in the notes.ini as a symbolic link. Make sure the Lotus transaction log
directory is always the actual physical path.
(NetBackup Clients: Intel-NT Linux2.4 RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
Description:
It was possible that the bpjobd process may hang under certain conditions.
It has been demonstrated that this can happen if bpduplicate and bptm
processes are killed, but it may occur in other situations. The bpjobd
process does not die, it just loops consuming CPU time, and nothing
is written to the debug log. This prevented the job DB from being updated
with the status of existing jobs, or new jobs. bpjobd must be killed and
restarted by the system administrator to resolve this problem.
This problem is indicated by the following data in the bpjobd debug log,
referring to non-existent job ID 3:
18:45:00.734 [17433] <2> process_active_job: Frame type is 3 (jobid 3)
Sock (93)
18:45:00.734 [17433] <2> process_active_job: Adding provider(1) for job(3)
socket (93)
18:45:00.734 [17433] <2> process_active_job: Begin to write (JOBTRYFILE) at
offset 68 job (3)
Workaround:
To avoid this issue, kill and restart the hung bpjobd.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A large number of down storage units would result in and apparent
scheduler hang. In reality, the scheduler was timing out to each media
server in series. This fix recognizes and skips duplicate attempts to a
down media server.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
To assist image database cleanup in 24x7 environments, image database
cleanup will always run in background. bpsched will not wait until the
cleanup is complete before scheduling new jobs. In addition, bpsched will
initiate an image database cleanup at periodic intervals, 12 hours by
default. The time interval may be changed by using the
bpconfig -cleanup_int <hours> command. For example, to change the interval
to 24 hours, execute the following command:
bpconfig -cleanup_int 24
Use a value of 0 to disable bpsched from starting the periodic image
database cleanup. The maximum value is 744 hours. Bpsched will still
perform an image database cleanup at the end of a session, however, it will
be run in background. On UNIX systems, bpadm may also be used to change
the interval.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The predict algorithm was not sorting correctly. It failed to position
cumulative incremental backups before the differential incremental backups.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
You can now perform Phase 1 imports on Backup Exec media in ACS and TLM
robots.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The scheduler debug log was filling with the following message:
"storage unit was not assigned for clientjob <host name> <policy name>
<stunit name> <copy>"
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When a database agent gets requeued multiple times in a very short period
of time, there were cases where the server would time out waiting for the
client to connect. This fix prevents the client from getting behind the
server in these instances.
(NetBackup Clients: Alpha HP Intel-NT Linux2.4 RS6000_433 RS6000_51 SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
The device configuration user interface can encounter a long delay when
selecting a robot. The time required to filter the lists in one case was
reported to be approximately 20 minutes.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Very large Teradata backups had an error where an overflow of an integer
byte count of fractional blocks caused the wrong size to be sent to bptm.
This size value did not match what bptm counted and the backup was then
aborted.
Workaround:
To avoid this issue, you can back up the large database using multiple
streams.
(NetBackup Clients: Intel-NT NCR )
--------------------------------------------------------------------------------
Description:
An Oracle autobackup of the control file is very slow because of the format
of the piece name.
(NetBackup Clients: Dgux HP Intel-NT Linux2.2 NCR RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
A multiplexed TIR duplication would fail if the prior backup duplication
had a TIR size greater than 1 Gigabyte, and would lead to a bptm crash.
Workaround:
To avoid this issue, retry the duplication using non-multiplexed
duplication. It is also possible that the duplication will succeed by
trying multiplexed duplication.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Performing an Exchange Information Store restore causes misleading "bogus"
bpbrm errors in the Activity Monitor. The restore is successful and the
Activity Monitor description looks like the following:
3/2/2004 9:07:38 AM - Error bpbrm(pid=268) from client backrest: TAR -
Restoring Exchange 2000 ESE object C:
Files.edb
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Exchange Mailbox backups would fail with a Dr. Watson under the following
conditions:
The problem occurred when the mailbox message (including the GUID), plus a
mangled name length, plus 12 (for some additional characters) would equal
exactly 512. This needs to take place at the end of a data block, which by
the default is 64K. The result is overrunning the end of the data block,
and this exception is the result.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
The following changes have been made:
- Added the drive, IBM 3592J
- Add the following new libraries:
- HP EML E-Series
- EMC Disk Library
- STK L7
- STK SL500
- STK Virtual Library
- Adds fixes for eject issue with the ADIC libraries.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added support for the following drives and media types for ACS:
- Drives:
- STK 10000A (T1)
- HP LTO-3
- Media:
- T10000T1
- T10000TS
- T10000CT
- LTO-400G
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If an SSO drive is DOWN on all servers, and its scan host unregisters
(services are shutdown), vmd/DA will not transfer this drive to another
scan host. If the drive is brought UP on a server(s), it will have no
scan host, and will stay in the NO-SCAN state.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Some FlashBackup backups would take longer on NetBackup 5.0 than they did
for NetBackup 3.4 because of additional overhead of the binary catalog.
Workaround:
Raise the maximum files per add value using the
/usr/openv/netbackup/MAX_FILES_PER_ADD to 9500, which will raise the limit
for all backups.
Additional Notes:
The number of files added per call to the catalog has been raised to 95000
from 500 for FlashBackup. This limit can be modified by putting the
desired value in /usr/openv/netbackup/FBU_MAX_FILES_PER_ADD, which only
affects FlashBackup backups.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in the following
robotic libraries. The drives are properly configured within the library,
instead of being configured as standalone drives.
- EMC Disk Library
- QUANTUM ValueLoader
- HP MSL6000 Series
- STK SL500
- STK L7
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
vmphyinv is unable to read the tape header in NDMP drives. This affects
NDMP drives and the NetWare media server (that are handled using NDMP
protocol).
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The SQL Server sometimes failed to create the VDI object within the
30 second default of "VDITIMEOUTSECONDS" during scheduled backups. To
resolve this issue, the VDI timeout has been increased to 300 seconds.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
A SQL Server move script created for a multi-stripe backup image sometimes
fails to include the .ldf file.
Workaround:
To avoid this issue, manually edit the move script to include the MOVE log
(.ldf) section and the restore will be successful.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
NetBackup SharePoint Portal Server backups fail when the NetBackup Client
Service logon account and the SharePoint Portal Server Logon account do
not match.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
The scheduler would take a long time scheduling multiple data stream jobs
if there were many policies that were due to be autodiscovered at once.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When selecting a media ID for backup, if the allocation date in the
media database does not match the assigned date in the media manager
database, FREEZE the media because there could be database inconsistencies.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Multiplexed jobs can hang if the DATASOCKET message is not recognized.
A log message of "unknown media message DATASOCKET" will appear in the
bpbrm debug log.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Exchange agent has the requirement that the NetBackup client
service account run under an Exchange Administrative account. However, if
the service is running as LocalSystem on a restore attempt, the restore
will hang and end with a status 5 after tar32 causes an exception fault.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
For NDMP restores on NetApp filers, more than 1024 files can be restored
using DAR.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
When performing an alternate client restore of RAW devices with the SAP
Agent the restore will fail. The following errors will be reported in
brrestore:
BR386E File /dev/vgsapiBWP/rBWPclui_1 reported as not found by backup
utility
The following information will be reported in the backint logs if logging
is ON and VERBOSE=5:
11:13:28.129 [20169] < 4> backint_find_master_time: WARNING: not found in
bplist list: /dev/rdsk/c1t4d0s1
11:13:28.129 [20169] < 2> backint_find_master_time: Display inquire_info
structure
11:13:28.129 [20169] < 2> backint_find_master_time: file_path_name =
> /dev/vgsapiBWP/rBWPclui_1<
11:13:28.129 [20169] < 2> backint_find_master_time: actual_file_path =
> /dev/vgsapiBWP/rBWPclui_1<
11:13:28.130 [20169] < 2> backint_find_master_time: bid =
> NS1096040689< dest_dir = > /dev/vgsapiBWC/rBWCclui_1<
11:13:28.130 [20169] < 2> backint_find_master_time: start_unix_time =
1096040689 ; end_unix_time = 1096040689 ; image_time = 0
11:13:28.130 [20169] < 2> backint_find_master_time: found = 0 ; raw_par
= 0 ; time_pos = 0 file_size = 0
11:13:28.130 [20169] < 2> backint_find_master_time: exit status = 2
11:13:28.131 [20169] < 4> backint_do_restore:
#NOTFOUND /dev/vgsapiBWP/rBWPclui_1
(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
If a set of configuration options in bp.conf is very large, it can cause
bpgetconfig and the GUI to not display any of the items. This applies to
items in bp.conf with the same name, for example CONNECT_OPTIONS or SERVER.
Additionally, if that set of configuration options is edited in the GUI,
for example to add a new server to the CONNECT_OPTIONS, all of the previous
data for that set of options will be lost and only the new data will be in
bp.conf.
Workaround:
To avoid this issue, you should reduce the number of configuration options
with the same name.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In a rare circumstance, the last block of a multiplexed, duplicated copy of
a TIR backup may be corrupt. A verification of the copy would not be
successful. The original backup is not affected. This does not affect
non-multiplexed duplications of a multiplexed TIR backup.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The current NetBackup 4.5 FP patch release installs an outdated VSP driver
(v1.03). What should be installed is the 1.05 version that resolves
several issues related to VSP snapshot creation on 64-bit volumes and
interaction with third party VSS snapshot providers.
(All NetBackup Windows Clients)
=========
NB_45_7_F
=========
Description:
Managing calendar-scheduled backups when the master server is in a
different time zone than the Administration GUI causes the jobs to run in
a restricted time window or not at all.
There is no longer a limit on the number of calendar include/exclude dates
within a schedule.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
All Vault duplications were deemed successful (as stated in the duplicate
logs); however, the detail.log shows error 308 (no images successfully
duplicated). This issue happens even for the most simple of vault
duplication (for example, one image). The speed of the duplication was also
considered reasonably fast.
Additional Notes:
This is an issue specific to AIX 5.2, as the fundamental behavior of a
libc function ( fgets() ) has changed. Perhaps to be consistent with a
recent POSIX proposal.
The change to code alleviates the AIX problem, and is benign on other
platforms.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
NetBackup re-initializes the ADIC Scalar 10K library (causing the library
to be inventoried) before downing the drive in the event of a hardware
error on the drive.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If SQL Server 7.0 is installed as the default instance on a host and one or
more SQL Server 2000 instances exist, the SQL agent "DBMS log on options"
dialog may display the incorrect SQL version when one of the other SQL
instances is selected.
For example, if the SQL 7.0 default instance is "remembered" from the
previous session and you select a different instance on the same host
machine, then the DBMS log on options dialog box will still identify 7.0 as
the current version.
This problem has been found in NetBackup 5.0 (pre-release) as well as 4.5 MP6.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Imports or verifies with detailed logging can take much longer than
without detailed logging.
Workaround:
When performing an import or a verify, do not request detailed logging.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Restores of remote clients initiated from a NetBackup server with detailed
logging can take much longer than restores without detailed logging.
Workaround:
Don't request detailed logs or initiate the restore from the remote
client.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In some restores from multiple images on the same tape, more than one
image restore can be started at the same time causing bptm to core dump.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The NetBackup Administration Console for Windows may crash on Multi-
Processor systems due to a threading issue with regards to pending requests
in the Device Monitor node.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
If a file has VxFS attributes such as reserve or fixed extent size, a
FlashBackup file restore would fail resulting in a zero length file.
(All NetBackup Servers: HP Intel-NT RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
If the user selects a differential database backup from the SQL Server
backup history dialog, the SQL agent should attempt to determine a full
recovery path. This functionality (removed in 4.5 MP1) is restored with
this patch.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Certain robotic conditions could cause a Vault job to end prematurely.
Retry logic has been added around the robotic inventory vault process to
accommodate this problem.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Ejecting more than ~642 tapes results in the vlteject process failing.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Performing consolidated ejects and reports could result in the completion
status of the individual sessions not being updated correctly. Vault could
incorrectly update a session as complete when it is not. This results in
the operator being unable to complete the ejects or reports for the
sessions that were consolidated.
Workaround:
Do not perform consolidated ejects or reports.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When a Vault session ejects media to a SCSI robot, the session may fail
with an error code 293 due to the robot being busy. Vault now retries the
eject operations when the robot is busy.
Additional Notes:
This problem can occur when tape mounts or GUI robotic operations are
performed during a Vault session.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The bpbrm -stream_count argument is not correct for frozen image or split
mirror backups. The error manifests itself in the "-stream_count" being
zero for stream number 1, and 'n-1' for streams 2 through n.
It is worse for frozen image or split mirror backups using retention
level 24: the -stream_count argument is zero for all streams.
Workaround:
1) Stagger multi-stream frozen image job start windows.
2) Avoid retention level 24 for multi-stream frozen image jobs.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
For ACS robot types, if a tape that is to be ejected is mounted while an
eject of that tape is in progress, the eject job may never complete.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The bpsched process core dumped and left a child process still running. The
remove_from_mpxgrp_activelist() function attempts to free pool information,
but the pool pointers are really residue. Changed add_to_active_job_lists
() function to initialize the malloc structure.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When starting a backup using -i (immediate), and -L (logging) turn on
progress logging for the client, the job doesn't appear in the bpjobd
monitor (Activity Monitor). I get the following error in the
bpjobd debug log: Jobid came as 0.
Currently adding formal ability to use backup progress logging on clients
when using the bpbackup -i, which is currently disallowed by bprd and
bpbackup. Also, note that bpbkar is successfully receiving the -L
option, so bpsched seems to pass along the log file successfully.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpsched core dumped on active node of VCS cluster while running jobs.
The problem is: the fixing of memory leaks went a little too far here
and tried to free a literal character pointer.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
PROBLEM: SQL restore dialog box did not scroll correctly.
SOLUTION: The scroll/resize logic has been altered to improve scrolling
properties of the restore dialog.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Performing a consolidated eject could result in volumes being moved into
the wrong off-site volume group.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
After running 'ADPrep' on a Windows 2000 Domain Controller, the bpbkar32
application may crash while performing a backup. The cause of the crash
has been linked to the backup of the SYSVOL information when the System
State is being backed up.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
On the Firewall tab of Host Properties in the Windows GUI, the settings
for existing clients change when new clients are added or deleted from the
list.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When a policy is configured to collect disaster recovery information as
well as multi data streams, there is a chance that the server may attempt
to collect multiple copies of the disaster recovery information from the
client at the same time. When this happens, the backups may generate a
status code of 1 (partially successful).
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When a system has more than 62 mounted volumes, backups may fail with
either a status 41 or a status 54. The exit status is due to the bpbkar32
application crashing.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
A backup of Lotus R6.0.3 or Lotus R6.5 will not back up subdirectories.
Additional Notes:
Support of Lotus R6.0.3 on Windows requires a Lotus patch (provided
as a hotfix) for SPR# THUR5LPPW9 to resolve an enumeration problem
encountered in the Lotus API function NSFSearch(). Customers should
contact Lotus Support and provide the SPR# to obtain the Lotus hotfix.
Support of Lotus R6.5 on Windows requires a Lotus patch (provided
as a hotfix) for SPR# THUR5LPPW9 to resolve an enumeration problem
encountered in the Lotus API function NSFSearch(). Customers should
contact Lotus Support and provide the SPR# to obtain the Lotus hotfix.
Without the appropriate hotfix, backups of Lotus Notes will fail and bpbkar
will log debug messages similar to this:
1:38:22.392 PM: [3444.1200] <3444> nbex_DebugLog: ERR - NBLNtoFINDDATA()
NSFDbOpenExtended('D:')
Failed: 0x103:File does not exist.
If the hotfix has been installed for Lotus R6.0.3, the Lotus Server console
will display the following version information:
Lotus Domino (r) Server (603HF80 for Windows/32)
If the hotfix has been installed for Lotus R6.5, the Lotus Server console
will display the following version information:
Lotus Domino (r) Server (65HF116 for Windows/32)
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
This change includes version 3.23.58 of MySQL for nbdbd.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The NetBackup Administration Console and bpps command lines could crash on
certain systems while attempting to gather process information via
Microsoft's Performance Counter APIs if the counter values are not the
defaults set by Microsoft.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The SQL agent should create user_ops directories so that backups will not
fail if the user deletes the directories or if the installation fails to
create them.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Alternate buffer method for backup should not be inhibited for
SQL Server 7.0.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
During an NDMP restore, and even though the NAS server reported a
NDMP_DATA_HALT_CONNECT_ERROR, NetBackup reports the restore as successful.
(Note: Receiving an NDMP_DATA_HALT_CONNECT_ERROR is rare. Most NAS servers
report an NDMP_DATA_HALT_INTERNAL_ERROR instead.)
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
When doing a Remote NDMP backup, the backup hangs after hitting EOM several
times.
This occurs when the tape hits end of media at the very end of the backup
while Remote NDMP is attempting to flush its internal buffers to tape.
Workaround:
Retry the backup with a different tape. This condition is not likely to
occur a second time on a different tape.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
A buffer overrun may cause the volume manager daemon vmd to fail.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The Number of parallel streams specified in an Oracle RMAN template that is
built using the Oracle RMAN Backup Wizard will be used for Archived Redo
Log backups in addition to Tablespace and Datafile backups. Previously,
only one stream was used for Archived Redo Log backups even if a greater
number of streams was specified in the template.
(All NetBackup Windows Clients Alpha Dgux HP Linux2.4 RS6000_433
SGI SOLARIS)
--------------------------------------------------------------------------------
Description:
If an inline tape copy job starts with multiplexing set to 1, another job
with multiplexing set greater that one will attempt to multiplex with the
first job. The multiplex setting of 1 on the first job caused the job to
run without multiplexing enabled. The second job will fail because it
cannot multiplex with the first job.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A restore from a Remote NDMP backup that spans tapes may indicate an error
occurred. This happens only with Remote NDMP on a Windows machine.
The bptm log shows "read_data_ndmp returned 0" which indicates the restore
was OK. Following this there is an MTFSF 1 tape command that fails with
IO_ERR.
Workaround:
This error can be ignored. Because read_data_ndmp returned good status, the
restore was successful. It is only the tape positioning that failed.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in the following
robotic libraries. The drives are properly configured within the library,
instead of being configured as standalone drives.
- Dell PV-122T
- Sony CSM-200
- Sepaton S2100
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When backing up a NetApp filer via a network mapped drive, errors may be
reported in the bpbkar32 debug log. The errors may contain the following
error code (WIN32 -1073741809: Unknown error). After getting this error
a couple of times, the backup process (bpbkar32) will crash.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When restoring a file, tar32 may crash. This will happen on a file that was
growing (increasing in size) during the course of the backup.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
If a restore fails because of a media mount timeout, bprd may core
dump when it finishes processing the restore.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A 134 status results in multiple tries in the Activity Monitor even though
they are not counted as tries.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If bpschedreq -predict is executed with a time that is not the current day,
the exclude dates will not be taken into account.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An imported backup of a backup copy other than copy 1 would base the
expiration time on the backup time rather than the current time, which
would result in the imported backup expiring too early.
Workaround:
The bpexpdate command may be used to change the expiration of the imported
backup.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When multiple densities are used in the same robot, not all drives will be
used.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The "Picking List" for the Robot Report was missing a Report Header. This
release fixes this problem.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Expiring one of the images from a multiple data stream backup causes a
restore to fail even though the images still exist.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Some files or directories show up in the wrong locations during restore
browsing or queries.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Calendar scheduled jobs may not run when administered from a different
time zone.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup resource DLL's are not being explicitly unloaded. This can cause
unneeded reboots during an upgrade install.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Collection of disaster recovery information from Windows clients fails.
The symptoms of this problem include:
1) Policy is configured to collect disaster recovery information.
2) Server connections to the client are supposed to use vnetd.
3) A firewall is present between the servers and the client.
When the server attempts to connect to the client to collect the disaster
recovery information, it will not use vnetd and it will fail.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Auto path correction will down drives that have a valid path, but do not
respond to commands. This patch allows auto path correction to down drives
that do not have valid paths.
This allows ltid to start even with missing paths.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The "Use Barcode Rules" check box is not checked by default. The default
is checked as long as the options dialog is not opened. Once you open the
options dialog, the default changes to unchecked. When you do an
inventory, the default should always be to use barcode rules.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Restore paths incorrect for NDMP path-based history.
The list of files for an NDMP backup image are missing the original backup
path. This occurs with path-based file history running NDMP V4.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
When automatic path correction is enabled, some robotic paths may be
incorrectly changed if the customer has a mix of serialized and
unserialized robots.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A 174 error (media manager - system error occurred) occurred when an end-of-
media status was returned while trying to write a end-of-file marker on the
tape. This may occur on the Windows or SGI platforms. The bptm log will
show an entry similar to the following:
00:30:40.803 [3256.4608] <2> io_ioctl: MTWEOF encountered EOM (error 1100),
return EOT
This is followed by an entry indicating "buffers out of sequence", and the
174 error.
(All NetBackup Servers: Intel-NT SGI)
--------------------------------------------------------------------------------
Description:
NDMP dump levels are always 1.
Additional Notes:
This fix was integrated into the NetBackup 4.5MP path, but the
NetBackup 4.5FP and 5.0 paths were missed.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The scheduler "predict" is out of sync with what actually gets run.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When different vault sessions are run concurrently, the vlteject.mstr file
may become corrupted because of timing issues with processes trying to
read/write to this file at the same time.
This fix reduces the chances of this file getting corrupted.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The problem fixed in this patch is related to the Media Going Off-site
reports for Vault. The Picking List for Robot and the Distribution List
for Vault were reporting an 'image count' of 0 even when there were tapes
being ejected with plenty of images on them. This issue has been resolved.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Drives keep going down every few days. Avrd reports semaphore errors
similar to the following in /var/adm/messages:
messages.0:Oct 28 21:56:28 server1 avrd[8148]: Error in Semaphore
Operation - Result too large
messages.0:Nov 1 03:20:54 server1 avrd[18968]: Error in Semaphore
Operation - I/O error
messages.1:Oct 20 01:31:34 server1 avrd[26744]: Error in Semaphore
Operation - I/O error
Workaround:
To avoid this issue, down the NDMP drives that are not working.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Exchange 2000 mailbox backup causes bpbkar to seg fault when processing the
first mailbox. A Status 42 "network read failed" appears in the Activity
Monitor at the master server. Exchange IS backups are successful.
From the bpbkar log:
01:23:32.111 AM: [896.2572] <2> ov_log::V_GlobalLog: INF -
MAPISession::ImpersonateUser(): !Logging on to server xxxxx as
user yyyyy!!
MessageStoreDN=/O=xxxx/OU=zzzzz/CN=Configuration/CN=Servers/CN=xxxxx
/CN=Microsoft Private MDB !!
MailBoxDN=/O=xxxx/OU=zzzzz/CN=recipients/CN=yyyyy
01:23:32.252 AM: [896.2572] <2> tar_backup::backup_startfile_state:
TAR - writing file 0 'Microsoft Exchange Mailboxes:Doe [yyyyy]'
***This is the last line of the log for this job.
Workaround:
Concerning Windows Registry Key:
HKEY_LOCAL_MACHINE\Software\microsoft\ESE97; REG_SZ;
5.2650.0017
Rename the registry key from ESE97 to ESE97_old and retry the mailbox
backup again.
All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Resolves a potential Dr. Watson on Windows NT if an NDMP drive path name is
too long (exceeds the stack). The new maximum length for drive path name is
128 characters.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
SAP's backint fails with status 25 when the server value is not set in
the .utl file and the SAP_SERVER environment variable is not set. The
server entry is not being picked up from bp.conf and passed to bplist.
Workaround:
Set the server value in the SAP init< SID> .utl file or set the SAP_SERVER
environment variable.
(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
If a client is down when the scheduler is doing autodiscovery, and the
Windows GUI attempts to modify a policy, the policy may get deleted.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When attempting an "invalid" alternate path mailbox restore attempt, the
restore fails with a status 5 and a Dr. Watson is generated for the
tar32.exe process.
The tar32 log ends with:
14:02:17 (38.001) UTF - /Microsoft Exchange Mailboxes/wankel
[wankel]/Top of Information Store/Inbox/Messages
<0000000063DAD1613F74304598422D2077E7E9FB07008D92BB8D1A7A7F418E6DC63AEE8
285B400000000393F0000EBEC8122CD95E64EA8FAF139C49A48880000000009300000>
14:02:17 (38.001) UTF - /Microsoft Exchange Mailboxes/wankel
[wankel]/Top of Information Store/Inbox/Messages
<0000000063DAD1613F74304598422D2077E7E9FB07008D92BB8D1A7A7F418E6DC63AEE8
285B400000000393F0000EBEC8122CD95E64EA8FAF139C49A48880000000009310000>
14:02:17 (38.001) Status of restore from image created 10/14/2002
12:25:06 PM = file read failed
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Sybase backups fail occasionally with a 143 error if the scheduler is
unable to connect to the client while writing the progress log.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NDMP backup restore can fail because some NDMP venders do not use "2" as the
mount point inode number.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Restores or backups may erroneously fail with a 52 status (timed out
waiting for media manager to mount volume).
Workaround:
To avoid this issue, set the media mount timeout to zero.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When ejecting media to an ACS robot, the eject process could hang because
of an unhandled volume status, STATUS_ROBOT_BUSY. This status is now
handled appropriately as an error condition.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When vault sessions are run on a Linux master, the contents of
vlteject.mstr are deleted during the eject phase. Thus the reports for the
session and any other pending ejects/reports fail with NetBackup status 296
(process called but nothing to do). This issue has been resolved.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
On UNIX systems, the tldcd and tl8cd robotic daemons may fail if
connections are opened and closed quickly with no data.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When restoring NAS data from an NDMP-attached tape drive, the bprecover
command fails with an EOM (end of media) error.
Workaround:
To avoid this issue, use a non-NDMP drive.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
In Eject/Inject operations with the vmchange command using the -w flag, a
user has 5 minutes to tell the system to continue, after they are prompted
to add remove volumes from the media access port. This 5 minute timeout is
not configurable.
This timeout can now be controlled using the vm.conf option
MAP_CONTINUE_TIMEOUT, on the robot control host.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A missing tape unmount on one of the copies when using Inline Tape Copy may
cause unnecessary 134 status codes (unable to process request because the
server resources are busy).
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The problem is that Vault's image list used for duplication is sorted by
increasing k-bytes and the customer would like a way to reverse this sort.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
During the suspend step of a vault session, a core dump may occur (in
particular on HP-UX systems).
Workaround:
The workaround for this issue would be to manually suspend tapes being
ejected using "bpmedia -suspend -m <media_id>".
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When performing drive cleaning from the java GUI, drive names with more
than 22 characters could cause problems for the GUI.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpjobd stops responding. The last few entries in the bpjobd log file
indicate multiple attempts to establish a connection from a client. The
Client was interrupted during the first connection handshake and began the
connection procedure again. This situation causes a deadlock condition.
Workaround:
To avoid this issue, restart bpjobd and then kill the offending client. You
can use netstat to find the client.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A warning is required when a library is deleted if there is media assigned
to it or if the last drive of that particular drive density is deleted from
a robot.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The Remote NDMP ndmpmoverlistener.exe process shows growing handle count
and page faults, which eventually brings down NDMP drives.
Workaround:
Stop and then restart the "NDMP Mover Agent" from services.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When NAS vendors do not send a notify data_halted message after sending a
last file history, remote NDMP waits and eventually fails with a timeout
error (error 99).
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Add support for Oracle 10g.
All NetBackup Windows Clients Alpha HP Linux2.2 RS6000_433 SOLARIS
--------------------------------------------------------------------------------
Description:
In some limited circumstances a change server command will result in the
console crashing. This issue has been resolved.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
bppllist -allpolicies or <policy> -U core dumps
Workaround:
1) Look for a policy that has an unusually long value for one of its
attributes, such as the keyword, or a policy that has many clients.
2) Run 'bppllist <policy name> -U' to display this one policy.
3) If bppllist aborts, modify the policy to reduce the length of
the long value.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Scheduler gets an occasional core dump when it is preparing to exit. The
error happens when trying to determine which storage units are busy.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Using a Binary Catalog could cause an inability to browse for restores under
certain file selection lists. This issue has been resolved.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Customers using noauth authentication with the NetBackup Administration
Console for Windows would not be able to start manual backup jobs if they
were not an Administrator on the system running this Windows GUI.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Suppose the master server and media server are different servers. Also
suppose that the media server and client are the same machine so that
shared memory backups and restores are normally done.
Suppose the master server is configured so "connect backs" with the media
server are done using VNETD. The typical bp.conf entry on the master server
would look like this:
CONNECT_OPTIONS = mediax 0 1 2
Where "mediax" is the hostname of the media server. The digit "1"
signifies that vnetd style connect backs are used.
In this case, restores will fail. Typically, the job will fail with error
code 5 and be marked as "incomplete" in the job monitor.
Workaround:
Do not use VNETD style connect backs with the media server if the media
server is also a client.
(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
Exchange backup does not support the bandwidth limitation setting.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
This issue fixed by this patch has to do with changing the expiration date
of disk images from vault after they have been successfully duplicated. If
bpduplicate is passed a really long list of image IDs and never gets a
chance to return to Vault, then Vault won't get a chance to change the
expiration date of the image.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Correct end-case problem in MPX read processing (for restores/duplications)
that may try to unmount a media that is already in use by another process.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When verifying very large backup images, the Activity Monitor would
incorrectly report a failure status that included a ?client process
aborted? error message. Testing showed that the verify job had not
actually failed and the incorrect status was displayed because the
keep-alive checks were not being sent to bpjobd if the bpbrm socket was
active for specified amount of time. This time interval to send
keep-alive packets has been corrected, resolving this issue.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup SQL Server agent connects to SQL Server 6.5 hosts with integrated
security.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When BATCHSIZE is set in the SQL agent batch file, some of the backups
fail with errors such as the following:
12:53:45 [2276,2476] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC
message. ODBC return code <-1>, SQL State <IM002>, Message Text <
[Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified>
12:53:45 [2276,2476] <16> Dbbackrec::PerformNBOperation: USER - Unable
to login into ODBC DSN <NBMSSQL_2276_2100> as user <sa>
or
12:54:00 [2276,2404] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC
message. ODBC return code <-1>, SQL State <08001>, Message Text <
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
or access denied.>
12:54:00 [2276,2404] <16> CODBCaccess::LogODBCerr: DBMS MSG - <
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect
()).>
12:54:00 [2276,2404] <16> CDBbackcat::LoginODBC: USER - Unable to login
into ODBC DSN <NBMSSQL_2276_2100> as user <sa>
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
If SQL Server is configured under binary collation, some images may not be
displayed in the NetBackup SQL agent's backup history window.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When creating VSP snapshots for backups, the snapshot creation can
disregard volumes in the VSP "Cache File Volume List" when they could have
been used as cache file locations.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When auto-sizing a VSP cache file when it is placed in a volume other than
the volume being snapshot, NetBackup may calculate its maximum size to a
value smaller than the correct value. This can cause VSP snapshot errors to
occur and the backup could end with status 155: disk is full.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When backing up RIS or SIS data with a backup that has VSP enabled to back
up open/active files in a file system backup, bpbkar32 will crash during
the backup.
Workaround:
To avoid this issue, disable VSP when backing up RIS/SIS data.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
A performance degradation with Exchange Mailbox backups was encountered
after upgrading from an MP release to an FP release while running the same
NetBackup configuration.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
A typographical error in the close_job_disconnect() function code corrupts
the
socket when bprd trying to disconnect from jobd.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If a backup image was originally written by NetBackup 3.1.1 and is then
archived using the NetBackup FP5 catalog archiving feature
("bpcatlist|bpcatarc|bpcatrm"), the .f file will be deleted without the
ability to use "bpcatres" to restore the file.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The FORCE_RESTORE_MEDIA_SERVER does not replace the server entry for TIR
fragment. Thus, when TIR information needs to be extracted from tape, bpdbm
tries to initiate a "bptm -restoretir" on the original server.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in HP ESL E-Series
robotic libraries. The drives are now properly configured within the
library, instead of being configured as standalone drives.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using the NetBackup Windows Oracle wizard, the user's authentication
choice is now correctly saved and used when building the RMAN template.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Users that do not have administrator privileges should not always see the
message "NetBackup was unable to start the required NetBackup Client
Service" when attempting a backup or restore from the Windows PC Client
GUI.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
On a multimedia type robot, robotic inventory was failing while inserting
media into the volume database. The inventory operation successfully inserts
media of one type but fails while inserting media of another type.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Problems querying/updating the volume database during an eject could lead
to the eject job failing prematurely, leaving a session incomplete.
Also, consolidated eject/report jobs that were partially successful could
be erroneously marked as complete and volumes may have an incorrect off-
site volume group leading to report inconsistencies.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Provide the ability for the user to control the format of the drive names
that are created by the Device Discovery Wizard.
Additional Notes:
The following variables could be used in generating a drive name:
- HN - hostname of the server where the drive is first discovered
- RN - robot number
- RT - robot type
- POS - Drive position, determined by robot type. One of the following:
- robot drive number
- vendor drive id
- ACS.LSM.PANEL.DRIVE
- SN - serial number of the drive
- DT - drive type (i.e. hcart, 8mm, dlt2)
- VEND - vendor ID of the drive obtained from the inquiry string of the
drive
- PROD - product ID of the drive obtained from the inquiry string of the
drive literal strings proceeded by a pound sign(#) containing
the allowable characters in a drive name.
- IDX - ensure an index is appended. Otherwise, an index will be
automatically be appended if needed to make a drive name unique.
Note: Any white space in the above entries will be collapsed.
These entries will allow a tiered approach. If the DRIVE_NAME_SEED
entry appears on a non-global-database host, that format will be
used. Otherwise, the vm.conf file on the global database host will
be checked for a DRIVE_NAME_SEED entry. If one exists, it will be
used. If none exists in either location, the default naming scheme
will be used. For tpconfig this is "Drive" followed by a number to
make it unique. For tpautoconf, this is VendorID, followed by
ProductID, followed by a number to make it unique.
EXAMPLES:
1) To generate the default names used by discovery provide the entry:
DRIVE_NAME_SEED = VEND:PROD:IDX
This will produce drive names of the form
QUANTUMDLT70000
2) To generate the names that contain the drive's product ID and
robot residence information, fields separated by minuses:
DRIVE_NAME_SEED = PROD:#-:RT:#-:RN:#-:POS
This will produce drive names of the form
DLT70000-TLD-0-1
Issues and Limitations
Some of the below items are just general drive naming issues, while others
relate specifically to this feature.
1. In a shared storage (SSO) environment drives will be named based on
the seed of the first host that discovers them. Subsequent hosts
will retain that drive name regardless of the value of their local
DRIVE_NAME_SEED vm.conf option.
2. The Hostname (HN) should be used with caution in SSO
configurations. Drives shared amongst hosts must have the same
name. See 1 above.
3. Drive names remain limited to 48 characters.
4. Valid characters are upper and lower case alphanumeric, plus, minus,
underscore, and period.
5. Drive names cannot start with a minus (-) character.
6. If robot residence information is used to generate the drive name, the
host that has the robot attached should be discovered first.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Provide a facility to swap drives without requiring the user to delete and
re-add drives, or re-run Device Discovery.
Additional Notes:
The following example shows how the -report_disc command is used to
report discrepancies between detected devices and Global Database.
In addition, an example of how to use the -replace drive_name
-path drive_path command is included.
# /usr/openv/volmgr/bin/tpautoconf -report_disc
======================= New Device (Tape) =======================
Inquiry = "QUANTUM DLT8000 0250"
Serial Number = PXB08P3242
Drive Path = /dev/rmt/119cbn
Found as TLD(6), Drive = 1
===================== Missing Device (Drive) =====================
Drive Name = QUANTUMDLT800014
Drive Path = /dev/rmt/9cbn
Inquiry = "QUANTUM DLT8000 0250"
Serial Number = PXB08P1345
TLD(6) definition Drive = 1
Hosts configured for this device:
Host = dandelion
Host = avocadocat
# /usr/openv/volmgr/bin/tpautoconf -replace_drive
QUANTUMDLT800014 -path
/dev/rmt/119cbn
Found a matching device in global DB, QUANTUMDLT800014 on host
dandelion
update of local DB on host dandelion completed
globalDB update for host dandelion completed
Found a matching device in global DB, QUANTUMDLT800014 on host
avocadocat
update of local DB on host avocadocat completed
globalDB update for host avocadocat completed
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If an error is encountered while attempting to open Lotus change
information during a Lotus backup, the backup will crash if the debug
logging level is increased. This problem has been resolved.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
When using the NetBackup PC Client Windows interface to do a Lotus Notes
user-directed backup, the NOTES.INI path field in the "Specify Backup
Options > Lotus Notes" page is now processed correctly.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Performing consolidated ejects for all robots could malfunction if the
vault configuration contains multiple robots of the same robot type. This
problem could result in media being left in an incorrect off-site volume
group. Also, media ejected from some of the robots doesn't occur but
appears to have completed successfully.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Vault catalog backups fail with a status code 306 if there is media in
the Catalog Backup volume pool that are expired.
In this case the first tape in available media has expired. Vault
immediately fails with a 306 rather than skipping this tape and trying
to use the next tape in the list.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
In configurations where the media server and master server are separate,
the master server host name is being used instead of the media server name
when changing the volume group of media that are moving back to the robot.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Backing up files whose length is changing results in corrupt data which
cannot be restored.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Non-root users of vault are unable to eject media with vault. The
vlteject.mstr.lock file gets created with 600 permissions under UNIX.
This will prevent non-root NBAC users from acquiring the lock, and ejects
will hang waiting for that lock file.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When a duplicate profile name existed in separate vaults, and selecting an
alternate session number, vltopmenu required that the triplet be fully
qualified, instead of first defaulting to the current vault.
Workaround:
To avoid this issue, you should not duplicate profile names.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
vltrun is frequently failing with a status 282 and also dumping core.
Subordinate commands executed by bv_run_system() must not be allowed to
return an exit status of 0, when the child was killed by a signal. Insure
that children killed by a signal, and have a zero exit status, are actually
attributed a non-zero exit status (EC_process_killed).
Additional Notes:
If the image database is corrupt, as it was in the problematic case, the
problem is exposed. bpimagelist had returned a 'space' where vault had
demanded, and expected, a significant entry. The resultant failure exposed
a long sequence of erroneous vault behavior.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
On a system running Windows 2000 (SP4), you may not be able to browse or
restore the second volume if 'SET HIST=N' is listed in the middle of the
policy's file list.
Workaround:
To avoid this issue, contact your Symantec customer support office for help
on manually fixing your catalog files.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Duplication of multiple copies using Inline Tape Copy may fail with a 20
error (invalid command parameter). The bptm log (the write side of the
duplication) shows an entry similar to the following:
14:55:48.274 [5586] <16> bptm: not enough parameters specified
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A media position error can occur when attempting to restore from a copy of
a backup created by Inline Tape Copy. The bptm log will show an entry that
is similar to the following (note the file number of 0):
13:12:27.348 [22187] <2> mpx_read_init: media id A00001, copy 1,
fragment 1 (839680 Kbytes) filenum 0 being considered for restore
The problem occurs when performing multiplexed backups using Inline Tape
Copy, and a new backup is started while waiting for a tape mount due to
hitting end-of-media.
Workaround:
To avoid this issue, the restore may be done from the other copy.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using Inline Tape Copy, the wrong media-id may be frozen when a media
error occurs on a copy other than the first copy. This happens when the
fail-on-error attribute is set for the failed copy. In this case, the
media-id for the first copy is frozen rather than the media-id for the copy
that obtained the error.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bprestore command fails with the error message "No files matched file
path for a date range"
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Unable to restore NDMP NetWare data due to an invalid path shown in catalog.
If \Serveris specified as a file selection that is backed
up, the Backup, Archive, and Restore screen shows the tree expanded as
Vol1.
The restore fails with "Cannot restore from filepath ,
NDMP_HALT_INTERNAL_ERROR occurred" and a status (5). The data cannot be
restored to the original location or redirected using a valid path.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
VOPIE Enhanced Authentication may not work when host names are longer than
32 characters. As a result, you may see Authentication Failed (error code
160) messages when connecting to systems with host names or client names
greater than 32 characters.
(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
A possible buffer over-run may be corrupting the eject information in
memory, causing ACS ejects to fail because the CAP was reported as not
existing, when in reality it did exist.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Exchange restores from multiple images fails with a communications failure
error. The log will have a message similar to the following:
17:58:45 (158515.002) ERR - unable to create object for restore:
Microsoft Information Store:files_1074011439 (BEDS
0xFFFFFE30: A communications failure has occurred.
Workaround:
Create a file named /usr/openv/netbackup/NON_MPX_RESTORE to force
sequential restores from multiple images.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The timeout for an ACS query is configurable using the ACS_QUERY_TIMEOUT
entry in vm.conf. The value of this entry is in minutes, for example:
ACS_QUERY_TIMEOUT = 30
This sets the timeout to 30 minutes.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Ejects that are partially-successful are erroneously marked as completed.
As a result, the operator cannot eject the remaining media or re-run
reports.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Added support for the SDLT-600 drive type and the SDLT_2 media type to
the ACS robotics.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Single MAP ejects may not query the ACSLS server for the correct MAP
causing the eject to fail.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The "from" and "received date" fields were not being updated correctly
on the restore of a message to an Exchange Public folder.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Enhance bptm to use MEDIA_UNMOUNT_DELAY for duplications to reduce
unnecessary unmounts/re-mounts during Vault sessions.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using "bpexpdate -recalculate" or "bpexpdate -backupid" to extend the
expiration date of one or more backups that have multiple copies, the media
expiration may not be correct for copies on removeable media if the first
copy is on disk.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
This enhancement enables NetBackup to work in a Plug and Play environment.
You can now use NetBackup with Plug and Play tape class drivers and the
Storport driver.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When performing backups with TIR plus move detection, some backups may not
verify correctly due to files/folders having identical file numbers.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Exchange Mailbox backups may hang for Exchange 2003 running on a 2003
cluster.
This hang only seems to happen on Exchange 2003 after mailboxes are
migrated from Exchange 5.5.
The last log entry in Debug logs would be:
"INF - MAPISession::ImpersonateUser(): Logging on to server
<Exchange_Virtual_Name>
as user <MailBox_Alias>! MessageStoreDN=/O=<Org>/OU=first administrative
group/
CN=Configuration/CN=Servers/CN=<Exchange_Virtual_Name>/CN=Microsoft Private
MDB
!MailBoxDN=/O=<Org>/OU=first administrative
group/CN=recipients/CN=<MailBox_Alias>"
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When performing System State backups on a Windows XP and/or a Windows 2003
Server, the backup may appear to hang when it backs up the Registry or it
may generate errors while backing up the Registry.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
bpbkar32 may generate an 'Exception number: c0000005 (access violation)'
(Dr Watson) when doing a cumulative backup of an Exchange 2000 Storage
Group and the first transaction log to be backed up is missing. The backup
ends with status 13. Typically, the log file is missing because the user
has deleted it.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Exchange 2000/2003 restores may fail when the restore includes many log
files.
The tar debug log may be as follows:
11:36:54.556 AM: [8140.4520] <2> ov_log::V_GlobalLogEx: INF -
exchange_2000_access::m_fWriteIoPartializer: dwBlockSize:4 dwSize:2
dwBufferPioCnt:0
11:36:54.556 AM: [8140.4520] <2> ov_log::V_GlobalLogEx: INF -
exchange_2000_access::m_fWriteIoPartializer: dwBlockSize:0 dwSize:65536
dwBufferPioCnt:2
11:36:54.571 AM: [8140.4520] <2> ov_log::V_GlobalLogEx: ERR -
exchange_2000_access::m_fWriteIoPartializer:FS_WriteObj() BlockSize(82)
returned on partialized I/O request
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
The Windows 2000 platforms were losing multiplexed groups. The user could
not cancel orphaned jobs within the multiplexed group, and additional jobs
could not be added to the multiplexed group.
Windows-specific code was added to display questionable pointer values
prior to releasing the multiplexed group. This minor change seems to have
resolved the problem, however, new information may suggest that this it a
Windows 2000 compiler optimization issue. Thus, this fix either masks the
problem, or helps isolate it.
(All NetBackup Servers)
================================================================================
================================================================================
This Feature Pack provides fixes to the VERITAS NetBackup (tm) NT server and
clients. It also contains fixes for NetBackup Add-on products and Database
Agents.
Symantec recommends that the backing up of active file systems be avoided,
or the use of snapshot technologies be implemented. The directory structure
reported back from the file system (to NetBackup) may not contain all of the
files available during the time of backup. NetBackup will not report errors
in many cases where the file's existence is not known to NetBackup as reported
by the file system.
================================================================================
=================
PACK DEPENDENCIES
=================
-- 4.5 FP6 must be installed prior to installing this Feature Pack.
-- For the latest robotics support please also download and install the
latest Mappings_4.5.<6 digit number>.zip from the support website:
www.support.veritas.com.
I. DOWNLOAD INSTRUCTIONS
II. INSTALLATION INSTRUCTIONS
III. UNINSTALL INSTRUCTIONS
IV. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_45_8_F
NB_45_7_F
=========================
I. DOWNLOAD INSTRUCTIONS
=========================
This is an update to NetBackup/Media Manager products
with the latest fixes for Windows NT NetBackup servers.
Download instructions:
1) Download the NB_45_9_F.winnt.intel_<6 digit number>.exe file
into a temporary directory.
where <6 digit number> is an internal tracking identifier
2) Extract the NB_45_9_F.winnt.intel_<6 digit number>.exe
by double-clicking on it.
This will create a number of files that include:
README.NT
and
Setup.exe
==============================
II. INSTALLATION INSTRUCTIONS
==============================
NOTE: For Feature Pack installation on Microsoft Cluster Environment:
- Install this Feature Pack on the inactive node(s) of the cluster,
performing Steps 1-4 below.
- Use the MSCS move group command to 'failover' the server to another node.
This should be done when the NetBackup system is quiet, that is, no
backups or restores are running.
- Install this Feature Pack on the newly inactive node of the cluster.
- (Optional) Use the MSCS move group command to 'failover' the server back
to the original node.
--------------------------------------------------------------------------------
Installation steps:
NOTE: If upgrading a NetBackup Windows 4.5 FP8 client to server or
Administration Console, the 4.5 Feature Pack must be uninstalled
prior to upgrading to 4.5 server or Administration Console.
1) Close all NetBackup Windows.
Make sure the NetBackup server system is quiet and has no active backups,
restores, duplications, etc., running. If there are NetBackup activities in
process, the Feature Pack will not install if the file to update is busy.
If a database client is being used, such as Oracle, ensure that the
database services are stopped. Database services can be stopped by
using the Control Panel -> Services tool. Repeat this process until
all databases have been stopped. These services must be restarted
once the patch is successfully installed.
2) Run Setup.exe. (Double-click on the icon from File Manager or Explorer
or run it from the command prompt.)
Setup.exe begins by stopping the appropriate NetBackup Services required
for the Feature Pack installation. Next, it will install the necessary
files into their correct locations. Finally, Setup.exe will restart the
appropriate NetBackup services.
3) Examine the <install_path>.Log file to ensure that no
errors took place during the installation, for example, an error during
Feature Pack installation because of a busy file.
4) Remove the temporary directory created in the download instructions.
============================
III. UNINSTALL INSTRUCTIONS
============================
**Important notice regarding un-installs on Windows**
Only the last Feature Pack installed on a Windows system can be un-installed.
1) Close all NetBackup Windows.
Make sure the NetBackup server system is quiet and has no active backups,
restores, duplications, etc., running.) If there are NetBackup activities
in process, the Feature Pack will not install if the file to update is busy.
If a database client is being used, such as Oracle, ensure that the
database services are stopped. Database services can be stopped by
using the Control Panel -> Services tool. Repeat this process until
all databases have been stopped. These services must be restarted
once the patch is successfully installed.
2) Go to <install dir of NetBackup>_Uninstaller.exe and
double-click on the executable.
(For example, C:Files_Uninstaller.exe)
3) Select the correct Pack to be uninstalled.
4) Click Uninstall.
5) You may review the trace file
(<install dir of NetBackup>_Uninstall.log)
to see what files were replaced.
==================================
IV. DESCRIPTION OF PROBLEMS FIXED
==================================
The following are descriptions of the problems fixed.
Please read the entire document before installing.
README Conventions:
Description
Describes particular problem or feature contained in this Feature Pack.
** Description **
Describes a problem that can lead to potential data loss. Please
read these problem descriptions carefully.
Workaround
Any available workarounds to a problem are also listed. Workarounds
can be used INSTEAD of applying the patch, however, Symantec strongly
recommends the "best practice" of being at the latest patch level.
Additional Notes
Any additional information regarding this problem or feature is included.
=============
Current pack
=============
================================================================================
Description:
Message lines in LTIerrno.h that begin with spaces instead of a tab are not
found by the search program.
Additional Notes:
The list of messages for MMm errors is changed and only effects localized
sights.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In the Windows NetBackup Administration Console, there is a timing issue
that causes the display to show multiple instances of the same physical
drive when there should be one line entry per physical drive in a SSO
environment.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The scheduler is modified to correctly process a status 134 error race
condition in a multiplex backup.
This condition occurs when a multiplex child bpsched starts a backup, but
the storage unit is over committed. A status 134 is sent back to the
multiplex child bpsched, but the child schedule is already adding another
backup to the multiplexed group.
The child schedule attempts to send the new jobs information to bpbrm, but
bpbrm has exited and the connection is defunct. Scheduler was incorrectly
logging the defunct connection in the job progress log. With this change
the scheduler will not log the broken socket, but will correctly read and
process the 134 status from the in-bound connection.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When performing Windows backups on an Itanium server running
Windows 2003, the backups may fail with a 54 and a 41 status.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Executing drfile.exe may generate an application error.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
bpretlevel loops echoing 'What?' when changing retention levels. No input
seems to be a satisfactory response to exit the loop until a ctrl-C is
entered. There does not seem to be any way to change retention levels
with the CLI because of this bug.
The following is the discovered resolution.
An earlier change had changed all occurrences of gets() to fgets(), but
failed to recognize that fgets() WILL return the '', whereas gets()
did not. The subsequent strcmp was not expecting the '', and
always failed. The solution is to strip the [new] trailing '' to
emulate the gets() behavior.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpbrm can hang if a database agent backup fails in a certain way.
The job appears to be running in the Activity Monitor until it is
terminated by the administrator.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
corrected situation where scheduler would lose a backup in the middle of a
catalog backup.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Multiplexed backup jobs would occasionally hang. This would happen if the
bptm or bpdm parent process crashed, or if bptm could not successfully add
the TIR fragment for a TIR backup. It may also happen because of a timing
problem in bpbrm when new jobs are started.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When backing up Lotus Notes databases, some databases were skipped. These
skipped databases were not reported as an error; the backup exited with a
status 0 instead of a status 1.
(All NetBackup Windows Clients Linux2.4 RS6000_433 RS6000_51 SOLARIS)
--------------------------------------------------------------------------------
Description:
If the add_slave_on_clients command is unable to add the media server
entries to one client, it may incorrectly update the media servers on
subsequent clients. Typically, only one media server will be added to the
remaining clients.
Workaround:
Use the Host Properties GUI to update the server list for the clients.
Use the bpsetconfig admincmd to update the server list for the clients.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
After a controlfile autobackup the image verification fails.(ORA-27206:
REQUESTED FILE NOT FOUND IN MEDIA MANAGEMENT CATALOG)
Workaround:
To avoid this issue, add the touch file USEDEFAULTDATERANGE to
/usr/openv/netbackup on UNIX or VERITASon Windows.
(NetBackup Clients: HP Intel-NT Linux2.2 NCR RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris)
--------------------------------------------------------------------------------
Description:
bprd cannot clean up a vault session directory that contains files that are
larger than 2GB .
(All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpimage ¿cleanup process fails with the message, "Too many files open"
when using ASCII catalog and FlashBackup policies.
Workaround:
To avoid this issue, run cleanup for a single client at a time.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup SQL Server agent fails when an attempt is made to back up
more than 255 databases using one batch file. This occurs if the backups
are individually specified in the database or if $ALL is used and there are
more than 255 databases on the SQL Server host.
When this occurs the Automatic backup job fails to terminate.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
During a NetBackup MSSQL scheduled backup, the bpbdb.log shows
a log entry with a severity <16>, however, the backup succeeds.
Receiving this error indicated that the was set incorrectly for an
informational message.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Corrected the display of new the ACS vendor media types: T10000T1,
T10000TS, and T10000CT. Also corrected the allowable type that is the
ACS vendor media type, LTO_400G.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpdbm may crash if it is unable to determine the host name of caller.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A SAP online backup is started and a Tablespace (PSAPES46CI) in the Oracle
database is placed in BACKUP MODE by the agent. However the backup receives
a STATUS 134 error in BPTM & BPBRM. The bpbkar, bptm, and bpbrm processes
exit and clean up after themselves. The SAP agent process remains active,
awaiting the backup to be queued and run again, leaving the Tablespace
(PSAPES46CI) still in BACKUP MODE.
(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
In certain firewall configurations, multi-stream backups from Linux client
may fail with status 25 if the vnetd connect-back is used.
(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
The vmoprcmd -comment <drive_index> <comment_string> command overwrites
the serial number that is specified if the comment_string size is 26.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NDMP restores fail with Hitachi NAS when restoring the entire backup image.
The NDMP log shows the path being sent twice in the NDMP_DATA_START_RECOVER
message.
Workaround:
Restores will work as long as the file system path is not selected (the
path that was initially backed up). If the entire image is needed for
restore, select all the files and directories in the file system path
instead.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
* Description:
NetBackup processes may core dump if an error occurs. The stack from the
core file showed problems with the ndmp_user_scsi() or ndmp_user_tape()
functions.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
On a multimedia type robot, robotic inventory was failing while inserting
media into the volume database. The inventory operation successfully inserts
media of one type but fails while inserting media of another type. It does
not take the media type of existing standalone media into consideration.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added a new ID for the duplicated message.
Changed:
ovgetmsg("DmeBrm0166N", LC_C, sizeof(lmsgl), lmsgl, lc_messages,
sizeof(cmsgl), cmsgl, "cannot create data socket" );
To:
ovgetmsg("DmeBrm0167N", LC_C, sizeof(lmsgl), lmsgl, lc_messages,
sizeof(cmsgl), cmsgl, "cannot create data socket" );
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Vault can physically eject tapes but it does not remove them from media
manager.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
An XBSA application would hang during a shared memory backup (such as, the
client and the media server are the same machine) if a problem occurred
that caused the bptm to exit. The BSASendData() call did not return.
(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
If the bpgetmedia options -h and -M were both specified, the -h argument
would always inherit the -M argument, and the original -h value would be
lost.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When bpbackup is run with the option to wait for the completion of the
backup job, a firewall between bpbackup and bprd can shut down the socket
while bpbackup waits for the completion status. This causes backint to
get stuck in an infinite loop during database backups.
(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
During the alternate client restore, the secondary restore process
was not passed the value for the browse client(source client).
(All NetBackup Windows Clients Linux2.4 RS6000_433 RS6000_51 SOLARIS)
--------------------------------------------------------------------------------
Description:
Updated this release to include the most recent device entries.
Fixed the following:
IBM3583 barcode reader recognition issue with newer library firmware.
Quantum PX720 barcode reader recognition issue.
Added the following:
Diligent VTF Open
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in the following
robotic libraries. The drives are properly configured within the library,
instead of being configured as standalone drives.
- NEC T40A
- HP UHDL
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The ACS robot inventory may timeout when the ACSLS server is
overloaded. Timeouts increased.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When backing up files using VSP to back up open/active files on Windows
clients, files deleted while the backup was running would not be backed up
and could not be restored. This was not the expected behavior because all
files that existed during the time the VSP snapshot creation occurred (at
the beginning of the backup) should have existed when the backup was run
and any file deletions during the course of the backup should have affected
the backup job, because backups using VSP used the VSP snapshots to
enumerate files to be backed up.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
If the forked re-read storage unit process detected a transient error, it
would error, exit, and then remove the scheduler message queues.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When running VSP-enabled backups to back up open/active files, backups would
intermittently hang after the VSP snapshot creation had taken place. The
bpbkar32 logs indicated that snapshots were successfully enabled for the
backup but inexplicably stopped while backing up files. The bpbkar32 back-up
process then stopped processing and appeared to hang until it was explicitly
killed by Windows Task Manager.
(All NetBackup Windows Clients)
================================================================================
=========
NB_45_8_F
=========
Description:
A NetBackup restore that has a path specified to be excluded from the restore,
but that path does not even exist in the backup image, was completing with a
partial success status of 1. Changes have been made so that a backup such as
this completes successfully with a status of 0.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Adjusted a loop used during the deletion of a mpx group. This loop was not
functioning correctly on the W2K platform and resulted in removal of
additional mpx groups.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
"Ghost" backup jobs were appearing in the Activity Monitor.
A deleted backup job could (partially) re-appear. This would only happen
to a deleted job that is one number lower than a multi-copy backup.
Example:
1) Job n finishes.
2) Job n is deleted from the Activity Monitor.
3) Multi-copy job n+1, n+2, n+3 finishes.
4) Activity monitor incorrectly updates jobs n, n+1, n+2.
5) Deleted job n (partially) re-appears.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The interrupt code paths for the Scheduler were simplified to eliminate
scheduler core dumps because the interrupt handlers were too "noisy".
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Corrected potential problems with memory leaks and non-initialized malloc
space.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When the scheduler verbose is set greater than 0, there is the potential for
Jobs to exit with a status 50. This is more likely on systems that experience
connection issues. The situation occurs when the scheduler prints a message
and loses the errno value. Armed with the incorrect errno value, the scheduler
exits (status 50) the current running jobs.
Workaround:
To avoid this issue, set the scheduler verbose to zero.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpplschedrec -deldayomonth command deletes a range of days instead of
the specified day.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A backup is established with the following:
- Multiplexing enabled
- Multi-copy enabled
- Continue backup on copy failure
Excessive failure messages are displayed if one of the copies fails, and
additional backups attempt to join the same multiplex group.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In the Windows client GUI, the "Temporary location for log and patch
files" for Exchange 2000 restores may now contain space characters.
Workaround:
To avoid this issue, do not use space characters in the "Temporary location
for log and patch files" path for Exchange 2000 restores.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Vault jobs fail with "status 23" when run from a vault policy if another
"Program" directory or file resides on the same drive on which NetBackup
is installed.
Workaround:
Run the vault job by using a vltrun command from a command prompt, run the
profile from the shortcut menu, or rename the other "Program" directory or
file on the drive.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When trying to perform a Lotus PIT restore (using PIT) when a secondary
restore is required to restore requested Lotus transaction log extents, the
following error is encountered:
"Invalid start date: 11/15/99" syntax error in bprestore. Only applies to
restoring Transaction Logs function - standard nsf files are ok.
tar debug log shows:
16:32:19 (101307.001) INF - Begin Lotus point in time database recovery to:
06/05/2004 16.29.22 CEDT
16:32:19 (101307.001) INF - Transaction Log:/A1VG3DATA/S0000160.TXN Required
for Recovery
16:32:19 (101307.001) INF - Requesting Restore of
Log:/A1VG3DATA/S0000160.TXN
Id:001c6243c1256e7d-f762d76fa9030000
LogNo:160
16:32:19 (101307.001) Invalid start date: 11/15/99
16:32:19 (101307.001) EXIT STATUS 144: invalid command usage
16:32:19 (101307.001) INF - NBLN_RecoverDb() RecoverErrorCode:0x13E3
DbIndex:0
16:32:19 (101307.001) ERR - /A1VG1DATA/c59admin_domino/testtl.nsf Recovery
Failed!
(0x13E3:Recovery Manager: Error from Logging Subsystem.)
Bprestore demonstrates incorrect syntax:
16:32:19.346 [83270] <2> logparams: -B -w -t 25 -s 11/15/99 -R
/usr/openv/netbackup/logs/user_ops/LN_Restore_Rename_File_87834.chg
/Transaction Logs/S0000160.TXN~001c6243c1256e7d-f762d76fa9030000
16:32:19.361 [83270] <16> process_args: Invalid start date: 11/15/99
16:32:19.361 [83270] <2> bprestore: exit with status = 144
Bplist can also recreate error with the following options;
# bplist -t 25 -l -R -s 11/15/1999
Invalid start date: 11/15/1999
EXIT STATUS 144: invalid command usage
(NetBackup Clients: Intel-NT Linux2.4 RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
Description:
SAP Alternate Client restores may fail. The SAP Agent was unable to read
the output file of the restore_filter script. This failure produced a log
similar to the following:
"14:30:00.381 [7082] <16> backint_restore_filter: cannot open restore
working file:
/oracle/BD1/sapbackup/backint_dir/.backint.filter.1085772595.7082
14:30:00.381 [7082] <16> backint_do_restore: ERROR: running restore filter"
In addition, the restore_filter script was unable to handle a use case
where source client (a backed-up client) did not have soft links to the
actual file paths of the SAP data files. During a restore on the target
client (a new destination client), the agent would not adjust file paths to
match the originally backed-up paths. This issue would produce a log file
similar to the following:
"**************************************************************************
Program: ./backint 5.0GA
Input File: ./in_re
Profile: ./initSAP.utl
Function: RESTORE
***************************************************************************
#NOTFOUND <input file name>
***************************************************************************"
or in the backint log:
"10:56:07.093 [2838] <2> backint_find_master_time: exit status = 2
10:56:07.094 [2838] <4> backint_do_restore: #NOTFOUND /tmp/bd1/file1"
(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
After a failure had occurred, the SAP DB Environment Agent would report a
Success despite the actual failure. This problem only occurred when an
agent is called into the SAP DB environment with the adapter program and
there were previously successful backups and current backup failures. A
problem similar to this would produce a log file similar to the following
example:
"
...
08:16:49.143 [1433628] <16> backint_system: ERROR: executing
command /usr/openv/netbackup/bin/bpbackup -w -t 17 -h pollux_bk -S
frsux071 -c ASV_SAP_A30_online -s Default-Policy -
L /usr/openv/netbackup/logs/user_ops/sap/.backint.log.0.1083392186.1282186 -
08:16:51.208 [1282186] <16> dbc_Wait: ERR - job (1433628) failed status (71)
...
08:16:52.853 [1282186] <4> backint_do_backup: #SAVED
NS1083106428 /home/adasav/A10/NB_puffer1/STAGE3.0
08:16:52.853 [1282186] <4> backint_do_backup: #SAVED
NS1083364604 /home/adasav/A10/NB_puffer1/STAGE1.0"
Note: The example above shows a backup command failed, but the agent
reported that the input files were saved. This happened because agent
saved these files in a previous backup. This might mislead the user into
thinking the backup of SAP on the SAP DB was successful when it actually
failed.
(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
The spin control for the "Number of Parallel Streams" field in the "Backup
Limits" page of the Windows Oracle backup wizard now works correctly.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
An NDMP backup in the ASCII catalog format would fail and produce the
following error in the bptm log.
08:42:17.202 [5704.5624] <2> write_data_ndmp: calling
ndmp_bpfsmap_create
08:42:18.304 [5704.5624] <2> write_data_ndmp: bpfsmap longjmp: setjmp
returned 6; aborting backup
...
08:42:18.764 [5704.5624] <2> write_data: write_data_ndmp() returned -8,
EXIT_Status 6, Kbytes = 1359099
08:42:18.774 [5704.5624] <2> write_backup: write_data() returned,
exit_status = 6, CINDEX = 0, TWIN_INDEX = 0, backup_status = -8
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
A dual stream backup starts only one backup for each Redo Log Group after
the first Redo Log Group is backed up correctly (two backups).
This problem occurs in following configuration:
1. BRARCHIVE is called with -f option
2. SAP Agent configuration file (init<SID>.utl) contains sched_log
parameter.
The sched_log parameter is the value of the second schedule that the SAP
Agent can use to backup archive logs. When this parameter is enabled, two
backups of archive logs will be performed. This enables backing up the same
archive logs to different media. This parameter is processed correctly by
the SAP Agent when BRARCHIVE is called without -f option.
However, when BRARCHIVE was called with the -f option, only the first
group of archive logs were backed up to both schedules. Any subsequent
group of archive logs would be backed up to only one (original) schedule.
(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
The scheduler does not automatically start "bpexpdate -deassignempty" to
deassign media that do not have associated images after "bprecover -l" has
been run.
Workaround:
If a bprecover -l has been executed, remove the following file:
UNIX:
/usr/openv/netbackup/bin/deassign_lock
Windows:
VERITAS_lock
Do not remove this file if a catalog recover (bprecover -r) has been done.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When performing an Intelligent Disaster Recovery and the communications
between the client and server are configured to use vnetd, the submission
of the restore request from the recovery wizard will fail.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When performing full backups of using the UNC naming convention, the
archive bits on some files are not getting cleared.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When performing an IDR restore with a bootable CD created from a Japanese
Windows 2000 SP 3 integrated CD, the setup fails with the following error:
"The following value in the .SIF file used by Setup is corrupted or
missing: Value 0 on the line in section [SourceDisksFiles]. With
key 'sp3.cab' error is received"
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
When performing a VSP-enabled backup, the first attempt at the backup does
not process the VSP excluded drives and crashes.
When a second attempt occurs, the backup acknowledges the VSP excluded
drives and then functions properly.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
In certain cases, a backup job may receive an error, but the job remains
active and must be manually cancelled.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
A loss of multiplexed groups within bpsched.exe resulted in the failure to
cancel multiplexed backups.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The following logging statement in bptm was confusing.
09:37:46.035 [16536] <4> ndmp_internal_open_and_auth: NDMP server DEBUG
suggests protocol version 3
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Attempting to restore from an image that was backed up with the following
setting would result in a failed status 5.
"SET FILES = ( Multiple Files ) "
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Exchange Server shutdowns due to lack of space on the transaction log file
device.
The transaction logs were probably not truncated because the Exchange
backup failed. The original backup may have failed due to networking or
media failures and retry attempts may fail with a status 1.
Investigation of the Error logs would reveal the following error,
"INF - HrESEBackupSetup: Microsoft Information Store = 0xc80001f9"
"ERR - XCHG_BackupRead() FS_ReadObj() Failed! 0xFFFFFE30:FS_COMM_FAILURE".
These errors indicate that the Exchange StorageGroup is already in
backup mode. Close inspection may also reveal that the bpbkar32 from the
original backup attempt is still running.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
You can now view the correct number of files backed up in the Activity
Monitor.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Update ltid such that it does not leave behind defunct processes when it
spawns vmd.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Bprd hits a segmentation fault and core dumps. The issue occurred when the
log-file path for the bprestore log exceeded 58 characters. This only
occurred when the media server involved was not the master server, and when
FQDN names were used.
To resolve this issue, the command buffer size has been increased to
BUFFLEN (4096), and implemented bounds checking on all string buffers,
where practicable, by using V_strlcpy, V_strlcat, and snprintf().
Additional Notes:
While libVcom.so and netbackup.dll contain no changes, they are required
to resolve new entry points introduced in libsfr.so. In addition,
libsfr.so is Solaris only.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A race condition existed when two restore jobs needed the same piece of
media, from the same server, when this media was not already in the media
database. This condition could cause the media to be added twice, and one
of the restores to fail.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Improved VMD debug logging to better enable analysis for slow servers.
Allow control of VMD child timeout, such that slow servers can be
interrupted, before VMD encounters connection timeout's on other
connections.
Add "VMD_CHILD_TIMEOUT = xx", to the vm.conf file. xx is the number of
seconds to wait for a child to release its lock on the volume database.
Allowable time is 60 to 360 seconds, where 360 is the default (a value
used prior to this patch).
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup was not properly examining the SCSI library mailslot status bits;
therefore, during ejects of more than a MAP-full of media, the eject
operation may abort after the first MAP-full is removed.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
While trying to reduce the size of a database, the command "bpimage -
cleanout -client dill-bk" was used. Using the command in this way caused
bpimage to core dump.
Workaround:
To avoid this issue, allow the nightly clean-up process to clean the
catalog.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup for Lotus Notes will successfully backup Domino transaction log
extents, but will NOT truncate them.
Workaround:
Do not specify the TRANSLOG_Path for the Lotus transaction log directory
in the notes.ini as a symbolic link. Make sure the Lotus transaction log
directory is always the actual physical path.
(NetBackup Clients: Intel-NT Linux2.4 RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
Description:
It was possible that the bpjobd process may hang under certain conditions.
It has been demonstrated that this can happen if bpduplicate and bptm
processes are killed, but it may occur in other situations. The bpjobd
process does not die, it just loops consuming CPU time, and nothing
is written to the debug log. This prevented the job DB from being updated
with the status of existing jobs, or new jobs. bpjobd must be killed and
restarted by the system administrator to resolve this problem.
This problem is indicated by the following data in the bpjobd debug log,
referring to non-existent job ID 3:
18:45:00.734 [17433] <2> process_active_job: Frame type is 3 (jobid 3)
Sock (93)
18:45:00.734 [17433] <2> process_active_job: Adding provider(1) for job(3)
socket (93)
18:45:00.734 [17433] <2> process_active_job: Begin to write (JOBTRYFILE) at
offset 68 job (3)
Workaround:
To avoid this issue, kill and restart the hung bpjobd.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A large number of down storage units would result in and apparent
scheduler hang. In reality, the scheduler was timing out to each media
server in series. This fix recognizes and skips duplicate attempts to a
down media server.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
To assist image database cleanup in 24x7 environments, image database
cleanup will always run in background. bpsched will not wait until the
cleanup is complete before scheduling new jobs. In addition, bpsched will
initiate an image database cleanup at periodic intervals, 12 hours by
default. The time interval may be changed by using the
bpconfig -cleanup_int <hours> command. For example, to change the interval
to 24 hours, execute the following command:
bpconfig -cleanup_int 24
Use a value of 0 to disable bpsched from starting the periodic image
database cleanup. The maximum value is 744 hours. Bpsched will still
perform an image database cleanup at the end of a session, however, it will
be run in background. On UNIX systems, bpadm may also be used to change
the interval.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The predict algorithm was not sorting correctly. It failed to position
cumulative incremental backups before the differential incremental backups.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
You can now perform Phase 1 imports on Backup Exec media in ACS and TLM
robots.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The scheduler debug log was filling with the following message:
"storage unit was not assigned for clientjob <host name> <policy name>
<stunit name> <copy>"
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When a database agent gets requeued multiple times in a very short period
of time, there were cases where the server would time out waiting for the
client to connect. This fix prevents the client from getting behind the
server in these instances.
(NetBackup Clients: Alpha HP Intel-NT Linux2.4 RS6000_433 RS6000_51 SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
The device configuration user interface can encounter a long delay when
selecting a robot. The time required to filter the lists in one case was
reported to be approximately 20 minutes.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Very large Teradata backups had an error where an overflow of an integer
byte count of fractional blocks caused the wrong size to be sent to bptm.
This size value did not match what bptm counted and the backup was then
aborted.
Workaround:
To avoid this issue, you can back up the large database using multiple
streams.
(NetBackup Clients: Intel-NT NCR )
--------------------------------------------------------------------------------
Description:
An Oracle autobackup of the control file is very slow because of the format
of the piece name.
(NetBackup Clients: Dgux HP Intel-NT Linux2.2 NCR RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
A multiplexed TIR duplication would fail if the prior backup duplication
had a TIR size greater than 1 Gigabyte, and would lead to a bptm crash.
Workaround:
To avoid this issue, retry the duplication using non-multiplexed
duplication. It is also possible that the duplication will succeed by
trying multiplexed duplication.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Performing an Exchange Information Store restore causes misleading "bogus"
bpbrm errors in the Activity Monitor. The restore is successful and the
Activity Monitor description looks like the following:
3/2/2004 9:07:38 AM - Error bpbrm(pid=268) from client backrest: TAR -
Restoring Exchange 2000 ESE object C:
Files.edb
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Exchange Mailbox backups would fail with a Dr. Watson under the following
conditions:
The problem occurred when the mailbox message (including the GUID), plus a
mangled name length, plus 12 (for some additional characters) would equal
exactly 512. This needs to take place at the end of a data block, which by
the default is 64K. The result is overrunning the end of the data block,
and this exception is the result.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
The following changes have been made:
- Added the drive, IBM 3592J
- Add the following new libraries:
- HP EML E-Series
- EMC Disk Library
- STK L7
- STK SL500
- STK Virtual Library
- Adds fixes for eject issue with the ADIC libraries.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added support for the following drives and media types for ACS:
- Drives:
- STK 10000A (T1)
- HP LTO-3
- Media:
- T10000T1
- T10000TS
- T10000CT
- LTO-400G
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If an SSO drive is DOWN on all servers, and its scan host unregisters
(services are shutdown), vmd/DA will not transfer this drive to another
scan host. If the drive is brought UP on a server(s), it will have no
scan host, and will stay in the NO-SCAN state.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Some FlashBackup backups would take longer on NetBackup 5.0 than they did
for NetBackup 3.4 because of additional overhead of the binary catalog.
Workaround:
Raise the maximum files per add value using the
/usr/openv/netbackup/MAX_FILES_PER_ADD to 9500, which will raise the limit
for all backups.
Additional Notes:
The number of files added per call to the catalog has been raised to 95000
from 500 for FlashBackup. This limit can be modified by putting the
desired value in /usr/openv/netbackup/FBU_MAX_FILES_PER_ADD, which only
affects FlashBackup backups.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in the following
robotic libraries. The drives are properly configured within the library,
instead of being configured as standalone drives.
- EMC Disk Library
- QUANTUM ValueLoader
- HP MSL6000 Series
- STK SL500
- STK L7
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
vmphyinv is unable to read the tape header in NDMP drives. This affects
NDMP drives and the NetWare media server (that are handled using NDMP
protocol).
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The SQL Server sometimes failed to create the VDI object within the
30 second default of "VDITIMEOUTSECONDS" during scheduled backups. To
resolve this issue, the VDI timeout has been increased to 300 seconds.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
A SQL Server move script created for a multi-stripe backup image sometimes
fails to include the .ldf file.
Workaround:
To avoid this issue, manually edit the move script to include the MOVE log
(.ldf) section and the restore will be successful.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
NetBackup SharePoint Portal Server backups fail when the NetBackup Client
Service logon account and the SharePoint Portal Server Logon account do
not match.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
The scheduler would take a long time scheduling multiple data stream jobs
if there were many policies that were due to be autodiscovered at once.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When selecting a media ID for backup, if the allocation date in the
media database does not match the assigned date in the media manager
database, FREEZE the media because there could be database inconsistencies.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Multiplexed jobs can hang if the DATASOCKET message is not recognized.
A log message of "unknown media message DATASOCKET" will appear in the
bpbrm debug log.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Exchange agent has the requirement that the NetBackup client
service account run under an Exchange Administrative account. However, if
the service is running as LocalSystem on a restore attempt, the restore
will hang and end with a status 5 after tar32 causes an exception fault.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
For NDMP restores on NetApp filers, more than 1024 files can be restored
using DAR.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
When performing an alternate client restore of RAW devices with the SAP
Agent the restore will fail. The following errors will be reported in
brrestore:
BR386E File /dev/vgsapiBWP/rBWPclui_1 reported as not found by backup
utility
The following information will be reported in the backint logs if logging
is ON and VERBOSE=5:
11:13:28.129 [20169] < 4> backint_find_master_time: WARNING: not found in
bplist list: /dev/rdsk/c1t4d0s1
11:13:28.129 [20169] < 2> backint_find_master_time: Display inquire_info
structure
11:13:28.129 [20169] < 2> backint_find_master_time: file_path_name =
> /dev/vgsapiBWP/rBWPclui_1<
11:13:28.129 [20169] < 2> backint_find_master_time: actual_file_path =
> /dev/vgsapiBWP/rBWPclui_1<
11:13:28.130 [20169] < 2> backint_find_master_time: bid =
> NS1096040689< dest_dir = > /dev/vgsapiBWC/rBWCclui_1<
11:13:28.130 [20169] < 2> backint_find_master_time: start_unix_time =
1096040689 ; end_unix_time = 1096040689 ; image_time = 0
11:13:28.130 [20169] < 2> backint_find_master_time: found = 0 ; raw_par
= 0 ; time_pos = 0 file_size = 0
11:13:28.130 [20169] < 2> backint_find_master_time: exit status = 2
11:13:28.131 [20169] < 4> backint_do_restore:
#NOTFOUND /dev/vgsapiBWP/rBWPclui_1
(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
If a set of configuration options in bp.conf is very large, it can cause
bpgetconfig and the GUI to not display any of the items. This applies to
items in bp.conf with the same name, for example CONNECT_OPTIONS or SERVER.
Additionally, if that set of configuration options is edited in the GUI,
for example to add a new server to the CONNECT_OPTIONS, all of the previous
data for that set of options will be lost and only the new data will be in
bp.conf.
Workaround:
To avoid this issue, you should reduce the number of configuration options
with the same name.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In a rare circumstance, the last block of a multiplexed, duplicated copy of
a TIR backup may be corrupt. A verification of the copy would not be
successful. The original backup is not affected. This does not affect
non-multiplexed duplications of a multiplexed TIR backup.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The current NetBackup 4.5 FP patch release installs an outdated VSP driver
(v1.03). What should be installed is the 1.05 version that resolves
several issues related to VSP snapshot creation on 64-bit volumes and
interaction with third party VSS snapshot providers.
(All NetBackup Windows Clients)
=========
NB_45_7_F
=========
Description:
Managing calendar-scheduled backups when the master server is in a
different time zone than the Administration GUI causes the jobs to run in
a restricted time window or not at all.
There is no longer a limit on the number of calendar include/exclude dates
within a schedule.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
All Vault duplications were deemed successful (as stated in the duplicate
logs); however, the detail.log shows error 308 (no images successfully
duplicated). This issue happens even for the most simple of vault
duplication (for example, one image). The speed of the duplication was also
considered reasonably fast.
Additional Notes:
This is an issue specific to AIX 5.2, as the fundamental behavior of a
libc function ( fgets() ) has changed. Perhaps to be consistent with a
recent POSIX proposal.
The change to code alleviates the AIX problem, and is benign on other
platforms.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
NetBackup re-initializes the ADIC Scalar 10K library (causing the library
to be inventoried) before downing the drive in the event of a hardware
error on the drive.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If SQL Server 7.0 is installed as the default instance on a host and one or
more SQL Server 2000 instances exist, the SQL agent "DBMS log on options"
dialog may display the incorrect SQL version when one of the other SQL
instances is selected.
For example, if the SQL 7.0 default instance is "remembered" from the
previous session and you select a different instance on the same host
machine, then the DBMS log on options dialog box will still identify 7.0 as
the current version.
This problem has been found in NetBackup 5.0 (pre-release) as well as 4.5 MP6.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Imports or verifies with detailed logging can take much longer than
without detailed logging.
Workaround:
When performing an import or a verify, do not request detailed logging.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Restores of remote clients initiated from a NetBackup server with detailed
logging can take much longer than restores without detailed logging.
Workaround:
Don't request detailed logs or initiate the restore from the remote
client.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In some restores from multiple images on the same tape, more than one
image restore can be started at the same time causing bptm to core dump.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The NetBackup Administration Console for Windows may crash on Multi-
Processor systems due to a threading issue with regards to pending requests
in the Device Monitor node.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
If a file has VxFS attributes such as reserve or fixed extent size, a
FlashBackup file restore would fail resulting in a zero length file.
(All NetBackup Servers: HP Intel-NT RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
If the user selects a differential database backup from the SQL Server
backup history dialog, the SQL agent should attempt to determine a full
recovery path. This functionality (removed in 4.5 MP1) is restored with
this patch.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Certain robotic conditions could cause a Vault job to end prematurely.
Retry logic has been added around the robotic inventory vault process to
accommodate this problem.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Ejecting more than ~642 tapes results in the vlteject process failing.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Performing consolidated ejects and reports could result in the completion
status of the individual sessions not being updated correctly. Vault could
incorrectly update a session as complete when it is not. This results in
the operator being unable to complete the ejects or reports for the
sessions that were consolidated.
Workaround:
Do not perform consolidated ejects or reports.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When a Vault session ejects media to a SCSI robot, the session may fail
with an error code 293 due to the robot being busy. Vault now retries the
eject operations when the robot is busy.
Additional Notes:
This problem can occur when tape mounts or GUI robotic operations are
performed during a Vault session.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The bpbrm -stream_count argument is not correct for frozen image or split
mirror backups. The error manifests itself in the "-stream_count" being
zero for stream number 1, and 'n-1' for streams 2 through n.
It is worse for frozen image or split mirror backups using retention
level 24: the -stream_count argument is zero for all streams.
Workaround:
1) Stagger multi-stream frozen image job start windows.
2) Avoid retention level 24 for multi-stream frozen image jobs.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
For ACS robot types, if a tape that is to be ejected is mounted while an
eject of that tape is in progress, the eject job may never complete.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The bpsched process core dumped and left a child process still running. The
remove_from_mpxgrp_activelist() function attempts to free pool information,
but the pool pointers are really residue. Changed add_to_active_job_lists
() function to initialize the malloc structure.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When starting a backup using -i (immediate), and -L (logging) turn on
progress logging for the client, the job doesn't appear in the bpjobd
monitor (Activity Monitor). I get the following error in the
bpjobd debug log: Jobid came as 0.
Currently adding formal ability to use backup progress logging on clients
when using the bpbackup -i, which is currently disallowed by bprd and
bpbackup. Also, note that bpbkar is successfully receiving the -L
option, so bpsched seems to pass along the log file successfully.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpsched core dumped on active node of VCS cluster while running jobs.
The problem is: the fixing of memory leaks went a little too far here
and tried to free a literal character pointer.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
PROBLEM: SQL restore dialog box did not scroll correctly.
SOLUTION: The scroll/resize logic has been altered to improve scrolling
properties of the restore dialog.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Performing a consolidated eject could result in volumes being moved into
the wrong off-site volume group.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
After running 'ADPrep' on a Windows 2000 Domain Controller, the bpbkar32
application may crash while performing a backup. The cause of the crash
has been linked to the backup of the SYSVOL information when the System
State is being backed up.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
On the Firewall tab of Host Properties in the Windows GUI, the settings
for existing clients change when new clients are added or deleted from the
list.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When a policy is configured to collect disaster recovery information as
well as multi data streams, there is a chance that the server may attempt
to collect multiple copies of the disaster recovery information from the
client at the same time. When this happens, the backups may generate a
status code of 1 (partially successful).
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When a system has more than 62 mounted volumes, backups may fail with
either a status 41 or a status 54. The exit status is due to the bpbkar32
application crashing.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
A backup of Lotus R6.0.3 or Lotus R6.5 will not back up subdirectories.
Additional Notes:
Support of Lotus R6.0.3 on Windows requires a Lotus patch (provided
as a hotfix) for SPR# THUR5LPPW9 to resolve an enumeration problem
encountered in the Lotus API function NSFSearch(). Customers should
contact Lotus Support and provide the SPR# to obtain the Lotus hotfix.
Support of Lotus R6.5 on Windows requires a Lotus patch (provided
as a hotfix) for SPR# THUR5LPPW9 to resolve an enumeration problem
encountered in the Lotus API function NSFSearch(). Customers should
contact Lotus Support and provide the SPR# to obtain the Lotus hotfix.
Without the appropriate hotfix, backups of Lotus Notes will fail and bpbkar
will log debug messages similar to this:
1:38:22.392 PM: [3444.1200] <3444> nbex_DebugLog: ERR - NBLNtoFINDDATA()
NSFDbOpenExtended('D:')
Failed: 0x103:File does not exist.
If the hotfix has been installed for Lotus R6.0.3, the Lotus Server console
will display the following version information:
Lotus Domino (r) Server (603HF80 for Windows/32)
If the hotfix has been installed for Lotus R6.5, the Lotus Server console
will display the following version information:
Lotus Domino (r) Server (65HF116 for Windows/32)
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
This change includes version 3.23.58 of MySQL for nbdbd.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The NetBackup Administration Console and bpps command lines could crash on
certain systems while attempting to gather process information via
Microsoft's Performance Counter APIs if the counter values are not the
defaults set by Microsoft.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The SQL agent should create user_ops directories so that backups will not
fail if the user deletes the directories or if the installation fails to
create them.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Alternate buffer method for backup should not be inhibited for
SQL Server 7.0.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
During an NDMP restore, and even though the NAS server reported a
NDMP_DATA_HALT_CONNECT_ERROR, NetBackup reports the restore as successful.
(Note: Receiving an NDMP_DATA_HALT_CONNECT_ERROR is rare. Most NAS servers
report an NDMP_DATA_HALT_INTERNAL_ERROR instead.)
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
When doing a Remote NDMP backup, the backup hangs after hitting EOM several
times.
This occurs when the tape hits end of media at the very end of the backup
while Remote NDMP is attempting to flush its internal buffers to tape.
Workaround:
Retry the backup with a different tape. This condition is not likely to
occur a second time on a different tape.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
A buffer overrun may cause the volume manager daemon vmd to fail.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The Number of parallel streams specified in an Oracle RMAN template that is
built using the Oracle RMAN Backup Wizard will be used for Archived Redo
Log backups in addition to Tablespace and Datafile backups. Previously,
only one stream was used for Archived Redo Log backups even if a greater
number of streams was specified in the template.
(All NetBackup Windows Clients Alpha Dgux HP Linux2.4 RS6000_433
SGI SOLARIS)
--------------------------------------------------------------------------------
Description:
If an inline tape copy job starts with multiplexing set to 1, another job
with multiplexing set greater that one will attempt to multiplex with the
first job. The multiplex setting of 1 on the first job caused the job to
run without multiplexing enabled. The second job will fail because it
cannot multiplex with the first job.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A restore from a Remote NDMP backup that spans tapes may indicate an error
occurred. This happens only with Remote NDMP on a Windows machine.
The bptm log shows "read_data_ndmp returned 0" which indicates the restore
was OK. Following this there is an MTFSF 1 tape command that fails with
IO_ERR.
Workaround:
This error can be ignored. Because read_data_ndmp returned good status, the
restore was successful. It is only the tape positioning that failed.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in the following
robotic libraries. The drives are properly configured within the library,
instead of being configured as standalone drives.
- Dell PV-122T
- Sony CSM-200
- Sepaton S2100
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When backing up a NetApp filer via a network mapped drive, errors may be
reported in the bpbkar32 debug log. The errors may contain the following
error code (WIN32 -1073741809: Unknown error). After getting this error
a couple of times, the backup process (bpbkar32) will crash.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When restoring a file, tar32 may crash. This will happen on a file that was
growing (increasing in size) during the course of the backup.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
If a restore fails because of a media mount timeout, bprd may core
dump when it finishes processing the restore.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A 134 status results in multiple tries in the Activity Monitor even though
they are not counted as tries.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If bpschedreq -predict is executed with a time that is not the current day,
the exclude dates will not be taken into account.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An imported backup of a backup copy other than copy 1 would base the
expiration time on the backup time rather than the current time, which
would result in the imported backup expiring too early.
Workaround:
The bpexpdate command may be used to change the expiration of the imported
backup.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When multiple densities are used in the same robot, not all drives will be
used.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The "Picking List" for the Robot Report was missing a Report Header. This
release fixes this problem.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Expiring one of the images from a multiple data stream backup causes a
restore to fail even though the images still exist.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Some files or directories show up in the wrong locations during restore
browsing or queries.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Calendar scheduled jobs may not run when administered from a different
time zone.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup resource DLL's are not being explicitly unloaded. This can cause
unneeded reboots during an upgrade install.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Collection of disaster recovery information from Windows clients fails.
The symptoms of this problem include:
1) Policy is configured to collect disaster recovery information.
2) Server connections to the client are supposed to use vnetd.
3) A firewall is present between the servers and the client.
When the server attempts to connect to the client to collect the disaster
recovery information, it will not use vnetd and it will fail.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Auto path correction will down drives that have a valid path, but do not
respond to commands. This patch allows auto path correction to down drives
that do not have valid paths.
This allows ltid to start even with missing paths.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The "Use Barcode Rules" check box is not checked by default. The default
is checked as long as the options dialog is not opened. Once you open the
options dialog, the default changes to unchecked. When you do an
inventory, the default should always be to use barcode rules.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Restore paths incorrect for NDMP path-based history.
The list of files for an NDMP backup image are missing the original backup
path. This occurs with path-based file history running NDMP V4.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
When automatic path correction is enabled, some robotic paths may be
incorrectly changed if the customer has a mix of serialized and
unserialized robots.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A 174 error (media manager - system error occurred) occurred when an end-of-
media status was returned while trying to write a end-of-file marker on the
tape. This may occur on the Windows or SGI platforms. The bptm log will
show an entry similar to the following:
00:30:40.803 [3256.4608] <2> io_ioctl: MTWEOF encountered EOM (error 1100),
return EOT
This is followed by an entry indicating "buffers out of sequence", and the
174 error.
(All NetBackup Servers: Intel-NT SGI)
--------------------------------------------------------------------------------
Description:
NDMP dump levels are always 1.
Additional Notes:
This fix was integrated into the NetBackup 4.5MP path, but the
NetBackup 4.5FP and 5.0 paths were missed.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The scheduler "predict" is out of sync with what actually gets run.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When different vault sessions are run concurrently, the vlteject.mstr file
may become corrupted because of timing issues with processes trying to
read/write to this file at the same time.
This fix reduces the chances of this file getting corrupted.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The problem fixed in this patch is related to the Media Going Off-site
reports for Vault. The Picking List for Robot and the Distribution List
for Vault were reporting an 'image count' of 0 even when there were tapes
being ejected with plenty of images on them. This issue has been resolved.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Drives keep going down every few days. Avrd reports semaphore errors
similar to the following in /var/adm/messages:
messages.0:Oct 28 21:56:28 server1 avrd[8148]: Error in Semaphore
Operation - Result too large
messages.0:Nov 1 03:20:54 server1 avrd[18968]: Error in Semaphore
Operation - I/O error
messages.1:Oct 20 01:31:34 server1 avrd[26744]: Error in Semaphore
Operation - I/O error
Workaround:
To avoid this issue, down the NDMP drives that are not working.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Exchange 2000 mailbox backup causes bpbkar to seg fault when processing the
first mailbox. A Status 42 "network read failed" appears in the Activity
Monitor at the master server. Exchange IS backups are successful.
From the bpbkar log:
01:23:32.111 AM: [896.2572] <2> ov_log::V_GlobalLog: INF -
MAPISession::ImpersonateUser(): !Logging on to server xxxxx as
user yyyyy!!
MessageStoreDN=/O=xxxx/OU=zzzzz/CN=Configuration/CN=Servers/CN=xxxxx
/CN=Microsoft Private MDB !!
MailBoxDN=/O=xxxx/OU=zzzzz/CN=recipients/CN=yyyyy
01:23:32.252 AM: [896.2572] <2> tar_backup::backup_startfile_state:
TAR - writing file 0 'Microsoft Exchange Mailboxes:Doe [yyyyy]'
***This is the last line of the log for this job.
Workaround:
Concerning Windows Registry Key:
HKEY_LOCAL_MACHINE\Software\microsoft\ESE97; REG_SZ;
5.2650.0017
Rename the registry key from ESE97 to ESE97_old and retry the mailbox
backup again.
All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Resolves a potential Dr. Watson on Windows NT if an NDMP drive path name is
too long (exceeds the stack). The new maximum length for drive path name is
128 characters.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
SAP's backint fails with status 25 when the server value is not set in
the .utl file and the SAP_SERVER environment variable is not set. The
server entry is not being picked up from bp.conf and passed to bplist.
Workaround:
Set the server value in the SAP init< SID> .utl file or set the SAP_SERVER
environment variable.
(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
If a client is down when the scheduler is doing autodiscovery, and the
Windows GUI attempts to modify a policy, the policy may get deleted.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When attempting an "invalid" alternate path mailbox restore attempt, the
restore fails with a status 5 and a Dr. Watson is generated for the
tar32.exe process.
The tar32 log ends with:
14:02:17 (38.001) UTF - /Microsoft Exchange Mailboxes/wankel
[wankel]/Top of Information Store/Inbox/Messages
<0000000063DAD1613F74304598422D2077E7E9FB07008D92BB8D1A7A7F418E6DC63AEE8
285B400000000393F0000EBEC8122CD95E64EA8FAF139C49A48880000000009300000>
14:02:17 (38.001) UTF - /Microsoft Exchange Mailboxes/wankel
[wankel]/Top of Information Store/Inbox/Messages
<0000000063DAD1613F74304598422D2077E7E9FB07008D92BB8D1A7A7F418E6DC63AEE8
285B400000000393F0000EBEC8122CD95E64EA8FAF139C49A48880000000009310000>
14:02:17 (38.001) Status of restore from image created 10/14/2002
12:25:06 PM = file read failed
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Sybase backups fail occasionally with a 143 error if the scheduler is
unable to connect to the client while writing the progress log.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NDMP backup restore can fail because some NDMP venders do not use "2" as the
mount point inode number.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Restores or backups may erroneously fail with a 52 status (timed out
waiting for media manager to mount volume).
Workaround:
To avoid this issue, set the media mount timeout to zero.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When ejecting media to an ACS robot, the eject process could hang because
of an unhandled volume status, STATUS_ROBOT_BUSY. This status is now
handled appropriately as an error condition.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When vault sessions are run on a Linux master, the contents of
vlteject.mstr are deleted during the eject phase. Thus the reports for the
session and any other pending ejects/reports fail with NetBackup status 296
(process called but nothing to do). This issue has been resolved.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
On UNIX systems, the tldcd and tl8cd robotic daemons may fail if
connections are opened and closed quickly with no data.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When restoring NAS data from an NDMP-attached tape drive, the bprecover
command fails with an EOM (end of media) error.
Workaround:
To avoid this issue, use a non-NDMP drive.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
In Eject/Inject operations with the vmchange command using the -w flag, a
user has 5 minutes to tell the system to continue, after they are prompted
to add remove volumes from the media access port. This 5 minute timeout is
not configurable.
This timeout can now be controlled using the vm.conf option
MAP_CONTINUE_TIMEOUT, on the robot control host.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A missing tape unmount on one of the copies when using Inline Tape Copy may
cause unnecessary 134 status codes (unable to process request because the
server resources are busy).
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The problem is that Vault's image list used for duplication is sorted by
increasing k-bytes and the customer would like a way to reverse this sort.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
During the suspend step of a vault session, a core dump may occur (in
particular on HP-UX systems).
Workaround:
The workaround for this issue would be to manually suspend tapes being
ejected using "bpmedia -suspend -m <media_id>".
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When performing drive cleaning from the java GUI, drive names with more
than 22 characters could cause problems for the GUI.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpjobd stops responding. The last few entries in the bpjobd log file
indicate multiple attempts to establish a connection from a client. The
Client was interrupted during the first connection handshake and began the
connection procedure again. This situation causes a deadlock condition.
Workaround:
To avoid this issue, restart bpjobd and then kill the offending client. You
can use netstat to find the client.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A warning is required when a library is deleted if there is media assigned
to it or if the last drive of that particular drive density is deleted from
a robot.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The Remote NDMP ndmpmoverlistener.exe process shows growing handle count
and page faults, which eventually brings down NDMP drives.
Workaround:
Stop and then restart the "NDMP Mover Agent" from services.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When NAS vendors do not send a notify data_halted message after sending a
last file history, remote NDMP waits and eventually fails with a timeout
error (error 99).
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Add support for Oracle 10g.
All NetBackup Windows Clients Alpha HP Linux2.2 RS6000_433 SOLARIS
--------------------------------------------------------------------------------
Description:
In some limited circumstances a change server command will result in the
console crashing. This issue has been resolved.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
bppllist -allpolicies or <policy> -U core dumps
Workaround:
1) Look for a policy that has an unusually long value for one of its
attributes, such as the keyword, or a policy that has many clients.
2) Run 'bppllist <policy name> -U' to display this one policy.
3) If bppllist aborts, modify the policy to reduce the length of
the long value.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Scheduler gets an occasional core dump when it is preparing to exit. The
error happens when trying to determine which storage units are busy.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Using a Binary Catalog could cause an inability to browse for restores under
certain file selection lists. This issue has been resolved.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Customers using noauth authentication with the NetBackup Administration
Console for Windows would not be able to start manual backup jobs if they
were not an Administrator on the system running this Windows GUI.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Suppose the master server and media server are different servers. Also
suppose that the media server and client are the same machine so that
shared memory backups and restores are normally done.
Suppose the master server is configured so "connect backs" with the media
server are done using VNETD. The typical bp.conf entry on the master server
would look like this:
CONNECT_OPTIONS = mediax 0 1 2
Where "mediax" is the hostname of the media server. The digit "1"
signifies that vnetd style connect backs are used.
In this case, restores will fail. Typically, the job will fail with error
code 5 and be marked as "incomplete" in the job monitor.
Workaround:
Do not use VNETD style connect backs with the media server if the media
server is also a client.
(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
Exchange backup does not support the bandwidth limitation setting.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
This issue fixed by this patch has to do with changing the expiration date
of disk images from vault after they have been successfully duplicated. If
bpduplicate is passed a really long list of image IDs and never gets a
chance to return to Vault, then Vault won't get a chance to change the
expiration date of the image.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Correct end-case problem in MPX read processing (for restores/duplications)
that may try to unmount a media that is already in use by another process.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When verifying very large backup images, the Activity Monitor would
incorrectly report a failure status that included a ?client process
aborted? error message. Testing showed that the verify job had not
actually failed and the incorrect status was displayed because the
keep-alive checks were not being sent to bpjobd if the bpbrm socket was
active for specified amount of time. This time interval to send
keep-alive packets has been corrected, resolving this issue.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup SQL Server agent connects to SQL Server 6.5 hosts with integrated
security.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When BATCHSIZE is set in the SQL agent batch file, some of the backups
fail with errors such as the following:
12:53:45 [2276,2476] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC
message. ODBC return code <-1>, SQL State <IM002>, Message Text <
[Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified>
12:53:45 [2276,2476] <16> Dbbackrec::PerformNBOperation: USER - Unable
to login into ODBC DSN <NBMSSQL_2276_2100> as user <sa>
or
12:54:00 [2276,2404] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC
message. ODBC return code <-1>, SQL State <08001>, Message Text <
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
or access denied.>
12:54:00 [2276,2404] <16> CODBCaccess::LogODBCerr: DBMS MSG - <
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect
()).>
12:54:00 [2276,2404] <16> CDBbackcat::LoginODBC: USER - Unable to login
into ODBC DSN <NBMSSQL_2276_2100> as user <sa>
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
If SQL Server is configured under binary collation, some images may not be
displayed in the NetBackup SQL agent's backup history window.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When creating VSP snapshots for backups, the snapshot creation can
disregard volumes in the VSP "Cache File Volume List" when they could have
been used as cache file locations.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When auto-sizing a VSP cache file when it is placed in a volume other than
the volume being snapshot, NetBackup may calculate its maximum size to a
value smaller than the correct value. This can cause VSP snapshot errors to
occur and the backup could end with status 155: disk is full.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When backing up RIS or SIS data with a backup that has VSP enabled to back
up open/active files in a file system backup, bpbkar32 will crash during
the backup.
Workaround:
To avoid this issue, disable VSP when backing up RIS/SIS data.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
A performance degradation with Exchange Mailbox backups was encountered
after upgrading from an MP release to an FP release while running the same
NetBackup configuration.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
A typographical error in the close_job_disconnect() function code corrupts
the
socket when bprd trying to disconnect from jobd.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If a backup image was originally written by NetBackup 3.1.1 and is then
archived using the NetBackup FP5 catalog archiving feature
("bpcatlist|bpcatarc|bpcatrm"), the .f file will be deleted without the
ability to use "bpcatres" to restore the file.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The FORCE_RESTORE_MEDIA_SERVER does not replace the server entry for TIR
fragment. Thus, when TIR information needs to be extracted from tape, bpdbm
tries to initiate a "bptm -restoretir" on the original server.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in HP ESL E-Series
robotic libraries. The drives are now properly configured within the
library, instead of being configured as standalone drives.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using the NetBackup Windows Oracle wizard, the user's authentication
choice is now correctly saved and used when building the RMAN template.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Users that do not have administrator privileges should not always see the
message "NetBackup was unable to start the required NetBackup Client
Service" when attempting a backup or restore from the Windows PC Client
GUI.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
On a multimedia type robot, robotic inventory was failing while inserting
media into the volume database. The inventory operation successfully inserts
media of one type but fails while inserting media of another type.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Problems querying/updating the volume database during an eject could lead
to the eject job failing prematurely, leaving a session incomplete.
Also, consolidated eject/report jobs that were partially successful could
be erroneously marked as complete and volumes may have an incorrect off-
site volume group leading to report inconsistencies.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Provide the ability for the user to control the format of the drive names
that are created by the Device Discovery Wizard.
Additional Notes:
The following variables could be used in generating a drive name:
- HN - hostname of the server where the drive is first discovered
- RN - robot number
- RT - robot type
- POS - Drive position, determined by robot type. One of the following:
- robot drive number
- vendor drive id
- ACS.LSM.PANEL.DRIVE
- SN - serial number of the drive
- DT - drive type (i.e. hcart, 8mm, dlt2)
- VEND - vendor ID of the drive obtained from the inquiry string of the
drive
- PROD - product ID of the drive obtained from the inquiry string of the
drive literal strings proceeded by a pound sign(#) containing
the allowable characters in a drive name.
- IDX - ensure an index is appended. Otherwise, an index will be
automatically be appended if needed to make a drive name unique.
Note: Any white space in the above entries will be collapsed.
These entries will allow a tiered approach. If the DRIVE_NAME_SEED
entry appears on a non-global-database host, that format will be
used. Otherwise, the vm.conf file on the global database host will
be checked for a DRIVE_NAME_SEED entry. If one exists, it will be
used. If none exists in either location, the default naming scheme
will be used. For tpconfig this is "Drive" followed by a number to
make it unique. For tpautoconf, this is VendorID, followed by
ProductID, followed by a number to make it unique.
EXAMPLES:
1) To generate the default names used by discovery provide the entry:
DRIVE_NAME_SEED = VEND:PROD:IDX
This will produce drive names of the form
QUANTUMDLT70000
2) To generate the names that contain the drive's product ID and
robot residence information, fields separated by minuses:
DRIVE_NAME_SEED = PROD:#-:RT:#-:RN:#-:POS
This will produce drive names of the form
DLT70000-TLD-0-1
Issues and Limitations
Some of the below items are just general drive naming issues, while others
relate specifically to this feature.
1. In a shared storage (SSO) environment drives will be named based on
the seed of the first host that discovers them. Subsequent hosts
will retain that drive name regardless of the value of their local
DRIVE_NAME_SEED vm.conf option.
2. The Hostname (HN) should be used with caution in SSO
configurations. Drives shared amongst hosts must have the same
name. See 1 above.
3. Drive names remain limited to 48 characters.
4. Valid characters are upper and lower case alphanumeric, plus, minus,
underscore, and period.
5. Drive names cannot start with a minus (-) character.
6. If robot residence information is used to generate the drive name, the
host that has the robot attached should be discovered first.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Provide a facility to swap drives without requiring the user to delete and
re-add drives, or re-run Device Discovery.
Additional Notes:
The following example shows how the -report_disc command is used to
report discrepancies between detected devices and Global Database.
In addition, an example of how to use the -replace drive_name
-path drive_path command is included.
# /usr/openv/volmgr/bin/tpautoconf -report_disc
======================= New Device (Tape) =======================
Inquiry = "QUANTUM DLT8000 0250"
Serial Number = PXB08P3242
Drive Path = /dev/rmt/119cbn
Found as TLD(6), Drive = 1
===================== Missing Device (Drive) =====================
Drive Name = QUANTUMDLT800014
Drive Path = /dev/rmt/9cbn
Inquiry = "QUANTUM DLT8000 0250"
Serial Number = PXB08P1345
TLD(6) definition Drive = 1
Hosts configured for this device:
Host = dandelion
Host = avocadocat
# /usr/openv/volmgr/bin/tpautoconf -replace_drive
QUANTUMDLT800014 -path
/dev/rmt/119cbn
Found a matching device in global DB, QUANTUMDLT800014 on host
dandelion
update of local DB on host dandelion completed
globalDB update for host dandelion completed
Found a matching device in global DB, QUANTUMDLT800014 on host
avocadocat
update of local DB on host avocadocat completed
globalDB update for host avocadocat completed
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If an error is encountered while attempting to open Lotus change
information during a Lotus backup, the backup will crash if the debug
logging level is increased. This problem has been resolved.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
When using the NetBackup PC Client Windows interface to do a Lotus Notes
user-directed backup, the NOTES.INI path field in the "Specify Backup
Options > Lotus Notes" page is now processed correctly.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Performing consolidated ejects for all robots could malfunction if the
vault configuration contains multiple robots of the same robot type. This
problem could result in media being left in an incorrect off-site volume
group. Also, media ejected from some of the robots doesn't occur but
appears to have completed successfully.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Vault catalog backups fail with a status code 306 if there is media in
the Catalog Backup volume pool that are expired.
In this case the first tape in available media has expired. Vault
immediately fails with a 306 rather than skipping this tape and trying
to use the next tape in the list.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
In configurations where the media server and master server are separate,
the master server host name is being used instead of the media server name
when changing the volume group of media that are moving back to the robot.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Backing up files whose length is changing results in corrupt data which
cannot be restored.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Non-root users of vault are unable to eject media with vault. The
vlteject.mstr.lock file gets created with 600 permissions under UNIX.
This will prevent non-root NBAC users from acquiring the lock, and ejects
will hang waiting for that lock file.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When a duplicate profile name existed in separate vaults, and selecting an
alternate session number, vltopmenu required that the triplet be fully
qualified, instead of first defaulting to the current vault.
Workaround:
To avoid this issue, you should not duplicate profile names.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
vltrun is frequently failing with a status 282 and also dumping core.
Subordinate commands executed by bv_run_system() must not be allowed to
return an exit status of 0, when the child was killed by a signal. Insure
that children killed by a signal, and have a zero exit status, are actually
attributed a non-zero exit status (EC_process_killed).
Additional Notes:
If the image database is corrupt, as it was in the problematic case, the
problem is exposed. bpimagelist had returned a 'space' where vault had
demanded, and expected, a significant entry. The resultant failure exposed
a long sequence of erroneous vault behavior.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
On a system running Windows 2000 (SP4), you may not be able to browse or
restore the second volume if 'SET HIST=N' is listed in the middle of the
policy's file list.
Workaround:
To avoid this issue, contact your Symantec customer support office for help
on manually fixing your catalog files.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Duplication of multiple copies using Inline Tape Copy may fail with a 20
error (invalid command parameter). The bptm log (the write side of the
duplication) shows an entry similar to the following:
14:55:48.274 [5586] <16> bptm: not enough parameters specified
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A media position error can occur when attempting to restore from a copy of
a backup created by Inline Tape Copy. The bptm log will show an entry that
is similar to the following (note the file number of 0):
13:12:27.348 [22187] <2> mpx_read_init: media id A00001, copy 1,
fragment 1 (839680 Kbytes) filenum 0 being considered for restore
The problem occurs when performing multiplexed backups using Inline Tape
Copy, and a new backup is started while waiting for a tape mount due to
hitting end-of-media.
Workaround:
To avoid this issue, the restore may be done from the other copy.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using Inline Tape Copy, the wrong media-id may be frozen when a media
error occurs on a copy other than the first copy. This happens when the
fail-on-error attribute is set for the failed copy. In this case, the
media-id for the first copy is frozen rather than the media-id for the copy
that obtained the error.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bprestore command fails with the error message "No files matched file
path for a date range"
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Unable to restore NDMP NetWare data due to an invalid path shown in catalog.
If \Serveris specified as a file selection that is backed
up, the Backup, Archive, and Restore screen shows the tree expanded as
Vol1.
The restore fails with "Cannot restore from filepath ,
NDMP_HALT_INTERNAL_ERROR occurred" and a status (5). The data cannot be
restored to the original location or redirected using a valid path.
(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
VOPIE Enhanced Authentication may not work when host names are longer than
32 characters. As a result, you may see Authentication Failed (error code
160) messages when connecting to systems with host names or client names
greater than 32 characters.
(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
A possible buffer over-run may be corrupting the eject information in
memory, causing ACS ejects to fail because the CAP was reported as not
existing, when in reality it did exist.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Exchange restores from multiple images fails with a communications failure
error. The log will have a message similar to the following:
17:58:45 (158515.002) ERR - unable to create object for restore:
Microsoft Information Store:files_1074011439 (BEDS
0xFFFFFE30: A communications failure has occurred.
Workaround:
Create a file named /usr/openv/netbackup/NON_MPX_RESTORE to force
sequential restores from multiple images.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The timeout for an ACS query is configurable using the ACS_QUERY_TIMEOUT
entry in vm.conf. The value of this entry is in minutes, for example:
ACS_QUERY_TIMEOUT = 30
This sets the timeout to 30 minutes.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Ejects that are partially-successful are erroneously marked as completed.
As a result, the operator cannot eject the remaining media or re-run
reports.
(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Added support for the SDLT-600 drive type and the SDLT_2 media type to
the ACS robotics.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Single MAP ejects may not query the ACSLS server for the correct MAP
causing the eject to fail.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The "from" and "received date" fields were not being updated correctly
on the restore of a message to an Exchange Public folder.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Enhance bptm to use MEDIA_UNMOUNT_DELAY for duplications to reduce
unnecessary unmounts/re-mounts during Vault sessions.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using "bpexpdate -recalculate" or "bpexpdate -backupid" to extend the
expiration date of one or more backups that have multiple copies, the media
expiration may not be correct for copies on removeable media if the first
copy is on disk.
(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
This enhancement enables NetBackup to work in a Plug and Play environment.
You can now use NetBackup with Plug and Play tape class drivers and the
Storport driver.
(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When performing backups with TIR plus move detection, some backups may not
verify correctly due to files/folders having identical file numbers.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
Exchange Mailbox backups may hang for Exchange 2003 running on a 2003
cluster.
This hang only seems to happen on Exchange 2003 after mailboxes are
migrated from Exchange 5.5.
The last log entry in Debug logs would be:
"INF - MAPISession::ImpersonateUser(): Logging on to server
<Exchange_Virtual_Name>
as user <MailBox_Alias>! MessageStoreDN=/O=<Org>/OU=first administrative
group/
CN=Configuration/CN=Servers/CN=<Exchange_Virtual_Name>/CN=Microsoft Private
MDB
!MailBoxDN=/O=<Org>/OU=first administrative
group/CN=recipients/CN=<MailBox_Alias>"
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When performing System State backups on a Windows XP and/or a Windows 2003
Server, the backup may appear to hang when it backs up the Registry or it
may generate errors while backing up the Registry.
(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
bpbkar32 may generate an 'Exception number: c0000005 (access violation)'
(Dr Watson) when doing a cumulative backup of an Exchange 2000 Storage
Group and the first transaction log to be backed up is missing. The backup
ends with status 13. Typically, the log file is missing because the user
has deleted it.
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Exchange 2000/2003 restores may fail when the restore includes many log
files.
The tar debug log may be as follows:
11:36:54.556 AM: [8140.4520] <2> ov_log::V_GlobalLogEx: INF -
exchange_2000_access::m_fWriteIoPartializer: dwBlockSize:4 dwSize:2
dwBufferPioCnt:0
11:36:54.556 AM: [8140.4520] <2> ov_log::V_GlobalLogEx: INF -
exchange_2000_access::m_fWriteIoPartializer: dwBlockSize:0 dwSize:65536
dwBufferPioCnt:2
11:36:54.571 AM: [8140.4520] <2> ov_log::V_GlobalLogEx: ERR -
exchange_2000_access::m_fWriteIoPartializer:FS_WriteObj() BlockSize(82)
returned on partialized I/O request
(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
The Windows 2000 platforms were losing multiplexed groups. The user could
not cancel orphaned jobs within the multiplexed group, and additional jobs
could not be added to the multiplexed group.
Windows-specific code was added to display questionable pointer values
prior to releasing the multiplexed group. This minor change seems to have
resolved the problem, however, new information may suggest that this it a
Windows 2000 compiler optimization issue. Thus, this fix either masks the
problem, or helps isolate it.
(All NetBackup Servers)
================================================================================
Attachments
|
|
Related Articles
Legacy ID
279433
Article URL http://www.symantec.com/docs/TECH44135
Terms of use for this information are found in Legal Notices
Thank you.