Anyone VERY experienced with Acronis True Image and Raid configurations?

----I limit my OS partition size to 40 to 60 GBs (with 600 GB of space!), enough room for the OS, the apps, temp files, and 60% extra 'head room' for whatevers and defrag. When cloning though, I try to limit the cloned image size to 8 to 12 GBs by not cloning freespace and making sure no unneeded data is present when cloned. Since I use seperate data HDs, this is easy to do. This solution will not work for all, or will need to be modified. I always try to keep my OS and data on separate HDs.

Remember to reset your page file to minimum size and so it's on the same partition as the OS before you clone! I usually make the page file setting after it's cloned to the second of my logic disk's OS partitions (sized just for that purpose) with a ton of unused freespace on the 'back' of that logic disk for better speed. Partitions toward the 'back' of the RAID disk transfer data slower than the 'front', and disks with more freespace will run noticeably faster.

OS partition> page file partition> freespace or data partition if separate HD(s) aren't used.

Remember to set up a partition for the image on the HD that your cloning to if you wish to store additional data or use the space for a page file etc. Otherwise Acronis will usurp the entire drive and create a single partition, oops! Remember to specify the removal of image slack space, and to delete or transfer unneeded files before you clone to minimize the image size and time needed to clone it. You may simple wish to keep an activated copy of the OS with only the mobo and vid drivers loaded, but no apps. I sometimes use multiply copies of the OS in different stages of completion; a fully loaded OS with all the apps configured is a real time saver, but can sometimes become a problem if issues with an app or MS update arise.

When you clone with Acronis you have to clone to the front of the HD and it must be free of all data/partitions or it will overwrite it when creating the clone. That's one limitation, however you can that out all of the slack space in your image to be cloned to minimize the image size. I don't use the compression feature. After you have cloned the image you can set up a second partition in the free space to store data or use as a scratch/page file disc; only disadvantage is the cloned image is always on the faster portion of the HD disc. Make sure the bios is set to boot of the new OS HD if you keep the HD with the back up clone on the same machine, something I normally do.

Having multiple HDs with same OS's with Acronis loaded can cause cloning issues and crashes which is why I as a dedicated, stand alone IDE HD for Acronis; Acronis is never installed on my main OS or it's copies. You can work around this potential issue different ways, or as simply as just pulling the HD to be cloned and doing it on a separate computer that has Acronis loaded.

Ha-ha, things happen... remember I never claimed this was idiot dumb easy, but much better than a cold reload from scratch when you don't have the time

-I shoot my images as I live, in the open-

Hey any movie peeps need a rigger? Blackhawk for hire.

-I shoot my images as I live, in the open-

Hey any movie peeps need a rigger? Blackhawk for hire.
 
I have a raid 1 configuration using motherboard Raid, Vista and
Acronis. Restores didn't work using the Linux standalone Acronis
because the controller for the raid wasn't recognized. Support
shipped me another Linux version which recognized the controller but
didn't recognize the raid information.

I built a Vista-PE (standalone bootable Vista) that included Acronis
and the motherboard drivers for the Raid controller. That worked
fine. I kind of wish Acronis would go this way rather than use Linux.
-- Linux has caused me nothing but trouble including 'seeing' RAIDed drives and not seeing others depending on the controller during installation. It saw my secondary Silicon Image, but not my mobo's Intel main controller. What a dumb bird...

-I shoot my images as I live, in the open-

Hey any movie peeps need a rigger? Blackhawk for hire.
 
----I limit my OS partition size to 40 to 60 GBs (with 600 GB of
space!), enough room for the OS, the apps, temp files, and 60% extra
'head room' for whatevers and defrag. When cloning though, I try to
limit the cloned image size to 8 to 12 GBs by not cloning freespace
and making sure no unneeded data is present when cloned. Since I use
seperate data HDs, this is easy to do. This solution will not work
for all, or will need to be modified. I always try to keep my OS and
data on separate HDs.

Remember to reset your page file to minimum size and so it's on the
same partition as the OS before you clone! I usually make the page
file setting after it's cloned to the second of my logic disk's OS
partitions (sized just for that purpose) with a ton of unused
freespace on the 'back' of that logic disk for better speed.
Partitions toward the 'back' of the RAID disk transfer data slower
than the 'front', and disks with more freespace will run noticeably
faster.

OS partition> page file partition> freespace or data partition if
separate HD(s) aren't used.

