Unsolved
This post is more than 5 years old
16 Posts
0
4133
Windows 2003 Mountvol, GUID and Label
Could someone tell me where windows holds the GUID, Volume Lable and Mount information.
We have W2003 and backup exchange using eseutil and BCV's etc.
Sometimes this process fails and we have the volumes on the server but not mounted under their mount points.
If I run mountvol I can see all the volumes and their GUIDS, but I want to be able to map a GUID back to a Mount point, and a volume label.
I know the GUID can be got using the mountvol, symntctl commands, but what I cant find anywhere is the mapping of GUID to mount point. Is this held in the registry somewhere as when the backup process works correctly all the BCV volumes get mounted correctly under their correct mount points.Oris it that as part of the backup process the mountvol command has the GUID and mount point string as part of it's command.
Thanks
Andy
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
June 10th, 2010 03:00
are you using TF/EIM ?
bencrookEMC
30 Posts
1
June 10th, 2010 06:00
HKLM\system\mounteddevices
kingy1
16 Posts
0
June 11th, 2010 00:00
is this in the registry
kingy1
16 Posts
0
June 11th, 2010 00:00
yes we are using TEIM, and the issue is this process fails quite a lot and the exchange guys would like to be able to work out when BCV's dont mount, where they should mount to based on GUID.
kingy1
16 Posts
0
June 11th, 2010 03:00
Ben,
How can I map this too the mount point filesystem
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
June 11th, 2010 04:00
i am using TEIM Snap with exchange 2007, pretty much the same thing you are doing with BCVs. Where in the process does it fail ? When it does vss import on the backup server ? When it runs eseutil ?
bencrookEMC
30 Posts
0
June 11th, 2010 05:00
usually you have a GUID entry and a DosDevice Driveletter entry that both would contain the same binary data within their entry, it takes a lot of manual work to match them up, be careful
...
kingy1
16 Posts
0
June 14th, 2010 01:00
It looks to fail most times with the vss import on the backup server and gets itself in a mess then. It doesn't fail all the time but when it does we have to change the vss flags etc
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
June 18th, 2010 04:00
something that will help you with VSS import issues is Microsoft utility "scrubber". Everytime VSS snapshot gets imported it creates an entry under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\enum\storage\Volume
after a while that hive gets pretty big and start causing VSS import issues. So what i do before every single backup i run scrubber that purges those entries, my VSS gets imported so much faster too.
SamCl
54 Posts
0
July 27th, 2010 00:00
If you are getting regular failures due to GUID changes I would recommend opening an SR with EMC to investigate more fully as the symptoms you are describing can be due to more than one cause.
If as stated in this thread you are running TEIM then you will need to run the relevant exbackup command with the -debugmode option and pipe the result to a file.
Then once you have recorded a failure a copy of the EMCReports output from both the backup side and the production node(s) are needed along with the debugmode output