Video Screencast Help

VM backup alwayes finished with "the backup failed to back up the requested files(6)" status

Created: 07 Jun 2014 • Updated: 04 Jul 2014 | 13 comments
This issue has been solved. See solution.

Hi all,

I still can't take vm backup for some client inside vshpere 5.5,when job start i recieved the below error's

 

6/7/2014 5:00:48 PM - Error bpbrm(pid=33007) from client XXXXX: ERR - Error opening the snapshot disks using given transport mode: Status 23
6/7/2014 5:00:49 PM - Critical bpbrm(pid=33007) from client XXXXX: FTL - cleanup() failed, status 6   

6/7/2014 5:02:00 PM - Info bpbkar(pid=0) done. status: 6: the backup failed to back up the requested files

 

i have a full admin permission in the vcenter,also i upgraded the master server to 7.6.0.2 and  appliance to 2.6.0.2

so please advice.

 

Operating Systems:

Comments 13 CommentsJump to latest comment

Riaan.Badenhorst's picture

Which transport method did you configure in the policy? The error below indicates that NetBackup could not reach the snapshot. This could be because you might have chosen SAN and the luns are not accessible to the backup host, or potentially the ports required to access the ESX server aren't open.

 

6/7/2014 5:00:48 PM - Error bpbrm(pid=33007) from client XXXXX: ERR - Error opening the snapshot disks using given transport mode: Status 23

 

 

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Marianne's picture

Please tell us all the steps that you have followed to configure VMware backup.

There is more to VMware backups than just supported NBU version.

See Overview of VMware tasks in NetBackup for VMware Administrator's Guide

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mohamedkhattab's picture

Hi all,

i tried all transport type but i'm still facing the same problem

 

Marianne,i follow up the steps inside the admin guide but without success.

 

Riaan.Badenhorst's picture

Turn up the logging and post the bpfis log.
 

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Mohamedkhattab's picture

