============================================ I. NEW FEATURES AND PLATFORM PROLIFERATIONS ============================================ The following items describe the new enhancements contains in this Hotfix.

For information about new 6.5.3 features and proliferations in, refer to the NetBackup 6.5.3 online Release Update Readme and the NetBackup 6.5.3 Documentation Update document on the Symantec Support Web site.

+ This release contains enhancements that enable NetBackup to make more knowledgeable schedule selections to meet daily backup frequency requirements. This intelligence helps to avoid backups that run soon after midnight if the same backup ran just before midnight. In policies with a daily frequency, NetBackup looks at the schedules in the day ahead to see if another schedule is available and determines whether it should run the backup during the later schedule.

For more information about this enhancement, refer to the following TechNote on the Symantec Support Web site.

================== II. KNOWN ISSUES ================== + (ET1514170) A schedule that is configured to open and close during the Daylight Savings Time (DST) changeover hour in the Spring of the year may not run. If you have any schedules configured to run during this window, Symantec recommends that you adjust the window of these schedules to a time that is outside of the DST changeover hour.

For more information about this issue, refer to the following TechNote on the Symantec Support Web site.

+ (ET1514238) While launching the NetBackup-Java Administration Console (using the jnbSA script) or the NetBackup-Java BAR user interface (using the jbpSA script) on a Linux IA 64-bit platform, you may encounter the following error message.

This error message occurs if you have not installed the Symantec Authentication Service (AT). You can ignore the error message and continue to work in the NetBackup console.

+ (ET1516790) An issue exists that can cause the NetBackup-Java Administration Console to display the time in the Tasks Performed window to be one off one hour from the actual time, based on a previous daylight savings time (DST) date.

To avoid this problem, Symantec recommends that you manually enter the correct settings in to the Adjust Application Timezone dialog, and save this as the default. This change is saved and then used on subsequent program operations to enable the NetBackup-Java Administration Console to use the correct default timezone.

To change the timezone, use the following steps as a guide. 1. With the NetBackup-Java Administration Console open, select File > Adjust application timezone.

2. From the Standard tab in the Adjust time window, do the following: a. Verify that your timezone appears as the timezone being used. b. Click the "Use custom timezone" check box.

3. Select the Custom tab. This tabbed page shows the timezone, current start and end times for daylight savings time (DST). Do the following to change the start and end dates appropriately for your timezone. a. Verify that your timezone appears in the Base Timezone On drop-down menu. c. Adjust the DST Start date and time as necessary for your region. d. Adjust the DST End date and time as necessary for your region. e. Click OK. Your times will adjust and the administration console will now show the correct time.

========================== III. DOWNLOAD INSTRUCTIONS ========================== This is an update to NetBackup/Media Manager products with the latest fixes for Windows NT NetBackup servers.

- When installing and uninstalling this pack, the instructions contained in the Online Readme always supersede the instructions contained in the installed version.

- Click on the "Download Now" link, near the bottom of this document prior to running the following installation procedure for this pack.

- Symantec recommends that you perform a catalog backup before and after you apply this Release Update.

- If you are planning to install this Hotfix as a part of an upgrade from a 6.0 MPx release, you must first install NetBackup 6.5 GA and NetBackup 6.5.3 before you install this Hotfix.

- NetBackup Master Server is not supported on Windows 2008.

- If you have BMR Boot server you should take down those processes before performing the install/uninstall.

- If you are planning to install this Hotfix as a part of an upgrade from a 5.x release then it is important that you understand that the existing NetBackup databases must be in a consistent state prior to beginning the upgrade. Information and tools to assist you in determining the current state of your database, as well as instructions to help you address any inconsistencies that you might discover can be viewed on the NetBackup Upgrade Portal, a part of the Symantec NetBackup Support Web site.

Install this Hotfix in a Windows CLUSTER Environment: ----------------------------------------------------- 1) Install this Hotfix locally on the nodes of the cluster where the NetBackup group is inactive. (follow steps 1-4 below)

NOTE: When installing on a VCS cluster, complete the installation of this pack on a single node before you begin installing on another node.

2) Install this Hotfix locally on the active node. This should be done when the NetBackup system is quiet, for example, no backups or restores running.

CAUTION: Do not failover the NetBackup Group until all NetBackup nodes (including the active NetBackup node) have the Hotfix installed.

1) Close all NetBackup Windows. Make sure the NetBackup system has no active backups, restores, duplications, etc., running. If there are NetBackup activities in process, the Hotfix will require a reboot 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 using the ControlPanel -> Services tool. Repeat this 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 Hotfix installation. Next, it will install the necessary files into their correct locations. Lastly, Setup.exe will restart the appropriate NetBackup services.

3) Examine the install log located under the user profile that completed the install. The following is an example of the user administrator that completed the install. This path may be hidden and you may need to unhide hidden or system files to view the log.

Search the install log for the following string to determine if an error has occurred. "Return Value 3".

4) Remove the temporary directory created in the download instructions.

NOTE: After installing NetBackup 6.5.3 on a Windows x86 system with a BMR Boot Server, start the BMR Boot Server Service manually.

NOTE: If you are installing the Hotfix using the silent install script, please review the <TEMP>.Log after the installation is finished, a reboot maybe required to complete the installation of the Hotfix. A search of the log for the key words "in use" will indicate which files were busy during the installation.

Symantec recommends that you perform a catalog backup after you have applied this Release Update.

