Maintenance Pack NB_SAP_60_7_M.tar provides fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 for SAP Database Agent on UNIX platforms.

Problem

Maintenance Pack NB_SAP_60_7_M.tar provides fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 for SAP Database Agent on UNIX platforms.

Solution

SAP 6.0GA Pack NB_SAP_60_7_M README SAP September 15, 2008
Requirement: NB_CLT_60_7_M
================================================================================
This Maintenance Pack provides fixes for Veritas NetBackup (tm) for SAP Database
Agent.

================================================================================


=================
PACK DEPENDENCIES
=================

-- Installation of this Maintenance Pack requires version 1.33.10.18
of Vrts_pack.install.

-- NB_CLT_60_7_M must be installed prior to installing this
Maintenance Pack.



I. NEW FEATURES AND PLATFORM PROLIFERATIONS
II. KNOWN ISSUES
III. DOWNLOAD INSTRUCTIONS
IV. INSTALLATION INSTRUCTIONS
V. UNINSTALL INSTRUCTIONS
VI. CURRENT MAINTENANCE PACK INDEX
VII. MAINTENANCE PACK CONTENT
Conventions
Current Maintenance Pack
NB_SAP_60_7_M
Maintenance Pack History
NB_SAP_60_6_M
NB_SAP_60_5_M
NB_SAP_60_4_M
NB_SAP_60_2_M



============================================
I. NEW FEATURES AND PLATFORM PROLIFERATIONS
============================================
Many new features, enhancements, and platform proliferations have been made
to NetBackup 6.0 MP7 in general. For a complete list of these additions, refer
to the New Features and Platform Proliferations section in the NB_CLT_60_7_M
online Readme that you installed prior to installing this package.




=================
II. KNOWN ISSUES
=================
This section contains known issues with this maintenance pack that have not
yet been fixed in NetBackup. These issues will likely be fixed in future
Maintenance Packs for this version of NetBackup.

There are no known issues with this Maintenance Pack.




==========================
III. DOWNLOAD INSTRUCTIONS
==========================
1) Download NB_SAP_60_7_M_<6 digit number>.tar into the /tmp
directory.

where <6 digit number> is an internal tracking identifier

2) Extract NB_SAP_60_7_M_<6 digit number>.tar
/bin/tar xvf NB_SAP_60_7_M_<6 digit number>.tar

This will create the files:
VrtsNB_SAP_60_7_M.README
VrtsNB_SAP_60_7_M.SAP.alpha_5.tar.Z
VrtsNB_SAP_60_7_M.SAP.hp11.00.tar.Z
VrtsNB_SAP_60_7_M.SAP.hpia64.tar.Z
VrtsNB_SAP_60_7_M.SAP.linux2.4.tar.Z
VrtsNB_SAP_60_7_M.SAP.linux64.tar.Z
VrtsNB_SAP_60_7_M.SAP.plinuxR_2.6.tar.Z
VrtsNB_SAP_60_7_M.SAP.plinuxS_2.6.tar.Z
VrtsNB_SAP_60_7_M.SAP.rs6000_51.tar.Z
VrtsNB_SAP_60_7_M.SAP.solaris8.tar.Z
VrtsNB_SAP_60_7_M.postinstall
VrtsNB_SAP_60_7_M.postuninstall
Vrts_pack.install




=============================
IV. INSTALLATION INSTRUCTIONS
=============================
** The content of this online Readme supersedes the information in the Readme
contained in the download. **

There are two ways to install database agent maintenance pack software.

1. Remote Installation: Loads the software on a master server with
the intent of pushing database software out to affected clients.

2. Local Installation: Loads and installs the software only to this
local machine.

---

Remote Installation:

As root on the NetBackup Master/Media server:

1. Install the Maintenance Pack binaries.

cd /tmp
/bin/sh Vrts_pack.install

Pick option 1 (Remote Installation) when prompted for the installation
method.

