Forum Discussion

sabby's avatar
sabby
Level 4
13 years ago

System State Backup

I have a W2K3 client(x86). The backup selection list is set to ALL_LOCAL_DRIVES. When the job is partially completed the log says that the system state files are being skipped.

****

21/08/2012 18:30:02 - requesting resource eefp-hcart3-robot-tld-0
21/08/2012 18:30:02 - requesting resource EEFP.NBU_CLIENT.MAXJOBS.XYZ
21/08/2012 18:30:02 - requesting resource EEFP.NBU_POLICY.MAXJOBS.EEFP_ALL_SERVERS
21/08/2012 18:30:02 - awaiting resource eefp-hcart3-robot-tld-0 - will retry physical later
21/08/2012 18:58:53 - granted resource EEFP.NBU_CLIENT.MAXJOBS.XYZ
21/08/2012 18:58:53 - granted resource EEFP.NBU_POLICY.MAXJOBS.EEFP_ALL_SERVERS
21/08/2012 18:58:53 - granted resource 0763L4
21/08/2012 18:58:53 - granted resource IBM.ULT3580-TD4.002
21/08/2012 18:58:53 - granted resource eefp-hcart3-robot-tld-0
21/08/2012 18:59:09 - connecting
21/08/2012 18:59:10 - connected; connect time: 00:00:01
21/08/2012 18:59:10 - begin writing
21/08/2012 19:04:27 - Warning bpbrm(pid=18220) from client XYZ: WRN - Removable Storage Management: unable to export database (WIN32 21: The device is not ready. )
21/08/2012 19:05:43 - Warning bpbrm(pid=18220) from client XYZ: WRN - can't open object: Shadow Copy Components:\System State\System Files\System Files (BEDS 0xE0009421: No component files present on the snapshot.)
21/08/2012 19:05:44 - Warning bpbrm(pid=18220) from client EXYZ WRN - can't open object: Shadow Copy Components:\System State\COM+ Class Registration Database\COM+ REGDB (BEDS 0xE0009421: No component files present on the snapshot.)
21/08/2012 19:05:44 - Warning bpbrm(pid=18220) from client XYZ: WRN - can't open object: Shadow Copy Components:\System State\Registry\Registry (BEDS 0xE0009421: No component files present on the snapshot.)
21/08/2012 19:05:44 - Warning bpbrm(pid=18220) from client EXYZ WRN - can't open object: Shadow Copy Components:\System Service\Windows Management Instrumentation\WMI (BEDS 0xE0009421: No component files present on the snapshot.)
21/08/2012 19:05:44 - Warning bpbrm(pid=18220) from client XYZ: WRN - can't open object: Shadow Copy Components:\System Service\Event Logs\Event Logs (BEDS 0xE0009421: No component files present on the snapshot.)
21/08/2012 19:05:51 - end writing; write time: 00:06:41
the requested operation was partially successful(1)

Since the system state is not being backed up still I am able to see the image of system state compenents on BAR Console(both master and client side) for that particular day of backup. Why is it so?

I created another policy for the same client keeping only Shadow Copy Components in the backup selection list, and tried another backup, this time the job got fully completed(Status 0). Why the system state is not backing up when we are taking ALL_LOCAL_DRIVES as backup selection?

Does the size of system state files always show zero KB in BAR Console?

Please find attached snapshots for reference.

7.1.x and Earlier
Backup and Recovery
NetBackup

7 Replies

Sort By
  • V4's avatar
    V4
    Level 6
    13 years ago

    check if this helps

    http://www.symantec.com/docs/TECH16248

     

    exclude:

    Windows 2000: <system drive>:\Winnt\system32\ntmsdata\

    Windows 2003 <system drive>:\WINDOWS\system32\ntmsdata\

  • V4's avatar
    V4
    Level 6
    13 years ago

    you can also refer

    https://www-secure.symantec.com/connect/forums/wrn-removable-storage-management-unable-export-database-win32-21-device-not-ready

     

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    PLEASE give us all relevant info:

    What is NBU version and patch level on the client?

    What is OS (incl patch level) on client?

    Have you tried to use Windows backup to backup SCC to disk? Was that successful?

  • sabby's avatar
    sabby
    Level 4
    13 years ago

    @Marianne: NBU Master and Client Version is 6.0 MP7

    OS of the Client is Windows Server 2003 Standard Edition, Service Pack 2 (x86). It's a virtual machine.

    As far as NTBackup is concerned, yes I have ran it and it was successful.

    ***

    @Mark_Solutions: As per the TN mentioned by you,

    Step 1: All the VSS writers are stable for the client.

    Step 2: No need to reboot the client, since the VSS writers are stable.

    Step 3: VSS is set for Open file backups in the master server host properties.

    Step 4: The storage area meant for the shadow copies for each drive is empty. Checked with the help of command: vssadmin list shadows /for=<Drive Letter:> (Result: No items found )

    ***

    Currently I am able to backup the system state files with a separate policy as stated above, but my question why its not able to backup under ALL_LOCAL_DRIVES?

     

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    PLEASE upgrade your environment.

    See http://www.symantec.com/business/support/index?page=releasedetails&key=15143

    Version 6.0 MP6

     

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    13 years ago

    As the client is 2003 then it may be a VSS issue - there are VSS rollup packages available - here is one link:

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

    It isn't a Domain Controller is it? You may need to set the NetBackup client service account to use a full domain admin account if it is.

    The earlier advice about excluding the ntmsdata folder is correct for the remvable storage manager error.

    Also agree with Marianne - you are way out of sync with the NBU version and really do need to upgrade.

    Finally, as you are in V6 it may still be a bpfis issue - you could check for abandoned bpfis snapshots that could be causing an issue by running the following on the client when no backups are running:

    bpfis query

    This will list any snapshots left behind and each will have an ID

    You can then use:

    bpfis delete -id xxxxxxx

    To remove them (if V6 had this facility - not sure if it did)

    Hope this helps