APPLICATIONS:\SqlServerWriter couldn't get volume Info on g:\. Error Code = 3

Thanks Carlos,

Here are the snapshots.

I'm using win2003, not 2008 is there a way to remove the snapshots?

C:\Program Files\Legato\nsr\applogs>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Contents of shadow copy set ID: {14aafbbc-bc0b-4873-93c6-01ba8ffd72ef}
   Contained 2 shadow copies at creation time: 3/12/2012 8:40:49 PM
      Shadow Copy ID: {310b0833-d9c0-4910-9ac8-65dda46f72bc}
         Original Volume: (C:)\\?\Volume{ad4bf8f0-0cfd-11dc-90b5-806e6f6e6963}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
         Originating Machine: server1
         Service Machine: server1
         Provider: 'Microsoft Software Shadow Copy provider 1.0'
         Type: ApplicationRollback
         Attributes: Persistent, No auto release, Differential, Exposed locally

Contents of shadow copy set ID: {6401816c-8c7e-4e41-a7c4-8eb2a4db5284}
   Contained 3 shadow copies at creation time: 3/27/2012 12:54:41 PM
      Shadow Copy ID: {f2f56656-76e7-45bf-89e3-6fcc1ee67944}
         Original Volume: (C:)\\?\Volume{ad4bf8f0-0cfd-11dc-90b5-806e6f6e6963}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy18
         Originating Machine: server1
         Service Machine: server1
         Provider: 'Microsoft Software Shadow Copy provider 1.0'
         Type: ApplicationRollback
         Attributes: Persistent, No auto release, Differential, Exposed locally

      Shadow Copy ID: {1e6babd3-4900-4495-9c75-512fbbb88717}
         Original Volume: (D:)\\?\Volume{ad4bf8f1-0cfd-11dc-90b5-806e6f6e6963}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy19
         Originating Machine: server1
         Service Machine: server1
         Provider: 'Microsoft Software Shadow Copy provider 1.0'
         Type: ApplicationRollback
         Attributes: Persistent, No auto release, Differential, Exposed locally

      Shadow Copy ID: {0a4249ae-c817-42a3-8afc-758e5a2ad533}
         Original Volume: (E:)\\?\Volume{3a0a482b-3540-11de-8d20-806e6f6e6963}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy17
         Originating Machine: server1
         Service Machine: server1
         Provider: 'Microsoft Software Shadow Copy provider 1.0'
         Type: ApplicationRollback
         Attributes: Persistent, No auto release, Differential, Exposed locally

Contents of shadow copy set ID: {a1469723-7a0c-4e21-9a37-1083dc60d337}
   Contained 3 shadow copies at creation time: 3/27/2012 4:56:22 PM
      Shadow Copy ID: {e856f13f-3181-43f0-a867-dc9ffb90c7c0}
         Original Volume: (C:)\\?\Volume{ad4bf8f0-0cfd-11dc-90b5-806e6f6e6963}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy24
         Originating Machine: server1
         Service Machine: server1
         Provider: 'Microsoft Software Shadow Copy provider 1.0'
         Type: ApplicationRollback
         Attributes: Persistent, No auto release, Differential, Exposed locally

      Shadow Copy ID: {0208e627-b884-4afd-9880-f023de436a69}
         Original Volume: (D:)\\?\Volume{ad4bf8f1-0cfd-11dc-90b5-806e6f6e6963}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy25
         Originating Machine: server1
         Service Machine: server1
         Provider: 'Microsoft Software Shadow Copy provider 1.0'
         Type: ApplicationRollback
         Attributes: Persistent, No auto release, Differential, Exposed locally

      Shadow Copy ID: {d4e44375-c9f4-4b94-99e3-8ef82ad0312f}
         Original Volume: (E:)\\?\Volume{3a0a482b-3540-11de-8d20-806e6f6e6963}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy23
         Originating Machine: server1
         Service Machine: server1
         Provider: 'Microsoft Software Shadow Copy provider 1.0'
         Type: ApplicationRollback
         Attributes: Persistent, No auto release, Differential, Exposed locally

Hi Alan,

You can download the support tools which include DISKSHADOW, otherwise please follow the steps described in the following KB:

https://solutions.emc.com/emcsolutionview.asp?id=esg110691

What about the status of the writers?

vssadmin list writers

Thank you.

Carlos.

Ok, the error log has gone from:

savegrp: suppressed 5 lines of verbose output

Drive String C:\ is already used up

c:\ has fs :NTFS

d:\ has fs :NTFS

e:\ has fs :NTFS

f:\ has fs :

couldn't get volume Info on g:\. Error Code = 3

Started nsrcscd Successfully

create_cl: Connecting to CSC RPC server on server1 (1)

create_cl: Connecting to CSC RPC server on server1 (2)

create_cl: Connecting to CSC RPC server on server1 (3)

create_cl: Connected to CSC RPC server on server1

authenticate_csc_client: Successfully authenticated with NetWorker server backup1

log_cl_auth: Client authentication type: RPCSEC_GSS (6)

NMM .. VSS Provider 'Microsoft Software Shadow Copy provider 1.0' used for volume 'C:\'.

NMM .. VSS Provider 'Microsoft Software Shadow Copy provider 1.0' used for volume 'E:\'.

NMM .. Preparing list of files for backup.

Started nsrsnapbwragent

to:

savegrp: suppressed 10 lines of verbose output

c:\ has fs :NTFS

d:\ has fs :NTFS

e:\ has fs :NTFS

couldn't get volume Info on f:\. Error Code = 3

Started nsrcscd Successfully

create_cl: Connecting to CSC RPC server on server1 (1)

create_cl: Connecting to CSC RPC server on server1 (2)

create_cl: Connecting to CSC RPC server on server1 (3)

create_cl: Connected to CSC RPC server on server1

authenticate_csc_client: Successfully authenticated with NetWorker server ausperbck1.goldbar.barrick.com

log_cl_auth: Client authentication type: RPCSEC_GSS (6)

NMM .. VSS Provider 'Microsoft Software Shadow Copy provider 1.0' used for volume 'C:\'.

NMM .. VSS Provider 'Microsoft Software Shadow Copy provider 1.0' used for volume 'D:\'.

NMM .. VSS Provider 'Microsoft Software Shadow Copy provider 1.0' used for volume 'E:\'.

NMM .. Preparing list of files for backup.

Started nsrsnapbwragent

However, the weird phantom drives have disapeard from my computer...

Hi Alan,

The "phantom" drives were old snapshots or shadows, that were removed already.

I think the problem here is related to the configuration of the VM itself.

If you check the drives configuration of the VM you will see some entry for G: or just a GUID instead of a drive letter.

You also need to check the configuration of those drives and the path where they will place the snapshots, however I would also suggest to take a look at the Application and System event logs, I'm sure there will be some useful information in there.

Thank you.

Carlos