2. Run update_dbclients to push pack software affected database agent clients.
For more information on how to run update_dbclients, refer to the NetBackup
for SAP System Administrator's Guide.

----

Local Installation:

As root on the NetBackup for SAP client:

1) Install Maintenance Pack binaries.

cd /tmp
/bin/sh Vrts_pack.install

Pick option 2, Local Installation, when prompted.




=========================
V. UNINSTALL INSTRUCTIONS
=========================
1) Close the NetBackup user interfaces.

If a database agent is being used, such as SAP,
ensure that the database services are stopped.

2) Change directory to the patch save directory.
Substitute the pack name for ${PACK.EN_US} in the following command:

cd /usr/openv/pack/${PACK.EN_US}/save

3) Run the un-install script:

./Vrts_pack.uninstall

4) Verify that the pack uninstalled successfully by checking
/usr/openv/pack/pack.history.

5) Only perform this step if the pack was originally pushed to remote
clients using update_dbclients. Please run update_dbclients after
the pack was successfully uninstalled on the master server.




==================================
VI. CURRENT MAINTENANCE PACK INDEX
==================================

This section contains a master index for all UNIX packages of Etracks that
have been fixed in this release, sorted according to the containers that
they comprise.


NB_60_7_M
---------
1128726 1145685 1146635 1150657 1172971 1178481 1194284 1175361 1196200 1160439
1191148 1193696 1197056 1201124 1186553 1201289 1200945 1193183 1186256 1202780
1181024 1046203 1188094 1193241 1200911 1196151 1204133 1194711 1203203 1203315
1204149 1203341 1196108 1206982 1149072 1203743 1206988 1209668 1141942 1210324
1181990 1205097 1157872 1028523 1193739 1202703 1139683 1213186 1210997 1213398
1194467 1198779 1163522 1194630 1186713 1159797 1215592 1215486 1213931 1146675
1213936 1217081 1019035 1003076 1199328 1173094 1211957 1209824 1210121 1219899
1206849 1204494 852979 1168028 1190482 1223027 1223019 1229928 1159536 1200897
1224637 1214052 1201393 1152608 1042411 1211653 1137917 1135737 1227823 814704
1175373 1236186 1237077 1237818 918372 1200166 1216170 1039111 1238630 1229969
1238098 1239178 1236032 1242512 1245566 1244766 1245997 1244622 1221477 1036931
1200190 1089296 1251778 1252326 1219002 1252345 1268942 1184332 1223173 1212526
1259059 1195231 1260503 1259252 1262091 1150199 1240367 1261507 1261430 1269061
1273387 1275369 1269918 1228938 1261282 1097416 1275549 1281153 1270235 1253532
1283873 1283865 1277786 1077528 1189875 1190428 1291060 1260324 1287242 1292773
1294647 1291761 1295792 1302098 1251842 1316727 1316894 1321914 1178607

NB_ADC_60_7_M
-------------
1179426 1220903 1227575 1239595 1235529 1231895 1219116 1134888 1211678 1275147
1227541 1210195 1361434

NB_BBS_60_7_M
-------------
1194900 1198426 1201794 1240183

NB_BMR_60_7_M
-------------
1201741 1212630 1213219 1219751 1222733 1231109 1228989 1212202 1175891 1195956


