cancel
Showing results for 
Search instead for 
Did you mean: 

backup stucks

NBU35
Level 6

Hi 

Master server Solaris 10, 7.6.0.3
Media Server Hp UX 11.31, 7.6.0.3
Client WIndows 2008 R2, 7.0.1

Connectivity is fine, bptestbpcd command is completeting without error.
Detailed status of job shows "begin writing" then job stcuks for hours and don't start writing.

There is only one IP on client which is teamd and getting used for backups.
checked Vss Wrtiers and get following message.

>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.


Howvere I checked Shadow copies are disabled on widnows for all drives.
In event viewer I see following error when ever I initiate backup.

Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid(S-1-5-21-2404701332-79391348-2085898168-1112.bak).  hr = 0x80070539, The security ID structure is invalid.

Operation:
   OnIdentify event
   Gathering Writer Data

Context:
   Execution Context: Shadow Copy Optimization Writer
   Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Name: Shadow Copy Optimization Writer
   Writer Instance ID: {81aa5b1b-91cd-44e9-a68e-f0c2583b7e3f}

please suggest.

1 ACCEPTED SOLUTION

Accepted Solutions

sdo
Level 6
Partner    VIP    Certified

NetBackup leverages/calls VSS.  If VSS is broken then this usually breaks backups.  NetBackup cannot auto-fix or work-around VSS errors.  You need to resolve the VSS error before backups will work again.  The usual first step to resolve VSS errors is to reboot the client.  Re-try the backup, if it still fails then enable NetBackup logging on the client.

View solution in original post

10 REPLIES 10

sdo
Level 6
Partner    VIP    Certified

NetBackup leverages/calls VSS.  If VSS is broken then this usually breaks backups.  NetBackup cannot auto-fix or work-around VSS errors.  You need to resolve the VSS error before backups will work again.  The usual first step to resolve VSS errors is to reboot the client.  Re-try the backup, if it still fails then enable NetBackup logging on the client.

View solution in original post

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

If you want WOFB to backup open files, you need to fix Microsoft VSS issue.

If you don't need open file backup, disable it via Host Properties -> Master -> Client Attributes -> Add/select client name.

NBU35
Level 6

WOFB is already disbaled for this client :(

Nicolai
Moderator
Moderator
Partner    VIP   

VSS is also used for backup of Shadow Copy Components - even with WOFB disabled VSS is still being used for SCC.

sdo
Level 6
Partner    VIP    Certified

I suspect that, whilst WOFB might be disabled (in NetBackup Client terms, for user visible volumes and folders), that VSS may still be used by Windows to secure parts of itself, i.e. Shadow Copy Components (aka System State).

Does the failing backup job include SCC and/or SS and/or ALL_LOCAL_DRIVES ?

Nicolai
Moderator
Moderator
Partner    VIP   

Yes - backup of SCC is a API netbackup calls that uses VSS

NBU35
Level 6

Yes, its backup selection list is ALL_LOCAL_DRIVES

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please select 'Allow multiple data streams' to ensure a new job is started for SCC and each drive letter.

This will narrow down where the problem is (at this point we can only assume that it is with backup of SCC).

Ensure bpbkar and bpfis log folders exist on the client.

You will need to take up the VSS issue with Microsoft.

NBU35
Level 6

nothing bpbkar folder, bpfis logs are attached.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

There must be something in bpbkar log.

Check that the folder name does not have typo error and that it is in correct folder on the client.

Have you tried the policy with 'Allow multiple data streams' ?

When posting logs, please post all text in Activity Monitor Details tab as well so that we can trace PIDs and timestamps.

*** EDIT ***

There are all sorts of " snapshot services" errors in bpfis log - you need to take the VSS issue up with Microsoft.