Aller au contenu principal

4 .tid backup files

Thread needs solution

Hello, First time ive had to use Acronis, hard drive packed in last night :o( but i made a back up of the drive earlier.

Problem im having is when i load the boot disc into my machine with its new hard drive it seems to be able to load only one of the back up files (four were originally created at 14GB each onto my usb hard drive a couple of months ago)

Message of mising Bootmgr message when finished.
I repaired this with a Win 7 disc, but seems much of my original old hard drive data is missing

Sorry, very new to Acronis, so probably something silly at my end..... suggestions welcome.

0 Users found this helpful

Which version of TrueImage and which version of Windows?

Click on link #3 and locate item #2 inside that link. The #2 link provides a procedure for restoring a new disk which is the easiest method.

Regarding the backup files, was this a single backup split into 4 files of 3 equal size plus the smaller 4th"?
Or was this a series of several backup, etc?

Thanks, pretty sure its ver 11, and PC is Win 7.

Yes, this was a single full back up done at the same time.

It was put onto an external LaCie 120GB HD. For some reason the files were split up into four, each the same size, 14Gb or so...

how do we get all four loaded onto the new drive?

I'm having trouble understanding why the 14GB in size. Maybe answer to these questions would help.

What names are assigned to the backup files?
Are all of the same date and time or nearly the same time?

I am assuming that version of TreuImage in use is the 2011 version which does support Windows 7. The older version 11 does not support 7.

Note: a single 14GB size backup files would indicate the used space was about 20GB.
Four 14GB size files (comprising a single backup) would indicate a used space of about 80GB.

Sorry, i made an error on file sizes...........

MyBackup1 = 3.99GB
MyBackup2 = 3.99GB
MyBackup3 = 3.99GB
MyBackup4 = 2.86GB

these were taken at the same date/time

i`ve looked at the old drive, it is a Maxtor 60GB item

Are Acronis boot discs all the same? I had to use one from a different version

thanks for help so far......... i am self-employed and this has all my work data on it

Yes, these files would indicate that a single backup was split automatically into 4 pieces and the cause of the split was most likely that the storage disk has a FAT32 file system. In order for the split not to occur, you would need a STORAGE disk which as a NTFS file system.

you should be able to boot from the TrueImage Rescue CD and choose "MyBAckup4" as to what should be restored and the entire 4 parts will be installed. You can use my illustration #2 or #3 listed inside link #3 below. Use whichever guide is most applicable to your situation.

Update!

Well i followed your instructions and it seemed to load in ok and gave the `success` message at the end.

However on reboot i got the `Bootmgr not found` message.
I got around that by doing a `repair` off a Win7 disc.

It then took a long time to boot, it could not find the desktop file and only loaded a black screen for the Desktop.

seems like a lot of the data is missing, Documents, Pictures, control Panel etc all empty. However the Programs folder looks ok.

not looking good im afraid...

Your problems would seem to indicate that the backup was not a backup of the entire contents of your disk.

Do you have any other backup--even old ones?

Which method of restore did you use? The #2 example or the #3 example or another method?

A backup of your entire disk would have included all the items that were missing.

Did your computer have any hidden or non-lettered partitions which may have been omitted from the backup?

No other back-ups,
i used no.2 example,
no other partitions,

would it possibly be a backup of a FAT32 drive onto a NTFS drive thats doing this? I never thought of that at the time

I could probably get away with retrieving some of the folders from the backup, can i still do that??

ps. original size was 60GB...... new drive im trying to load to is 80Gb

The backup file has not been changed. You should be able to retrieve individual files or folders.
The copy of a fat32 drive onto an NTFS disk as part of a backup store would not have a bearing.

As you are restoring to a larger drive, I would suggest that you use the example #1 in the #3 link below.

Perhaps post a screen capture of your disk structure. Open Window Disk Management graphical view and this view will show you the partition layout that current exists on your computer.

If your restore was on top of the old disk, the restore may have changed this from the original but it might give us a clue as to your problems. If the restore was NOT on top of the old disk, a screen capture of that disk would give us something to match to.

What brand and model laptop is involved?

Do you know whether your backup was an all inclusive backup which included all partitions--including any non-lettered partitions?

When you restored the backup, did you also checkmark the "recover disk signature? as described in the #2 guide?

It sounds like the drive letter is not correct for the restored Windows C: drive. Most likely either the Disk Signature is incorrect or the original drive "saw" the new drive (or another drive with the same signature). The problem makes it look like everything is really messed up, but it's really caused by one character being wrong in the Registry.

Are you restoring the Disk Signature also?

Is the new drive the only drive connected when restoring (besides the USB drive with the backups)?

Is the new drive the only drive connected when booting for the first time?

The basic steps would be to make sure only the new drive and the USB drive are connected. Boot to TI and restore the backup to the new drive (select to restore the Disk Signature and set the partition Active if it's the only partition). Then disconnect the USB drive, remove the TI boot media, and reboot into the BIOS. Set the new drive as the default booting drive and save the changes. Then try booting the drive.

You may also be able to fix the problem when booted into the system. The basic procedure is outlined in this post.