The original Software Alert for this issue was sent out on September 7, 2005, and was delivered originally for 5.0 MP5 and 5.1 MP3 (including MP3A).  The information in this TechNote has been updated (as of 9/20/2005) and this issue is known to affect the following versions of NetBackup Master & Media Servers:

Windows Operating Systems:
NetBackup Server 5.0 Maintenance Pack 5 (MP5)
NetBackup Server 5.1 Maintenance Pack 3 (MP3) and 5.1 MP3A
NetBackup Enterprise Server 5.0 Maintenance Pack 5 (MP5)
NetBackup Enterprise Server 5.1 Maintenance Pack 3 (MP3) and 5.1 MP3A


UNIX Operating Systems:
NetBackup Server 5.0 and all Maintenance Pack levels.
NetBackup Server 5.1 and all Maintenance Pack levels.
NetBackup Enterprise Server 5.0 and 5.0 MP1 through 5.0 MP5
NetBackup Enterprise Server 5.1 and 5.1 MP1 through 5.1 MP3A.

If a Disk Staging Storage Unit (DSSU) is configured on the Media Server(s) with a space in the "Absolute pathname to directory", images created on that DSSU will not relocate to the Final Destination Storage Unit.  

Reference: NetBackup System Administrator's Guide for Windows or UNIX, Volume I

Disk Staging is conducted in two separate operations:
Stage I: A backup creates an image on the disk staging storage unit.
Stage II: A relocation schedule determines when the image from the disk staging storage unit should be relocated to the destination storage unit.

Note: Stage II will fail if the DSSU contains a space in the "Absolute pathname to directory".  The failure can occur during both scheduled and manual relocation.

Caution: There is a rare chance of data loss, in the case where the original backup image created on the DSSU is manually expired and no other copies of the image exist, due to the relocation not occurring.

What is not Affected?
1. Manual duplications are not affected by this issue.
2. The original backup copy written to the DSSU is not affected.
3. Clients are not affected by this issue.

How to Determine if Affected
The DSSU relocation job will exit with Status Code 0 (successful); however, the image copy to the final storage unit does not exist and is not available in any reports or command queries.  A relocation job is an automatic policy beginning with "__DSSU_POLICY_" and ending with the name of the Storage Unit.

Example relocation job name: __DSSU_POLICY_Name_Of_Storage_Unit

To verify if the relocation image copy exists:

1. Open a NetBackup Windows or Java Administration console.

2. Expand NetBackup Management and then Reports in the left pane.

3. Click the Images on Media report.

4. Specify the Client name and <All Media>, then run the report.

5. Observe within the results if any image copies are missing by noting the "Copy Number" column.

Additionally, as a result of disk images not being relocated, these images will not be cleaned from the DSSU volume. This can result in a disk full condition on the volume that the DSSU is writing to.

Note: Backups written to a DSSU when the volume is full results in an Exit Status 84:  media write error.

Please follow a recommended workaround, or apply the fix when available, so that image relocation and cleaning continues as expected.

Workarounds:
Symantec strongly recommends implementing one of the three following workarounds.  Please note:  The third workaround listed is for Windows only and should only be performed as a last resort.  

1.  Duplicate images to a new DSSU:

a.  Create a new DSSU(s) that do not contain a space.  

b.  Reconfigure policies and discontinue use of any DSSU(s) with a space configured in the path.

c.  Manually duplicate/move images from the former DSSU (that contained the space) to the new DSSU.  Note:  This is a critical step to prevent data loss.  If these images are not manually duplicated/moved prior to expiration, there is a potential for data loss.

2.  Duplicate images to another Storage Unit:

a.  Reconfigure policies to discontinue use of any DSSU(s) with a space configured in the path.

b.  Manually duplicate images from the former DSSU to another Tape or Disk Storage Unit.

3.  Windows Only:  Uninstall the affected Maintenance Pack, as this issue has not been reported at previous patch levels.   Uninstall of the Maintenance Pack should occur in the following order:

- Media Servers

- Clients that are backed up by affected Media Servers.

- Master Server (If the Master is being used as a Media Server and is therefore affected).

Please refer to the readme for the respective Maintenance Pack for specific instructions on uninstalling.  These are viewable from the patch downloads found below, in the "Related Documents" section.  Additionally, the Master Server should always be at the same patch level, or higher, than any Media Servers.


Formal Resolution
This issue is formally resolved in the following NetBackup Enterprise Server/Server Maintenance Packs, currently scheduled for release Q4 of 2005:

NetBackup Enterprise Server/Server 5.0 Maintenance Pack 6 (MP6)

NetBackup Enterprise Server/Server 5.1 Maintenance Pack 4 (MP4)

The patches mentioned above can be found on the following Support site:    http://www.support.veritas.com/menu_ddProduct_NBUESVR_view_DOWNLOAD.htm

Symantec strongly recommends the following best practices:

1.  Always perform a FULL backup prior to and after any changes to your environment.
2.  Always make sure that the environment is running the latest version and patch level.

If you have any questions or concerns about this issue, please contact Symantec Enterprise Technical Support.


If you have not received this TechNote from the Symantec Email Notification Service for Software Alerts, please subscribe at the following link:
 http://maillist.support.veritas.com/subscribe.asp