I have some VMs failing with the error 4204: Incompatible client found.
The final status error is 6.
If the job is re-run it runs fine no issues.
vCenter is clean, no errors, no orphaned snapshots
Thoughts?
03/01/2016 00:02:02 - Info ...
Wanted to get some input from folks here.
NBU 7.6.1.2 on Linux (Master and Media). VMWare backup running like a champ for about 1.5 years. VMWare vCetner Appliance (VCSA) was upgrades to 6.0u1b (was 6.0). After that upgrade we started recieving m...
VM Admins are building their new vCenter 6 environment. While discussing backups was told that the cluster names in the new vCenterB would be the same as the old vCenterA for a short amount of time until migration is complete. My VIP queries are ba...
Just started getting some errors in VMWare backups after VMs were storage vmotioned to a newly provisioned LUN.
The Datastore LUN is presented to my Media Agents and I have verified that I can see the LUN on the Media Agents.
Not all VMs on the LUN...
Have a dumb question that I havent been able to find an answer to...
If I have a policy disabled at the beginning of a backup window, but then enable it 2 hours after the start of the window do I need to run the backup manually or will the scheduler...
Veritas is asking for more logs now and VMWare has already been involved. We hope the 2 will get along and work thorugh this! I will update as we get further along.
Per Veritas PM of VMware
Just wanted to get us all on the same page. I checked with our Engineering team on this issue and here is their response:
“The issue with 5.5 update 3b was the disabling of SSLV3. This was done for 6.0 GA and required us t...
Just in case someone else needs this info:
Our veritas technical rep got ahodl of the PM responsible for VMWare. This is the response.
Just wanted to get us all on the same page. I checked with our Engineering team on this issue and here is th...
We ran fine with limits with a resource limit of 3 on datastore until the 6.0u1b upgrade. This would allow about 100-150 vms to backup at a time across 3 media agents.
Last night we set to vcenter and snapshot to 20 and datastore 2 and still see er...
Interesting thought on a vmotion moving the VMs so the database is not up to date.
That might explain why a manual backup runs fine.
On your point, too many jobs overloading vcenter... whats too many jobs? I see the best practices just says to run...
