Veritas NetBackup™ Appliance Release Notes
- About NetBackup Appliance 3.0
- NetBackup Appliance 3.0 features, enhancements, and changes
- NetBackup Appliance Hardware features
- NetBackup Appliance compatibility
- Operational notes
- About NetBackup support utilities
- Appendix A. Release content
- Appendix B. Related documents
New Operational Notes for NetBackup Appliance 3.0
Note:
If you are familiar with the Operational Notes for the previous release, review this section to see only the newly documented content for this release. You should also check the Release content appendix of this document to see the issues that have been resolved for this release.
Note:
The notes and the known issues that are documented in this section may also apply to previous releases.
The following list contains the notes and the known issues that are newly documented for this release:
The Monitor > SDCS > Audit View EventType <code> command does not accept the following event type codes, so you cannot audit the related SDCS logs from the NetBackup Appliance Shell Menu. However, you can use the page from the NetBackup Appliance Web Console to audit those logs.
PBOP
IPS Overflow
PCRE
IPS Create
PDES
IPS Destroy
PFIL
IPS File
PMNT
IPS Mount
PNET
IPS Network
POSC
IPS System Call
PPST
IPS PSET
PREG
IPS Registry
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).
Only a QLogic Small Form-Factor Pluggable (SFP+) module is supported in the 10Gb Ethernet/iSCSI card. This applies to configuration H of the NetBackup 5240 appliance.
A VLAN can be configured on either the network interface or the iSCSI interface. If VLAN is configured on both the network and iSCSI interface, 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.
Network Interface
iSCSI Interface
Description
IP
VLAN
IP
VLAN
Subnet X
None
Subnet X
None
Supported
Subnet X
None
Subnet Y
VLAN A
Supported
Subnet X
VLAN B
Subnet X
VLAN B
Supported
Subnet X
VLAN B
Subnet Y
VLAN B
Not Supported
If you run the iSCSI> Target Discover Portal or 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 like first run theiSCSI> Target Discover iSNS command for iscsi1 and then iscsi2, only the recent record is displayed by theiSCSI> Target Show All command. For example the column in the Target Show All command may not show both the interfaces (iscsi1, iscsi2) for some targets. It 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.
The Intel hardware process that monitors appliance components may fail when attempting to collect inventory. Inventory is collected every 24 hours. If an inventory failure occurs, the DIMM type component information that appears in the NetBackup Appliance Shell Menuis incorrect. For example, the Monitor > Hardware ShowHealth Appliance or Monitor > Hardware ShowHealth Appliance DIMM commands would show the following DIMM component status:
This condition exists until the next inventory collection occurs 24 hours later.
Each inventory failure generates a core file in
/log/crash/
with a file name format ofcore.intelHw.<PID>
, wherePID
is the process identifier of the failed process.Any SNMP alerts that are generated when this issue occurs are missed until the next inventory. This issue does not affect Email alerts.
This issue is intermittent and may not occur at all in some cases.
To work around this issue, you can initiate an inventory collection manually by restarting the as-collector service from the Support menu. To restart this service, enter the following command:
Support > Service Restart as-collector
When the inventory collection has completed, the shell menu should show the correct DIMM status. The inventory collection typically takes about one to five minutes to complete, although some system configurations may take up to an hour.
During system startup, some VCS-related error messages may occur and store in the LOGROOT/>OS>messages log file. You can use the Main > Support > Logs > Browse command to check the log file. Any messages that begin with VCS ERROR are irrelevant to the appliance software version 3.0 and you can safely ignore them. The following is an example message that may appear in the log file:
VCS ERROR V-16-1-11032 Registration failed.
The Copyright symbol on the About page of the NetBackup Appliance Web Console may appear as unreadable characters. The statement on this page should appear as the following:
Copyright © 2016 Veritas Technologies LLC. All rights reserved.
If you resize an AdvancedDisk partition on the appliance, a scenario can occur in which the new space is not added to the NetBackup disk pool. A warning similar to the following appears:
Use of uninitialized value $newMountPoints[0] in join or string at /opt/NBUAppliance/scripts/nbapp_nbstorage.pm line 1752
In this scenario, the Main > Manage > Storage > Show command displays the new partition size, but the disk pool in NetBackup does not. If you encounter this issue, run the resize operation again with the same set of parameters to ensure that NetBackup receives the correct information.