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!
Unable to connect to host / Backup selections
Hi guys, I'm facing an issue with the backup selections for MS-Windows type policies that I want to create on NetBackup 7.6.1 and 8.1. Getting message "Unable to connect to host". I have tried many suggested solutions in the forum without success. So I want to start a new discussion on my specific case. Can I get any help?
Changing VMware type policy from VIP to manual VM selection
I have recently changed a policy from VMware Intelligent policy queries to manual VM selection. The reasoning for this was to make use of the max jobs pr. policy limitation, which are not possible to use with VIP. I kept getting failures during the snapshot with NetBackup reporting a code 4239: Unable to find the virtual machine 24-07-201810:57:24-Criticalbpbrm(pid=74644)fromclientSERVER:FTL-VMware_freeze:UnabletolocatevirtualmachineSERVER usingVMdisplayname This error occured even when changing to VM Hostname or a different identifier. I spent quite a bit of time trying to work out why it wasn't working, until I remembered having the same issue earlier in the year. The solution was to just create a new policy (do not copy it, as that will have the same issue), and then there are no problems. My question is, has anyone else experienced it? Its not really a massive issue, but you do risk spending time troubleshooting it as the error is a bit general. The logs weren't very useful either. Caspar
Policy Update
Hello, Have recently modified policy schedules in an existing policy. Created a new schedules for both Differential and Full backups, and deleted old schedules through which Full and Differential backups have been done manually. There are no scheduled backups. The scheduled Differential backup to be triggered next day has not started. Tried manual backup of Differential backup with new schedule. However, the polcy defined scheduled backup type is showing Differential, but when backup started it was taking a Full backup. Does, deleting old schedules of Full backup have any impact on newly created schedules. Will Differential backups trigger before an Full backup is done? NetBackup 7.7.3 Version was used for VMWare backups.