NB_CLT_60_7_M
-------------
1128726 1145685 1146635 1150657 1172971 1178481 1194284 1175361 1196200 1160439
1191148 1193696 1197056 1201124 1186553 1201289 1200945 1193183 1186256 1202780
1181024 1046203 1188094 1193241 1200911 1196151 1204133 1194711 1203203 1203315
1204149 1203341 1196108 1206982 1149072 1203743 1206988 1209668 1141942 1210324
1181990 1205097 1157872 1028523 1193739 1202703 1139683 1213186 1210997 1213398
1194467 1198779 1163522 1194630 1186713 1159797 1215592 1215486 1213931 1146675
1213936 1217081 1019035 1003076 1199328 1173094 1211957 1209824 1210121 1219899
1206849 1204494 852979 1168028 1190482 1223027 1223019 1229928 1159536 1200897
1224637 1214052 1201393 1152608 1042411 1211653 1137917 1135737 1227823 814704
1175373 1236186 1237077 1237818 918372 1204203 1200166 1216170 1039111 1238630
1229969 1238098 1239178 1236032 1242512 1245566 1244766 1245997 1244622 1221477
1036931 1200190 1089296 1251778 1252326 1219002 1252345 1268942 1184332 1223173
1212526 1259059 1195231 1260503 1259252 1262091 1150199 1240367 1261507 1261430
1269061 1273387 1250877 1275369 1269918 1228938 1261282 1097416 1275549 1281153
1271278 1270235 1253532 1283873 1283865 1277786 1077528 1189875 1190428 1291060
1260324 1287242 1292773 1294647 1291761 1296282 1295792 1302098 1251842 1316727
1316894 1321914 1178607

NB_DB2_60_7_M
-------------
1294774

NB_DMP_60_7_M
-------------
1152587 1213695 1222258 1214070 1235538 1233401 1249754 1257297

NB_ENC_60_7_M
-------------
1238098

NB_INX_60_7_M
-------------
1145850

NB_JAV_60_7_M
-------------
1188650 1194367 1135270 1187772 1205636 384091 1278056 1255609 1301700

NB_LOT_60_7_M
-------------
1314264

NB_NOM_60_7_M
-------------
1226692 1233746 1195149 1238422 1204000 1122893 1036931 1283800 1291729

NB_ORA_60_7_M
-------------
1226883 1224664 1294774

NB_SAP_60_7_M
-------------
1209710 1142467 1210594

NB_SMU_60_7_M
-------------
1280906

NB_VLT_60_7_M
-------------
1238369 1166277 1283692 1297162 1385494




=============================
VII. MAINTENANCE PACK CONTENT
=============================
This section contains the maintenance pack conventions, content, and historical
content that is applicable to the release.

Conventions:
------------
The following list describes the conventions used in the subsections that
following this section. Each item listed in the Current Maintenance Pack
subsection describes a feature, enhancement, or issue fixed with this
Maintenance Pack.

Description
Describes a particular problem contained in this 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 available patch level.

Additional Notes
Any additional information regarding a problem is included.



Current Maintenance Pack
------------------------
Each item listed in this section describes a feature, enhancement, or change
that comprises this Maintenance Pack. Please read this section thoroughly to
understand the contents of this update.
--------------------------------------------------------------------------------
Etrack Incident = ET1209710
Associated Primary Etrack = ET1204922
Titan cases: 311-817-301

Description:
In NetBackup 6.x, a backup taken using backint.exe would contain a
non-unique "keyword". If you depended on this "keyword" value to run
scripts, such as a verify script or a restore script, then those scripts
would not run correctly. A change has been made to ensure a unique
"keyword" is generated so user scripts will not fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1142467

Description:
When running disaster recovery using BRRECOVER, if the init<DBSID>.sap
file was not present, BRRECOVER would call BACKINT without the
-p init<DBSID>.utl parameter.

If NetBackup for SAP is called without the util file parameter, it checks
for the SAP_RECOVERY environment variable. If the environment variable is
set to "disaster", the restore is allowed without util file parameter. In
this case NetBackup for SAP does the restore using the default SAP policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1210594
Associated Primary Etrack = ET1202943
Titan cases: 281-258-932

Description:
6.x Media server (bpbrm) would skip encryption for a 5.x SAP agent.

--------------------------------------------------------------------------------



Maintenance Pack History
------------------------

This section contains an accumulative list of all maintenance pack information
contained in previous releases.


=============
NB_SAP_60_6_M
=============
Etrack Incident = ET642819
Titan cases: 290-596-813

Description:
Added NFS-mounted file system backup support to the SAP agent.
--------------------------------------------------------------------------------
Etrack Incident = ET637916
Titan cases: 240-182-267

