Overview

 An improper PTT configuration can result in a variety of problems:

•     Drives not presented in NDMP
• Error occurs indicating that DXi is not an NDMP host (CT: Where do we find the error message  in the DXi or NBU logs?) When we document this, make sure to note that this is a known issue with NBU.
• Known NBU issue using IP addresses higher than 128.xxx
• Slow performance when duplicating to physical tape
•     Drive stability
•     PTT can't access tape drives 

This section provides examples of the following:

• Incorrectly and correctly configured PTT devices in NBU
• An example of the DXi configuration
• Actions required to initiate a duplication in NBU to verify the configuration.  

To configure PTT correctly use the appropriate Application Specific Configuration Guides found on CSWeb:

 

• Quantum DXi Symantec NetBackup Application Specific Configuration Guide
• EMC NetWorker Backup Application Specific Configuration Guide
• Atempo Time Navigvator Application Specific Configuration Guide
• Symantec Backup Exec Application Specific Configuration Guide

 

Note: The DXi Users Guide and Field Service Manual both document a recommendation to add a "fake" host with a  WWPN that does not exist in the Customer SAN.  The documentation will be corrected in the future to remove the recommendation to configure a "fake" host. 

 

The DXi Users Guides and Field Service Manuals reference "drives dedicated to application specific path to tape." This information suggests the physical drives cannot be shared in an NBU SSO environment.  While this information is also incorrect, sharing the PTT physical tape drives can be a bit complex when configuring the drives to NBU and the DXi. 

 

 LC: verify with Greg the correct process to configure drive for SSO/PTT

 

Devices that are Correctly Configured for PTT

When devices are correctly configured for PTT, each VTL drive will have a local SCSI path and an NDMP path.  The screenshot below shows correctly configured PTT devices, drive 000 is highlighted in the top pane of the Device Monitor, the bottom pane shows drive 000 configured with SCSI and NDMP paths.  The NDMP path is required for communication of the NDMP control session information this information triggers the transfer of data from the VTL media to the physical tape media. 

 

 

NBU screenshot of a properly configured PTT device 

 

LC Let's highlight the bottom devices in this screenshot to draw their attention

LC Do we want to note the non-shared configuration in the top half of the screenshot

LC We should add configuration details for SSO using the information learned in SR  1272594

LC Add an example of incorreclty configured PTT devices

LC Add examples of the DXi configuration

 

Example screen that shows correctly configured PTT devices

 

Once the Backup Application Specific configuration is complete, each VTL drive will have a SCSI path and an NDMP path and both drives should be in an up state. This state is indicated by the green up-arrow next to the paths as shown in the screenshot above.

 

 

Once PTT is configured using the NetBackup Application Specific Guide a duplication job should be initiated to verify the configuration.  There are multiple ways to initiate a duplication within NBU, Storage Lifecycle Policy, SLP, manual initiation using the NBU catalog, or use of the Vault Policies.  When using SLPs to initiate a duplication there will be a 30 minute delay between the successful completion of the backup and the start of the duplication.  To avoid the delay a duplication can be manually initiated using the following steps.

    Using the NBU catalog locate a successful backup

    Right click on the backup and select duplication

 

Once a duplication jog is started on the media server an NDMP control session is established by the media server to the DXi.  NBU uses the control session to communicate the commands to the DXi to move data from virtual media to physical media using the FC path configured from the DXi to the physical tape library.

 

NBU will automatically attempt to use Direct Copy, the NDMP control sesssion,  to communicate to the DXi.  You will find messages in the DXi and NBU logs indicating Direct Copy is being used for the duplication activity, if the devices are not correctly configured the messages will indicate Directo Copy errors and NBU will use the alternate path moving data over the ethernet connection between the DXi and the NBU host. 

 

A quick tutorial will be added here sometime this week 4/25 - 4/29 

 

 

 

 

Highlight the need for NDMP path and SCSI path

---

Known NBU issue using IP addresses higher than 128.xxx

An NBU bug causes an error when using a valid IP address of the DXi. While the IP address is valid NBU mangles the address used for the Data connect session. The IP address that NetBackup was attempting to use in the case where this was discovered was 127.255.255.255, which was found in the ndmp debug logs on both the DXi system and NBU.
 

 

 

 

 

 

---

 

What's Next?

Operational Issues >