10:19:19.538 [9480.11352] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_VDI -clnt shpsymbk02 -vm_client 169.254.1.152 -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
10:19:19.585 [9480.11352] <4> bpfis: set vm client 169.254.1.152 as ol_client_name
10:19:19.600 [9480.11352] <4> bpfis: Starting keep alive thread.
10:19:19.616 [9480.11352] <4> bpfis: INF - BACKUP START 9480
10:19:19.632 [9480.11352] <4> bpfis: Starting keep alive thread.
10:19:19.632 [9480.11352] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
10:19:26.059 [4812.7268] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_VDI -clnt shpsymbk02 -vm_client 169.254.1.152 -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
10:19:26.059 [4812.7268] <4> bpfis: set vm client 169.254.1.152 as ol_client_name
10:19:26.059 [4812.7268] <4> bpfis: Starting keep alive thread.
10:19:26.059 [4812.7268] <4> bpfis: INF - BACKUP START 4812
10:19:26.059 [4812.7268] <4> bpfis: Starting keep alive thread.
10:19:26.059 [4812.7268] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
10:23:04.306 [10620.848] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_VDI -clnt shpsymbk02 -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
10:23:04.306 [10620.848] <4> bpfis: set vm client XXXXX as ol_client_name
10:23:04.306 [10620.848] <4> bpfis: Starting keep alive thread.
10:23:04.306 [10620.848] <4> bpfis: INF - BACKUP START 10620
10:23:04.321 [10620.848] <4> bpfis: Starting keep alive thread.
10:23:04.321 [10620.848] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:28:50.236 [1184.11788] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:28:50.236 [1184.11788] <4> bpfis: set vm client XXXXXX as ol_client_name
11:28:50.236 [1184.11788] <4> bpfis: Starting keep alive thread.
11:28:50.236 [1184.11788] <4> bpfis: INF - BACKUP START 1184
11:28:50.439 [1184.11788] <4> bpfis: Starting keep alive thread.
11:28:50.439 [1184.11788] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:28:52.233 [5784.8244] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:28:52.233 [5784.8244] <4> bpfis: set vm client XXXXX as ol_client_name
11:28:52.233 [5784.8244] <4> bpfis: Starting keep alive thread.
11:28:52.233 [5784.8244] <4> bpfis: INF - BACKUP START 5784
11:28:52.389 [5784.8244] <4> bpfis: Starting keep alive thread.
11:28:52.389 [5784.8244] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:30:43.883 [11660.12156] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:30:43.883 [11660.12156] <4> bpfis: set vm client XXXXX as ol_client_name
11:30:43.883 [11660.12156] <4> bpfis: Starting keep alive thread.
11:30:43.883 [11660.12156] <4> bpfis: INF - BACKUP START 11660
11:30:43.899 [11660.12156] <4> bpfis: Starting keep alive thread.
11:30:43.899 [11660.12156] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:30:45.662 [12104.9556] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX-copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:30:45.662 [12104.9556] <4> bpfis: set vm client XXXXX as ol_client_name
11:30:45.662 [12104.9556] <4> bpfis: Starting keep alive thread.
11:30:45.662 [12104.9556] <4> bpfis: INF - BACKUP START 12104
11:30:45.677 [12104.9556] <4> bpfis: Starting keep alive thread.
11:30:45.677 [12104.9556] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:30:46.801 [9936.12120] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX-copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:30:46.801 [9936.12120] <4> bpfis: set vm client XXXXX as ol_client_name
11:30:46.801 [9936.12120] <4> bpfis: Starting keep alive thread.
11:30:46.801 [9936.12120] <4> bpfis: INF - BACKUP START 9936
11:30:46.941 [9936.12120] <4> bpfis: Starting keep alive thread.
11:30:46.941 [9936.12120] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:30:47.815 [6692.9164] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:30:47.815 [6692.9164] <4> bpfis: set vm client XXXXX as ol_client_name
11:30:47.815 [6692.9164] <4> bpfis: Starting keep alive thread.
11:30:47.815 [6692.9164] <4> bpfis: INF - BACKUP START 6692
11:30:48.017 [6692.9164] <4> bpfis: Starting keep alive thread.
11:30:48.017 [6692.9164] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:30:48.985 [8800.11008] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:30:48.985 [8800.11008] <4> bpfis: set vm client XXXXX as ol_client_name
11:30:48.985 [8800.11008] <4> bpfis: Starting keep alive thread.
11:30:48.985 [8800.11008] <4> bpfis: INF - BACKUP START 8800
11:30:48.985 [8800.11008] <4> bpfis: Starting keep alive thread.
11:30:48.985 [8800.11008] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:38:17.990 [8164.10604] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:38:17.990 [8164.10604] <4> bpfis: set vm client XXXXX as ol_client_name
11:38:17.990 [8164.10604] <4> bpfis: Starting keep alive thread.
11:38:17.990 [8164.10604] <4> bpfis: INF - BACKUP START 8164
11:38:18.005 [8164.10604] <4> bpfis: Starting keep alive thread.
11:38:18.005 [8164.10604] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:38:20.205 [11332.11088] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:38:20.205 [11332.11088] <4> bpfis: set vm client XXXXX as ol_client_name
11:38:20.205 [11332.11088] <4> bpfis: Starting keep alive thread.
11:38:20.205 [11332.11088] <4> bpfis: INF - BACKUP START 11332
11:38:20.205 [11332.11088] <4> bpfis: Starting keep alive thread.
11:38:20.205 [11332.11088] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:38:21.375 [10548.11472] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA 02 -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:38:21.375 [10548.11472] <4> bpfis: set vm client XXXXXX as ol_client_name
11:38:21.375 [10548.11472] <4> bpfis: Starting keep alive thread.
11:38:21.375 [10548.11472] <4> bpfis: INF - BACKUP START 10548
11:38:21.375 [10548.11472] <4> bpfis: Starting keep alive thread.
11:38:21.375 [10548.11472] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:38:22.280 [10100.10600] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:38:22.280 [10100.10600] <4> bpfis: set vm client XXXXX as ol_client_name
11:38:22.280 [10100.10600] <4> bpfis: Starting keep alive thread.
11:38:22.280 [10100.10600] <4> bpfis: INF - BACKUP START 10100
11:38:22.280 [10100.10600] <4> bpfis: Starting keep alive thread.
11:38:22.280 [10100.10600] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
11:38:22.342 [10640.9268] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
11:38:22.342 [10640.9268] <4> bpfis: set vm client XXXXX as ol_client_name
11:38:22.342 [10640.9268] <4> bpfis: Starting keep alive thread.
11:38:22.342 [10640.9268] <4> bpfis: INF - BACKUP START 10640
11:38:22.342 [10640.9268] <4> bpfis: Starting keep alive thread.
11:38:22.342 [10640.9268] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
12:09:59.186 [9396.8224] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
12:09:59.186 [9396.8224] <4> bpfis: set vm client XXXXX as ol_client_name
12:09:59.186 [9396.8224] <4> bpfis: Starting keep alive thread.
12:09:59.186 [9396.8224] <4> bpfis: INF - BACKUP START 9396
12:09:59.186 [9396.8224] <4> bpfis: Starting keep alive thread.
12:09:59.186 [9396.8224] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
12:10:01.042 [8720.5648] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
12:10:01.042 [8720.5648] <4> bpfis: set vm client XXXXX as ol_client_name
12:10:01.042 [8720.5648] <4> bpfis: Starting keep alive thread.
12:10:01.042 [8720.5648] <4> bpfis: INF - BACKUP START 8720
12:10:01.058 [8720.5648] <4> bpfis: Starting keep alive thread.
12:10:01.058 [8720.5648] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
12:13:16.248 [10644.552] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
12:13:16.248 [10644.552] <4> bpfis: set vm client XXXXX as ol_client_name
12:13:16.248 [10644.552] <4> bpfis: Starting keep alive thread.
12:13:16.248 [10644.552] <4> bpfis: INF - BACKUP START 10644
12:13:16.248 [10644.552] <4> bpfis: Starting keep alive thread.
12:13:16.248 [10644.552] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
12:15:06.229 [7408.9948] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
12:15:06.229 [7408.9948] <4> bpfis: set vm client XXXXX as ol_client_name
12:15:06.229 [7408.9948] <4> bpfis: Starting keep alive thread.
12:15:06.229 [7408.9948] <4> bpfis: INF - BACKUP START 7408
12:15:06.229 [7408.9948] <4> bpfis: Starting keep alive thread.
12:15:06.229 [7408.9948] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
12:19:02.744 [10724.10128] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
12:19:02.744 [10724.10128] <4> bpfis: set vm client XXXXX as ol_client_name
12:19:02.744 [10724.10128] <4> bpfis: Starting keep alive thread.
12:19:02.744 [10724.10128] <4> bpfis: INF - BACKUP START 10724
12:19:02.744 [10724.10128] <4> bpfis: Starting keep alive thread.
12:19:02.744 [10724.10128] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
12:19:04.741 [11312.9220] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe deletedb -noserverstate -policy VM_REMEDY -clnt AAAAA -vm_client XXXXX -copy 1 -prev_bli_incr 0 -vm_bli_cleanup
12:19:04.741 [11312.9220] <4> bpfis: set vm client XXXXX as ol_client_name
12:19:04.741 [11312.9220] <4> bpfis: Starting keep alive thread.
12:19:04.741 [11312.9220] <4> bpfis: INF - BACKUP START 11312
12:19:04.741 [11312.9220] <4> bpfis: Starting keep alive thread.
12:19:04.741 [11312.9220] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
16:00:21.769 [2348.9944] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe create -owner NBU -fso -WOFB -fim VSS:prov_type=1,snap_attr=0,max_snapshots=1 -id KFHSANWK_1402232402 -nbu_version 123731970 E:\Program Files\Veritas\kms
16:00:21.785 [2348.9944] <2> bpfis main: received FIM as [43] VSS:prov_type=1,snap_attr=0,max_snapshots=1
16:00:21.801 [2348.9944] <2> bpfis main: VSS provider type: 1
16:00:21.925 [2348.9944] <4> bpfis: Starting keep alive thread.
16:00:21.925 [2348.9944] <4> bpfis: INF - BACKUP START 2348
16:00:21.925 [2348.9944] <2> check_special_names: got path entry as :<E:\Program Files\Veritas\kms>
16:00:21.925 [2348.9944] <2> check_special_names: after conversion returning :<E:\Program Files\Veritas\kms>
16:00:22.159 [2348.9944] <8> bpfis: WRN - VfMS error 10; see following messages:
16:00:22.159 [2348.9944] <8> bpfis: WRN - Non-fatal method error was reported
16:00:22.159 [2348.9944] <8> bpfis: WRN -
16:00:22.159 [2348.9944] <8> bpfis: WRN - VfMS method error 0; see following message:
16:00:22.159 [2348.9944] <8> bpfis: WRN -
16:00:22.191 [2348.9944] <8> bpfis: WRN - VfMS error 10; see following messages:
16:00:22.191 [2348.9944] <8> bpfis: WRN - Non-fatal method error was reported
16:00:22.191 [2348.9944] <8> bpfis: WRN -
16:00:22.191 [2348.9944] <8> bpfis: WRN - VfMS method error 0; see following message:
16:00:22.191 [2348.9944] <8> bpfis: WRN -
16:00:22.971 [2348.9944] <4> bpfis: INF - FIS_ID=KFHSANWK_1402232402
16:00:22.986 [2348.9944] <4> bpfis: parameter client_type 13, fis_accl 0, fis_accl_cksv -1, SNAPSHOT_IS_HERE 1
16:00:22.986 [2348.9944] <8> bpfis: Failed to open flush NetBackup Change Journal databases mutex
16:00:22.986 [2348.9944] <4> bpfis main: read_registry_dw_value for VSS_CONCURRENT_OPERATIONS: return status 2, return value 0
16:00:22.986 [2348.9944] <4> bpfis main: VSS Snapshot create Mutex lock acquired
16:00:22.986 [2348.9944] <4> bpfis: INF - Preparing freeze of E:\ using snapshot method VSS.
16:00:22.986 [2348.9944] <4> bpfis: INF - Created mount point E:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_E__2348_1
16:00:32.487 [2348.9944] <4> bpfis: INF - Deleted mount point E:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_E__2348_1
16:00:32.502 [2348.9944] <4> try_vss_unlockmutex: VSS Snapshot Mutex Unlock
16:00:32.502 [2348.9944] <2> determine_vss_provider_type: Get the VSS provider type used for the snapshot
16:00:32.502 [2348.9944] <2> determine_vss_provider_type: VSS system provider
16:00:32.502 [2348.9944] <4> bpfis: INF - REMAP FILE BACKUP E:\Program Files\Veritas\kms USING \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7\Program Files\Veritas\kms OPTIONS:ALT_PATH_PREFIX=E:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_2348_1,FITYPE=MIRROR,MNTPOINT=E:\,FSTYPE=NTFS
16:00:32.534 [2348.9944] <2> getFileName:  FileName is [E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\KFHSANWK_1402232402_copy1.lock]
16:00:32.534 [2348.9944] <2> getFileName:  FileName is [E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\KFHSANWK_1402232402_copy1.lock]
16:00:32.534 [2348.9944] <2> addSnapshotReference: SnapShot Locked <KFHSANWK_1402232402>
16:00:32.534 [2348.9944] <2> addReference:    Added  refferent jobid[0] pid[2348]
16:00:32.534 [2348.9944] <2> writeSnapshotLockFile:    Writing type[0] refcount[1]
16:00:32.534 [2348.9944] <2> writeSnapshotLockFile:    Writing Flags [0] [0]
16:00:32.534 [2348.9944] <2> writeSnapshotLockFile:   Writing Last addReffernt Time [Thu Jan 01 03:00:00 1970
]
16:00:32.534 [2348.9944] <2> writeSnapshotLockFile:   Writing Last Hostname []
16:00:32.534 [2348.9944] <2> writeSnapshotLockFile:    Writing jobid[0] pid [2348]
16:00:32.565 [2348.9944] <2> addSnapshotReference: SnapShot unlockLocked <KFHSANWK_1402232402>
16:00:32.565 [2348.9944] <4> bpfis: Starting keep alive thread.
16:00:32.705 [2348.9944] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
16:00:34.718 [2348.9944] <8> bpfis: WRN - Error closing stdout
16:00:36.200 [7844.9992] <2> logparams: bpfis delete -id KFHSANWK_1402232402 -copy 1 -WOFB
16:00:36.200 [7844.9992] <4> bpfis: Starting keep alive thread.
16:00:36.200 [7844.9992] <4> bpfis: Acquiring snapshot lock:retry count [0]
16:00:36.200 [7844.9992] <2> getFileName:  FileName is [E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\KFHSANWK_1402232402_copy1.lock]
16:00:36.200 [7844.9992] <2> getFileName:  FileName is [E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\KFHSANWK_1402232402_copy1.lock]
16:00:36.200 [7844.9992] <2> readSnapshotLockFile:    Read type[0] refcount[1]
16:00:36.200 [7844.9992] <2> readSnapshotLockFile:    Read Flags [0] [0]
16:00:36.200 [7844.9992] <2> readSnapshotLockFile:   Read Last addReffernt Time [Thu Jan 01 03:00:00 1970
]
16:00:36.200 [7844.9992] <2> readSnapshotLockFile:   Read hostname []
16:00:36.200 [7844.9992] <2> readSnapshotLockFile:    Read jobid[0] pid [2348]
16:00:36.200 [7844.9992] <2> cleanup:  Deleting ref type jobid[0] pid [2348]
16:00:36.200 [7844.9992] <4> bpfis: INF - BACKUP START 7844
16:00:36.215 [7844.9992] <8> bpfis: WRN - VfMS error 10; see following messages:
16:00:36.215 [7844.9992] <8> bpfis: WRN - Non-fatal method error was reported
16:00:36.215 [7844.9992] <8> bpfis: WRN -
16:00:36.215 [7844.9992] <8> bpfis: WRN - VfMS method error 0; see following message:
16:00:36.215 [7844.9992] <8> bpfis: WRN -
16:00:36.215 [7844.9992] <8> bpfis: WRN - VfMS error 10; see following messages:
16:00:36.215 [7844.9992] <8> bpfis: WRN - Non-fatal method error was reported
16:00:36.215 [7844.9992] <8> bpfis: WRN -
16:00:36.215 [7844.9992] <8> bpfis: WRN - VfMS method error 0; see following message:
16:00:36.215 [7844.9992] <8> bpfis: WRN -
16:00:36.746 [7844.9992] <4> bpfis: INF - Thawing E:\ using snapshot method VSS.
16:00:36.902 [7844.9992] <4> bpfis: INF - do_thaw return value: 0
16:00:36.902 [7844.9992] <4> bpfis: INF - BPFIS MESSAGE Routing to stream based backup for windows open file backup case, generating remap directive