Description:
Added LOFS-mounted file system backup support to the SAP agent.
--------------------------------------------------------------------------------
Etrack Incident = ET1082843
Associated Primary Etrack = ET1075693
Titan cases: 320-055-552

Description:
Added additional status information to the SAP BRTOOLS log.
--------------------------------------------------------------------------------




=============
NB_SAP_60_5_M
=============
--------------------------------------------------------------------------------
Etrack Incident = ET596559

Description:
If an SAP backup is initiated without a definition for "policy" in the
init<SID>.utl file, then the backup fails with the following error messages
in the backint log:

9:52:22.021 [3632.3884] <4> do_file_backup: VxBSACreateObject - SUCCESS
09:52:22.021 [3632.3884] <16> VxBSAGetPolicyInfo: ERR - policy_name is null
09:52:22.021 [3632.3884] <4> do_file_backup: A NULL pointer was encountered
in a required argument.
09:52:22.021 [3632.3884] <4> do_backup: Exit with status: <2>.

Workaround:
To resolve this issue, add a definition for Policy in the parameters
file(init<SID>.utl).
--------------------------------------------------------------------------------
Etrack Incident = ET862912

Description:
Support for -fillup/-f option of BRBACKUP & BRRESTORE tools was added to
the NetBackup SAP Agent with this feature. If the backup/restore job
terminates and you do not want to repeat the complete backup/restore
again, the -f/-fillup option of BRBACKUP/BRRESTORE can be used now to
backup/restore only those files that were not saved and/or restored
earlier.

To use this feature for backups, configure 'Take checkpoints every _'
option for the SAP policy to a time period (range: 5-180 minutes).
Checkpoints are taken periodically after this time period. If the
backup job fails after taking a checkpoint, the partial image is
created until that checkpoint is retained. The SAP Agent gives
BackupIDs for files that are saved in this partial image.
Brbackup -f/-fillup option can be used to backup the remaining files.

The commands for backup are:
brbackup -d util_file -m all -c -f <brbackup_failed_job_log_name>
or
brbackup -d util_file -m all -c -f last

For restores, this feature is enabled automatically. If the restore job
fails after successfully restoring a few files, the SAP Agent reports
success for those files and reports an error for the remaining files.
BRRESTORE with -f/fillup option can be used to start a restore of the
remaining files.

The commands for restore are:
brrestore -d util_file -b <brbackup_log_name or last> -m all -c -f
<brbackup_failed_job_log_name>
or
brrestore -d util_file -b <brbackup_log_name or last> -m all -c -f last
--------------------------------------------------------------------------------
Etrack Incident = ET995557
Associated Primary Etrack = ET992997
Titan cases: 280-994-289

Description:
From the NetBackup 6.0GA release and onwards, the "exclude_list" becomes
active in SAP Backups. This issue affects UNIX only.

Workaround:
To avoid this issue do at least one of the following:
- Create the Policy Specific Exclude Lists as: exclude_list.<policyname>
- Create a SAP-specific exclude list that is empty
- Temporarily remove the exclude lists
--------------------------------------------------------------------------------
Etrack Incident = ET1012795 ET1003554
Titan cases: 280-903-224

Description:
Multiplexed SAP backups that use (Standard) AES-128 Encryption would fail
with the error, "ERR - backup failed:49 <client did not start>".
--------------------------------------------------------------------------------
Etrack Incident = ET1002794
Associated Primary Etrack = ET1004537
Titan cases: 240459567

Description:
A change has been made to provide support for overriding the schedule that
is specified in the utl file for an SAP standard backup.


Additional Notes:
This change includes two environment variables, SAP_SCHED and
SAP_SNC_SCHED.

SAPSCHED: Use this variable for standard backups. If a user wants to
override the schedule that is specified in the utl file, he/she must
to specify SAP_SCHED. This will be the Application backup schedule.
In addition, it will also be used for future enhancements of an
advanced backup. [Currently, the behavior of SAP_SCHED is same as
NetBackup 6.0GA and earlier].

