cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

VMware backups failed -4204 status code

Hi Folks,

VMware backups are failing with error 4204.

May 5, 2020 11:22:50 PM - Info nbjm (pid=10644) starting backup job (jobid=2273265) for client str8-docfin-01v, policy STR-VMware-Linux-Staging, schedule VMware-Daily-Differential
May 5, 2020 11:22:50 PM - Info nbjm (pid=10644) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2273265, request id:{58312CAF-32A3-44F6-B17A-12DB03ABA5EC})
May 5, 2020 11:22:50 PM - requesting resource STR-SEPA-DLY-DV-01-DP-SU1
May 5, 2020 11:22:50 PM - requesting resource adr4-backup-01.adm.aamc.org.NBU_CLIENT.MAXJOBS.str8-docfin-01v
May 5, 2020 11:22:50 PM - requesting resource adr4-backup-01.adm.aamc.org.VMware.Datastore.enl8-vcenter-01v.ent.aamc.org/STR
May 5, 2020 11:22:55 PM - granted resource  adr4-backup-01.adm.aamc.org.NBU_CLIENT.MAXJOBS.str8-docfin-01v
May 5, 2020 11:22:55 PM - granted resource  adr4-backup-01.adm.aamc.org.VMware.Datastore.enl8-vcenter-01v.ent.aamc.org/STR DataCenter/STR-STG-NMBL-LNX-CL2
May 5, 2020 11:22:55 PM - granted resource  MediaID=@aaabH;DiskVolume=STR-SEPA-DLY-DV-01;DiskPool=STR-SEPA-DLY-DV-01-DP;Path=STR-SEPA-DLY-DV-01;StorageServer=enr2-sepaton-01-ost.tan.aamc.org;MediaServer=adr4-backup-01.adm.aamc.org
May 5, 2020 11:22:55 PM - granted resource  STR-SEPA-DLY-DV-01-DP-SU1
May 5, 2020 11:23:38 PM - estimated 6193732 kbytes needed
May 5, 2020 11:23:38 PM - begin Parent Job
May 5, 2020 11:23:38 PM - begin Application Snapshot: Step By Condition
Operation Status: 0
May 5, 2020 11:23:38 PM - end Application Snapshot: Step By Condition; elapsed time 0:00:00
May 5, 2020 11:23:38 PM - begin Application Snapshot: Read File List
Operation Status: 0
May 5, 2020 11:23:38 PM - end Application Snapshot: Read File List; elapsed time 0:00:00
May 5, 2020 11:23:38 PM - begin Application Snapshot: Create Snapshot
May 5, 2020 11:23:38 PM - Info bpbrm (pid=7700) str8-docfin-01v is the host to backup data from
May 5, 2020 11:23:38 PM - Info bpbrm (pid=7700) reading file list for client
May 5, 2020 11:23:38 PM - Info bpbrm (pid=7700) start bpfis on client
May 5, 2020 11:23:38 PM - Info bpbrm (pid=7700) Starting create snapshot processing
May 5, 2020 11:23:38 PM - started process bpbrm (pid=7700)
May 5, 2020 11:23:39 PM - Info bpfis (pid=9240) Backup started
May 5, 2020 11:26:20 PM - snapshot backup of client str8-docfin-01v using method VMware_v2
May 5, 2020 11:31:21 PM - Critical bpbrm (pid=7700) from client str8-docfin-01v: FTL - VMware_freeze: Unable to get servers at line 4787
May 5, 2020 11:31:21 PM - Critical bpbrm (pid=7700) from client str8-docfin-01v: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
May 5, 2020 11:31:21 PM - Critical bpbrm (pid=7700) from client str8-docfin-01v: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
May 5, 2020 11:31:21 PM - Critical bpbrm (pid=7700) from client str8-docfin-01v: FTL - snapshot processing failed, status 4204
May 5, 2020 11:31:21 PM - Critical bpbrm (pid=7700) from client str8-docfin-01v: FTL - snapshot creation failed, status 4204
May 5, 2020 11:31:21 PM - Warning bpbrm (pid=7700) from client str8-docfin-01v: WRN - ALL_LOCAL_DRIVES is not frozen
May 5, 2020 11:31:21 PM - Info bpfis (pid=9240) done. status: 4204
May 5, 2020 11:31:21 PM - end Application Snapshot: Create Snapshot; elapsed time 0:07:43
May 5, 2020 11:31:21 PM - Info bpfis (pid=9240) done. status: 4204: Incompatible client found
May 5, 2020 11:31:21 PM - Info bpbrm (pid=17044) Starting delete snapshot processing
May 5, 2020 11:31:21 PM - end writing
Operation Status: 4204
May 5, 2020 11:31:21 PM - begin Application Snapshot: Stop On Error
Operation Status: 0
May 5, 2020 11:31:21 PM - end Application Snapshot: Stop On Error; elapsed time 0:00:00
May 5, 2020 11:31:21 PM - begin Application Snapshot: Cleanup Resources
May 5, 2020 11:31:21 PM - end Application Snapshot: Cleanup Resources; elapsed time 0:00:00
May 5, 2020 11:31:21 PM - begin Application Snapshot: Delete Snapshot
May 5, 2020 11:31:21 PM - started process bpbrm (pid=17044)
May 5, 2020 11:31:22 PM - Info bpfis (pid=14604) Backup started
May 5, 2020 11:31:22 PM - Warning bpbrm (pid=17044) from client str8-docfin-01v: cannot open D:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.str8-docfin-01v_1588735418.1.0
May 5, 2020 11:31:22 PM - Info bpfis (pid=14604) done. status: 4207
May 5, 2020 11:31:22 PM - end Parent Job; elapsed time 0:07:44
May 5, 2020 11:31:22 PM - Info bpfis (pid=14604) done. status: 4207: Could not fetch snapshot metadata or state files
May 5, 2020 11:31:22 PM - end writing
Operation Status: 4207
May 5, 2020 11:31:22 PM - end Application Snapshot: Delete Snapshot; elapsed time 0:00:01
Operation Status: 4204
Incompatible client found  (4204)

 

 

Please suggest us to troubleshoot the issue., backups configured based on query.and few of the backups only getting failed and rest of the backups are completed for the same policy.

and backup is failing for different server every day not for the same host.

We have changed the VM identifier as VM displayname is it impact on it.

 

Tags (2)
2 Replies
Highlighted

Re: VMware backups failed -4204 status code

Saw this:  "Incompatible client found"

Have you checked that your infrastructure versions and config are supported in the NetBackup SCL and HCL ?

Highlighted

Re: VMware backups failed -4204 status code

What happens when you run the 'Test Query' function from the policy? 

I've seen issues with VIP when there was a full file system (/log I believe). There were 100s of .xml files that clogged up the file system, preventing the query from functioning correctly.

Have you tested backups by manually specifying the problematic VMs?