• Commonly used to backup NAS shares or partitions.
  • UNC = Uniform Naming Convention
  • Example:  //?/UNC/server/share or //?UNC/Server/Volume/File
  • //?/UNC/<servername or ip>/<sharename>/<directory>  (note the <> are for emphasis and should not be included in the UNC path)
Example Scenario: You have a network share on a NAS server that you want to back up.  Our agent software cannot be installed directly on the NAS server because it is not running a standard operating system that is supported. 


What to do? 

Use UNC to backup that share:

  • Add a new client to the Clients > Summary list or use an existing Windows client.
  • Edit the client's backup file set to include the UNC path to the NAS share.  The path must begin with "//?/UNC/"
  • Examples:  //?/UNC/serve_name/share or //?/UNC/IP address/Folder_to_start_in
  • The agent must be configured to run as a user account that has access to this path rather than the default "Local System".  This can be configured in either the RVXConfig tool or in the Services window of the client machine. This account must also have backup operator permissions in the network.


Note: If the share you are backing up is NOT a windows file server, you will need to enable the File Set option to Ignore Win32 attributes. If the job message logs have "ERR=00000522:A required privilege is not held by the client.." for every file you might need to turn on the File Set option to Ignore Win32 attributes. 

A less optimal alternative  is to set up a mapped drive from a Windows computer and include that mapped drive as part of the backup for that Windows client.  This method will require the agent to be manually started by the user as a program rather than as a service.