I basically create aSystem ImageusingAOMEIas and when I need to. I have also written a Batch Script that I use toBackupmy important Data folders, which I can run several times a day if required usingXCopy.
Like most things, people have their OWN ways ofImaging & Backupto suit their needs.
Sorry doctor I seem to have a problem ...
These are not all in use at any one time and are mostly partitions on two 8TB spinners The Windows drive is an M2 and the Fast Storage is a conventional SSD that is used to store the databases of my image processing software
The other drives are the ones on the two spinners and the "Spares" are temporary data mostly - The first currently hold my Windows 11 ISO's in addition ISO Installers for XP, Vista Win7 Win10 for client support I also keep ISO's of the CD/DVD's that come with peripherals ( I do prefer to download the latest drivers but it's sometimes useful to have originals).
my backups are spread over the 5 Weekdays to keep the individuals loads to a manageable time frame.
I do use the base level of compression in Backupper, I would prefer not to use compression but you have to make compromises
Dumb question (always). What is the difference between making a C-drive backup and a system backup.
Which should give the most protection, or better yet, which is more likely to fail and need restoring?
A system drive backup (default is C but I have seen other letters), includes the essential system partitions needed to make a drive function as a bootable system where as a C: drive backup would only backup the single c: drive so if you needed to restore a working system you would need some way the regenerate the missing partitions
You should always use a system backup unless you had some specific need for only the c: drive - I have seen systems reused on different hardware but this involves manually creating partitions so is not advised except in emergencies and a lot of work can be involved.
the one partition contains the actual boot system, the others, one or more are added by some feature updates, these can appear if the original `extra system partitions are filled up
Just for interest really.
I created theBootable Mediausing theLinux - Create Bootable Disc Based On Linux Kerneloption which created anISO[Export ISO File], which you can then eitherBurnto CD or USB. What I did was Copy the ISO file to myVentoycreated USB andBootedit to make sure it worked, which it DID. I also keep my latestSystem Imageson the USB as well as on anInternal Partition.
> AOMEI - Making Linux Bootable CD
About Ventoy:
Ventoy is an open source tool to create a bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files.
With Ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)/EFI files to the USB drive and boot them directly. You can copy many files at a time and Ventoy will give you a boot menu to select them.
Most types of OS are supported [ Windows/WinPE/Linux/Unix/VMware/Xen... ], including, x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI, ARM64 UEFI and MIPS64EL UEFI.
Basically, depending on the size of the USB, you can have ALL yourBootable ISO'son the USB. Additionally, you can also havePortable Apps,Tools,Utilities,Folders, andFiles, ALL on theNon-Bootable Partitionof the USB.
> Ventoy - Main Page
> Ventoy - Screenshots
> Ventoy - Download Page
Also, @EdTittel, a Windows Insider MVP member, wrote this in his blog . . .
> TOP 3 2020 WINDOWS 10 UTILITIES
I have created a USB using Ventoy and find it an invaluable resource. It is probably the best thing that has ever happened toBootable Media!
I hope this helps.
Last edited by Paul Black; 10 Sep 2021 at 12:29.
This is the second time I've tried AOMEI and the second time I've been burned by it. Here's the latest episode:
I have two external hard drives (G: and H:). Last night I installed AOMEI and did a disk backup to external drive H:. It worked fine. The problem started when I tried to create a bootable WinPE USB stick (which my system assigned drive letter I:). During the creation process, I started getting messages that drive G: (which wasn't even involved in anything I was doing with AOMEI) needed to be formatted in order to be usable. When I checked, the formatting on drive G: was gone. Fortunately, I didn't have anything critical on drive G:.
I had something similar happen the last time I tried Backupper - in that case, the Win PE media creation ignored my designated USB stick drive letter and reformatted one of the external hard drives.
I use AOMEI's partitioning software and have never had a problem with it. And I have to say the actual backup process worked really well. But the boot media creation process seems to have a problem with external hard drives, at least on my system.
Hello @squibbon,
VERY strange indeed, I haveNEVERhad that happen.
I have just spent some time testing [ 2 Tests ] your scenario on my system for you. As you have seen in MY previous post, I used theLinux - Create Bootable Disc Based On Linux Kerneloption and copied it to myVentoy USB.
Test 1:
- I attached an
ExternalDrive andBooted.- I pressed
F12atBootand selected theVentoy USB.- I selected
AOMEIfrom the menu and waited for it to load.- I selected
Restoreand selected aSystem Imageon theInternalDrive.- It was fine.
Test 2:
- I attached an
ExternalDrive andBooted.- I pressed
F12atBootand selected theVentoy USB.- I selected
AOMEIfrom the menu and waited for it to load.- I selected
Restoreand selected theExternalDrive.- It was fine.
I doNOTknow if this helps orNOT.
Really not applicable to my situation, @Paul Black. The issue happened during creation of a Win PE bootable USB stick using the tool with the AOMEI program itself.
Quote
