Hi,
Thiago_Ribeiro
More about my environment:
- transport mode: san
- We have Exchange DAG with 2 nodes running on vmware machine
- Master and media server have the same netbackup version
- I create 2 type of policy to backup DAG
Exchange backup with VMware
Exchange agent (like physical)
- As the previous post, we try to backup VM only (HCM-MAIL-MB2) for testing and getting more info about this issue.
- When I run backup non-VMware, there is only HCM-MAIL-MB1 was taken snapshot and backup completed. HCM-MAIL-MB2 go to fail with below message:
=== log ===
6/8/2017 7:10:29 PM - Info bpbrm(pid=4304) HCM-MAIL-MB2 is the host to backup data from
6/8/2017 7:10:29 PM - Info bpbrm(pid=4304) reading file list for client
6/8/2017 7:10:29 PM - Info bpbrm(pid=4304) start bpfis on client
6/8/2017 7:10:29 PM - Info bpbrm(pid=4304) Starting create snapshot processing
6/8/2017 7:10:30 PM - Info bpfis(pid=5316) Backup started
6/8/2017 7:11:04 PM - Info nbjm(pid=7032) starting backup job (jobid=11733) for client HCM-MAIL-MB2, policy hcm-mail-dag, schedule full
6/8/2017 7:11:04 PM - Info nbjm(pid=7032) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=11733, request id:{AF13163A-DBD7-4948-85D2-2D69DEBEED5E})
6/8/2017 7:11:04 PM - requesting resource dedup_pool-stu
6/8/2017 7:11:04 PM - requesting resource masterserver.NBU_CLIENT.MAXJOBS.HCM-MAIL-MB2
6/8/2017 7:11:04 PM - requesting resource masterserver.NBU_POLICY.MAXJOBS.hcm-mail-dag
6/8/2017 7:11:04 PM - granted resource masterserver.NBU_CLIENT.MAXJOBS.HCM-MAIL-MB2
6/8/2017 7:11:04 PM - granted resource masterserver.NBU_POLICY.MAXJOBS.hcm-mail-dag
6/8/2017 7:11:04 PM - granted resource MediaID=@aaaa8;DiskVolume=PureDiskVolume;DiskPool=dedup_pool;Path=PureDiskVolume;StorageServer=mediaserver;MediaServer=mediaserver
6/8/2017 7:11:04 PM - granted resource dedup_pool-stu
6/8/2017 7:11:04 PM - estimated 0 Kbytes needed
6/8/2017 7:11:04 PM - begin Parent Job
6/8/2017 7:11:04 PM - begin Exchange 14 Snapshot, Step By Condition
Status 0
6/8/2017 7:11:04 PM - end Exchange 14 Snapshot, Step By Condition; elapsed time: 0:00:00
6/8/2017 7:11:04 PM - begin Exchange 14 Snapshot, Read File List
Status 0
6/8/2017 7:11:04 PM - end Exchange 14 Snapshot, Read File List; elapsed time: 0:00:00
6/8/2017 7:11:04 PM - begin Exchange 14 Snapshot, Create Snapshot
6/8/2017 7:11:04 PM - started
6/8/2017 7:11:17 PM - started process bpbrm (4304)
6/8/2017 7:54:10 PM - Critical bpbrm(pid=4304) from client HCM-MAIL-MB2: FTL - vfm_freeze: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze
6/8/2017 7:54:10 PM - Critical bpbrm(pid=4304) from client HCM-MAIL-MB2: FTL -
6/8/2017 7:54:10 PM - Critical bpbrm(pid=4304) from client HCM-MAIL-MB2: FTL - snapshot preparation failed, status 156
6/8/2017 7:54:10 PM - Warning bpbrm(pid=4304) from client HCM-MAIL-MB2: WRN - Microsoft Information Store:\HCM DB04 is not frozen
6/8/2017 7:54:11 PM - Info bpfis(pid=5316) done. status: 156
6/8/2017 7:54:11 PM - end Exchange 14 Snapshot, Create Snapshot; elapsed time: 0:43:07
6/8/2017 7:54:11 PM - Info bpfis(pid=5316) done. status: 156: snapshot error encountered
6/8/2017 7:54:12 PM - Info bpbrm(pid=8338) Starting delete snapshot processing
6/8/2017 7:54:13 PM - Info bpfis(pid=21420) Backup started
6/8/2017 7:54:15 PM - Critical bpbrm(pid=8338) from client HCM-MAIL-MB2: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.hcm-mail-dag_1496923864.1.0
6/8/2017 7:54:16 PM - Info bpfis(pid=21420) done. status: 4207
6/8/2017 7:54:16 PM - end Parent Job; elapsed time: 0:43:12
6/8/2017 7:54:16 PM - Info bpfis(pid=21420) done. status: 4207: Could not fetch snapshot metadata or state files
6/8/2017 7:55:00 PM - end writing
Status 156
6/8/2017 7:55:00 PM - end Exchange 14 Snapshot, Create Snapshot; elapsed time: 0:43:56
6/8/2017 7:55:00 PM - begin Exchange 14 Snapshot, Stop On Error
Status 0
6/8/2017 7:55:00 PM - end Exchange 14 Snapshot, Stop On Error; elapsed time: 0:00:00
6/8/2017 7:55:00 PM - begin Exchange 14 Snapshot, Delete Snapshot
6/8/2017 7:55:01 PM - started process bpbrm (8338)
6/8/2017 7:55:05 PM - end writing
Status 4207
6/8/2017 7:55:05 PM - end Exchange 14 Snapshot, Delete Snapshot; elapsed time: 0:00:05
Status 156
6/8/2017 7:55:05 PM - end Parent Job; elapsed time: 0:44:01
snapshot error encountered (156)
=============
So, I try to backup HCM-MAIL-MB2 only (VMware backup) --> error code 6, 23 as my first post.
Then, I try to run backup DAG with VMware nbd mode, It seems that running but with very slow speed. The Application State Capture on HCM-MAIL-MB2:
=== log ===
6/9/2017 6:00:18 PM - Info nbjm(pid=7032) starting backup job (jobid=11767) for client HCM-MAIL-MB2.pvep.com.vn, policy hcm-mail-dag_VMware, schedule full
6/9/2017 6:00:18 PM - Info nbjm(pid=7032) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=11767, request id:{17BD3A27-B64D-4BEC-9FCA-B5B3D069AFA5})
6/9/2017 6:00:18 PM - requesting resource dedup_pool-stu
6/9/2017 6:00:18 PM - requesting resource masterserver.NBU_CLIENT.MAXJOBS.HCM-MAIL-MB2.pvep.com.vn
6/9/2017 6:00:18 PM - granted resource masterserver.NBU_CLIENT.MAXJOBS.HCM-MAIL-MB2.pvep.com.vn
6/9/2017 6:00:20 PM - estimated 0 Kbytes needed
6/9/2017 6:00:20 PM - begin Parent Job
6/9/2017 6:00:20 PM - begin Application State Capture, Step By Condition
Status 0
6/9/2017 6:00:20 PM - end Application State Capture, Step By Condition; elapsed time: 0:00:00
6/9/2017 6:00:20 PM - begin Application State Capture, Application State Capture
6/9/2017 6:43:17 PM - Critical ascc(pid=5380) Exchange: vfm_freeze: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze
6/9/2017 6:43:17 PM - Critical ascc(pid=5380) Exchange:
6/9/2017 6:43:17 PM - Info ascc(pid=5380) Exchange: snapshot preparation successful, with the following information: Found the Symantec VSS Provider installed on this VM.
6/9/2017 6:43:17 PM - Warning ascc(pid=5380) Exchange: snapshot preparation successful, with the following condition: It appears that the Symantec VSS Provider did not execute properly on the previous VM snapshot.
6/9/2017 6:43:17 PM - Critical ascc(pid=5380) Exchange: snapshot preparation failed, status 156
Status 13
6/9/2017 6:44:06 PM - end Application State Capture, Application State Capture; elapsed time: 0:43:46
Status 13
6/9/2017 6:44:06 PM - end Parent Job; elapsed time: 0:43:46
file read failed (13)
======
on MB1:
=== log ===
6/9/2017 6:00:18 PM - Info nbjm(pid=7032) starting backup job (jobid=11766) for client HCM-MAIL-MB1.pvep.com.vn, policy hcm-mail-dag_VMware, schedule full
6/9/2017 6:00:18 PM - Info nbjm(pid=7032) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=11766, request id:{426EA02C-D18F-43D4-8A93-66B4AB05A9DC})
6/9/2017 6:00:18 PM - requesting resource dedup_pool-stu
6/9/2017 6:00:18 PM - requesting resource masterserver.NBU_CLIENT.MAXJOBS.HCM-MAIL-MB1.pvep.com.vn
6/9/2017 6:00:18 PM - granted resource masterserver.NBU_CLIENT.MAXJOBS.HCM-MAIL-MB1.pvep.com.vn
6/9/2017 6:00:18 PM - estimated 0 Kbytes needed
6/9/2017 6:00:18 PM - begin Parent Job
6/9/2017 6:00:18 PM - begin Application State Capture, Step By Condition
Status 0
6/9/2017 6:00:18 PM - end Application State Capture, Step By Condition; elapsed time: 0:00:00
6/9/2017 6:00:18 PM - begin Application State Capture, Application State Capture
6/9/2017 6:00:31 PM - Info ascc(pid=5372) Exchange: snapshot preparation successful, with the following information: Found the Symantec VSS Provider installed on this VM.
6/9/2017 6:00:31 PM - Warning ascc(pid=5372) Exchange: snapshot preparation successful, with the following condition: It appears that the Symantec VSS Provider did not execute properly on the previous VM snapshot.
6/9/2017 6:00:31 PM - Warning ascc(pid=5372) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\HCM Archive' is not supported because volume <L:\> is on a GPT disk and is not supported.
6/9/2017 6:00:31 PM - Warning ascc(pid=5372) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\HCM Archive' is not supported because volume <M:\> is on a GPT disk and is not supported.
6/9/2017 6:00:32 PM - Warning ascc(pid=5372) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\HCM Archive' is not supported because volume <L:\> is on a GPT disk and is not supported.
6/9/2017 6:00:32 PM - Warning ascc(pid=5372) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\HCM DB01' is not supported because volume <D:\> is on a GPT disk and is not supported.
6/9/2017 6:00:32 PM - Warning ascc(pid=5372) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\HCM DB01' is not supported because volume <E:\> is on a GPT disk and is not supported.
6/9/2017 6:00:32 PM - Warning ascc(pid=5372) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\HCM DB01' is not supported because volume <D:\> is on a GPT disk and is not supported.
6/9/2017 6:00:32 PM - Warning ascc(pid=5372) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\HCM DB02' is not supported because volume <F:\> is on a GPT disk and is not supported.
6/9/2017 6:00:32 PM - Warning ascc(pid=5372) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\HCM DB02' is not supported because volume <G:\> is on a GPT disk and is not supported.
6/9/2017 6:00:32 PM - Warning ascc(pid=5372) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\HCM DB02' is not supported because volume <F:\> is on a GPT disk and is not supported.
6/9/2017 6:00:33 PM - Info ascc(pid=5372) Exchange: Host HCM-MAIL-MB1.pvep.com.vn successfully protected Exchange and cataloged under HCM-MAIL-MB1
Status 1
6/9/2017 6:01:22 PM - end Application State Capture, Application State Capture; elapsed time: 0:01:04
Status 1
6/9/2017 6:01:22 PM - end Parent Job; elapsed time: 0:01:04
the requested operation was partially successful (1)
The job was successfully completed, but some files may have been
busy or inaccessible. See the problems report or the client's logs for more details.
===
Lowell_Palecek: Thank you, I will check
Marianne:
What is configured as VM backup host?
--> Mediaserver
Can you confirm that datastores are zoned/mapped to the backup host and can be seen at OS-level?
--> Yes, they all were mapped to mediaserver
Was SAN transport mode explicitly selected in the policy?
Have you tried nbd?
--> I tried with nbd and find the error on Application State Capture job as above (the backup job still writting now with slow speed)
Are other VMs backing up fine?
If so, which transport mode?
--> Yes, I have some other VMs still backing up fine with san transport mode
Are you aware that NBU 7.6.x ran out of support 4 months ago?
--> No, I dont know this info before read your note.
![]()
Thank you all.
NDT
