Naming of archives and an error message

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 0

Hello,

I wanted to ask about 2 things:

1. When making an incremental backup with time/datestamps, the archive name is that of the first (full) backup. However, after several backups, the archive name suggests an outdated backup because it has not changed. Why is it not possible to have a general name for the archive (like documents) and subsequently time-stamped names for the individual backups. Something like this (in the recovery tab):

- Documents
Documents_1/1/2010 (full backup)
Documents_1/5/2010 (incremental b.)
Documents_1/10/2010 (incremental b.)

Currently it is like this:

- Documents_1/1/2010
Documents_1/1/2010 (full backup)
Documents_1/5/2010 (incremental b.)
Documents_1/10/2010 (incremental b.)

You can manually rename the archive, but I would rather prefer if one could specify a completely different archive name.

2. I am using Acronis True Image Home 2010 and I'm getting "invalid script file" entries in the "Task&Log" Panel when performing a task. Sometimes they go away after, but sometimes they do not.

Mon, 07/19/2010 - 21:42
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Hello Johannes!

Welcome to our Forum, and thank you for finding time to join us! I understand your concerns and will be glad to address them.

I regret to inform you that currently style of naming the archive can hardly be changed, due to lot of processes related to it. But this is very valuable suggestion, and be sure I'll forward it to the Development team in a minute. They will take it under consideration and see whether there's any possibility for implementing it in the next releaze.

"Invalid script file" refers to the traces of deleted backup plans, which were left in the registry. It doesn't affect products stability or backup performance, but can be rather annoying. I'm glad to inform you that it can be easily resolved. Please follow the below instructions:

  1. Download Scheduler Manager, run it (Start -> Run -> cmd, browse the folder it's saved to and run it) and issue the following command: 
    task zap
    It will clear all the traces of all tasks left
  2. Download Scheduler Update and run it on the problem machine. It will update all necessary components automatically
  3. Reboot the machine
  4. Recreate the tasks

This should resolve the issue faced.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!

Tue, 07/20/2010 - 14:06