Re: Problem restoring files from windows file server
I've been able to start the FLR, i cannot said how beacause i did to many thing. But i'm not able to restore a long file name with special character in it.
To use FLR, the network card must be in the same vlan as the Veeam Backup & Replication server, otherwise, the backup server will not be able to communicate with the FLR and you will received an error talking about ssh port 22.
My only option will be to restore VM hard disks, add it to a VM and take the file i need. Not tested...
To use FLR, the network card must be in the same vlan as the Veeam Backup & Replication server, otherwise, the backup server will not be able to communicate with the FLR and you will received an error talking about ssh port 22.
My only option will be to restore VM hard disks, add it to a VM and take the file i need. Not tested...
-
- VP, Product Management
- Posts: 6029
- Liked: 2856 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
- Contact:
Re: Problem restoring files from windows file server
Actually, you can simply perform an instant restore of the VM (to a new location), not powered on, and then attach the disk to a running VM to copy the files. That would probably be the fastest and simplest way.DanQcCa wrote:My only option will be to restore VM hard disks, add it to a VM and take the file i need. Not tested...
I think you could also use a little trick with hardlinks when using a "regular" Veeam FLR, but I haven't tried this. I will setup a test in my lab.
Re: Problem restoring files from windows file server
I've been able to start the FLR, i cannot said how beacause i did to many thing. But i'm not able to restore a long file name with special character in it.
To use FLR, the network card must be in the same vlan as the Veeam Backup & Replication server, otherwise, the backup server will not be able to communicate with the FLR and you will received an error talking about ssh port 22.
My only option will be to restore VM hard disks, add it to a VM and take the file i need. Not tested...
To use FLR, the network card must be in the same vlan as the Veeam Backup & Replication server, otherwise, the backup server will not be able to communicate with the FLR and you will received an error talking about ssh port 22.
My only option will be to restore VM hard disks, add it to a VM and take the file i need. Not tested...
-
- VP, Product Management
- Posts: 6029
- Liked: 2856 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
- Contact:
Re: Problem restoring files from windows file server
In my testing I was able to simply use Windows Explorer instead of the Veeam File Browser to restore the file. I just tested this by created a very long/deep path. I then started the normal "Guest Files (Windows)" restore wizard and browsed to the file which caused the Veeam File Browser to error with the message noted above. At this point I opened Windows Explorer (while leaving the Veeam File Browser up) so that I could browse to C:\VeeamFLR\<servername>\<volume#\<biglongpath> and was able to copy the files out just fine. Have you tried this?
Re: Problem restoring files from windows file server
tsightler you are the KING! Your solution worked. I just try it and i've been able to restore a too long path/file name from a windows 2003 replica.
I also try it from a backup and it worked also.
THANKS tsightler, you found a way to bypass the Veeam Backup Browser problem
I also try it from a backup and it worked also.
THANKS tsightler, you found a way to bypass the Veeam Backup Browser problem
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Nov 13, 2012 4:20 pm
- Full Name: Richard Deveson
- Contact:
Re: Problem restoring files from windows file server
So come on Veeam, where is your fix to this
your all to good at giving workarounds....surely this has gone on long enough?
your all to good at giving workarounds....surely this has gone on long enough?
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Aug 16, 2011 11:12 pm
- Full Name: Nathan Simkins
- Contact:
Re: Problem restoring files from windows file server
tsightler - your workaround is by far the simplest. Thanks!
-
- Novice
- Posts: 9
- Liked: never
- Joined: Oct 14, 2011 10:34 pm
- Full Name: Chris Oleson
- Contact:
Re: Problem restoring files from windows file server
Thank you so much!tsightler wrote:In my testing I was able to simply use Windows Explorer instead of the Veeam File Browser to restore the file. I just tested this by created a very long/deep path. I then started the normal "Guest Files (Windows)" restore wizard and browsed to the file which caused the Veeam File Browser to error with the message noted above. At this point I opened Windows Explorer (while leaving the Veeam File Browser up) so that I could browse to C:\VeeamFLR\<servername>\<volume#\<biglongpath> and was able to copy the files out just fine. Have you tried this?
-
- Novice
- Posts: 8
- Liked: never
- Joined: Jan 09, 2013 3:35 pm
- Full Name: Peter Bohlken
- Contact:
Re: Problem restoring files from windows file server
On my environment the VeeamFLR is on the C: drive.
What i did is mount the VM
Restore succeeded -> browse thru c:\VeeamFLR\BACKUPJOB name\Volume3 -> to the TOO long path select files and copy those somewhere locally/network share
Then use something like totalcommander to mount/browse to wanted server/location with that too long path and paste the files.
Restore done with workaroound (but dont need to do like http://www.veeam.com/KB1459)
What i did is mount the VM
Restore succeeded -> browse thru c:\VeeamFLR\BACKUPJOB name\Volume3 -> to the TOO long path select files and copy those somewhere locally/network share
Then use something like totalcommander to mount/browse to wanted server/location with that too long path and paste the files.
Restore done with workaroound (but dont need to do like http://www.veeam.com/KB1459)
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Jun 13, 2012 8:38 am
- Full Name: Christian Fröhlich
- Contact:
Re: Problem restoring files from windows file server
Hi,
we have the same problem with long path names. The standard file or path restore to the orginal location is not possible if you have more then 259 caracters in the source or target path.
The work around from tsightler is working fine, but it is not great solution and so easy.
It is fixed in the new version 7?
Thank you!
we have the same problem with long path names. The standard file or path restore to the orginal location is not possible if you have more then 259 caracters in the source or target path.
The work around from tsightler is working fine, but it is not great solution and so easy.
It is fixed in the new version 7?
Thank you!
-
- Veeam Software
- Posts: 21133
- Liked: 2140 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Problem restoring files from windows file server
Supposed to be fixed in v7.BigMacNix wrote:It is fixed in the new version 7?
-
- Veteran
- Posts: 366
- Liked: 24 times
- Joined: May 01, 2013 9:54 pm
- Full Name: Julien
- Contact:
Re: Problem restoring files from windows file server
i am on 6.1 applied all the patches ,no vail,
you guy having a kind of solution or just the word arround?
my company is thinking to move to Veeam, but i think will have to hold now, untill all is stable and i dont need to do any work arrond,
in the mean while Symantec exec is doing the job,
you guy having a kind of solution or just the word arround?
my company is thinking to move to Veeam, but i think will have to hold now, untill all is stable and i dont need to do any work arrond,
in the mean while Symantec exec is doing the job,
-
- Chief Product Officer
- Posts: 31746
- Liked: 7250 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Problem restoring files from windows file server
This specific issue very long name file name issues should be addressed in 7.0...
By the way, the latest product version is 6.5, and I do recommend that you upgrade.
6.5 had some enhancements around file level recovery, in case your issue is different.
By the way, the latest product version is 6.5, and I do recommend that you upgrade.
6.5 had some enhancements around file level recovery, in case your issue is different.
-
- Veteran
- Posts: 366
- Liked: 24 times
- Joined: May 01, 2013 9:54 pm
- Full Name: Julien
- Contact:
Re: Problem restoring files from windows file server
i am sorry i am already on 6.5 i typed wrong,Gostev wrote:This specific issue very long name file name issues should be addressed in 7.0...
By the way, the latest product version is 6.5, and I do recommend that you upgrade.
6.5 had some enhancements around file level recovery, in case your issue is different.
when do we expect the version 7 ?
-
- Product Manager
- Posts: 20360
- Liked: 2287 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Problem restoring files from windows file server
The version 7 is scheduled to come out in Q3 and it will have the abovementioned problem fixed.
For more information about version 7 and its new features kindly see the following page:
http://go.veeam.com/v7.html
Hope this helps.
Thanks.
For more information about version 7 and its new features kindly see the following page:
http://go.veeam.com/v7.html
Hope this helps.
Thanks.
-
- Influencer
- Posts: 21
- Liked: 2 times
- Joined: Jul 05, 2012 11:23 am
- Full Name: Simon Gatke
- Contact:
[MERGED] Re: Problem restoring files from windows file serve
Just to add us to the Veeam customers having issues with file level restores.
We are using Veeam in a HyperV environment.
When we Restore Guest Files (Windows), we are often hit by the "filename or path too long" error.
This happens even though the path is not *that* long.
It looks like the error happens because of the way Veeam mounts the backup: C:\Veeamflr\servername\volume{9015c908-6ba6-11e2-b24f-00155d961401}\...
When using such a long path to get to the backup files, we don't really need very long filenames or paths to our real date before we run into the limitation.
I understand this is supposed to be fixed in version 7, which we will be looking very much forward to.
We are using Veeam in a HyperV environment.
When we Restore Guest Files (Windows), we are often hit by the "filename or path too long" error.
This happens even though the path is not *that* long.
It looks like the error happens because of the way Veeam mounts the backup: C:\Veeamflr\servername\volume{9015c908-6ba6-11e2-b24f-00155d961401}\...
When using such a long path to get to the backup files, we don't really need very long filenames or paths to our real date before we run into the limitation.
I understand this is supposed to be fixed in version 7, which we will be looking very much forward to.
-
- Novice
- Posts: 9
- Liked: never
- Joined: Dec 13, 2011 5:15 pm
- Full Name: ZUNO WINTEL
- Contact:
Re: Problem restoring files from windows file server
v7 - restore works for long paths, hovewer option "Copy to" (from replica to anywhere you want) does not work which is a pity and I am very disappointed about that ...
-
- Veeam Software
- Posts: 21133
- Liked: 2140 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Problem restoring files from windows file server
Denis, are you stating that restore to original location works, however the Copy To option for the same file in the Backup Browser does not?
-
- Veeam Software
- Posts: 21133
- Liked: 2140 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Problem restoring files from windows file server
This was confirmed to be an issue (Copy To command not working for long paths). As a workaround, you can use any file browser that handles long names properly and get the required objects from the C:\VeeamFLR\VMName\VolumeX\ folder.
-
- Novice
- Posts: 9
- Liked: never
- Joined: Dec 13, 2011 5:15 pm
- Full Name: ZUNO WINTEL
- Contact:
Re: Problem restoring files from windows file server
Alex,
you got the point - however I'd really like to use this feature as we are restoring files/dirs from file server replicas pretty often and I'd need to preserve timestamps, permissions etc - that's why it's really important to us. As workaround, I am using robocopy, but if Veeam team will fix that, I will be more than happy ( I bet I will be not alone )
you got the point - however I'd really like to use this feature as we are restoring files/dirs from file server replicas pretty often and I'd need to preserve timestamps, permissions etc - that's why it's really important to us. As workaround, I am using robocopy, but if Veeam team will fix that, I will be more than happy ( I bet I will be not alone )
-
- Veeam Software
- Posts: 21133
- Liked: 2140 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Problem restoring files from windows file server
Sure, thanks for pointing this one out.
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Oct 09, 2013 11:34 am
- Contact:
[MERGED]:Restoring file share from VM to an alternative loca
Hello,
I need to restore an entire network share from a VM to a physical server. I was able to attempt a restore using the "Copy To:" command, however the process failed because of some of the very long path names for the files.
I can't use Explorer or another file copy program because a lot of the folders in this share are accessible to only one user (home folders). Even Domain Admins don't have rights to access these folders.
BackupExec, which we used before Veeam, was able to do this without difficulty. I could restore a share to any location, regardless of the length of paths or filenames.
Any thoughts as to what I can do?
Thanks
Jason
I need to restore an entire network share from a VM to a physical server. I was able to attempt a restore using the "Copy To:" command, however the process failed because of some of the very long path names for the files.
I can't use Explorer or another file copy program because a lot of the folders in this share are accessible to only one user (home folders). Even Domain Admins don't have rights to access these folders.
BackupExec, which we used before Veeam, was able to do this without difficulty. I could restore a share to any location, regardless of the length of paths or filenames.
Any thoughts as to what I can do?
Thanks
Jason
-
- Product Manager
- Posts: 14684
- Liked: 1693 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Problem restoring files from windows file server
Jason,
Please review the conversation above regarding your problem. Thank you.
Please review the conversation above regarding your problem. Thank you.
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Oct 09, 2013 11:34 am
- Contact:
Re: Problem restoring files from windows file server
Thanks, but I already had.
The suggestion was to use Explorer or Robocopy. Those won't work as the only account with access to many of the folders is the user themselves (Domain admins, local admins, etc... don't have access).
Is this something that is going to be fixed in the future? If Robocopy can do it, why can't Veeam?
Jason
The suggestion was to use Explorer or Robocopy. Those won't work as the only account with access to many of the folders is the user themselves (Domain admins, local admins, etc... don't have access).
Is this something that is going to be fixed in the future? If Robocopy can do it, why can't Veeam?
Jason
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Oct 09, 2013 11:34 am
- Contact:
Re: Problem restoring files from windows file server
I just solved my own problem:
http://social.technet.microsoft.com/For ... g-b-switch
Using the /b /zb switches works wonders.
Thanks,
Jason
http://social.technet.microsoft.com/For ... g-b-switch
Using the /b /zb switches works wonders.
Thanks,
Jason
-
- Veeam Software
- Posts: 21133
- Liked: 2140 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Problem restoring files from windows file server
Chances are this will be fixed in the next patch.jedwards-lux wrote:Is this something that is going to be fixed in the future? If Robocopy can do it, why can't Veeam?
-
- Novice
- Posts: 3
- Liked: never
- Joined: Nov 29, 2013 5:06 am
- Full Name: Alex Pablet
- Contact:
Re: Problem restoring files from windows file server
For these kinds of issues, you can use Long Path Tool, it works good!
-
- Chief Product Officer
- Posts: 31746
- Liked: 7250 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Problem restoring files from windows file server
Copy To issue is fixed in 7.0 R2.
-
- Novice
- Posts: 3
- Liked: never
- Joined: Feb 06, 2014 2:01 pm
- Contact:
Re: Problem restoring files from windows file server
Hello.
We are using Veeam B&R Version 7.0.0.690 (licenced).
We have several backups...one backup (that I want to restore) is stored on an USB HDD. So I Importet the .vbm file into Veeam and tried to "restore guest files (Windows)".
When I said "copy to" I wanted to copy it to the path C:\ ...but the job failed with the message: The specified path, file name, or both are too long. The fully qualified name must be less than 260 characters, and the directory name must be less than 248 characters
I just read the first page of this topic. But it didn't help.
So can you tell me how to workaround this issue?
Is there a chance to mount the backup file under Windows? It is very important to me (as always when restoring files ^^).
Kind regards!
We are using Veeam B&R Version 7.0.0.690 (licenced).
We have several backups...one backup (that I want to restore) is stored on an USB HDD. So I Importet the .vbm file into Veeam and tried to "restore guest files (Windows)".
When I said "copy to" I wanted to copy it to the path C:\ ...but the job failed with the message: The specified path, file name, or both are too long. The fully qualified name must be less than 260 characters, and the directory name must be less than 248 characters
I just read the first page of this topic. But it didn't help.
So can you tell me how to workaround this issue?
Is there a chance to mount the backup file under Windows? It is very important to me (as always when restoring files ^^).
Kind regards!
-
- Veeam Software
- Posts: 21133
- Liked: 2140 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Problem restoring files from windows file server
Please install the Veeam B&R 7.0 R2 update resolving this issue. Thanks.
Who is online
Users browsing this forum: Google [Bot], Semrush [Bot] and 2 guests