Cloning of SSD to a HD resulting in a non-bootable SSD ?!
I usually improve my systems safety by cloning my harddisks to ones of the same size, which i put in a save place after the procedure.
But with Windows 7 and my new OCZ-SSD this failes for some reason.
The SSD is a OCZ Vertex 3 240GB, the HD a Samsung SP2504C 256GB.
The SSD has just one partition with Windows 7.
The clone on the Samsung HD works fine, is bootable and seems to have received all the data from the SSD.
But the SSD does not boot any more, no matter if i remove the HD or not or what i adjust in the BIOS.
When cloning backwards, from the HD to the SSD, the SSD works again fine.
I know, that i cannot have two bootable HDs at the same time, which of course is not the plan.
Can it be, that True image switches of the boot-capability of the source-SSD and if so, can i prevent that somehow?
Mainboard: Gigabyte H67A-UD3H-B3
CPU: I7-2600K
RAM: 16GB
Windows 7 Ultimate 6.01.7601 SP1
Thanks, Thomas, Germany
Following along....I want to do this with a SSD boot drive and a backup bootable HDD. For me as you state the SSD works fine when reverse cloning from the HDD to the SSD, and that is what I would want. But one would want to try the HDD to make sure it works, and not have to clone the SSD to get it to work as you are having to do.
So, my question has been answered with respect to using TI to clone a HDD daily from the SSD, and thus have a bootable HDD, but if in doing so the SSD no longer boots then this is of no value.
Hope you get it solved.
Bob,
Some users absolutely want to use a cloned disk as a backup. Their choice.
Most commonly, users want to be able to restore a system at the disk sector level. For this, doing a disk and partition backup, storing this backup and possibly multiple versions of it on a backup disk, and using a recovery CD to restore this backup to the original disk or a different disk, is the way to go.
Doing a disk and partition backup is the same technology as doing a clone. The only difference is that a backup will store the data being moved in a temporary storage file (a TIB archive file), while a cloning process will lay out the data immediately in the target disk.
Thanks Pat. Yes, the image backups is what I use now and it works fine for backup purposes.
For the SSD bootable system a cloned HDD "bootable" backup is what I am looking to do. This will allow immediate boot to the HDD and use of the PC. This instead of waiting for a replacement SSD and replacement of files with the image from a total backup to a HDD.
Thomas...check out "Casper" as it will possibly result in a working SSD after cloning.
http://www.fssdev.com/
I am planning a new PC using a SSD as a boot drive. I would like to use a HDD as a bootable back to the SSD.
Q1. Can Casper clone from the SSD > HDD on a daily/weekly basis. Then if the SSD fails I can boot from the HDD?
Q2. Can I clone the SSD from the HDD if the SSD needs replacement?
Q3.. Can I use an additional 2nd HDD for daily changes to the SSD?
It's yes to all.
NOTE: By default, Casper will maintain the partition alignment strategy of the source device unless it can identify the destination as a solid state (SSD) or long data sector (LDS) device. For example, if the source partitions are aligned to optimized boundaries, then Casper will align the destination partitions to optimized boundaries. Conversely, if the source partitions are aligned to traditional (e.g., cylinder/head) boundaries and the destination is not an SSD or LDS device, then Casper will align the destination partitions likewise. If Casper can identify the destination as an SSD or LDS device and the source device defines unaligned partitions, Casper will align the destination partitions to optimized boundaries.
Optimized partition alignment is done in the same manner as Windows Vista and later.
Because USB and Firewire interfaces can make it impossible for products like Casper to identify a solid state drive when attached via USB or Firewire, it may be necessary to force Casper to use Optimized partition alignment when using one of these interfaces to attach a solid state drive.
Follow this procedure to force Casper to use optimized partition alignment on the destination disk:
Start Casper
Click Explore to open Casper Explorer
From the Tools menu, click Options
On the General tab within the Settings box under Partition Alignment, select Optimized
Click OK to apply and close the dialog
With Optimized selected, Casper will always optimize the alignment of the partitions on the destination device - regardless of the alignment on the source device. Optimized alignment is essential for all SSD and LDS devices.
Regards,
--Jim
Technical Support
Future Systems Solutions
NOTE: Casper has a SmartClone feature:
http://www.fssdev.com/products/casper/smartclone.aspx
Auto clone from the SSD >> HDD with only the changes that occur...equal fast daily clones!!
Interesting product. How does this work? Can you have the SSD and the clone at the same time in the computer through some boot manager?
You would schedule the clone at some point, daily, weekly, etc. It will then only copy changed files to the bootable cloned HDD so the procedure is quick. This keeps the HDD up-to-date from changes on the SSD. Some cheapo HDD would work fine and doesn't take long, but it gives you a bootable backup to allow the PC to be used, AND can be used to clone the new replacement SSD when installed.
So the clone stays attached to the computer the whole time, or just during the cloning updates? Can the clone be attached when you boot?
For my use, the cloned HDD is internal in the PC (desktop/workstation type). I suppose one could use a USB HDD however.
I use a USB HDD for backup weekly and keep offsite.
Yes, you can keep the clone attached at all times since the SSD is the boot drive.