Software Compatibility List Netbackup

[Kenneth]

Thecustomer is still running NetBackup 8.1.1, and due to various reasons will not consider upgrading to 8.3 or 9.x anytime soon.

This Nbu 8.1.1 environment is currently handing the VMware backups of a vCenter 6.7U3 + ESXi 6.7U3 cluster.

This is fine according to the NetBackup version compatibility list.

Whether this is officially supported by Veritas is not important to them right now, they just want to know if VMware backups will continue to work.

I suppose I can spin up a lab to test this, but just thought I'd ask here first.

Well... NBU can do backups/snapshot either via vcenter or esxi directly... all you need to do is... remove vcenter crednetials and add credentials for each esxi and modify all VMware policies (VIP) whereever vcenter name was used in query.

Please point out to them that for Veritas, "unsupported" generally means - "It might work. It might not. It probably won't cause anyone who looks at it to spontaneously combust. Your servers probably won't explode. Your data center probably won't suddenly spawn carnivorous goats. Since we haven't actually tested that code with those versions though, WE PROMISE NOTHING."

=)

So yeah, if they want to upgrade their VM environment to something Veritas doesn't support, Veritas promises nothing about what will happen. Including fun things like backups working but not restores, showing successful backups when nothing actually worked, or taking snapshots of each VM but never releasing them.

