Command Line NTBackup Won't Backup Files Using UNC Naming

 Last reviewed: May 9, 1997
Article ID: Q104081
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

Windows NT Backup (NTBACKUP.EXE) does not support uniform naming convention (UNC) naming for paths. For example, when issuing the command 

   ntbackup backup \\server1\share\<dirname>
Windows NT Backup will not backup any files in the specified directory, even though files exist in the directory (\<dirname>).

MORE INFORMATION

This might be an issue for someone (such as a network administrator) who wants to make nightly backups using the AT command (which schedules programs to run on a computer at a specified time and date).

For example, you may want to issue the following command 

   AT 3:30am backup.bat
where the contents of the BACKUP.BAT file are the following: 

   ntbackup backup \\server1\share\sys
When you are using UNC naming conventions, you can avoid mapping a drive letter to a network resource; however, Windows NT Backup does not support UNC naming.

In the above example, then, the correct contents for the BACKUP.BAT is the following: 

   rem Disconnect the current network resource if it exists.
   net use o: /d
   rem Connect to the correct network resource for the backup.
   net use o: \\server1\share
   rem Run the backup to the network resource.
   ntbackup backup o:\sys
   rem Disconnect the current network resource.
   net use o: /d

Additional query words: prodnt
Keywords : kbtool ntutil
Version : 3.1
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.