Registering computers
Computers within the estate must be registered to NetBackup Self Service. This requirement includes the name for display in the UI and configuration data for use with NetBackup.
You can register a computer in three different ways: through the user interface, through NetBackup cloud asset import, or automatically through vCloud Director import. A single tenant can have more than one source of computer, for example, virtual machines imported from vCloud Director and physical computers imported through the API.
You can register a computer from the Assets page on the home page with . Help text is available to assist in completion of the data. Fields are validated for accurate data either during entry or when you click .
To remove a computer registration, go to the list on the Assets home page, select an asset, and use the link from the button. Computer registration cannot be edited so it is recommended that a computer registration is deleted and recreated if changes are required. Be sure to use the same computer code when you recreate a computer registration.
The computer registration process includes an automatic refresh of protection data and image data from NetBackup. Protection data indicates what is protected either by schedule or by a one-off Backup Now task. If you click from the button on the asset details page, you can synchronize protection and backup images of a computer. Typically synchronization should not require manual intervention. Exceptions might be if you want to immediately see images from a new protection policy or images that have been created manually.
See the SDK documentation in the Install directory.
You can automatically import a vCloud hierarchy from vCloud Director and register the computers with NetBackup Self Service. The import is performed on a tenant by tenant basis using individual credentials.
A vCloud Director import must define the vCloud Director instance from which the hierarchy is imported. Additionally, it must specify the NetBackup Self Service settings you want to associate with it.
An import must specify a Protection Type and a Backup Server that the imported hierarchy is associated with.
An import may optionally use virtual data center (vDC) filtering. When vDC filtering is enabled, only vDCs in the filter are imported. Filtering occurs on a per tenant basis and each must be set up with a filter to import any vDCs. Each vDC should appear only in a single tenant's filter.
When vDC filtering is disabled, all vDCs that are visible through the import credentials are imported.
Use the option on the Asset Imports > vCloud Director page to create a new vCloud Director Import. Follow the on-screen prompts to create a corresponding vCloud Import Integration Setting section.
If the vCloud Director is version 9.5 or higher, you must specify an administrator user name and password for the vCloud Director system. You must also add credentials for each of the underlying vCenter servers that the vCloud Director manages if you use version 10.1 or earlier. The credentials are not required for version 10.2 and later. Each vCenter server must be running version 6.5 or higher. Select and then to add each vCenter. The vCenter is identified using the . This URL must match the name that is registered in vCloud Director.
You must specify logon credentials at a tenant level to enable import. The credentials in vCloud Director are defined against an Organization and must have the right. Only a single tenant can import computers from any vCloud Director Organization.
When you create a new tenant, the Add Tenant form supports specifying credentials for a single vCloud Director system as part of the tenant creation process. You can update credentials on the Details tab in . Once the initial password is set, a tenant-administrator can update the vCloud Director password that is used to access vCloud Director. The tenant-administrator updates the password through a drop-down on the root node of their Computers list.
Table: vCloud Director Import Settings
Item | Details |
|---|---|
vCloud Director API URL | This value should be set to the URL of the vCloud Director API, in the format of https://hostname/api/. |
Location | The name of the NetBackup backup server the computers are registered to. |
Online | Indicates if the vCloud Director instance is considered online. Self Service does not use the instances that are not online. |
Ignore SSL Certificate Errors | This option allows the Self Service to connect to vCloud Director instances where the SSL certificate is not valid. |
vCloud UserName | The username that the tenant uses to connect to the vCloud Director API. Each tenant must have their own credentials. It must be in the format userid@vOrg. Must be set at the tenant level only. |
vCloud Password | The tenant's corresponding vCloud Director password. Must be set at the tenant level only. |
Protection Type Code | The protection type that is applied to imported computers. |
Use vDC Filter | Set to enable vDC filtering. |
vDC Filter | The filter to apply to vDCs during an import. This filter is a comma separated list and vDC names are case-sensitive. Set at the tenant level only. |
Display Name | The name that is displayed for users. This name is displayed on the default view of the home page |
Include Metadata | Determines if the metadata should be included in the import. |
vCloud Admin UserName | The administrator user for vCloud in the format: Administrator@System. Required if using vCloud Director 9.5 or higher. |
vCloud Admin Password | The password of the account with Admin credentials in vCloud. Required if using vCloud Director 9.5 or higher. |
Computers that are imported from vCloud Director are displayed to the tenant-user in a two-paned tree-view. Computers are listed within their parent containers. If the computer is from vCloud, containers display in left pane. When you click on the lowest level container, the contents are displayed on the right pane. Protection can be applied at either the container or the computer level. When only non-vCloud Director computers are registered, they are displayed in a full width list.
You can automatically import Kubernetes assets from NetBackup and register them with Self Service. The import is performed on a tenant by tenant basis, using filters or individual credentials.
You must define the NetBackup server from which the assets are to be imported.
Additionally, you must specify the Self Service settings you want to associate with it.
You must specify a Protection Type and a Tenant that you want to associate the imported assets with.
You must specify at least the Kubernetes cluster to identify the imported assets. You may also specify a set of other filter criteria (one or multiple names spaces) which every asset must meet for it to be imported. During setup you can preview the results of the current filter criteria.
You can automatically import Nutanix assets from NetBackup and register them with Self Service. The import is performed on a tenant by tenant basis. The import uses filters or individual credentials.
You must define the NetBackup server from which the assets are to be imported. Additionally, you must specify the Self Service settings you want to associate with it.
You must specify a Protection Type and a Tenant that you want to associate the imported assets with.
You must specify at least the Nutanix prism central or Nutanix Cluster to identify the imported assets. You may also specify a set of other filter criteria which every asset must meet for it to be imported. The criteria can include things like project name or VM Display name (starts with, ends with, or contains). During setup you can preview the results of the current filter criteria.
Additional validation exists for when you save the Nutanix import. Self Service validates that the selected primary server and the selected protection plan are configured with the storage in the Configure Storage screen. This validation has been added because we need storage information for creating the protection on the fly in NetBackup primary server from NetBackup Self Service.
Be aware that during the import NetBackup Self Service does not allow duplicate assets with the same display name. This behavior is default behavior for all workloads in NetBackup Self Service.
You can automatically import cloud assets from NetBackup and register them with Self Service. The import is performed on a tenant by tenant basis, using individual credentials.
You must define the NetBackup server from which the assets are to be imported. Additionally, you must specify the Self Service settings you want to associate with it.
You must specify a Protection Type and a Tenant that you want to associate the imported assets with.
You may also specify which types of cloud assets are to be imported.
You must specify logon credentials for each import. These credentials must only have access to the specified tenant's assets.
You can automatically import vCenter assets from NetBackup and register them with Self Service. The import is performed on a tenant by tenant basis, using filters or individual credentials.
You must define the NetBackup server from which the assets are to be imported.
Additionally, you must specify the Self Service settings you want to associate with it.
You must specify a Protection Type and a Tenant that you want to associate the imported assets with.
You must specify at least the vCenter server to identify the imported assets. You may also specify a set of other filter criteria which every asset must meet for it to be imported. During setup you can preview the results of the current filter criteria.
Alternatively, you can set up individual credentials for the import and use the NetBackup RBAC configuration to determine which assets are imported.