16:00:36.902 [7844.9992] <4> bpfis: INF - REMAP FILE BACKUP E:\Program Files\Veritas\kms
16:00:36.902 [7844.9992] <4> bpfis: Starting keep alive thread.
16:00:36.902 [7844.9992] <2> deleteReference:    reference not found in the list
16:00:36.902 [7844.9992] <4> bpfis: Delete reference: status [-4]
16:00:36.902 [7844.9992] <2> writeSnapshotLockFile:    Writing type[2] refcount[0]
16:00:36.902 [7844.9992] <2> writeSnapshotLockFile:    Writing Flags [0] [0]
16:00:36.902 [7844.9992] <2> writeSnapshotLockFile:   Writing Last addReffernt Time [Thu Jan 01 03:00:00 1970
]
16:00:36.902 [7844.9992] <2> writeSnapshotLockFile:   Writing Last Hostname []
16:00:36.933 [7844.9992] <2> getFileName:  FileName is [E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\KFHSANWK_1402232402_copy1.lock]
16:00:36.933 [7844.9992] <2> getFileName:  FileName is [E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\KFHSANWK_1402232402_copy1.lock]
16:00:36.933 [7844.9992] <2> unlockSnapshot:    file[E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\KFHSANWK_1402232402_copy1.lock] : zero reference count
16:00:36.933 [7844.9992] <4> bpfis: Released snapshot lock: status [0]
16:00:36.933 [7844.9992] <4> do_post_processing: Deleting snapshot lock files from client for id [KFHSANWK_1402232402] and copy_number [1]
16:00:36.933 [7844.9992] <2> getFileName:  FileName is [E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\KFHSANWK_1402232402_copy1.lock]
16:00:36.933 [7844.9992] <2> getFileName:  FileName is [E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\KFHSANWK_1402232402_copy1.lock]
16:00:36.933 [7844.9992] <2> deleteSnapshotLockFile:    file[E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\KFHSANWK_1402232402_copy1.lock] deleted: status[0]
16:00:37.011 [7844.9992] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed

 

