cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

error 4201

Zippo0526
Level 3

‎03-30-2017 04:18 AM

Hello,

Need some help with a backup that used to work and now has been failing with error 4201

Master and media servers are Windows 2012 R2 with NBU 7.7.3, Client is Windows 2003 with version 7.6.0.4.  the policy is flashbackup-Windows.  This is NOT a hyper-v server or client.

Thanks

Scott

Detailed status

03/29/2017 19:28:44 - Info nbjm (pid=6256) starting backup job (jobid=340826) for client kocfs01, policy Prod_FS_Servers_FB, schedule Daily_Inc
03/29/2017 19:28:44 - Info nbjm (pid=6256) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=340826, request id:{2368684A-892E-4357-A444-A30B1AC848E6})
03/29/2017 19:28:44 - requesting resource Catalyst_Servers_Store_01-stu
03/29/2017 19:28:44 - requesting resource kocbkup02.NBU_CLIENT.MAXJOBS.kocfs01
03/29/2017 19:28:44 - requesting resource kocbkup02.NBU_POLICY.MAXJOBS.Prod_FS_Servers_FB
03/29/2017 19:28:44 - granted resource  kocbkup02.NBU_CLIENT.MAXJOBS.kocfs01
03/29/2017 19:28:44 - granted resource  kocbkup02.NBU_POLICY.MAXJOBS.Prod_FS_Servers_FB
03/29/2017 19:28:44 - granted resource  MediaID=@aaaaM;DiskVolume=Catalyst_Servers_Store_01;DiskPool=Catalyst_Servers_Store_01;Path=Catalyst_Servers_Store_01;StorageServer=COFC-USE641T60101;MediaServer=kocbkup02
03/29/2017 19:28:44 - granted resource  Catalyst_Servers_Store_01-stu
03/29/2017 19:28:44 - estimated 22071894 kbytes needed
03/29/2017 19:28:44 - begin Parent Job
03/29/2017 19:28:44 - begin Flash Backup Windows: Start Notify Script
03/29/2017 19:28:44 - Info RUNCMD (pid=25992) started
03/29/2017 19:28:44 - Info RUNCMD (pid=25992) exiting with status: 0
Operation Status: 0
03/29/2017 19:28:44 - end Flash Backup Windows: Start Notify Script; elapsed time 0:00:00
03/29/2017 19:28:44 - begin Flash Backup Windows: Step By Condition
Operation Status: 0
03/29/2017 19:28:44 - end Flash Backup Windows: Step By Condition; elapsed time 0:00:00
03/29/2017 19:28:44 - begin Flash Backup Windows: Stream Discovery
Operation Status: 0
03/29/2017 19:28:44 - end Flash Backup Windows: Stream Discovery; elapsed time 0:00:00
03/29/2017 19:28:44 - begin Flash Backup Windows: Read File List
Operation Status: 0
03/29/2017 19:28:44 - end Flash Backup Windows: Read File List; elapsed time 0:00:00
03/29/2017 19:28:44 - begin Flash Backup Windows: Create Snapshot
03/29/2017 19:28:44 - started process bpbrm (pid=11304)
03/29/2017 19:28:48 - Info bpbrm (pid=11304) kocfs01 is the host to backup data from
03/29/2017 19:28:48 - Info bpbrm (pid=11304) reading file list for client
03/29/2017 19:28:49 - Info bpbrm (pid=11304) start bpfis on client
03/29/2017 19:28:49 - Info bpbrm (pid=11304) Starting create snapshot processing
03/29/2017 19:28:50 - Info bpfis (pid=6044) Backup started
03/29/2017 19:28:55 - Critical bpbrm (pid=11304) from client kocfs01: FTL - vfm_freeze_commit: method: VSS, type: FIM, function: VSS_make
03/29/2017 19:28:55 - Critical bpbrm (pid=11304) from client kocfs01: FTL - snapshot services: snapshot creation failed: provider-private error.
03/29/2017 19:28:55 - Critical bpbrm (pid=11304) from client kocfs01: FTL - vfm_freeze_commit: method: VSS, type: FIM, function: VSS_make
03/29/2017 19:28:55 - Critical bpbrm (pid=11304) from client kocfs01: FTL - snapshot services: snapshot creation failed: provider-private error.
03/29/2017 19:28:55 - Critical bpbrm (pid=11304) from client kocfs01: FTL - snapshot processing failed, status 4201
03/29/2017 19:28:55 - Critical bpbrm (pid=11304) from client kocfs01: FTL - snapshot creation failed, status 4201
03/29/2017 19:28:55 - Warning bpbrm (pid=11304) from client kocfs01: WRN - \\.\g:\ is not frozen
03/29/2017 19:28:55 - Warning bpbrm (pid=11304) from client kocfs01: WRN - \\.\c:\ is not frozen
03/29/2017 19:28:55 - Warning bpbrm (pid=11304) from client kocfs01: WRN - \\.\m:\ is not frozen
03/29/2017 19:28:55 - Critical bpbrm (pid=11304) from client kocfs01: FTL - vfm_fi_terminate: method: VxFI, type: FIM, function: VxFI_detach
03/29/2017 19:28:55 - Critical bpbrm (pid=11304) from client kocfs01: FTL - snapshot services: snapshot detach failed 1 times: invalid argument(s).
03/29/2017 19:28:55 - Info bpfis (pid=6044) done. status: 4201
03/29/2017 19:28:55 - end Flash Backup Windows: Create Snapshot; elapsed time 0:00:11
03/29/2017 19:28:55 - Info bpfis (pid=6044) done. status: 4201: Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries.
03/29/2017 19:28:55 - end writing
Operation Status: 4201
03/29/2017 19:28:55 - end Parent Job; elapsed time 0:00:11
03/29/2017 19:28:55 - begin Flash Backup Windows: Stop On Error
Operation Status: 0
03/29/2017 19:28:55 - end Flash Backup Windows: Stop On Error; elapsed time 0:00:00
03/29/2017 19:28:55 - begin Flash Backup Windows: Delete Snapshot
03/29/2017 19:28:55 - started process bpbrm (pid=24064)
03/29/2017 19:29:00 - Info bpbrm (pid=24064) Starting delete snapshot processing
03/29/2017 19:29:02 - Info bpfis (pid=6792) Backup started
03/29/2017 19:29:02 - Critical bpbrm (pid=24064) from client kocfs01: cannot open C:\Program Files\VERITAS\NetBackup\online_util\fi_cntl\bpfis.fim.kocfs01_1490830124.1.0
03/29/2017 19:29:02 - Info bpfis (pid=6792) done. status: 4207
03/29/2017 19:29:02 - end Flash Backup Windows: Delete Snapshot; elapsed time 0:00:07
03/29/2017 19:29:02 - Info bpfis (pid=6792) done. status: 4207: Could not fetch snapshot metadata or state files
03/29/2017 19:29:02 - end writing
Operation Status: 4207
03/29/2017 19:29:02 - begin Flash Backup Windows: End Notify Script
03/29/2017 19:29:02 - Info RUNCMD (pid=14996) started
03/29/2017 19:29:02 - Info RUNCMD (pid=14996) exiting with status: 0
Operation Status: 0
03/29/2017 19:29:02 - end Flash Backup Windows: End Notify Script; elapsed time 0:00:00
Operation Status: 4201
Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries  (4201)

 

0 Kudos
Reply
2 REPLIES 2

Michael_G_Ander
Level 6
Certified

‎03-30-2017 05:03 AM

Have mostly seen this status in connection with Hyper-V backups, but basically it tells you there is a problem with the snapshot.

You will have to look at the bpfis log and the event logs on the client.

A good starting point is always to run vssadmin list writers and see if any is not stable.

Other than that, the most common cause is a too small shadow storage area for the snapshot, unfortunately this is seldom logged anywhere.

https://blogs.technet.microsoft.com/askcore/2010/06/18/reasons-why-the-error-enumeration-of-the-file... is about system state, but contains a lot of tips about VSS and troubleshooting it.

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue
0 Kudos
Reply

Tape_Archived
Moderator
Moderator
   VIP   

‎03-30-2017 05:58 AM

Want to add a note that Windows 2003 is supported until NetBackup client 7.5.0.7 version so make sure if there was recent netbackup client upgrade or changes. I see the server is on 7.5.0.7 as per your notes.

0 Kudos
Reply