The following procedure is only for users who want to install NetBackup 6.5.3.1 client on a Windows Vista system:

NOTE: Remote installations are not supported for Vista on Windows 32- and 64-bit Systems.

To install NetBackup 6.5.3.1 client on a Vista system: 1. Install NetBackup 6.5 GA from a CD. You must use the custom install option and choose to NOT to install VSP. 2. Install the NetBackup 6.5.3 Release Update. 3. Install the NetBackup 6.5.3.1 Hotfix. 4. If you are given a list of client platforms from which to select, select the Windows 2003 with the chipset, either x86 or x64, that matches your system.

NOTE: After installing NetBackup on a Windows Vista client platform and starting the Backup, Restore and Archive user interface, you may receive a dialog warning you that the user interface is not compatible with Vista. You can disregard the warning and proceed with using the user interface.

To add a Windows Vista client to a policy: 1. Create a Windows policy or use an existing Windows policy. 2. If you are given a list of client platforms from which to select, select the Windows 2003 with the chipset, either x86 or x64, that matches your system.

To use Open File Backup:

1. VSP is not supported on Vista. If Open File Backup is enabled for a Vista client (this is the default), VSS will always be used to create the snapshot.

NOTE: When uninstalling on a VCS cluster, complete the uninstall of this pack on a single node before you begin uninstalling on another node.

1) Uninstall this Hotfix from the nodes of the cluster where the NetBackup group is inactive. (follow steps 1-2 below)

2) Uninstall this Hotfix from the active NetBackup node. This should be done when the NetBackup system is quiet, for example, no backups or restores running.

CAUTION: Do not failover the NetBackup Group until all NetBackup nodes (including the active NetBackup node) have the Hotfix uninstalled.

**Important notice regarding un-installs on Windows** Only the last update installed on a Windows system can be un-installed.

1) Close all NetBackup Windows. Make sure the NetBackup server has no active backups, restores, duplications, etc., running. If there are NetBackup activities in process, the Hotfix 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 via the Control Panel -> Services tool. Repeat this until all databases have been stopped. These services must be restarted once the patch is successfully uninstalled.

2) Go to Add/Remove programs dialog box and select the correct update to be uninstalled.

=================== VII. HOTFIX CONTENT =================== This section contains the conventions, content, and historical content that are 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 Hotfix subsection describes a feature, enhancement, or issue fixed with this Hotfix.

Description Describes a particular problem contained in this Hotfix.

** 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.

Description: A change was made to address an issue that caused the NDMP dmplevel to not be reset properly after a full backup was run. -------------------------------------------------------------------------------- Etrack Incident = ET1443700 Associated Primary Etrack = ET1391305 Titan cases: 220-374-967 320-135-491

**Description: Calendar incremental backups would not run on the same day as calendar full backups. -------------------------------------------------------------------------------- Etrack Incident = ET1476457 Associated Primary Etrack = ET1409915 Titan cases: 240-820-679

Description: MS SQL backups would run twice when an automatic backup was started.

Additional Notes: This issue would occur when immediate backups were submitted and the policy name was spelled with an incorrect case from the bpbackup command. Symantec recommends that you use care when specifying the policy name. -------------------------------------------------------------------------------- Etrack Incident = ET1476459 Associated Primary Etrack = ET1445633 Titan cases: 312-046-169 281-453-350 291-104-679

Description: A change has been added to address an issue that would allow jobs to run continuously while the time changed because of daylight savings time. -------------------------------------------------------------------------------- Etrack Incident = ET1476454 Associated Primary Etrack = ET1386189 Titan cases: 320-127-126 220-416-368 230-596-851

Description: A problem existed that caused nbpem to core dump when there was a heavy load on the master server and nbpem failed to open or read the bprd comm file for immediate or user backups. -------------------------------------------------------------------------------- Etrack Incident = ET1476436 Associated Primary Etrack = ET1443574 Titan cases: 220-457-153

Description: A change has been made to address a core dump issue found with nbpem that would occur when a user attempted to restart a user-initiated backup that had failed. -------------------------------------------------------------------------------- Etrack Incident = ET1480329

Description: A logic error had been identified and corrected in daemons that run on Veritas NetBackup master, media, and client servers. Successful access to and manipulation of this logic error could potentially lead to arbitrary command execution with elevated privileges on a vulnerable system.

For more information about this issue, refer to the following TechNote on the Symantec Support Web site.

Description: Additional corrections have been added to this release that ensure the proper handling of daylight savings time. For additional information on the issues that this fix resolves, refer to the following TechAlert on the Symantec Support Web site.

Description: A calendar schedule that crosses multiple days would stop scheduling completely after running on the last full day when only one window was open for the week. -------------------------------------------------------------------------------- Etrack Incident = ET1487540

Description: A change has been made to address an erroneous statement that appeared in the NetBackup Administration Console for Windows after NetBackup 6.5.3 was installed. -------------------------------------------------------------------------------- Etrack Incident = ET1507022

Description: The nbemmcmd command did not allow for the server to be added with a triple-dot version (6.x.x.x) and did not display the version correctly. A change has been made to the command and the version is now correctly displayed. --------------------------------------------------------------------------------

Release Update History ----------------------

For a complete accumulative list of all 6.5.x Release Update information contained in previous releases refer to the NetBackup 6.5.3 online Readme.

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

Related Articles

Article Languages

Translated Content

Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.

Attachment

Products

Subscribe to Article

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?