Marianne's picture

Please show us the policy config.
On master server:
bppllist <policy-name> -L

The next log that we will need is vxms log.

See in Troubleshooting chapter of NBU for VMware manual (chapter 14):
To configure VxMS logging on a Linux backup host.

Please copy logs to .txt files (e.g. vxms.txt) and upload as File attachments.

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mohamedkhattab's picture

bpplist result:

 

Policy Name:       VM_REMEDY
Options:           0x0
template:          FALSE
audit_reason:         ?
Names:             (none)
Policy Type:       VMware (40)
Active:            yes
Effective date:    06/03/2013 09:54:02
File Restore Raw:  yes
Application Consistent:  yes
Mult. Data Stream: no
Perform Snapshot Backup:   yes
Snapshot Method:           VMware_v2
Snapshot Method Arguments: Virtual_machine_backup=2,disable_quiesce=1,drive_selection=0,enable_vClou
d=0,exclude_swap=1,file_system_optimization=1,ignore_irvm=1,multi_org=1,nameuse=1,post_events=0,rHz=
10,rLim=10,rTO=0,serverlist=,skipnodisk=0,snapact=2,trantype=nbd:hotadd:san:nbdssl
Perform Offhost Backup:    yes
Backup Copy:               0
Use Data Mover:            no
Data Mover Type:           -1
Use Alternate Client:      no
Alternate Client Name:     shpsymbk02
Use Virtual Machine:      1
Hyper-V Server Name:     (none)
Enable Instant Recovery:   no
Policy Priority:   0
Max Jobs/Policy:   Unlimited
Disaster Recovery: 0
Collect BMR Info:  no
Keyword:           (none specified)
Data Classification:       -
Residence is Storage Lifecycle Policy:    no
Client Encrypt:    no
Checkpoint:        no
Residence:         stu_disk_shpsymbk02
Volume Pool:       HO_Monthly1
Server Group:      *ANY*
Granular Restore Info:  no
Exchange Source attributes:              no
Exchange DAG Preferred Server: (none defined)
Application Discovery:      no
Discovery Lifetime:      28800 seconds
ASC Application and attributes: (none defined)
Generation:      136
Ignore Client Direct:  yes
Enable Metadata Indexing:  no
Index server name:  NULL
Use Accelerator:  no
Client/HW/OS/Pri/DMI/CIT:  SHVRMDAP01 vmx-08 windows8Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  SHVRMDWB01 vmx-08 windows8Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  SHVRMDWB02 vmx-08 windows8Server64Guest 0 0 0 0 ?
Include:           ALL_LOCAL_DRIVES
Schedule:              Monthly
  Type:                FULL (0)
  Calendar sched: Enabled
   Included Dates-----------
       No days of week entered
      Day 28 of month
   Excluded Dates----------
      No specific exclude dates entered
      No exclude days of week entered
  Retention Level:     0 (1 week)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  PFI Recovery:        0
  Maximum MPX:         1
  Number Copies:       1
  Fail on Error:       0
  Residence:           SLP_Monthly
  Volume Pool:         (same as policy volume pool)
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         1
  Schedule indexing:   0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      018:00:00  029:00:00   018:00:00  029:00:00
   Monday      018:00:00  029:00:00   042:00:00  053:00:00
   Tuesday     018:00:00  029:00:00   066:00:00  077:00:00
   Wednesday   018:00:00  029:00:00   090:00:00  101:00:00
   Thursday    018:00:00  029:00:00   114:00:00  125:00:00
   Friday      018:00:00  029:00:00   138:00:00  149:00:00
   Saturday    018:00:00  029:00:00   162:00:00  173:00:00 005:00:00
