Veritas NetBackup™ Appliance Release Notes

If your NetBackup 5330 Appliance includes a Primary Storage Shelf and an Expansion Storage Shelf, and the expansion shelf has configured RAID volumes on it, it should not be removed from the appliance setup. If the expansion shelf is removed, the primary shelf behaves as if the expansion shelf has lost power, and it produces errors. If you need to remove the expansion shelf, you need to run the Support > RAID Clear command before you can remove the expansion shelf from the setup.

If you install a new version of NetBackup Appliance on a previously used appliance, you may receive the following error message during the appliance configuration:

Cannot recover the existing MSDP partition because the NetBackup 
disk pool and storage unit could not be determined. … 
- [Error] Could not configure the appliance.

This error occurs when a preexisting Media Server Deduplication Pool (MSDP) disk pool has a + in the disk pool name. If you encounter this issue, you need to change the disk pool name so that it does not include a + and manually configure the MSDP partition. Use the Manage > Storage > Resize command to configure the partition.

When you attempt to copy a software update to the share directory, do not initiate any other commands until the copy finishes. If you run a command during the copy process, you may see that the software update is listed and available. However, if you install that software update, it can fail.

If you receive an email stating "No license exists" during the initial configuration of a media server, you can safely disregard the email. The email is sent during host name configuration. The license key file is renamed when it is modified with the new host name, and the alert mechanism cannot locate the license temporarily. When the configuration completes, the license is set correctly. You can check the license key on the Manage > License page of the NetBackup Appliance Web Console or with the Main > Manage > License > List command in the NetBackup Appliance Shell Menu.

iSCSI supports IPv4 addresses only. iSCSI connections over IPv6 are not supported. In addition, the initiator and the target must be on the same Layer 2 network (L2).

A VLAN can be configured on either the network interface or the iSCSI interface. If a VLAN is configured on both the network and iSCSI interfaces, the VLAN for the network interface is effective on both the interfaces. Note that when VLAN is configured on both the network and iSCSI interface on different subnets, the configuration is not supported.

If you run the iSCSI> Target Discover Portal or the iSCSI> Target Discover iSNS command again after the targets are connected, it overrides the existing connection settings like target credentials. If the target requires authentication, you need to enter the target credentials again when the existing sessions are reconnected. The existing sessions need to be reconnected if the appliance restarts or when you change the IQN for the appliance or when the iSCSI processes are restarted etc.

When targets are discovered by using iSNS on two iSCSI interfaces, only the recent record is displayed by the Target Show All command. For example if you run the Target Discover iSNS command for iscsi1 and then iscsi2, the Interfaces column in the Target Show All command output may not show both of the interfaces (iscsi1, iscsi2) for some targets. It actually shows the interface from the most recent command (iscsi2 in this case) for some targets.

The iSCSI> Target Disconnect command takes more time to complete if workloads are running on the iSCSI interface.

You may see the following messages appear on the NetBackup Appliance Shell Menu:

Message from syslogd@host at Sep 12 10:09:14 ...
iscsid:
Message from syslogd@host at Sep 12 10:13:27 ...
iscsid:
Message from syslogd@host at Sep 12 10:17:53 ...
iscsid:

These messages may appear at different times on the NetBackup Appliance Shell Menu. They may appear when you are running an iSCSI command, in the middle of a command output, or even when the console is idle. These messages are harmless and should be ignored.

When CHAP authentication is enabled on a target device and targets are discovered by using iSNS, the iSCSI > Target Discover command may not prompt for target credentials.