Veritas NetBackup™ Release Notes
- About NetBackup 8.3.0.2
- New features, enhancements, and changes
- Operational notes
- About NetBackup 8.3.0.2 operational notes
- NetBackup installation and upgrade operational notes
- After initiating CA migration, connection errors may occur
- If NetBackup 8.3.0.2 upgrade fails on Windows, revert to previous log folder structure
- Native installation requirements
- NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
- Do not install from the menu that appears when the installation DVD is inserted
- About support for HP-UX Itanium vPars SRP containers
- NetBackup administration and general operational notes
- The nbdeployutil utility may fail to generate usage reports for traditional licensing
- Child backup jobs may enter a queued state for workloads that use BigData policy
- Errors are shown in the jobs detail when NetBackup attempts to expire images from non-WORM capable storage
- NetBackup web server certificate renewal failure during initiation of NetBackup CA migration or upgrade
- Microsoft Azure backup fails if the resource group name contains a period (.)
- SLP does not retry multistreaming backup if child job fails or is canceled
- Granular restores require adequate available space on target
- Stale devices shown on the device tree
- NetBackup administration interface operational notes
- Search limitations for security events lists in the NetBackup web UI
- Using X forwarding to launch the NetBackup Administration Console can fail on certain Linux platforms
- Intermittent issues with X forwarding of NetBackup Administration Console
- NetBackup Administration Console fails in Simplified Chinese UTF-8 locale on Solaris SPARC 64-bit systems with Solaris 10 Update 2 or later
- NetBackup Bare Metal Restore operational notes
- NetBackup Cloud operational notes
- NetBackup with Veritas CloudPoint operational notes
- On-host agent may be unavailable after restore with a snapshot taken with NetBackup CloudPoint 8.3
- Application status of original instances may report errors for host-consistent restores to alternate locations
- Public cloud not supported with gov cloud or China region
- Indexing not supported on instances created from AWS Marketplaces AMIs
- Consistent host snapshot might fail
- Image clean-up may fail for Microsoft Azure workloads
- Configuring AWS plug-in with IAM role showed that the Authentication Method field is blank
- MongoDB create snapshot job may freeze
- Updating a cloud plug-in while a job runs causes job failure
- Permission denied error occurs if both user and password are updated
- Different source and target zones for Google Cloud Platform are not supported
- Broken files system detected
- NetBackup deduplication operational notes
- NetBackup for NDMP operational notes
- NetBackup internationalization and localization operational notes
- NetBackup Snapshot Client operational notes
- NetBackup virtualization operational notes
- Appendix A. About SORT for NetBackup Users
- Appendix B. NetBackup installation requirements
- Appendix C. NetBackup compatibility requirements
- Appendix D. Other NetBackup documentation and related documents
On-host agent may be unavailable after restore with a snapshot taken with NetBackup CloudPoint 8.3
After a restore that uses a snapshot that was taken with NetBackup CloudPoint 8.3, the on-host agent may not be available.
The on-host agent is unable to connect to rabbitmq after a CloudPoint upgrade and continues to fail for some time. The jobs that are triggered while the agent is not connect to rabbitmq fail with error:
Agent agent.203f5661cdd0448bbb63138b5000e0c7 is offline on the host azure-vm-a3d6ef3b-e12f-4754-ba75-84084c1d693c.
During the upgrade, the on-host agent from an actual VM "auto-grt-97230" released the earlier connection, and the agent on the restored VM was able to connect on the same queue. After the upgrade, the source on-host agent did not get the lock and then continued to fail with the resource_locked error, making the on-host agent offline.
Workaround:
Follow these steps if you want to take the application-consistent snapshots of the restored instance:
On the restored host:
For a Linux on-host agent, follow the steps from the Veritas NetBackup CloudPoint Install and Upgrade Guide section Registering the Linux-based agent.
For a Windows on-host agent, follow the steps from the Veritas NetBackup CloudPoint Install and Upgrade Guide section Registering the Windows-based agent.
Note:
Ensure that you have removed the previously installed on-host agent before installation and re-registration.
On the source host:
Log in to the host.
Restart the
flexsnap-agent:Linux:
sudo systemctl stop flexsnap-agent.service
sudo systemctl start flexsnap-agent.service
Windows:
Restart Veritas NetBackup CloudPoint Agent service
Follow the steps below if you want to take the crash-consistent snapshots of the restored instance:
On the restored host:
Follow the steps from the Veritas NetBackup CloudPoint Install and Upgrade Guide section Removing the CloudPoint agents.
Follow the steps below on the host from which the snapshot was restored:
Log in to the host.
Restart the
flexsnap-agent:Linux:
sudo systemctl stop flexsnap-agent.service
sudo systemctl start flexsnap-agent.service
Windows:
Restart Veritas NetBackup CloudPoint Agent service