Remember to set up a partition for the image on the HD that your
cloning to if you wish to store additional data or use the space for
a page file etc. Otherwise Acronis will usurp the entire drive and
create a single partition, oops! Remember to specify the removal of
image slack space, and to delete or transfer unneeded files before
you clone to minimize the image size and time needed to clone it. You
may simple wish to keep an activated copy of the OS with only the
mobo and vid drivers loaded, but no apps. I sometimes use multiply
copies of the OS in different stages of completion; a fully loaded OS
with all the apps configured is a real time saver, but can sometimes
become a problem if issues with an app or MS update arise.

When you clone with Acronis you have to clone to the front of the HD
and it must be free of all data/partitions or it will overwrite it
when creating the clone. That's one limitation, however you can that
out all of the slack space in your image to be cloned to minimize the
image size. I don't use the compression feature. After you have
cloned the image you can set up a second partition in the free space
to store data or use as a scratch/page file disc; only disadvantage
is the cloned image is always on the faster portion of the HD disc.
Make sure the bios is set to boot of the new OS HD if you keep the HD
with the back up clone on the same machine, something I normally do.

Having multiple HDs with same OS's with Acronis loaded can cause
cloning issues and crashes which is why I as a dedicated, stand alone
IDE HD for Acronis; Acronis is never installed on my main OS or it's
copies. You can work around this potential issue different ways, or
as simply as just pulling the HD to be cloned and doing it on a
separate computer that has Acronis loaded.

Ha-ha, things happen... remember I never claimed this was idiot dumb
easy, but much better than a cold reload from scratch when you don't
have the time

-I shoot my images as I live, in the open-

Hey any movie peeps need a rigger? Blackhawk for hire.

-I shoot my images as I live, in the open-

Hey any movie peeps need a rigger? Blackhawk for hire.
My Primary Hard Drive BOX is a 360 Gb SATA premium 24/7 type drive. Partition C: has 97.6 Gb with 20.9 Gb used with ONLY the installed OS (XP Pro) plus Installed Software and NO user files.

Partition D: of the same BOX is 200 Gb with only 6 Gb used and all of this is for support drivers, downloads, software source Versions, etc that is needed (if and when) I have to do a complete re-install of everything such I had to do for this computer 9 months ago when new. NO user files on this Drive.

Yes, I could use a smaller capacity drive but the price of the better drives of the small capacity is very close to the drives up to (and through) 500 GB -- so I chose to use the present size drive.

I don't use RAID of any type so that would evidently be a plus for using Acronis -- based on some of the comments I have read. I keep the present photo images available for immediate use -- plus 2 full backups at all times so "Hopefully" I am covered especially since one set is off site in my Bank Lock Box....
--
Vernon...
 
My Primary Hard Drive BOX is a 360 Gb SATA premium 24/7 type drive.
Partition C: has 97.6 Gb with 20.9 Gb used with ONLY the installed OS
(XP Pro) plus Installed Software and NO user files.
Partition D: of the same BOX is 200 Gb with only 6 Gb used and all of
this is for support drivers, downloads, software source Versions, etc
that is needed (if and when) I have to do a complete re-install of
everything such I had to do for this computer 9 months ago when new.
NO user files on this Drive.
Yes, I could use a smaller capacity drive but the price of the better
drives of the small capacity is very close to the drives up to (and
through) 500 GB -- so I chose to use the present size drive.
I don't use RAID of any type so that would evidently be a plus for
using Acronis -- based on some of the comments I have read. I keep
the present photo images available for immediate use -- plus 2 full
backups at all times so "Hopefully" I am covered especially since one
set is off site in my Bank Lock Box....
--
Vernon...
--The hard drive size isn't an issue to speed, but the platter size does impact the potential read/write speeds. A SATA2 interface with a SATA2 HD also will give a noticeable speed increase.

To spite what some say, Acronis and hardware implemented RAIDed disks get along fine; Acronis doesn't 'see' individual HDs, just the one logic disk as define by the hardware controller and the RAID info on the HDs themselves. Windows behaves the same way, and I'm pretty sure of this because the HD S/Ns are invisible to Windows on RAIDed disks, but are visible on the same machine when not in a RAID configuration. The dumber you keep MS, the better. I have used Acronis on both my Intel and Silicon Image RAID controllers with no issues at all. People will have issues if they don't quick zero fill HDs before they clone to them; on a RAID system EACH hard drive MUST be zero filled as they all contain RAID volume data used by the controller IF the RAID configuration is changed. A full format will not delete this data or some that Windows adds during installation. Sometimes a full zero fill is needed, and again it must be all the HDs in that array. A single HD from a broken array should be zeroed out to avoid possible issues with the mobo/card RAID controller.

