Ask the Community
Groups
Volume Mountpoints in Windows can lead to backup failures - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Volume Mountpoints in Windows can lead to backup failures</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="purpose">Purpose</h3> <p>Describe how mountpoints without drive letters can cause backup failures</p> <h3 data-id="description">Description</h3> <p>In Windows it is possible to define an NTFS folder as a mountpoint. These mountpoints do not have drive letters.</p> <p><a href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc938934.aspx">http://technet.microsoft.com/en-us/library/cc938934.aspx</a></p> <h3 data-id="cause">Cause</h3> <p>A backup has failed. In the backup summary output, you note the inability to identify information about a volume listing the following format with a "?" where the drive letter should be, and the GUID does not match any known partitions:</p> <p>\\?\Volume {GUID}\</p> <h3 data-id="resolution">Resolution</h3> <p>If the server is a physical machine, use the mountvol command for windows to remove the mountpoint. The command:</p> <p>MOUNTVOL /D \\?\Volume{UUID} will remove the mountpoint for the volume listed.</p> <p>If the server is a virtual server, it should be possible to use VMWare or Hyper-V backups of the machine instead of the agent backups and obtain successful backups without removing the mountpoint.</p> <h3 data-id="third-party-sources">Third-Party Sources</h3> <p><a href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc772586%28v%3Dws.10%29.aspx">http://technet.microsoft.com/en-us/library/cc772586(v=ws.10).aspx</a></p> </article> </main>