F5F Stay Refreshed Software General Software Check if the Clone drive appears in Macrium Reflect's list on your desktop.

Check if the Clone drive appears in Macrium Reflect's list on your desktop.

Check if the Clone drive appears in Macrium Reflect's list on your desktop.

Pages (2): Previous 1 2
S
squirelymayo
Member
89
07-11-2016, 12:39 AM
#11
A waste of time on a drive.
Restoring our C drive might take about an hour or two?
How often will you do that?
An image lets the rest of the drive be used for anything.
S
squirelymayo
07-11-2016, 12:39 AM #11

A waste of time on a drive.
Restoring our C drive might take about an hour or two?
How often will you do that?
An image lets the rest of the drive be used for anything.

M
MR_SYKE
Junior Member
41
07-11-2016, 01:22 AM
#12
When an SSD fails, replacing it with a clone is quicker than restoring from an image. Simply swap the drive and then transfer any new data onto the replacement.
M
MR_SYKE
07-11-2016, 01:22 AM #12

When an SSD fails, replacing it with a clone is quicker than restoring from an image. Simply swap the drive and then transfer any new data onto the replacement.

T
thebjmax1
Senior Member
395
07-12-2016, 12:41 AM
#13
How crucial is an additional 15 to 60 minutes for you, unless it happened every day?
Cloning has certain limitations not present in imaging.
Cloning is usually the preferred option when switching from a functional drive to another, such as when your old drive is still working but too small, or when transitioning from HDD to SSD.
Imaging tends to be the better choice for recovering from serious issues...like a failed drive, corrupted software, viruses, etc., which are types of disasters.
Choose what suits you best.
T
thebjmax1
07-12-2016, 12:41 AM #13

How crucial is an additional 15 to 60 minutes for you, unless it happened every day?
Cloning has certain limitations not present in imaging.
Cloning is usually the preferred option when switching from a functional drive to another, such as when your old drive is still working but too small, or when transitioning from HDD to SSD.
Imaging tends to be the better choice for recovering from serious issues...like a failed drive, corrupted software, viruses, etc., which are types of disasters.
Choose what suits you best.

F
Firewolf361
Junior Member
49
07-16-2016, 11:55 PM
#14
Faster? Yes, but waiting an hour for an Image to save itself to a replacement drive, every few years or so, is quite bothersome. With an Image, you can also perform Incremental or Differential backups. A clone represents a single moment in time. I run an Incremental backup every night across all six drives, saving them in a folder structure on my NAS. Each nightly increment takes only a minute or two. I can restore any or all drives to their state from the past 30 days. A clone happens once. In three weeks from now, your clone will be three weeks old. With Images, you can utilize the entire rest of the target drive. With a clone, that’s not possible.
F
Firewolf361
07-16-2016, 11:55 PM #14

Faster? Yes, but waiting an hour for an Image to save itself to a replacement drive, every few years or so, is quite bothersome. With an Image, you can also perform Incremental or Differential backups. A clone represents a single moment in time. I run an Incremental backup every night across all six drives, saving them in a folder structure on my NAS. Each nightly increment takes only a minute or two. I can restore any or all drives to their state from the past 30 days. A clone happens once. In three weeks from now, your clone will be three weeks old. With Images, you can utilize the entire rest of the target drive. With a clone, that’s not possible.

A
adamgames2016
Member
133
08-03-2016, 09:20 PM
#15
For imaging/snapshotting, the suggested intervals are once a day, every hour, every two hours, or continuously in real-time. This approach helps avoid creating excessive files that could complicate recovery efforts.
A
adamgames2016
08-03-2016, 09:20 PM #15

For imaging/snapshotting, the suggested intervals are once a day, every hour, every two hours, or continuously in real-time. This approach helps avoid creating excessive files that could complicate recovery efforts.

O
okA_
Member
141
08-03-2016, 10:49 PM
#16
I generate images once a month. I retain the latest two. If my drive stops working now, I would restore an image I created about two weeks prior.
My Windows and applications evolve gradually. It doesn’t really matter if my restored image is from two weeks ago. If they changed more often, I’d likely create a new one weekly or as needed.
I only use full images. Some use increments or differentials.
A complete image forms a single large file. Store it in a location that accommodates its size—preferably outside the main image partition, maybe on an external drive. By default, it gets a random name like m30qx08er8ssir0svv2.mrimg, which makes dating easy.
My personal data updates every hour. I perform backups several times daily using another program, not Macrium. If I had to restore personal information, it would remain within a few hours of being outdated.
Images are saved on a partition-by-partition basis. You decide which partitions to include in the file.
I treat the image backup just like any other important personal data file.
You’re clearly the best at determining how often you should back up. Most people don’t bother at all.
O
okA_
08-03-2016, 10:49 PM #16

I generate images once a month. I retain the latest two. If my drive stops working now, I would restore an image I created about two weeks prior.
My Windows and applications evolve gradually. It doesn’t really matter if my restored image is from two weeks ago. If they changed more often, I’d likely create a new one weekly or as needed.
I only use full images. Some use increments or differentials.
A complete image forms a single large file. Store it in a location that accommodates its size—preferably outside the main image partition, maybe on an external drive. By default, it gets a random name like m30qx08er8ssir0svv2.mrimg, which makes dating easy.
My personal data updates every hour. I perform backups several times daily using another program, not Macrium. If I had to restore personal information, it would remain within a few hours of being outdated.
Images are saved on a partition-by-partition basis. You decide which partitions to include in the file.
I treat the image backup just like any other important personal data file.
You’re clearly the best at determining how often you should back up. Most people don’t bother at all.

L
LForLoser_
Member
79
08-09-2016, 10:12 AM
#17
It all depends on your setup. There isn't a single ideal method. I perform nightly, every other day, weekly incremental backups, or full backups regularly. Each system behaves differently. My primary system uses full backups, supplemented by nightly incremental copies for each drive. Maintain backups over a rolling 30-day period. For my smaller HTPC, a full image is taken once a week. Retain five copies. My spouse's system keeps full images every other day, also maintaining a rolling 30-day backup. If you require a particular file from the past week, Macrium allows mounting an image as a drive letter. Determine the desired date, mount the appropriate image, and retrieve the needed file. Or, in case of a severe infection, revert to an image created before the issue occurred.
L
LForLoser_
08-09-2016, 10:12 AM #17

It all depends on your setup. There isn't a single ideal method. I perform nightly, every other day, weekly incremental backups, or full backups regularly. Each system behaves differently. My primary system uses full backups, supplemented by nightly incremental copies for each drive. Maintain backups over a rolling 30-day period. For my smaller HTPC, a full image is taken once a week. Retain five copies. My spouse's system keeps full images every other day, also maintaining a rolling 30-day backup. If you require a particular file from the past week, Macrium allows mounting an image as a drive letter. Determine the desired date, mount the appropriate image, and retrieve the needed file. Or, in case of a severe infection, revert to an image created before the issue occurred.

Pages (2): Previous 1 2