Salta al contenuto principale

Suggest A Scheme?

Thread needs solution

Due to lack of intelligence, I cannot seem to work out how to tailor my backup scheme to my requirements. This is a lack in me unfortunately and not TI.

I have a c: solid state system disk with my Win7 installation and program files plus a spinning HD d: with all my data files, pictures music, etc. I wish to back up to a USB 3 1Tb drive. A full backup of my system and data yields a 196Gb .tib file. I back up every day upon machine shut down.

What I want is backups for the last 28days and for them to be automatically cleaned up after that for space reasons. If space is spare, I'd like TI to carry on backing up. If space is short I'd like it TI to delete as necessary.

I'd amend parameters from gained experience with the scheme I decide upon until I made best use of the 1Tb disk capacity.

I'd really appreciate any help. Is my use of a USB3 drive OK, by the way?

0 Users found this helpful

David,

Are you imaging both drives to the same tib file or to put it another way, are you using one task to include both drives?

Personally I like to have separate tasks and image files for the OS drive (mine is an SSD) and my data drives (spinners). This reduces slightly the chance of loosing everything if a tib file becomes corrupted.

As far as using a USB 3.0 drive, make sure that when booted from the recovery CD Linux can see your USB 3.0 drive. You may need to attach it to a USB 2.0 port for recovery purposes.

You are better off having TI make a specific number of images and then have it delete them - size specifications have been known to cause problems.

Have you looked at Grover's Guides? I think you might find them useful.

Bear in mind, you will need to leave enough space on your drive equal to the largest image you have, plus the total of all images on your drive as TI will make a new complete image before either deleting or consolidating the old ones.

If you have any further questions on Grover's guidesetc, just post again.

There is a link to his guides in the left hand margin.

***edited typing mistake***

Thanks for those observations, Colin. I'll go through Grover's as you suggest.

I image both files to the .tib but I take your point about separate files. Presumably I can image the SSD and spinner separately but in one operation or batch.

David,

David Thorpe wrote:

Presumably I can image the SSD and spinner separately but in one operation or batch.

If you are scheduling the tasks you have them run one after the other. To do that you set the first task to run at, let's say' 7:00 am, you then schedule the second task to start anytime after that, so you could have 7:05 or if you know the first task takes on average 20 minutes you can have the second task start 20 minutes later. TI will queue the tasks so if the first is running the second will wait until the first has finished.

Here is a snipshot of my tasks. Note! I am using ABR11.5, so True Image tasks look different, but this is just to show how I have two tasks that run on from each other, TI works exactly the same way in this instance.

Allegato Dimensione
125478-106597.png 5.67 KB