cancel
Showing results for 
Search instead for 
Did you mean: 

Warning bpbrm (pid=15894) from client cprvnmsbi: WRN - C:\ is not frozen

Willie_SA
Level 6
Partner Accredited

NetBackup 7.1 Master / Media Server - UNIX Solaris 10

Windows 2003 Client - 7.1

Policy  - ALL_LOCAL_DRIVES

 

Message in Job Activity Monitor:

Warning bpbrm (pid=15894) from client cprvnmsbi: WRN - C:\ is not frozen

Job complete with Status Code 1

1 ACCEPTED SOLUTION

Accepted Solutions

Willie_SA
Level 6
Partner Accredited

It has just come to light that the Windows 2003 license key is not activated on this system.

They are going to investigate it right now.

 

Could this be part of the reason why we are encountering this error?

View solution in original post

20 REPLIES 20

mph999
Level 6
Employee Accredited

Is the client on a virtual machine ?

mph999
Level 6
Employee Accredited

In the policy for the client, what is the backup selection ?

Willie_SA
Level 6
Partner Accredited

Client on virtual Machine. YES

Backup Selection:        ALL_LOCAL_DRIVES

Marianne
Level 6
Partner    VIP    Accredited Certified

'Not frozen' looks like a snapshot error.

Please create these folders on the client in the ...\NetBackup\logs folder:

bpfis
bpbkar

Please post bpfis log after next failure as attachment.

We will let you know if we need bpbkar as well.

Willie_SA
Level 6
Partner Accredited

Floders created.

Going to run backup manually again.

Marianne
Level 6
Partner    VIP    Accredited Certified

Is NBU Client software installed in the VM (functioning as 'normal' Windows client) or doing vStorage backup?

Please give us full policy config:

On master:

bppllist <policy-name> -L

 

Willie_SA
Level 6
Partner Accredited

Attached find the bpfis file.

Willie_SA
Level 6
Partner Accredited

NBU Client 7.1 installed as normal client - not VM. Is there a way I can dou ble check?

Attached the bppllist output.

Mark_Solutions
Level 6
Partner Accredited Certified

I see it is using VSS but fails to make the snapshot

Run (from a command line) vssadmin list writers to see their state and also, as this is a Windows 2003 Server check for the latest VSS rollup package from Microsoft - see this sort of error a lot

#edit# KB940349 I believe

Marianne
Level 6
Partner    VIP    Accredited Certified

The policy type is the first key:

Policy Type:       MS-Windows (13)
.....
Perform Snapshot Backup:   no

VStorage backup will be configured as FlashBackup-Windows policy with VM-specific snapshot parameters.

Willie_SA
Level 6
Partner Accredited

Attached copy of vssadmin output.

 

Hoe do I check that VSS rollup package?

Willie_SA
Level 6
Partner Accredited

Please remember that this Policy is for 15 clients. changes to the Policy can effect alot of other clients.

BUT I can create a seperate Policy for this one.

Marianne
Level 6
Partner    VIP    Accredited Certified

vStorage backups needs separate licensing and configuration of a backup host.

We just needed to understand what exactly we are troubleshooting - normal client or vStorage backups.

Seems Marks is on the right path with MS fixes for VSS.

Mark_Solutions
Level 6
Partner Accredited Certified

AH! - Almost all failed!

I would download the rollup package :

http://support.microsoft.com/kb/940349
http://www.microsoft.com/download/en/details.aspx?id=11896

The server needs a reboot anyway based on what is shown

Willie_SA
Level 6
Partner Accredited

Will book for a reboot.

And download mentioned files.

Willie_SA
Level 6
Partner Accredited

It has just come to light that the Windows 2003 license key is not activated on this system.

They are going to investigate it right now.

 

Could this be part of the reason why we are encountering this error?

Willie_SA
Level 6
Partner Accredited

After activating the Lic key - I reran the backup and it completed with Status 0.

All working now.

Thank you

Willie_SA
Level 6
Partner Accredited

Do I need to delte those bpfis and bpbkar directories I created for the log files?

Will they eventually take up lots of space?

Marianne
Level 6
Partner    VIP    Accredited Certified

Willie, these folders are always useful for troubleshooting.

I usually reccommend to have these folders at level 0 (default) logging. It just makes troubleshooting tunaround time so much quicker if the logs are already there. Level 0 logs should not consume large amounts of space.

Logs are kept for 28 days by default. This setting is stored on the master under Host Properties -> Master -> Clean-up.

If clients have limited space on C-drive where NBU is installed (like less than 1 GB free space) best to remove folders.