Use Network Share to Restore VEEAM Image or Not?
I'm trying to make good use of the VEEAM free imaging tool for bare metal backups.
I can get the image files OK but have a few questions about restore operations.
Assuming that I need to apply this to a number of computers (not too large a number) and that others may have to do the restorations, I'd like to save the files on a network share rather than, say, an external USB drive that can be made "local" when the time for restoration comes.
Clearly, one is going to want to test the restoration process and I'm willing to deal with variations in computers regarding "can this one boot from a USB or DVD?".
But, in the first test using a network drive, I couldn't get the VEEAM restore system to see any network shares.
This is in a workgroup environment with a number of file shares on the network.
I've already determined that the NIC driver seems to be present and have configured its settings after / during boot to match the workgroup subnet.
But that's as far as I can get.
Also, I'm not expecting name service so use file-sharing computer IP addresses such as:
\\10.10.10.33\[sharename]
I don't want to find a solution for a one-off computer. I want to be able to do this over a range of different computers.
Suggestions? I'd rather not give up on a network share as the image source. But, if that's the conventional wisdom then I guess I'll have to more seriously consider just that.
I can get the image files OK but have a few questions about restore operations.
Assuming that I need to apply this to a number of computers (not too large a number) and that others may have to do the restorations, I'd like to save the files on a network share rather than, say, an external USB drive that can be made "local" when the time for restoration comes.
Clearly, one is going to want to test the restoration process and I'm willing to deal with variations in computers regarding "can this one boot from a USB or DVD?".
But, in the first test using a network drive, I couldn't get the VEEAM restore system to see any network shares.
This is in a workgroup environment with a number of file shares on the network.
I've already determined that the NIC driver seems to be present and have configured its settings after / during boot to match the workgroup subnet.
But that's as far as I can get.
Also, I'm not expecting name service so use file-sharing computer IP addresses such as:
\\10.10.10.33\[sharename]
I don't want to find a solution for a one-off computer. I want to be able to do this over a range of different computers.
Suggestions? I'd rather not give up on a network share as the image source. But, if that's the conventional wisdom then I guess I'll have to more seriously consider just that.
David Johnson, CD
Yes use a network share and you already stated you have to use the ip address, you will also have to enter the shares password prompt
Fred, Assuming you are using the VEB: https://www.veeam.com/windows-endpoint-server-backup-free.html
Why not provision the backup repository on the NAS (NFS) Share and then configure it as per: https://helpcenter.veeam.com/docs/agentforwindows/userguide/backup_job_share.html?ver=21
Why not provision the backup repository on the NAS (NFS) Share and then configure it as per: https://helpcenter.veeam.com/docs/agentforwindows/userguide/backup_job_share.html?ver=21
ASKER
David Johnson: That's what I tried to do. It didn't work.
Sernior IT System Engineer: There is no NAS but I guess there could be.....
Sernior IT System Engineer: There is no NAS but I guess there could be.....
We don't have any issues using a Windows Network Share which sits on a NAS, for use with Backup and Restore.
Must be something wrong with your network, or restore recovery cdrom, USB image.
I wrote an EE Article about it here
HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
Must be something wrong with your network, or restore recovery cdrom, USB image.
I wrote an EE Article about it here
HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
ASKER
Andrew: Thank you so much for the response. What a great paper! Very clear.
At:
At:
So, I'm stuck at this point.
The share is on a Windows workstation in use as a file server for the subnet and works just fine in normal operations.
Might the chosen DNS address matter? I can't imagine in that IP addresses are being used.
Would it matter if one were using a NAS instead of a Windows workstation?
Does it matter that SMB1 has been disabled?
Thanks again.
At:
Select Bare Metal Recovery and hit enter. Please note the Network Icon is lit, and does not have a cross through it, important if completing a restore from your network resource.(In our case there is no DHCP server so I had to click on the network icon and put in static IP, mask, gateway and DNS addresses).
At:
Enter the shared folder name and credentials if required, followed by Next to continue.I entered the shared folder name (using IP address as \\[ipaddress]\[sharename] and the result was consistently a message that conveyed that nothing was found.
So, I'm stuck at this point.
The share is on a Windows workstation in use as a file server for the subnet and works just fine in normal operations.
Might the chosen DNS address matter? I can't imagine in that IP addresses are being used.
Would it matter if one were using a NAS instead of a Windows workstation?
Does it matter that SMB1 has been disabled?
Thanks again.
Drop out to a command prompt and diagnose with ping
Something network wise is not working. We also use IP Address
We use NAS's (plural) and not Windows with no issues, and we are not use SMBv1
Something network wise is not working. We also use IP Address
We use NAS's (plural) and not Windows with no issues, and we are not use SMBv1
ASKER
Andrew: I'm experimenting here in my office. I just found that specifying the backup location behaved the same, odd, way as the previous restore attempts until I put the entire path in the address. I didn't work with the "Browse" button to see what shorter, upper level, paths may have done. Earlier, it appeared that Browse just didn't work. But that's a test I'll do next. Right now running a backup so I can proceed with the full scenario.
Thanks!
Thanks!
ASKER
I just completed a set of tests in my office. In this case there is DHCP service.
I got exactly the same results.
- To boot from CD, use [Space Bar] and NOT Enter as in "use any key"!!
- Be patient. It takes some time to come up.
- Assure the network setup is done.
- Run Command Prompt to see if you can ping the "server" NAME. (YES)
- Run Bare Metal Restore
- Enter the Server name UNC \\name and Browse. "Last error: The list of servers for this workgroup is not currently available".
This happens even if \\ipaddress.
This happens even if \\ipaddress\[full path\]
Depending on how you try this, some error messages are:
"The network name cannot be found"
All this matches what I did yesterday on the client's network.
I got exactly the same results.
- To boot from CD, use [Space Bar] and NOT Enter as in "use any key"!!
- Be patient. It takes some time to come up.
- Assure the network setup is done.
- Run Command Prompt to see if you can ping the "server" NAME. (YES)
- Run Bare Metal Restore
- Enter the Server name UNC \\name and Browse. "Last error: The list of servers for this workgroup is not currently available".
This happens even if \\ipaddress.
This happens even if \\ipaddress\[full path\]
Depending on how you try this, some error messages are:
"The network name cannot be found"
All this matches what I did yesterday on the client's network.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No. And I should have mentioned that I'm also transitioning my office network to a domain. So now I'm not sure how this should be working. Well, the "transition" is mostly done really....
ASKER
That is, if I run the following from the command line,
net use Z: \\[filesharecomputer]\[sha
This works! Thank you..
However, since Z: is now a local "drive", I look for the backup file in a LOCAL drive and find it backup.vbm. YAY!!
But, the recovery tool still says that a backup file wasn't found!!
net use Z: \\[filesharecomputer]\[sha
This works! Thank you..
However, since Z: is now a local "drive", I look for the backup file in a LOCAL drive and find it backup.vbm. YAY!!
But, the recovery tool still says that a backup file wasn't found!!
Z:\ is a network drive not a local drive
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Andrew: Thanks again!
Not to be too picky but I would say that Z: is a local drive in that Z: only has meaning locally. And, indeed, that's where the .vbm file is found by the VEEAM tool. But, yes, Z: *points to* a network entity indirectly.
I am using the latest software. VEEAM Agent for Microsoft Windows v 2.4.1
I wish there were a way to separate the recovery process from the recovery data but there being drivers involved, perhaps that's asking too much.
I'm tempted to try older software at this point. Where?
Not to be too picky but I would say that Z: is a local drive in that Z: only has meaning locally. And, indeed, that's where the .vbm file is found by the VEEAM tool. But, yes, Z: *points to* a network entity indirectly.
I am using the latest software. VEEAM Agent for Microsoft Windows v 2.4.1
I wish there were a way to separate the recovery process from the recovery data but there being drivers involved, perhaps that's asking too much.
I'm tempted to try older software at this point. Where?
I'm not sure you'll be able to get the old software.
Maybe a support request with Veeam on this...
In terms of how software access it, it's not a local disk, like a USB plugged into a computer is not a local disk!
Maybe a support request with Veeam on this...
In terms of how software access it, it's not a local disk, like a USB plugged into a computer is not a local disk!
ASKER
I found a copy of the old software and am trying it now. Heh, it works!
I opened a case with them.
What I meant about local disk vs. not local was based on "can one assign a drive letter to it?" If yes, then local.
But, I can imagine other definitions such as "in terms of how software accesses it". That's not something I know about well enough.
Thanks!
I opened a case with them.
What I meant about local disk vs. not local was based on "can one assign a drive letter to it?" If yes, then local.
But, I can imagine other definitions such as "in terms of how software accesses it". That's not something I know about well enough.
Thanks!
ASKER
Thanks all!
very odd bug, I wonder if they've been doing something with SMB signing....
ASKER
Yes. If you hadn't suggested using the command line to test this, I wouldn't have made such good progress!
ASKER
I recently reported test results to VEEAM. I've attached them in case anyone is interested. The latest recovery boot release isn't acting as if it's very solid when file searching is involved.
But, yes, at least it can be made to work with Network Shares - just more than a little tricky there!
VEEAM-P5ND-Test-Results.pdf
VEEAM-WIN10Test-Results.pdf
But, yes, at least it can be made to work with Network Shares - just more than a little tricky there!
VEEAM-P5ND-Test-Results.pdf
VEEAM-WIN10Test-Results.pdf