Skrevet av Emne: BackupExec: Path not found when adding Backup-to-Disk folder  (Lest 4793 ganger)

ATC

  • Gjest
BackupExec: Path not found when adding Backup-to-Disk folder
« på: 09. ſeptember 2009, 13:41 pm »
  • [applaud]0
  • [smite]0
  • After mapping a remote drive to a local drive letter, any attempt to add this drive letter (or directories within) as a Backup-to-Disk folder fails with an error message indicating that the requested path does not exist.

    It DOES exist, and I have write permissions. What is going on?



    ATC

    • Gjest
    [Solved] BackupExec: Path not found when adding Backup-to-Disk folder
    « Svar #1 på: 09. ſeptember 2009, 13:41 pm »
  • [applaud]0
  • [smite]0
  • BackupExec runs as a service, this means that any drive letters mapped for a logged-in user basically "does not exist" from BackupExec's point of view.

    Only local drives (as in "made available by a device driver") are visible to such services (By the way, this is also why you cannot share a mapped drive in Windows)

    The solution is to specify the UNC path directly to the shared resource. Unfortunately, BackupExec is too braindead to understand that an UNC path may contain the character "." in an IP address or a FQDN, so you'll have to edit "C:\WINDOWS\system32\drivers\etc\hosts" or make sure the host name can be resolved via WINS or DNS. Further, if you are using NFS, note that Windows does not distinguish between the formats \\host\share and host:/share (this ofcourse means you can't mix SMB/CIFS and NFS on the same host)