Before Reinstall ... Windows Desktop Backup
-
@BRRABill said:
Did some testing today.
DISK2VHD was quick to get running, and took around 11 minutes to do a full VHD backup.
DRIVEIMAGEXML kept freezing on this particular machine. Odd. (I tried multiple times.)
MACRIUM took about 11 minutes as well. A little longer up front to install the program.
VEEAM took a consider amount of time to download and install. It also took about 23 minutes to run the backup.
So anyway ... just some interesting numbers.
I think DISK2VHD might be the way to go moving forward.
The question is in the event of things like a hard drive upgrade, etc... would you be able to use Disk2VHD to restore a VHD file to a new hard drive or no?
Thanks for the numbers... those are good to see!
How do the backup sizes compare?
-
@dafyre said:
The question is in the event of things like a hard drive upgrade, etc... would you be able to use Disk2VHD to restore a VHD file to a new hard drive or no?
That I do not know the answer to.
I do know the VHD will not boot in VirtualBox, and even if it did, it wouldn't be activated, as Microsoft doesn't support virtualizing the desktops for the most part.
Another downside I ran into with the VHD method us having to take ownership of a lot of stuff, which can be very time consuming. nI have to see how the othe programs dump the data back on the disk. But I am assuming permissions will be stripped.
-
@BRRABill said:
@dafyre said:
The question is in the event of things like a hard drive upgrade, etc... would you be able to use Disk2VHD to restore a VHD file to a new hard drive or no?
That I do not know the answer to.
I do know the VHD will not boot in VirtualBox, and even if it didn't, it wouldn't be activated, as Microsoft doesn't support virtualizing the desktops for the most part.
Another downside I ran into with the VHD method us having to take ownership of a lot of stuff, which can be very time consuming. nI have to see how the othe programs dump the data back on the disk. But I am assuming permissions will be stripped.
That is the point of using Veeam. First it creates a restore boot ISO. Then it makes the initial backup. Your ongoing subsequent backups are minutes because it builds incrementals, the same as the main product.
-
@JaredBusch said:
That is the point of using Veeam. First it creates a restore boot ISO. Then it makes the initial backup. Your ongoing subsequent backups are minutes because it builds incrementals, the same as the main product.
For this scenario, I was asking about a one time backup.
I agree something like Veeam would be more appropriate for the scenario you are talking about, with continual backups of an continually functioning system.
-
Here is a desktop at a client that we backup with Veeam because of some specialized config and software.
That 26 minute duration? Veeam rebuilding the full backup from the incrementals.
-
@dafyre said:
How do the backup sizes compare?
Just running "out of the box", so to speak, they were all about the same.
Macrium must have compression enabled by default because it was a smaller.
Macrium also retains security, BTW, so there is no difference to taking ownership as in the VHD.
-
@JaredBusch said:
Here is a desktop at a client that we backup with Veeam because of some specialized config and software.
Yes you have to clarify that or someone here will yell at you for backing up an endpoint like this.
-
@BRRABill said:
@JaredBusch said:
Here is a desktop at a client that we backup with Veeam because of some specialized config and software.
Yes you have to clarify that or someone here will yell at you for backing up an endpoint like this.
I would yell at me.
-
-
@BRRABill said:
@JaredBusch said:
I would yell at me.
I mentioned no names. LOL.
That is all outside the point of the topic. You want a solid and reliable backup and restore solution, use Veeam Endpoint Backup.
You just want to make an image, use clonezilla or disk2vhd.
-
@JaredBusch said:
You just want to make an image, use clonezilla or disk2vhd.
I think disk2vhd is going to be my new go-to.
Nothing to install, it's quick, and does the job.
Clonezilla isn't right for my application, because primarily I want to be able to pull the data out of the VHD to put back onto the fresh install.
Veeam seemed to work, but it's a large install and a longer backup.
-
@JaredBusch said:
@BRRABill said:
@JaredBusch said:
I would yell at me.
I mentioned no names. LOL.
That is all outside the point of the topic. You want a solid and reliable backup and restore solution, use Veeam Endpoint Backup.
You just want to make an image, use clonezilla or disk2vhd.
This is a backup because you are wiping out a machine and reinstalling. Clonezilla is super easy for this - though @BRRABill asked about mounting the backup and recovering a file here or a file there - I don't know if this is possible, you might have to restore the whole image to a VM (virtual box) and then recover the files you want.
@JaredBusch can you mount a Veeam Endpoint and directly recover a file?
-
@JaredBusch said:
@BRRABill said:
I mentioned no names. LOL.
That is all outside the point of the topic.
What? No joking allowed today on ML?
#sadThursday
-
-
@BRRABill said:
@JaredBusch said:
You just want to make an image, use clonezilla or disk2vhd.
I think disk2vhd is going to be my new go-to.
Nothing to install, it's quick, and does the job.
Clonezilla isn't right for my application, because primarily I want to be able to pull the data out of the VHD to put back onto the fresh install.
Veeam seemed to work, but it's a large install and a longer backup.
You are (again) missing the point.
I am not sure how more clear I could make it than my last post. The software is for two completely different tasks. Yes you can use all of them for anything, but that is not the design of the software. Of course a piece of software will not perform well when being used outside of its designed methodology.
-
@BRRABill said:
Macrium also retains security, BTW, so there is no difference to taking ownership as in the VHD.
I take it back. You CAN browse the backup/image in Macrium without having to take ownership. Sweet.