Schedule:              Weekly
  Type:                FULL (0)
  Calendar sched: Enabled
   Included Dates-----------
      Friday, Week 1
      Friday, Week 2
      Friday, Week 3
      Friday, Week 4
      Friday, Week 5
   Excluded Dates----------
      No specific exclude dates entered
      No exclude days of week entered
  Retention Level:     0 (1 week)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  PFI Recovery:        0
  Maximum MPX:         1
  Number Copies:       1
  Fail on Error:       0
  Residence:           SLP_Weekly
  Volume Pool:         (same as policy volume pool)
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         1
  Schedule indexing:   0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      018:00:00  037:40:00   018:00:00  037:40:00
   Monday      018:00:00  037:40:00   042:00:00  061:40:00
   Tuesday     018:00:00  037:40:00   066:00:00  085:40:00
   Wednesday   018:00:00  037:40:00   090:00:00  109:40:00
   Thursday    018:00:00  037:40:00   114:00:00  133:40:00
   Friday      018:00:00  037:40:00   138:00:00  157:40:00
   Saturday    018:00:00  037:40:00   162:00:00  181:40:00 013:40:00

Riaan.Badenhorst's picture

Do all these clients fail or just one?

 

Client/HW/OS/Pri/DMI/CIT:  SHVRMDAP01 vmx-08 windows8Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  SHVRMDWB01 vmx-08 windows8Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  SHVRMDWB02 vmx-08 windows8Server64Guest 0 0 0 0 ?

 

