Nuts and Bolts in NetBackup for VMware
Looking for the details on NetBackup for VMware? Would you like to know about the nuts and bolts inside? We recently published, and we intend to publish more on technical details on award winning NetBackup for VMware protection. As there are many blogs in this series, I am publishing this blog as a container for this series. The series so far:
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.
Multiple Clients Failing - VMware - status 196
Hi All, I am pretty new to Veritas Netbackup systems and I have been dealing with a status 196 on a client environment that has now been happening for a month. This issue is resulting in multiple policies failing due to a backup window timeout error. The policies failing are VMWare policies and are configured to use the vsphere intellingent policy backup method using annotations. I raised a veritas support case and the TSE based on his investigation advised to reduce the number of backup jobs from each policy running at any given time. However this atleast for now can not be done due to the client's requirement of not having backups run during business hours. Currently the backups are set to full backups and are backing up sizes raning from 4TB, 2TB, 1TB. I was wondering if any assistance or knowledge share can be done here to help troubleshoot and diagnose the issue at hand? Happy to provid emore clear and concise information for further understanding. Many Thanks!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.vCenter 7.0 and NetBackup 8.1(Appliance version 3.1) incompatibility Issue. Backup Fails!
Hello, First of all, I'm not familiar with NetBackup. I just noticed that all VMware VM backups fail after I upgraded vCenter from 6.7 to 7.0. NetBackup 8.1 console> Media and Device Management> Credentials> Virtual Machine Server, the login to new vCenter fails, which I think why all VM backup fails. NetBackup Core Support confirmed that this is incompatiblity issue and I have to upgrade my Appliance and the other media server and Netbackup to upper version. Can anyone layout the steps and links how I can perform this upgrade? I searched knowledge bases but Appliance white papers talk about only appliance, Netbackup talks about only netbackup upgreade. Much Appreciated in advance.