71 On System State, C:\, and Shadow Copy Backup

[Learning_Everyd]

Master = WIN2003 Enterprise Ed. w/SP2, NBU 6.5.6

Client = WIN2003 Enterprise Ed. w/SP2 x64, NBU 6.5.6

bppllist =

Policy Name:       vm-korinar2

  Policy Type:         MS-Windows-NT
  Active:              yes
  Effective date:      12/11/2008 17:26:02
  Backup network drvs: no
  Collect TIR info:    no
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     950
  Max Jobs/Policy:     13
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           Development
  Volume Pool:         LTO4_Tapes
  Server Group:        *ANY*
  Keyword:             StarTeam DEV - Stephanie S. Raj Ramani
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no

Granular Restore Info:  no
  HW/OS/Client:  PC-x64        Windows2003   vkorinar2.earth.com

  Include:  c:\
            System State:\
            Shadow Copy Components:\

  Schedule:          Full
    Type:            Full Backup
    Frequency:       every 7 days
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 8 (1 year)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Friday     18:00:00  -->  Sunday     20:00:00

  Schedule:          User
    Type:            User Backup
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 8 (1 year)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     24:00:00
          Monday     00:00:00  -->  Monday     24:00:00
          Tuesday    00:00:00  -->  Tuesday    24:00:00
          Wednesday  00:00:00  -->  Wednesday  24:00:00
          Thursday   00:00:00  -->  Thursday   24:00:00
          Friday     00:00:00  -->  Friday     24:00:00
          Saturday   00:00:00  -->  Saturday   24:00:00

  Schedule:          Incremental
    Type:            Cumulative Incremental Backup
    Frequency:       every 1 day
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 3 (1 month)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Monday     18:00:00  -->  Tuesday    08:30:00
          Tuesday    18:00:00  -->  Wednesday  08:30:00
          Wednesday  18:00:00  -->  Thursday   08:30:00
          Thursday   18:00:00  -->  Friday     08:30:00

Detailed Status =

11/18/2011 2:01:04 PM - requesting resource Development
11/18/2011 2:01:04 PM - requesting resource ma-atl06.us.manh.com.NBU_CLIENT.MAXJOBS.vkorinar2.earth.com
11/18/2011 2:01:04 PM - requesting resource ma-atl06.us.manh.com.NBU_POLICY.MAXJOBS.VM-Korinar2
11/18/2011 2:01:04 PM - granted resource ma-atl06.us.manh.com.NBU_CLIENT.MAXJOBS.vkorinar2.earth.com
11/18/2011 2:01:04 PM - granted resource ma-atl06.us.manh.com.NBU_POLICY.MAXJOBS.VM-Korinar2
11/18/2011 2:01:04 PM - granted resource LT4208
11/18/2011 2:01:04 PM - granted resource HP.ULTRIUM4-SCSI.003
11/18/2011 2:01:04 PM - granted resource ma-atl103-hcart
11/18/2011 2:01:04 PM - estimated 0 kbytes needed
11/18/2011 2:01:06 PM - started process bpbrm (4260)
11/18/2011 2:01:09 PM - connecting
11/18/2011 2:01:10 PM - connected; connect time: 00:00:01
11/18/2011 2:01:15 PM - Error bpbrm(pid=4260) could not send server status message      
11/18/2011 2:01:18 PM - end writing
none of the files in the file list exist(71)

The OS is in tact and server is operational.  Is it not finding any of the directories in the selection list?  How can this be? 

LE

[Will_Restore]

SOLUTION/WORKAROUND:

The VSS Writer is needed in order to communicate with the Shadow Copy Component Writers on a Windows 2003 OS. If the VSS writers is in a corrupt/inconsistent state. It is necessary to repair Microsoft's VSS components to resolve the issue.  In this case, the solution was found in the following Microsoft Q article, however this is not the only VSS issue that can cause a Status 71.

See the below Microsoft Article for additional information on repair this issue:

http://support.microsoft.com/kb/907574

Symantec recommends contacting Microsoft for the official solution.

Article URL http://www.symantec.com/docs/TECH57394

 

[Will_Restore]

does backing up just the C:\ drive work?

[Marianne]

PLEASE do not include  System State:\ and Shadow Copy Components:\ in the same policy.

Shadow Copy Components:\ includes System State:\. See p. 183 of NBU 6.5 Admin Guide I for Windows http://www.symantec.com/docs/TECH52803

I see you have "Mult. Data Streams:  yes" in policy attributes. This means that separate jobs will be initiated for C:\, System State:\ and Shadow Copy Components:\.

Check the Overview tab of the job to see which one failed with 71.

[Nicolai]

This directive backup all drives local to the client as well as system_state and shadow_copy_components. If you wan't a backup of only drive C: you can exclude those using a exclude list. Excluding drives can be carried out using the BAR gui on the client or using the master server console using Properties -> Clients.

If ALL_LOCAL_DRIVES still fail with 71, make sure the bpfis debug log is enabled in [install_path]/netbackup/logs

[Will_Restore]

why did the forum suddenly get tiny fonts? 

Knowlegebase is still fine so I don't think it's anything on my end.

[tom_sprouse · Accepted solution]

Marianne is correct, you do not want to specify both Shadow Copy Components AND System State in the same policy.

If this is a Windows 2003 or higher, you should be using Shadow Copy Components only, as it will include the System State.

The job details provided above does not show which backup selection is failing with status 71.

I would assume this is not the C: Drive - but you never know these days. :)

In either case, when you backup Shadow Copy or System State, the Volume Shadow Service is started to backup the VSS Writers.

If one backup has a lock on these VSS Writers, then the subsequent stream cannot access (or in this case see) the VSS Writer and will fail with a status 71 - none of the files in the file list exist.

I hope this answers any / all of your questions / concerns. 

---