Personally I have my doubts it will work (I'd guess it will fail at the initial authentication/query stage) but highly recommend you test things out in a lab to confirm. I also highly recommend you start immediately sending lots and lots of emails to the involved managers saying why this is a really bad idea and that you won't be held accountable for people deliberately deploying vendor-unsupported configurations, etc.

You can back up your data to virtual tapes, archive the tapes, and manage your virtual tape library (VTL) devices by using Veritas NetBackup. In this topic, you can find basic documentation on how to configure the NetBackup application for a Tape Gateway and perform a backup and restore operation. To do so, you can use the following versions of NetBackup:

The procedure for using these versions of Backup Exec with a Tape Gateway is similar. For detailed information about how to use NetBackup, see the Veritas Services and Operations Readiness Tools (SORT) on the Veritas website. For Veritas support information on hardware compatibility, see the NetBackup 7.0 - 7.6.x Hardware Compatibility List, NetBackup 8.0 - 8.1.x Hardware Compatibility List, or NetBackup 8.2 - 8.x.x Hardware Compatibility List on the Veritas website.

After you have connected the virtual tape library (VTL) devices to the Windows client, you configure Veritas NetBackup storage to recognize your devices. For information about how to connect VTL devices to the Windows client, see Connecting Your VTL Devices.

The process then inventories your medium changer and virtual tapes in the NetBackup Enterprise Media Management (EMM) database. NetBackup stores media information, device configuration, and tape status in the EMM.

In the Robot Inventory window, choose Yes once the inventory is complete. Choosing Yes here updates the configuration and moves virtual tapes found in import/export slots to the virtual tape library.

Now that you have connected your devices and made them available to your backup application, you are ready to test your gateway. To test your gateway, you back up data onto the virtual tapes you created and archive the tapes.

You should back up only a small amount of data for this Getting Started exercise, because there are costs associated with storing, archiving, and retrieving data. For pricing information, see Pricing on the Storage Gateway detail page.

From the list of virtual tapes, open the context (right-click) menu for the tape you want to add to the volume pool, and choose Change to open the Change Volumes dialog box. The following screenshot shows the Change Volumes dialog box.

To find the barcode of the virtual tape where NetBackup wrote the file data during the backup, look in the Job Details window as described in the following procedure. You need this barcode in the procedure in the next section, where you archive the tape.

In the Storage Gateway console, verify the status of the tape you are archiving in the gateway's VTL. It can take some time to finish uploading data to AWS. During this time, the ejected tape is listed in the gateway's VTL with the status IN TRANSIT TO VTS. When archiving starts, the status is ARCHIVING. Once data upload has completed, the ejected tape is no longer listed in the VTL but is archived in S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive.

Use the Backup, Archive, and Restore software installed with the Veritas NetBackup application. This process is the same as restoring data from physical tapes. For instructions, see Veritas Services and Operations Readiness Tools (SORT) on the Veritas website.

The Center for Internet Security (CIS) profiles available in the scap-security-guide (SSG) package are now aligned with CIS Red Hat Enterprise Linux 8 Benchmark version 2.0.0. This version of the benchmark adds new requirements, removed requirements that are no longer relevant, and reordered some existing requirements. The update impacts the references in the relevant rules and the accuracy of the respective profiles.

Changes in the system configuration and the clevis-luks-systemd subpackage enable the Clevis encryption client to unlock also LUKS-encrypted volumes that mount late in the boot process without using the systemctl enable clevis-luks-askpass.path command during the deployment process.

Identity Management (IdM) in RHEL 8.7 introduces a Technology Preview where you can delegate user authentication to external identity providers (IdPs) that support the OAuth 2 Device Authorization Grant flow. When these users authenticate with SSSD, and after they complete authentication and authorization at the external IdP, they receive RHEL IdM single sign-on capabilities with Kerberos tickets.

To ensure your system remains supported after upgrading to RHEL 8.6, either update to the latest RHEL 8.7 version or ensure that the RHEL 8.6 Extended Update Support (EUS) repositories have been enabled.

For the successful in-place upgrade of RHEL 7.6 for IBM POWER 9 (little endian) and IBM Z (structure A) architectures, you must manually download the specific Leapp data. For more information, see the Leapp data snapshots for an in-place upgrade Knowledgebase article.

Instructions on how to perform an in-place upgrade from RHEL 8 to RHEL 9 using the Leapp utility are provided by the document Upgrading from RHEL 8 to RHEL 9. Major differences between RHEL 8 and RHEL 9 are documented in Considerations in adopting RHEL 9.

If you are using CentOS Linux 8 or Oracle Linux 8, you can convert your operating system to RHEL 8 using the Red Hat-supported Convert2RHEL utility. For more information, see Converting from an RPM-based Linux distribution to RHEL.

If you are using an earlier version of CentOS Linux or Oracle Linux, namely versions 6 or 7, you can convert your operating system to RHEL and then perform an in-place upgrade to RHEL 8. Note that CentOS Linux 6 and Oracle Linux 6 conversions use the unsupported Convert2RHEL utility. For more information on unsupported conversions, see How to perform an unsupported conversion from a RHEL-derived Linux distribution to RHEL.

Red Hat Customer Portal Labs is a set of tools in a section of the Customer Portal available at The applications in Red Hat Customer Portal Labs can help you improve performance, quickly troubleshoot issues, identify security problems, and quickly deploy and configure complex applications. Some of the most popular applications are:

Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures. For a list of available subscriptions, see Subscription Utilization on the Customer Portal.

The Installation ISO image is in multiple GB size, and as a result, it might not fit on optical media formats. A USB key or USB hard drive is recommended when using the Installation ISO image to create bootable installation media. You can also use the Image Builder tool to create customized RHEL images. For more information about Image Builder, see the Composing a customized RHEL system image document.

See the Performing a standard RHEL 8 installation document for instructions on downloading ISO images, creating installation media, and completing a RHEL installation. For automated Kickstart installations and other advanced topics, see the Performing an advanced RHEL 8 installation document.

For a list of users and groups created by RPMs in a base RHEL installation, and the steps to obtain this list, see the What are all of the users and groups in a base RHEL installation? Knowledgebase article.

Content in the BaseOS repository is intended to provide the core set of the underlying OS functionality that provides the foundation for all installations. This content is available in the RPM format and is subject to support terms similar to those in previous releases of RHEL. For a list of packages distributed through BaseOS, see the Package manifest.

Content in the Application Stream repository includes additional user space applications, runtime languages, and databases in support of the varied workloads and use cases. Application Streams are available in the familiar RPM format, as an extension to the RPM format called modules, or as Software Collections. For a list of packages available in AppStream, see the Package manifest.

In addition, the CodeReady Linux Builder repository is available with all RHEL subscriptions. It provides additional packages for use by developers. Packages included in the CodeReady Linux Builder repository are unsupported.

3a8082e126