Many times I will use the RAID controller's bios based utility window to delete the array and recreate a new one before I clone to the new RAID logical disk, most times this will work with no zero filling needed, but not always! When in doubt or when fresh loads keep crashing for no apparent reason, zero fill.

Occasionally data in other sections of the HD other than the boot can cause issues, especially malware, a full zero fill is warranted for this and will cure the seemingly impossible problems sometimes. I try to avoid this on all except new HDs as it takes a long time to zero fill 4 HDs!

It's a very good idea to do a full zero fill on all new HDs and it helps to test them as well. All new HDs should at the very least have a quick zero fill done before being use. This can save a lot of time, trouble, and potential grief in the future. A HD will sometimes become 'dead' and not fully accessible even by the controller due to errors in it's boot sector. I just had this happen with one of my Raptors; a full zero fill fixed it. Ha-ha remember if your clone copy HD fails you lose your back up, best to have two!
 
Holy smokes, that's a lot of info that I didn't understand.

Thanks though, I'll pass it on.
--
George with the (big) rack
 
I got the puter yesterday delivered by UPS and it was all broken to hell. They must have dropped it from the big truck on the ground or something. The box didn't look as bad as the computer but even if you drop it flat, there would be no damage to the box but the insides would be jolted all to hell.

The metal tabs that have the screw holes for the drive cages to be mounted to the back of the computer were twisted all to hell so whatever they did to it, they must have tossed it around pretty bad. I tried to bend the tabs with my bare hands and I could barely move them so they are very thick and they were all bent to hell :(

Now for the fun part, trying to collect on the computer. Luckily, I had the builder take it to the UPS store and had THEM pack it and insure for the full price.

However, this is going to be another set back because now it's going to take another very long time to redo or fix this :(

So, depending on what they do, I may have him redo the whole thing.

I will insist on having them pick up the box and just pay up but we'll see. I've already talked to my lawyer just in case so he's kinda standing by. I paid over $60 just in insurance but that usually doesn't mean shi*.

Here's a question, how much will a RAID 0+1 slow things down vs Raid 0?

Ie, having three Raid 0 drives that are then mirrored into a second array of identical drives?

In case I haven't mentioned it, he also installed ALL my software which is another reason the build took so long. I wanted ALL of installed and tested and then an image made.
--
George with the (big) rack
 
for me has NEVER been about BACKING up my stuff. I simply do NOT want to have to REINSTALL ALL my software every time the computer gets "dirty" or crashes. I have just about all my files in a WORK directory which I back up every so often with Laplink or something. That is NOT the issue for me. I want to be able to get back up and running simply and smoothly in case something happens.
--
George with the (big) rack
 
The few times I have used my acronis on my current laptop, it has worked fine and of course, with the exception of the time I deleted ALL my acronis images. That was a set back :)

It is super simple to make an image and equally simple to restore it. I definitely recommend you download the trial and give it a shot. IF you do, e mail me and I'll talk you through ONE option that some people miss that is pretty important.
--
George with the (big) rack
 
It is simpler to have a separate partition or separate drive on the same computer where you store your images (of course, backed up somewhere else) and from there, RESTORE the image to where it is going. C partition or whatever. Very smooth. Didn't work as well from external sources.
--
George with the (big) rack
 
George.
Just my 2 cents to the whole situation......

FORGET about an internal RAID. No matter if it's a 0, 0+1, 5 or whatever. I've lost an internal RAID 0+1 about 18 months ago. No warning about bad disks whatsoever, but nonetheless actually 3 of the 4 disks had errors, and I lost the work (and photos!!!) of the last 7 months! A nightmare!

Get your self 3-4 good and fast HD's:
1:OS
2:APPS
3:Data/Swap
(4):Swap

