Vidéos d'aide de Screencast

restore of folder on unix server failing

Created: 12 Juillet 2010 • Updated: 15 Août 2010 | 10 comments
Ce problème a été résolu. Voir la solution.
Hi Guys.
 
I'm trying to restore a directory from HP-UX server to another HP-UX server  but am getting the error (WIN32 123: The filename, directory name, or volume label syntax is incorrect).I have selected the below options
 
restore everything to its original location
overwrite existing files - selected
 
The destination server has the same folder  as the source server. Not sure why i'm getting the error.Please help.
 
Master Server: NetBackup-Solaris10 6.5.4 (SunOS  5.10 Generic_138888-03 sun4u sparc SUNW,SPARC-Enterprise)
 
Source Server:NetBackup-HP-UX11.11 6.5.3 (HP-UX  B.11.11 U 9000/800 999245314 unlimited-user license)
Destination Server:NetBackup-HP-UX11.23 6.5.4 (HP-UX B.11.23 U ia64 3277856930 unlimited-user license)

Commentaires CommentairesAccéder au dernier commentaire

l'image des Marianne

I'm battling to read your screendump. Please copy the text rather than posting a screendump.

I can make out WIN32 errors - are you sure this is a Unix (HP-UX) restore?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

l'image des Marianne

If you are using a Windows Admin Console on your desktop, please check what the configured Client Name is for your desktop. If the name was changed to that of the restore client, it will try to restore the files to your desktop.

Have a look at the solution to this post:

https://www-secure.symantec.com/connect/forums/res...

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

l'image des Kisad

Hi Marianne,

I know it looks weird and hard to believe but both source and destination is HP-UX machines.  i have pasted the versions above :) 

The backup image is on disk (datadomain)

Heres the errors..

begin Restore

07/12/2010 10:39:26 - restoring from image 
07/12/2010 10:39:27 - requesting resource @aaaad
07/12/2010 10:39:27 - granted resource  MediaID=@aaaad;DiskVolume=-lsu1;DiskPool=;Path=-lsu1;StorageServer=;MediaServer=
07/12/2010 10:34:13 - connecting
07/12/2010 10:34:21 - connected; connect time: 0:00:00
07/12/2010 10:34:22 - started process bptm (pid=4557)
07/12/2010 10:34:30 - Warning bpbrm (pid=4550) from client : WRN - can't create file: tmp:\jr\content_storage_01\0000f93c\80\21\cc\9f.pdf (WIN32 123: The filename, directory name, or volume label syntax is incorrect. )
07/12/2010 10:34:29 - begin reading
07/12/2010 10:34:32 - Warning bpbrm (pid=4550) from client : WRN - can't create file: tmp:\jr\content_storage_01\0000f93c\80\21\cc\a6.doc (WIN32 123: The filename, directory name, or volume label syntax is incorrect. )
07/12/2010 10:34:32 - Warning bpbrm (pid=4550) from client : WRN - can't create file: tmp:\jr\content_storage_01\0000f93c\80\21\cc\a7.pdf (WIN32 123: The filename, directory name, or volume label syntax is incorrect. )
07/12/2010 10:34:33 - Warning bpbrm (pid=4550) from client : WRN - can't create file: tmp:\jr\content_storage_01\0000f93c\80\21\cc\ae.doc (WIN32 123: The filename, directory name, or volume label syntax is incorrect. )
07/12/2010 10:34:34 - Warning bpbrm (pid=4550) from client : WRN - can't create file: tmp:\jr\content_storage_01\0000f93c\80\21\cc\af.pdf (WIN32 123: The filename, directory name, or volume label syntax is incorrect. )
07/12/2010 10:34:34 - Warning bpbrm (pid=4550) from client : WRN - can't create file: tmp:\jr\content_storage_01\0000f93c\80\21\cc\b6.doc (WIN32 123: The filename, directory name, or volume label syntax is incorrect. )
07/12/2010 10:34:34 - Warning bpbrm (pid=4550) from client : WRN - can't create file: tmp:\jr\content_storage_01\0000f93c\80\21\cc\b7.pdf (WIN32 123: The filename, directory name, or volume label syntax is incorrect. )
07/12/2010 10:34:35 - Warning bpbrm (pid=4550) from client : WRN - can't create file: tmp:\jr\content_storage_01\0000f93c\80\21\cc\be.doc (WIN32 123: The filename, directory name, or volume label syntax is incorrect. )
07/12/2010 10:38:19 - end reading; read time: 0:03:50
07/12/2010 10:43:53 - restored from image ; restore time: 0:04:27
07/12/2010 10:43:54 - end Restore; elapsed time 0:05:25
07/12/2010 10:38:36 - Error bpbrm (pid=4550) client restore EXIT STATUS 5: the restore failed to recover the requested files
the restore failed to recover the requested files (5)

Thanks
Kisad

l'image des Marianne

Please find this section in the bprd log on the Master server:

##.##.## [####.####] <2> restorefiles:    browse_client =
##.##.## [####.####] <2> restorefiles:    requesting_client =
##.##.## [####.####] <2> restorefiles:    destination_client =
##.##.## [####.####] <2> restorefiles:    requesting_client_hostname =
##.##.## [####.####] <2> restorefiles:    destination_client_hostname =

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

l'image des davidbe

maybe its cause I don't know HP much but why is there a ':' in your filepath?

l'image des CRZ

Your log: tmp:\jr\content_storage_01\0000f93c\80\21\cc\9f.pdf
Shouldn't that be: /tmp/jr/content_storage_01/0000f93c/80/21/cc/9f.pdf?

Re-check the policy settings - is something "MS-Windows" where it should be "Standard?"


bit.ly/76LBN | APPLBN | 761LBN

l'image des Andy Welburn

but it does actually look like that when inputting the parameters for the actual restore path - a bit disconcerting when you're a *NIX bod!

l'image des Kisad

Hi Guys,

Thank You for your time and responses.I was able to finaly perform the restore successfully. This is what i did ...

1.Tried restore on the master server  and another HP-UX server. restore completed successfully on both.
2.Got the original destination server rebooted and retried the restore but still got the same error message.
3.uninstalled and reinstalled NBU binaries on the destination server and retried the restore. It worked and restore completed with status 0.

I guess the reinstallation of the NBU binaries resolved the problem but i still cant make sense on why the WIN32 error kept appearing.

Thanks
Kisad

SOLUTION
l'image des Andy Welburn

Strange indeed!

Have marked your post as solution.

l'image des Kisad

Thanks Andy. Have opened a support case, will post an update if he finds something in the logs.

Thanks
Kisad