Start a Conversation

Unsolved

This post is more than 5 years old

4898

September 7th, 2018 08:00

Exchange database backup fails

Exchange database backup fails with this error..

Can anyone advice what "Driver not active for volume" means? There's literally zero reference about it on the internet.

Many thanks !

107092:nsrnmmsv: Version information for C:\Program Files\EMC NetWorker\nsr\bin\nsrnmmsv.exe: Original file name: nsrnmmsv.exe Version: 9.1.0 (ntx64) Comments: Supporting Microsoft Volume Shadow Copy Service

127159:nsrnmmsv: Created temp path C:\Program Files\EMC NetWorker\nsr\tmp\nmm\2018-09-07_11-41-02_5492-5496\.

nsrnmmsv: multithreaded save set parallelism==6

145369:nsrnmmsv: Initialization success -- Exchange shell successfully initialized. Required for Exchange.

133296 1536334864 0 0 0 5496 5492 0 client-computer.domain.com nsrnmmsv NSR info 26 Starting backup operation. 0

145369 1536334865 0 0 0 5496 5492 0 client-computer.domain.com nsrnmmsv NSR info 89 Initialization success -- Exchange shell successfully initialized. Required for Exchange. 0

159219 1536334867 5 0 0 5496 5492 0 client-computer.domain.com nsrnmmsv NSR critical 31 Driver not active for volume %s 1 0 48 \\?\Volume{e200533e-0a8b-11e8-9b19-000c29e7b1bf}

95958 1536334867 5 0 0 5496 5492 0 client-computer.domain.com nsrnmmsv NSR critical 36 Cannot initialize the write tracker. 0

95959 1536334867 0 0 0 5496 5492 0 client-computer.domain.com nsrnmmsv NSR info 87 The write tracker initialization failed. Performing a block based backup at level full. 0

137907 1536334867 2 0 0 5496 5492 0 client-computer.domain.com nsrnmmsv NSR warning 66 Unable to start write tracker session. Backup cannot be completed. 0

139527 1536334867 3 0 0 5496 5492 0 client-computer.domain.com nsrnmmsv NSR error 51 The backup operation did not complete successfully. 0

102333 1536334867 3 0 0 5496 5492 0 client-computer.domain.com nsrnmmsv NSR error 21 Exiting with failure. 0

2018-09-07 3:41:07 PM Removing files under temp path C:\Program Files\EMC NetWorker\nsr\tmp\nmm\2018-09-07_11-41-02_5492-5496.

--- Job Indications ---

Internal error. Save job failed, please refer to log file for more information.

client-computer.domain.com:pseudo_saveset: retried 1 times.

14 Posts

September 10th, 2018 14:00

I see this on the exchange client event logs:

Log Name:      System

Source:        Service Control Manager

Date:          10/09/2018 17:46:08 Z

Event ID:      7000

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      client-computer.domain.com

Description:

The BBB Write Interceptor Driver service failed to start due to the following error:

Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Event Xml:

http://schemas.microsoft.com/win/2004/08/events/event ">

 

   

    7000

    0

    2

    0

    0

    0x8080000000000000

   

    30536

   

   

    System

    client-computer.domain.com

   

 

 

    BBB Write Interceptor Driver

    %%577

 

September 11th, 2018 07:00

Hi Victor,

Can you check if you can move the mailbox database to a different disk drive than the one it is currently present on? e.g.  move mailbox datbase from D:\ drive to E:\ drive or in other ways, from current residing drive to some other drive.

Also, check the event and application event logs. Any writer failures will have to checked and resolved.

You can uncheck the "Block Based Backup" option in NMC under the client properties.

Regards,

Chetan

14 Posts

September 11th, 2018 11:00

I tried.. failed with the same NetWorker Errors..

From the Exchange client, I see these events:

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied.

. This is often caused by incorrect security settings in either the writer or requestor process.

The BBB Write Interceptor Driver service failed to start due to the following error:

Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

C:\>sc start nsrbbb

[SC] StartService FAILED 577:


Windows cannot verify the digital signature for this file. A recent hardware or

software change might have installed a file that is signed incorrectly or damage

d, or that might be malicious software from an unknown source.

Actually I was able to fix it as such: (after MANY hours of research)

1. Restart the computer and during startup, press F8.

2. Select Advanced Boot Options.

3. Select Disable Driver Signature Enforcement.

4. Boot into Windows and uninstall the unsigned driver.

Does anyone know a permanent solution?

No Events found!

Top