Make images of 1 and 2. (don't forget to make new images if you install new apps :) )

Get yourself an external Storage Server - preferably with a RAID 5. I've got a 4GB Buffallo Terrastation Live standing next to me, and it works wonders. For synchronisation I use Mobility Basic ( http://www.mobility.com ).
It synchronises at a time-interval of your choice (weeks, days, hours).

But as I started saying - just my 2 cents....

Regards
Lars
 
I've tried several linux distros with my new mobo and it sounds similar to your issues. I put together a ASUS P5Q-E that uses the P45 chipset (no RAID). Works great with Win XP Pro but I can't find a single linux distro that recognizes the drives correctly. PATA not at all. I also tried the Seagate and Maxtor backup software that is based on Acronis product and neither worked correctly. I think one of the distros scrambled my SATA NTFS boot partition. I'm not a linux person so don't have enough experience to track the problem and had to give up and stay with XP. Your posts sound similar. I'd appreciate any idea how to config/install any linux distro, if possible. Have a great day.
 
A copy would be kept somewhere else. OR as you said from another drive but from within that same computer. Makes it simpler
--
George with the (big) rack
 
For starters, I have the external NAS which I will probably keep for a second backup.

IF they compensate me now, I may add an INTERNAL RAid 5 for storage in addition to the regular OS drives and so on, we'll see.

The Raid 0 was for speed only.
--
George with the (big) rack
 
the case from a fairly high position and it coming to a complete halt. The case itself did fairly well but the drive cages that were heavy, must have continued to travel so to speak due to their mass before finally getting ripped off their mounts. The guy didn't ship it broken and UPS store packed it and since it has acrylic covers, the store would have noticed it if the computer guy tried to ship something not attached properly.
--
George with the (big) rack
 
Don't use another partition, you always want to use a separate
physical drive, otherwise a drive failure will wipe out the original
data and the backup.
Torsten, you are absolutely correct. In fact, Each time I make a Backup of my Primary drive BOX, I use a different Hard Drive (BOX) to write the Image file TO.

I always have 3 Backups with each stored on different hard drive units so to have some assurance of having a (NOT too distant in time) backup. I backup the Primary Drive BOX every 10 days to 2 weeks.
--
Vernon...
 
My Primary Hard Drive BOX is a 360 Gb SATA premium 24/7 type drive.
Partition C: has 97.6 Gb with 20.9 Gb used with ONLY the installed OS
(XP Pro) plus Installed Software and NO user files.
Partition D: of the same BOX is 200 Gb with only 6 Gb used and all of
this is for support drivers, downloads, software source Versions, etc
that is needed (if and when) I have to do a complete re-install of
everything such I had to do for this computer 9 months ago when new.
NO user files on this Drive.
Yes, I could use a smaller capacity drive but the price of the better
drives of the small capacity is very close to the drives up to (and
through) 500 GB -- so I chose to use the present size drive.
I don't use RAID of any type so that would evidently be a plus for
using Acronis -- based on some of the comments I have read. I keep
the present photo images available for immediate use -- plus 2 full
backups at all times so "Hopefully" I am covered especially since one
set is off site in my Bank Lock Box....
--
Vernon...
--The hard drive size isn't an issue to speed, but the platter size
does impact the potential read/write speeds. A SATA2 interface with
a SATA2 HD also will give a noticeable speed increase.
To spite what some say, Acronis and hardware implemented RAIDed disks
get along fine; Acronis doesn't 'see' individual HDs, just the one
logic disk as define by the hardware controller and the RAID info on
the HDs themselves. Windows behaves the same way, and I'm pretty
sure of this because the HD S/Ns are invisible to Windows on RAIDed
disks, but are visible on the same machine when not in a RAID
configuration. The dumber you keep MS, the better. I have used
Acronis on both my Intel and Silicon Image RAID controllers with no
issues at all. People will have issues if they don't quick zero fill
HDs before they clone to them; on a RAID system EACH hard drive MUST
be zero filled as they all contain RAID volume data used by the
controller IF the RAID configuration is changed. A full format will
not delete this data or some that Windows adds during installation.
Sometimes a full zero fill is needed, and again it must be all the
HDs in that array. A single HD from a broken array should be zeroed
out to avoid possible issues with the mobo/card RAID controller.
Many times I will use the RAID controller's bios based utility window
to delete the array and recreate a new one before I clone to the new
RAID logical disk, most times this will work with no zero filling
needed, but not always! When in doubt or when fresh loads keep
crashing for no apparent reason, zero fill.

Occasionally data in other sections of the HD other than the boot can
cause issues, especially malware, a full zero fill is warranted for
this and will cure the seemingly impossible problems sometimes. I
try to avoid this on all except new HDs as it takes a long time to
zero fill 4 HDs!
It's a very good idea to do a full zero fill on all new HDs and it
helps to test them as well. All new HDs should at the very least
have a quick zero fill done before being use. This can save a lot of
time, trouble, and potential grief in the future. A HD will
sometimes become 'dead' and not fully accessible even by the
controller due to errors in it's boot sector. I just had this happen
with one of my Raptors; a full zero fill fixed it. Ha-ha remember if
your clone copy HD fails you lose your back up, best to have two!
You have probably (in the past) mentioned what software you use to Zero fill Hard Drives but I either missed that or didn't keep a reference to that information.
What software do you use to Zero Fill ??

Your comments regarding different RAID Controllers makes me believe that if a Controller completely Fails, there may be issues of using another controller in order to read the contents of the Drive(s).
--
Vernon...
 

Keyboard shortcuts

Back
Top