TeraByte Unlimited

@anastrophe
First, thank you for your kind words. I often wonder if these batch scripts are of use to other users, so it is good to hear some positive feedback!

Second, I must apologise for the bad download link. I have corrected it just now.

Thirdly, could you let me know of the problems you are having using the IFW_Backup scripts, either on the forum or to my email address in the documentation. This will enable me to make any required improvements.

Kind regards

Regrettably I am still getting the same error. I've checked the IFW_Env.cmd file, it has the correct disk selected as before "(set par0=/d:w2)". The script chooses the correct source disk, attempts to begin incremental imaging, then fails with "IFW error code = 8". I've attached screenshots which give better clarity into the exact machinations. I've double checked the disk ID, it is as specified, and I've performed a full backup directly from IFW itself using the same settings.

Puzzling.

your partitioning or signature changed on the source drive, you'll need to create a new full.

Interesting and odd. No changes to my hardware/partitions/etc since last full backup, only change had been updating IFW itself. But indeed, forcing a new full appears to have "cured" it. Thank you very much!

21-Oct-2023 Vn 4.18 - Enhancements.

• Added an alternate 'set rax' (Run After) entry in the IFW_Env.cmd file, which can be used to strip any MyDefrag logs from the combined log that can be viewed with the 'TBI Notify' utility.
• Clarified some documentation.

Thanks Tom.

TeraByte Support wrote: ↑Sun Oct 22, 2023 4:56 am Thanks Tom.

Thank you Tom, much appreciated.

When I ran the IFW_Backup_Set_up_4.18 to update my current scripts, where the new 'sets' were shown, it also showed a lot of the script itself. I presume not intentional, thought I should let you know.

Hi YesAndNo

The screenshot looks completely normal if the update was from a version prior to Vn 4.16. It is showing the additional entries that were created from Vn 4.16 up to the current Vn 4.18. This report is designed to bring these additions to your attention in case you wish to make use of these new options.

The 'set rax' run-after entries do involve a few lines of batch code to be executed, if one of these entries is activated. Here is a quote from that part of the IFW_Env.cmd file:

Use one of the default rax entries to make the latest logs available to
the 'TBI_Notify' utility. You can change the number in 'set num=10' in
the first line to specify how many of the latest old logs to append,
or you can set this to -1 to append all the logs.

Select either the first 'rax' entry to make the complete logs available
or use the second 'rax' entry which suppresses any MyDefrag logs from
the copied files.

Cheers

Okay, thanks a lot Tom.