NetBackup 7.5.0.5, cannot restore to different path

Yes, seen that here as well.  Upgraded from 7.0 to 7.5.0.5 and now a push restore from the Master or media server(s) does not allow restoring to a different directory. 

We restore users folder to s sub-folder called RESTORED, and let them figure out what file(s) they want.  We are so used to just clicking on the second button and adding RESTORED so we found this *very* quickly, screen-snip attached. 

*However*, using UNIX-like string for the taget path i.e.

 /F/mnt/staff/staff-home-1/eng/mm/mmpo/RESTORED *did* work.

Basically, Netbackup 7.5.0.5 may have "fixed" this syntax, but for us Windows users, a retrograde step. 

Outline of what kit we have:

SUN/Oracle-based master/media servers, most of our clients are VMWare ones so we use 4, VM-based "clients" to backup snampshotes. 

The snip shown is the Java GUI running on the Master server (Solaris-based, Netbackup 7.5.0.5), requesting a Windows client (W2003, netbackup 7.5.0.5) ) to restore to another Windows 2003 server (clinet 6.0MP4?)

I saw same problem last week. I manage it by connecting to client on java GUI. Requesting restore from client works with alternate path.

Hi Ron,

I believe you're already working a case with us around this issue? 

For anyone else who comes across this thread who may be experiencing this issue, I would like to point out the two excellent workarounds already discovered by both Ron and Bertil above, either of which will avoid the error popup:

• Use the Windows Remote Administration Console instead of the Java console.
• Change your "Windows" file path to a "UNIX" one by removing the colon from the drive name, prepending with a forward slash ("/") and changing all backslash ("\") characters in the path to forward ones - for example, "Z:\RESTORED" would become "/Z/RESTORED" instead.

This is another of those issues where it's more aggravating than disastrous - but "aggravating" isn't much consolation, and we'll work hard on resolving this (what we're pretty sure is a) defect.

Try to set the Destination ith the Network Path

\\SERVERNAME\DRIVE(Or Share c$)\DESTINATION\DIRECTORY

Be sure the destination directory exist.

2nd attempt at updating this post, the first one doesn't seem to have been saved.

Chris is correct, there is an EEB now available, see his post above. 

Note that the EEB installer is looking for the version.txt file to determine if you have the correct version for this EEB.  If you do not have the full NetBackup client or server installed on the computer from which you are running the Java GUI, the EEB installer will fail because it is looking for the version.txt file which is not part of the Java GUI install.

You will have to extract the files from the EEB using a "-extractonly" switch and manually replace the .jar file in your Java GUI install directory. 

Here's a quick update on this issue:

We have attached a hotfix to this TechNote:

When running the NetBackup 7.5.0.5 Java admin console and restoring windows clients to alternate directories, an "invalid destination pathname" error is displayed.
 http://symantec.com/docs/TECH203806

If you don't want to use the workaround of converting your Windows path to a "UNIX style" path, download and install the nbjP.jar file attached to this TechNote and restart your Java GUI.

This'll be fixed in 7.5.0.6 as well, for sure.