SAP_SNC_SCHED: For advanced backups you must specify the SAP_SNC_SCHED.
This will be the Automatic schedule [Automatic Full, Automatic
Differential Incremental, or Automatic Cumulative Incremental backup
type].

For detailed information on how to use the SAP_SNC_SCHED variable,
refer to the following Tech-Note on the Symantec Support web site.
http://entsupport.symantec.com/docs/282337
--------------------------------------------------------------------------------
Etrack Incident = ET1041952
Associated Primary Etrack = ET992544
Titan cases: 290-427-226

Description:
Changes were made to address a backint/bprm/bpkar/brbackup handshake
failure that would occur at end of a backup. An explanation of the
problem follows.

A backup may sit in the scheduler queue for more than 25 hours. Then
over the next two hours it performs a successful backup of the data
files. The backup of each file involves a quiesce, backup, and
unquiesce. This sequence is successful for the datafiles. The quiesce
and backup of the control file is also successful.

- bpbkar shows a successful data transfer and request to take the
control file out of backup mode.
- bpbkar shows the completion of the job including client and
server status 0.
- bptm shows successful completion.
- bpbrm shows successful completion.

However, backint appears to have not yet received the #END or
UNQUIESCE for the control file. Hence when bpbrm.child exits, the
sockets to backint are removed and backint reports the loss.
--------------------------------------------------------------------------------
Etrack Incident = ET1079265
Associated Primary Etrack = ET1075693
Titan cases: 320-055-552

**Description:
There were situations where the SAP data files to be backed up
were skipped during the backup. The backup status was still
reported as being successful (status 0) in NetBackup and as being
saved in the brbackup detail log. This backup set would not be
usable in an SAP/Oracle DR situation.

A message similar to the following may appear in the bpbrm log:
<4> bpbrm main: from client xyz: TRV - object not found for
file system backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1081508
Associated Primary Etrack = ET1075693
Titan cases: 320-055-552

**Description:
A fix was added that resolves an issue where SAP backups may
report success even though some of the data files being backed
up were skipped.
--------------------------------------------------------------------------------




=============
NB_SAP_60_4_M
=============
Etrack Incident = ET637921

Description:
A change was added to ensure restores from legacy images do not fail
on Windows clients.
--------------------------------------------------------------------------------
Etrack Incident = ET784650

Description:
NetBackup communication between components that were separated by a
firewall did not work. For instance, when a master server was behind the
firewall and a media server was outside the firewall, all communication
from the master server had an internal host address that was not accessible
from outside systems.

This is the same when clients and other services are in question.

Additional Notes:
To activate NAT address replacement, systems outside of the firewall should
have the FIREWALL_IN parameter specified in their bp.conf/registry.

Format: FIREWALL_IN=hostname1,nat_address1|hostname2,nat_address2|...

Where: <hostname> is the name of the host system that needs to be accessed
and <nat_address> is the actual NAT address for the firewall to do
forwarding.




=============
NB_SAP_60_2_M
=============

Etrack Incident = ET426647

Description:
The SAP Agent now supports Split-Mirror Backups through the NetBackup
Advanced Client and is available in this NetBackup 6.0 MP2 release.

The following list identifies the key Advanced Client features that are
now supported as well as the benefits that SAP customers will recieve:

- Off-host Backup - Backup overhead moves critical systems to an
Alternate Data mover

- Block-Level Incremental Backup and Recovery - Less data leads to
high-performance data protection.

This feature is supported in: Solaris, HP-UX PA Risc, AIX5 and
Windows 2000/2003 platforms. Refer to the compatibility support matrix
for applicable methods in the above platforms.

For more detailed information about this new feature, refer to the
following TechNote on the Symantec Support web site.

http://entsupport.symantec.com/docs/282337
================================================================================


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)