cancel
Showing results for 
Search instead for 
Did you mean: 

Volume resolution error for (System State:\System Files\System Files)

PranavB
Level 4

Good Day Geeks !

 

there are two systems that are giving issues while backing up their shadow copy components.

Below is the error:

 

 Volume resolution error for (System State:\System Files\System Files)

 

 

We have tried downgrading them as they were running on 7.6.0.1

OS is 2k8 R2

Tried taking backup without using snapshot ,tried VSP but none worked.

Please suggest if we need to check on something.

 

PS: Also have tried ignoring backups of unresolved drives.

 

Thanks,

Pranav B

1 ACCEPTED SOLUTION

Accepted Solutions

Pangal
Level 5

Hi,

        Increase the logging to maximum and fire the backup. Check the bpbkar log . Check whether nbu is unable to resolve any path

 

 

 

 

View solution in original post

7 REPLIES 7

chack22
Level 4

Not sure if it's relevant to 2008R2, but maybe here?

http://www.symantec.com/business/support/index?page=content&id=TECH176793

 

PranavB
Level 4

we did apply this hot fix on one of our systems giving same error but result is same.

We still struggling to get it working.

 

 

PranavB

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

VSP was discontinued in NBU 7.0 already.

Is the Windows Client a member of a cluster?
What is in Backup Selection for this client?

Have you checked VSS status?
vssadmin list writers
vssadmin list providers
 

Have you tried to use Windows Backup on the client to backup system state to local drive?

Please show us all text in Activity Monitor Details tab and ensure these log folders exist on the client:
bpfis
bpbkar

Copy logs to .txt files (e.g. bpfis.txt) and upload as File attachments.

 

 

Mark_Solutions
Level 6
Partner Accredited Certified

Where do the drives reside?

If they are SAN drives located on Hitachi or similar SAN the client may have VSS writers provided by the SAN

You can check to see if anything other than the default VSS writers are installed using:

vssadmin list providers

If so then from the \netbackup\bin\ directory run:

w2koption -backup -snapshotprovidertype 1

This forces the system to use the Windows VSS writers - usually backups get a 156 error but not always.

It can also be a floppy drive mapped to a VMware server or a recovery partition that doesn't have a drive letter assigned

See what the bpfis and bpbkar logs show - you may need to ramp the logging on the client right up

Pangal
Level 5

Hi,

        Increase the logging to maximum and fire the backup. Check the bpbkar log . Check whether nbu is unable to resolve any path

 

 

 

 

View solution in original post

PranavB
Level 4

Sory to reply late on this but found issue with unknown entry in the registry.

There was a path of E drive which shadow copy was trying to backup up but in real it doesn't exist ,so i had to exclude unresolved path for E drive and it is backing up fine.

 

I found the track of this path in bpbkar logs.

 

PranavB

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You will agree that Pangal provided you with the solution:

Increase the logging to maximum and fire the backup. Check the bpbkar log . Check whether nbu is unable to resolve any path

 

 Please clear the solution for your own post and mark Pangal's post as solution.

Thanks.