04-23-2013 01:52 AM
Hi guys,
Hoping someone can help me with this, I have hunted around forum/internet and tried various things ver the last couple of days but it seems the 156 error is a bit generic and could mean many things. The error I am getting is:-
Could anyone shed any light on this please? Am new to this system so not really sure where to start!
Many Thanks
John
Solved! Go to Solution.
04-24-2013 01:41 AM
I have not had a look at the bpfis log yet...
What is the size of the volume that you need to backup?
There may be a problem with space on other drives to create the snapshot.
See this TN for ways to test the actual snapshot with bpfis and vssadmin: http://www.symantec.com/docs/TECH47808
04-23-2013 05:53 AM
1) Confrim WOFB for the client is using VSS ( instead of VSP )
2) Look in the application event viewer for any ESE or VSS errors
3) Please upload bpfis from the client
4) From a command line on the client, please run the following and reply back with the output :
vssadmin list writers
vssadmin list providers
04-23-2013 07:28 AM
Hi Dyneshia,
Thanks for the reply, here goes:-
1) Yep using VSS
2) There are no errors or warnings that mention ESE or VSS
3) Sorry not sure how to do this, did a Google search and plenty of instances of people doing it but no mention of how! I have found the bpfis.exe but do not see a log export option in parameters etc. any chance of a quick "how to" please?
4) vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
04-23-2013 08:14 AM
On the client create :
<install path> veritas\netbackup\logs\bpfis
Increase verobisty : on the Client- Open up the Backup Archive Restore GUI -> file - > client properties -> troubleshooting ->set general to 2 and verbosity to 5.
Run through the issue and set Verbosity back to 0.
upload the bpsfis
04-23-2013 08:16 AM
On more thing ( sorry .... just reread and see this is a flash backup ) do the same on the backup host . However you can increase the verbosity through the server host properties
04-23-2013 08:20 AM
Also , as a test , create snapshot manually on the client using vcentre
04-23-2013 08:26 AM
Beautiful, thanks will set this up to run on tonights backup and report back tomorrow.
04-23-2013 08:30 AM
This is a physical machine I am backing up so no vcentre I'm afraid!
04-23-2013 09:50 AM
Ok, np. Just ignore the vcneter and storage server ;)
On the client create :
<install path> veritas\netbackup\logs\bpfis
Increase verbosity : on the Client- Open up the Backup Archive Restore GUI -> file - > client properties -> troubleshooting ->set general to 2 and verbosity to 5.
Run through the issue and set Verbosity back to 0.
upload the bpfis
04-24-2013 01:16 AM
Beautiful, thanks, one bpfis log as requested:-
04-24-2013 01:41 AM
I have not had a look at the bpfis log yet...
What is the size of the volume that you need to backup?
There may be a problem with space on other drives to create the snapshot.
See this TN for ways to test the actual snapshot with bpfis and vssadmin: http://www.symantec.com/docs/TECH47808
04-24-2013 02:24 AM
Hi Marianne,
Thanks for the thoughts, I have run through that test creating and deleting the snapshots and it all seems to work successfully so guess that's all ok?
04-24-2013 06:03 AM
I think Marianne might be on the right track regarding the size.
From your bpfis log :
22:00:30.333 [7056.7504] <2> onlfi_vfms_logf: snapshot services: vss:Tue Apr 23 2013 22:00:30.333000 <Thread id - 7504> VSS API ERROR:- API [IsVolumeSupported] return val = 80042308 [VSS_E_OBJECT_NOT_FOUND]
22:00:30.333 [7056.460] <2> onlfi_vfms_logf: snapshot services: fivsp:Tue Apr 23 2013 22:00:30.333000 VspFiCoordinator::interpose cant interpose due to volume [\\.\PHYSICALDRIVE2] infn not found
22:00:30.333 [7056.7504] <2> onlfi_vfms_logf: snapshot services: vss:Tue Apr 23 2013 22:00:30.333000 <Thread id - 7504> VSS API ERROR:- API [IsVolumeSupported] return val = 80042308 [VSS_E_OBJECT_NOT_FOUND]
22:00:30.333 [7056.460] <2> onlfi_vfms_logf: snapshot services: fivsp:Tue Apr 23 2013 22:00:30.333000 VspFiCoordinator::interpose cant interpose due to open volume [UDID##HP##HSV##5000-1FE1-5023-DC00##6001-4380-05DE-7859-0000-8000-0164-0000] failed
22:00:41.817 [7056.460] <16> bpfis main: FTL - snapshot creation failed, status 156
22:00:41.817 [7056.460] <2> onlfi_thaw: fim=auto
22:00:41.817 [7056.460] <2> onlfi_thaw: fim=VSS
22:00:41.817 [7056.460] <4> onlfi_thaw: Thawing \\.\D:\ using snapshot method VSS.
22:00:41.817 [7056.460] <8> onlfi_thaw: \\.\D:\ is not frozen
22:00:41.817 [7056.460] <4> onlfi_thaw: Thawing \\.\E:\ using snapshot method VSS.
22:00:41.817 [7056.460] <8> onlfi_thaw: \\.\E:\ is not frozen
22:00:41.817 [7056.460] <2> onlfi_thaw: fim=VSP
22:00:41.817 [7056.460] <2> onlfi_thaw: fim=Hyper-V
22:00:41.817 [7056.460] <2> onlfi_thaw: fim=VMware
22:00:41.817 [7056.460] <2> onlfi_thaw: fim=NAS_Snapshot
22:00:41.817 [7056.460] <2> onlfi_thaw: fim=VSS_Writer
22:00:41.817 [7056.460] <8> bpfis Exit: WRN - snapshot delete returned status 20
22:00:41.833 [7056.460] <2> ol_cleanup: removing C:\Program Files\Veritas\NetBackup\temp\INT-WIN-GEMINI-FLASH+7056+1.std_filelist
22:00:41.833 [7056.460] <2> onlfi_vfms_logf: snapshot services: improper disposition parameter.
Questions :
1) What OS is this running on ?
2) Version of NBU ?
3) Do you see ANY errors in the event viewer during the time of the backup ?
4) upload the policy output : netbackup\bin\admincmd\bppllist <policy name> -L
This may be some help : http://www.symantec.com/docs/TECH129884
04-24-2013 07:24 AM
The Shadow copies are set to create on a seperate drive that is only used for them and is currently has 232Gb free space out of 255Gb. Disk drive we are backing up is 1.4Tb used on a 2Tb drive so is that too small? Looking at that link it suggests 1:5 ratio if I am reading it right?
04-24-2013 07:25 AM
Just odd as Shadow copies are working fine it is just the back ups failing
04-24-2013 07:32 AM
1) The server is 2003 R2
2) Do you mean the NetBackup client version if so it is 6.5.4?
3) No there is only one error since 5 pm last night (backups run at 10pm) and it is just a "Windows saved user ************ registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use." so unrelated
4) attached
04-24-2013 07:36 AM
04-24-2013 07:46 AM
I could change it for tonight and see what happens, strange though as policy hasn't changed for years! Will try anything at this point though!
04-24-2013 08:13 AM
The policy may not have changed, but your data is consantly growing/changing.
Let us know how it goes.
04-25-2013 01:18 AM
Came in this morning to no error message!
So it looks like either the data size is the issue (as the second drive is an extra 270Gb which may be tipping it over the edge) I will run it tonight just on the E drive and see if it errors (incase it is something on the drive itself) but if not I think you guys may have nailed it. I'll report back tomorrow, thank you.