If only one or some are failing, check if they are in the same datastore or not. Also check if they are on the same esx or not. The bpfis log shows no error in the snapshot creation, if you check in vcenter while running the backup you'll probably notice all three get there snapshot created, the only issue is NetBackup cannot get to where the snapshot is located.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Marianne's picture

I see 2 things in your policy:

Application Consistent:  yes
...
Alternate Client Name:     shpsymbk02

"Application Consistent" means you want to backup one the following: Exchange, SQL or Sharepoint.
This type of backup needs the NBU client software installed on these clients and some additional config on these clients.

Sure this is what you want to do?
If so, check NBU for VMware guide as well as the appropriate Agent Guide for additional config steps.
If not, remove this option.

About "Alternate Client Name" - is this your Appliance?
We do not really have insight into backup destination because all schedules are controlled by SLPs.
 

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mohamedkhattab's picture

I removed the application Consistent option,also note the shpsymbk02 is my appliance.

i checked the VMware guide and followed all the configuration steps but without success.

any other solution to fix the issue or not?

Marianne's picture

As per my post above:

The next log that we will need is vxms log.

See in Troubleshooting chapter of NBU for VMware manual (chapter 14):
To configure VxMS logging on a Linux backup host.

Please copy logs to .txt files (e.g. vxms.txt) and upload as File attachments.

Please also share screemshots of SLP config.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Stuart Green's picture

Check in vSphere against your hosts that they licensed for vStorage API feature.

Crucial that the vsphere permission is added at the vcenter server object top level and not at any other object level and set to Propogate to children.

Here's another gotcha. You might have you permission inserted at a lower level object for No Access - overriding the top level.

Why? This is actually handy in a vSphere environment with global datacenters but may be backing up using different products in different geographies relative to vStorage. So add the NetBackup for Vmware credentials user as No Access on datacenters you dont need access to enumerate for your VM backups, and you will only see the VM's you want to backup and not see others in the NetBackup VM selection dialog of the VMware policy.

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

SOLUTION