NetBackup Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Flex Appliance 6.0 new features, enhancements, and changes
- Flex Appliance 6.1 new features, enhancements, and changes
- Flex Appliance 6.2 new features, enhancements, and changes
- Flex Appliance 6.3 new features, enhancements, and changes
- Supported update paths to this release
- Operational notes
- Flex Appliance 6.0 release content
- Flex Appliance 6.1 release content
- Flex Appliance 6.2 release content
- Flex Appliance 6.3 release content
- Getting started
- Managing network settings for instances
- Managing users
- Overview of the Flex Appliance default users
- Managing Flex Appliance Console users and tenants
- Adding a tenant
- Editing a tenant
- Removing a tenant
- Adding a local user to the Flex Appliance Console
- Connecting a remote user domain to the Flex Appliance Console
- Editing a remote user domain in the Flex Appliance Console
- Importing a remote user or user group to the Flex Appliance Console
- Managing single sign-on (SSO)
- Managing identity providers (IDPs)
- Importing a single sign-on user or user group to the Flex Appliance Console
- Managing user authentication with smart cards or digital certificates
- Changing a local user password in the Flex Appliance Console
- Expiring local user passwords in the Flex Appliance Console
- Unlocking a user account in the Flex Appliance Console
- Managing open sessions
- Removing user or service accounts from the Flex Appliance Console
- Changing the password policy
- Changing the hostadmin user password in the Flex Appliance Shell
- Changing the sysadmin user password in the Veritas Remote Management Interface
- Managing multifactor authentication
- Using Flex Appliance Console accounts for API automation
- Using Flex Appliance
- Managing the repository
- Creating application instances
- Managing application instances from Flex Appliance and NetBackup
- Managing application instances from Flex Appliance
- Upgrading application instances
- Updating an application instance to a newer revision
- About Flex Appliance updates
- Changing the BIOS password
- Locating the node serial number
- Remote replication
- About remote replication
- Pairing appliances for remote replication
- Creating a replica
- Managing remote replication
- Remote replication best practices
- Monitoring remote replication
- Editing the replication network
- Repairing a lost connection between paired appliances
- Pausing and resuming replication
- Resolving discrepancies between an active and a replica instance
- Changing the replication role of an instance
- Unlinking active and replica instances
- Forgetting a paired appliance
- Appliance security
- Monitoring the appliance
- Registering an appliance
- Configuring alerts
- Viewing performance metrics
- Monitoring the appliance from the System Health Insights portal
- Viewing the hardware status
- Viewing hardware faults
- Viewing system data
- Clearing the hardware status
- Forwarding logs
- Providing access for external monitoring
- Revoking access for external monitoring
- Reconfiguring the appliance
- Reconfiguring the appliance network
- Changing DNS or Hosts file settings
- Shutting down the appliance
- Performing a factory reset
- Performing a reimage
- Recovering storage data after a factory reset or a reimage
- Performing a storage reset
- Removing a node
- Viewing or resetting the storage shelf order on a 52xx appliance
- Troubleshooting guidelines
Operational notes
This topic explains important aspects of Flex Appliance 6.x operations that may not be documented elsewhere in the documentation.
The following list contains the notes and the known issues that apply for the Flex Appliance 6.x software:
If you configure remote replication with a network interface that has a name that is longer than 13 characters including the VLAN ID, the configuration fails with the following message:
Failed to create high availability replication link.
To avoid this issue, make sure that the interface that you select has a name that is 13 characters or less including the VLAN ID.
When the appliance turns on, you may receive the following false alerts if the services take longer than usual to start:
V-475-130-30007: The metrics-node service is not in an optimal state.
V-475-130-30009: The metrics-storage service is not in an optimal state.
If you have not received a second alert after four hours, you can safely ignore these alerts.
If you have more than 10 VLAN tags configured with an IPv6 network, instances may not start cleanly. To avoid this issue, do not configure more than 10 VLAN tags with an IPv6 network.
Flex Appliance does not currently restrict you from adding a local user and a remote user with the same username. However, upgrade issues can occur if you do. Do not use duplicate usernames across local and remote users.
If a server communicates with the appliance with a domain name that is not in the appliance
hostsfile, the server name is not masked in the logs.After a restart, if you check the status of the services on the appliance node, the settings-sync service may show as failed.
This issue is fixed in version 6.3.
To resolve the status on an earlier version, restart the node again. Alternatively, you can manually sync the settings with the system sync-settings command, but the command does not change the status of the settings-sync service itself.
After you update to version 6.0 or 6.1, the system might send the following alerts once, depending on the load conditions:
V-475-130-30007: The metrics-node service is not in an optimal state.
V-475-130-30009: The metrics-storage service is not in an optimal state.
If you do not receive these alert messages again, the system is functioning normally. You can safely ignore them.
This issue is resolved in version 6.2.
On version 6.0, the Live firewall settings on the instance details page of a WORM instance are not properly aligned, and some of the content is not visible.
This issue is fixed in version 6.1.
To work around this issue on version 6.0, copy the content and paste it an editor to view the full contents.
When you update the firmware on a multi-node appliance, you may receive alerts between the updates of the first and the second node. Once you complete the update on the second node, you should receive notifications that the alerts have been resolved.
When you edit the roles for a user and select a base role, some of the extended roles are grayed out. These extended roles are included as part of the selected base role.
In version 6.1, the role descriptions have been updated to indicate why the roles are grayed out.
If you generate a Data Collect log package with data masking enabled, the
private_mapfile that is included uses the same key value for multiple entries.After a new installation or an upgrade to version 6.x, SAN client (Fibre Transport Media Server) backups do not work on NetBackup application instances earlier than version 10.3. To use SAN client on an earlier supported version, you must install an EEB.
You can find the EEBs at the following locations:
Note:
Update the appliance before you upgrade the instance or install the EEB.
For this release, the Performance graphs on the Flex Appliance Console Home page show data only in the UTC time zone.
Alerts are not currently sent for the metrics that can be set with the set alerts hardware-threshold command.
During a firmware update, an issue can occur with the storage shelf controller that causes an update failure message to appear. If you see a failure message, it may have appeared in error, and the update may still have worked. Run the following command to confirm the firmware version:
show hardware-health primaryshelf component=controller
While an update is in progress on version 6.0 or 6.1, do not perform any other operations in the Flex Appliance Shell or the Flex Appliance Console.
Starting with version 6.2, all other operations are blocked.
When you install application add-ons on an instance, the Flex Appliance Console lets you select different versions of the same OST plug-in. However, this configuration is not supported, and if you select more than one version of the same plug-in, the Install add-ons page shows duplicate entries. Only install one version of each OST plug-in on an instance. If you need to change the version of an OST plug-in that is already installed, first uninstall it, and then install the new version.
On version 6.0, if the host0 or host1 port is not connected to the appliance node during initial configuration, the following error message appears that does not provide complete information:
"Network card for <interface name> is missing. Make sure that all network interfaces are connected to the appliance."
If you encounter this message, verify that all ports are connected according to the initial configuration guidelines. See Initial configuration guidelines and checklist. Then restart the node to continue the configuration.
In version 6.1, this message has been updated to provide more accurate information.