NMM 2.3 - couldn't get volume Info on e:\.

I'm not aware that NMM should create ramdsik.  Is it possible to check registry and see if there are any references to E drive while NMM is not running?

Hi, and thanks for your answer.

Unfortunatly searching the registry for "e:\" yields no results. The systems has no Ramdisk driver installed either (no HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Services\ Ramdisk\" entry in the registry)

Vssadmin list volumes shows no odd volumes:

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

Volume path: \\?\Volume{e0b6686a-b404-11df-aed8-806e6f6e6963}\
    Volume name: \\?\Volume{e0b6686a-b404-11df-aed8-806e6f6e6963}\
Volume path: S:\
    Volume name: \\?\Volume{69625d1b-b439-11df-abe6-00155d560d02}\
Volume path: C:\EXCHANGELOG\LOG1\
    Volume name: \\?\Volume{829fcbe0-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGELOG\LOG2\
    Volume name: \\?\Volume{829fcbe7-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGELOG\LOG3\
    Volume name: \\?\Volume{829fcbee-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGELOG\LOG4\
    Volume name: \\?\Volume{829fcbf5-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGELOG\LOG5\
    Volume name: \\?\Volume{829fcbf8-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGELOG\LOG6\
    Volume name: \\?\Volume{829fcbfb-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGEMDB\DB1\
    Volume name: \\?\Volume{829fcc0a-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGEMDB\DB2\
    Volume name: \\?\Volume{829fcc11-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGEMDB\DB3\
    Volume name: \\?\Volume{829fcc18-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGEMDB\DB4\
    Volume name: \\?\Volume{829fcc1f-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGEMDB\DB5\
    Volume name: \\?\Volume{829fcc26-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGEMDB\DB6\
    Volume name: \\?\Volume{829fcc2d-27e1-11e0-a3d1-00155d560d04}\
Volume path: C:\EXCHANGEMDB\DB7\
    Volume name: \\?\Volume{98ea3531-5e8d-11e0-a545-00155d560d04}\
Volume path: C:\
    Volume name: \\?\Volume{e0b6686b-b404-11df-aed8-806e6f6e6963}\

One thing that might be interesting though is that the system is a virtual system. Has NMM 2.3 been verified with Hyper-V?

Yes... actually compatibility guide claims:

NMM 2.3 adds support for Hyper-V R2 parent partition backups Supports Hyper-V Parent Partition backups of system state, data volumes, Hyper-V configuration files and all/individual Hyper-V Child Partitions (Guests)

Hallo Stefan,

each VSS writer has its own repository for important objects like drivers, system files, applications, mount points ...

Once registered in such a repository an entry is never deleted. So this repository can be not up to date and tons

of VSS backup problems in the past were caused by such a mismatch. VSS is really a nightmare.

Networker now ignores missing entries and just reports them.

You should open a support case with microsoft.

regards

Bernd

Hi Bernd,

the VSS Metadata was a good idea. I just looked through it but found no sign of a Volume named d:\ or e:\

The only thing I found that closely resembles a different volume name would be this part of the Cluster Database:

Component "Cluster Database:\Cluster Database"
                        - Name: Cluster Database
                        - Logical path:
                        - Full path: \Cluster Database
                        - Caption: ClusterDatabase
                        - Type: VSS_CT_FILEGROUP [2]
                        - Is selectable: TRUE
                        - Is top level: TRUE
                        - Notify on backup complete: FALSE
                        - Paths affected by this component:
                                - C:\Windows\cluster\
                        - Volumes affected by this component:
                                - \\?\Volume{e0b6686b-b404-11df-aed8-806e6f6e6963}\
                        - Component Dependencies:

Hopefully having the "e:\" in the Name "Cluster Database:\Cluster Database" does not confuse NMM.