Netbackup self service compatiblity with Master server hosted over Flex appliance
Hello, I am trying to add NetBackup master server hosted over Flex appliance in Netbackup self service but after adding the Master server check connectivity option not working. As per Netbackup self service configuration guide prereqesties are : The user account that NetBackup Self Service uses to logon to SSH on the master server needs sudo configuration: ■ The user account should not use requiretty. ■ The user account should not require a sudo password. ■ With sudo, the user account should run all commands in /usr/openv/netbackup/bin and /usr/openv/netbackup/bin/admincmd. So i created new user on Netbackup master server and give superuser rights to user. so that user can execute all netbackup commands without sudo.But still check connectivity option not working. Is there any sperate procedure to add Netbackup master server (hosted on Flex appliance) in Netbackup self service ? In Netbackup self service documentation and Flex appliance documentation no procedure found.
Trouble Shooting: Self Service data synchronization issues
Troubleshooting NetBackup Self Service data synchronization issues Note: the tab ‘Locations’ has been renamed to ‘Backup Servers’ in Self Service 8.1.2. This post will cover: • Issues with data synchronization • Generated reports from connected master servers • Connection issues between Self Service and connected master servers, or other systems such as vCloud Director Backup Catalog data incorrect Running a manual system sync can help with issues like backups not showing against computer. This will refresh all computers with any new catalog data created since the last sync. Monitoring tab > System Sync > Run Now - If an older backup is missing, catalog data will not be included in the system sync - If data is missing, on the Computers tab, manually refresh the specific computer by clicking Refresh NetBackup data, via the cog, - All catalog data for the computer will be resynchronized Dashboard reports not accurate Perform a manual system sync to refresh catalog data and update dashboard reports. Monitoring tab > System Sync > Run Now Computer not found (vCloud Director) If the computer was imported from vCloud Director, a tenant admin can perform a manual refresh to import any changes in the estate since the last scheduled sync. Note: the tenant admin should check the vCloud Director Password is correct. Tenant computer list > click on top level vCloud node > cog > Refresh Self Service administrator can also perform a manual import on the Monitoring tab, for tenants. Please note: For VMware query-based policies, NetBackup caches the result of the policy query based on value in the ‘Reuse VM selection query results for…’ attribute. Depending on the frequency shown, there may be some time where the computer has been provisioned in VMware but is not available to the policy (as the cached results do not include it). Please contact your local Veritas representative for more information on this. A tenant cannot find the computer in their computer list Questions: - Does the computer exist in the inventory? - Does the user have restricted permissions to view the computer? This could be set by the tenant administrator user. Computer > User Access tab. - Has the computer been registered against the wrong tenant? - Are computers being registered via custom integration? Check integration components.vCenter client auto discovery
This solution below provides a means to schedule the import of vCenter VMs into NetBackup Self Service (NSS). The import uses securely stored credentials to connect to a vCenter environment associated with the relevant Master Server and imports VMs from a vCenter folder which an NSS tenant has been mapped to. The import compares a tenant’s NSS machine list with the associated vCenter folder, registering new machines for VMs found in vCenter and removing machine registrations where the VM no longer exists in vCenter (and no backup images exist for the machine in NetBackup). A scheduled task will be created in NSS with standard options to run the import on a regular basis.