TeraByte Product Release Thread

IFL - With or Without Networking?

I have always downloaded IFL with Networking even though I think that I do not need Networking.

Are there any disadvantage(s) to using IFL with Networking when you probably do not need it?

What are some examples of using the Networking in IFL?

Thanks in Advance.

 

I used to download IFL both with and without networking. The without networking disk used to boot faster but not anymore. I only download the with networking version now.

When I image the kids' computers (with IFW) the image goes to my computer. If I need to restore their OS partition I boot IFL on their computer and browse to the image on my computer.

Actually I can do the whole restore of their OS from my computer but that is more complex.

 

hi

is there a way to limit the number or the size of the incremental backup(images) via schedule in image for windows?

i mean i would like to make online a full back, a incremental backup and and keep only another incremental backup every week but no more
in short 3 files not more

i would like to have it in auto , could i do it?
let image for windows overwrite the second incremental backup

thanks
cheers

 

Sure. IFW makes differential image backups and not incremental. But I'm sure you know that.

What are your command lines for the full and the differential backups?

 

yes
sorry differential images

but can i setup to do it ?
i created a full image and a differential image , can i setup image for windows to create only 1 diffenrential image every week

in short i want to keep only 1 image , and 2 differential images not more

thanks
cheers

 

Yes, you can do that by modifying the IFW batch file. Can you post the batch files for the full and differential images?

 

i haven't a batch file
i create a backup and a differential image manually

now i would like to force image for windows to create only 1 differential image every week

 

You must have batch files. Pretend you are going to create a base image. At the Options screen click Show Command, put a tick in Save to file, OK, OK, call it "base", Save. You now have a file called base.bat.

Do the same thing pretending you are creating a differential image. Call it "diff".

Post both batch files when you are ready.

 

and have I to use the windows schedule to do it?
image for windows has a service , but it doesn't include an internal scheduler,does it?

thanks a lot Brian !

 

IFW does include a basic way of using the Windows Scheduler but we need to modify the batch file so it creates your diffs weekly but only keeps the last two.

So you could schedule your diffs to run at anytime in the day or even at 2 am followed by a shutdown. Your choice.

I suggest running the base backup manually for the time being. Whenever you need a new base backup move the current backups into another folder and then double click base.bat. The diffs will continue to be created automatically. You don't have to touch diff.bat.

 

thanks Brian always very kind

so i run image for windows , select backup change only (edit in case settings ,next select the partition , select the target file ...

now i read the manual and the help files , but i can't find for example how put only day , mouth and year (for example 12-02-12 or 12-02-2012 $YYYY$ , have not the tilde on my keyboard

edit the setting of the back up , click show command , and copy and paste

and create a new schedule to run every 2 weeks.... for example


do it right?
is the way to go,isn't?
click on schedule should do the same task but open a schedule window

what's better , command line and click on schedule?

thanks again!
by the way is there a cleaner , to make a clean install of image for windows?

 

Don't use those dated filenames. You will see why later.

Call the base backup "mantrabase"

Call the diff backup "mantradiff"

Here is an example of a base

"C:\Program Files\TeraByte Unlimited\Image for Windows\V2\imagew.exe" /b /d:w0@0xC /f:"E:\mantrabase" /vb /mp

Here is an example of a diff

"C:\Program Files\TeraByte Unlimited\Image for Windows\V2\imagew.exe" /b /base:"E:\mantrabase" /f:"E:\mantradiff" /vb /mp



Edit.... We won't be using the IFW Schedule button.

Edit.. I just copied the command line but I want you to copy the text from your batch files. They will be more complete than my examples.

 

ok i will do it
for the name i got i can't set the date in the name

by the way , no tool to make a clean install of image for windows ?
i read a topic about acronis , files left and regkey ...

 

That doesn't apply to IFW. Just install the new version over the top of the old version.

 

You must have fixed filenames in the batch files. I never use dated image names as the date and time appears next to it anyway in the Date Created column of Windows Explorer.

 

i did monitor the installer , and when i uninstall it , lefts many keys

 

Bryan... quick question. Recently tried to restore an IFW image (used sectors) to a smaller partition, even though "used" sector space was much smaller than the destination partition... it failed saying the destination partition was smaller than the source. To quickly get around this anomaly, I resized the source partition (equal to the destination) and reimaged it, then the ensuing restore was fine.

Does IFW support this type of restoration? I looked through all the cryptic options and found nothing that jumps right out at me.

Any help, greatly appreciated...

 

i guess you had to turn on Scale to Target or Scale to Fit to perform this task , is it right Brian?

i guess you have already read Method 1


thanks

 

Thanks, Mantra! I believe the COMPACT feature in the imager is exactly what Ineeded.

I'll test in the near future (one more SSD conversion to go )

 

hi

i thope it will work ,i would like to know about your next test
because i'm going to do the same job , restore an image (with 35gb of data stored in a 100gb partition) to a smaller partition (60gb)

i was sure that Scale to Fit was the right way , though i can't find this option in image for windows restore options

 

TRF,

I'm sure you are familiar with these numbers but for completeness here goes. In IFW, IFD, IFL, using the Backup choice, select a partition, Information. You will see 3 numbers. Those for my test WinXP are..

1810 MB used
2187 MB free
2087 MB to restore

The last number indicates how far the sectors in use are spread over the partition. In practice you often have to go one cylinder larger as I needed a 2094 MB partition to restore the image.

Same with the Compact option. An extra cylinder. The Compact option compacted the data to 1819 MB and this restored into an 1819 MB partition.

Edit... I wasn't using 2048 sector aligned partitions on that HD. The numbers would likely be more "correct" with 2048 sector aligned partitions.

 

bigger to smaller

i read carefully your answer ,above all to go one cylinder larger

but may i ask you a question ?

to restore an image of a bigger partition to a smaller partition (solid disk or an hard disk) taking into account about how the data is spread over the partition , conosolidation is the only way ,isn't it?

Scale to Fit (i read the manual) is not a feature for this purpose,isn't it?

by the way , about

should a consolidate defrag fix it?

thanks Brian!

 

Re: bigger to smaller

The TeraByte link you posted is very helpful. The Compact option is an easy way to do the job. Also the old method of resizing the source partition smaller and then creating an image.

It is only for Entire Drive backup/restore, not partition backup/restore.

In my experience, almost never. I don't bother trying anymore.

 

Re: bigger to smaller

thanks
but when i highlight a partition and click compact a warning come up about data loss

but the compact feature does affect the partition (does it change the partition to image) or the image file ? according the warning

in short i tried to find out a program perfect to image and restore , seems that image for windows lacks of easy feature like paragon or acronis or other software that can do it without problems

 

Re: bigger to smaller

It's just a standard warning. Data loss could occur but it must be unusual. If you look at the source partition before and after compaction you would see this... ( * is sectors in use, - is free space)

before
[***--***--*----]

after
[*******--------] (this would be with maximum compaction. You don't have to do maximum compaction)

The partition size remains unchanged. It's just the sectors in use that are moved.

Personal preference I guess. I like it very much especially the way it can be automated.