TI Home 2009 - Question About Backup to NAS

If the bootable CD sees the NAS then it will backup to it. But I'm not sure about it being formatted as EXT2 - maybe someone else will comment on this.

bump

AKFubar:

If you are backing up from a PC to the NAS, or restoring from the NAS to a PC, it doesn't matter which file system is in use on the NAS. As long as the NAS is publishing a standard file share using Windows networking or Linux Samba, it won't matter.

Thanks for your replies Mark and DwnNDrty!

Cheers!

Hello AKFubar,

Thank you for posting your question, I would like to add some information to the advises posted by DwnNDrty and Mark.

If you schedule a task in an Acronis backup product to save an image to a mapped drive, you may find that the operation does not succeed sometimes, and sometimes it does. When you map a drive, it becomes mapped only under your Windows account. The Acronis product runs its tasks using the system account and so it is sometimes impossible to locate your mapped drive (especially when you are logged off).

Please use a full UNC path (e.g. \\server\share\) instead of a mapped drive.

You can also use a pre backup command to mount the mapped drive for an Acronis scheduled task:

1. Download map.drive.txt;
2. Follow instructions in Using Batch Files in Acronis True Image.

Please let us know the results, we should be sure that the program runs flawless for you. If the provided information is not clear or if you have any other question do not hesitate to post them and we will be glad to answer.

Thank you.

I have TI Home 2009 installed (build 9809).

I have scripts that do partition backup to a NAS. The NAS requires login credentials, which are in the scripts. The scripts were created when I used TI Home 9.0.

I upgraded to TI Home 2009 earlier this year, and the old scripts continue to work under TI Home 2009. (However, TI2009 will not edit these old scripts.) These scripts appear in a section titled "Custom tasks".

I have tried to create a new, editable, script with TI Home 2009 to do the identical backup as one of the old scripts. The new script appears at the bottom in a section called "Backup". The script does NOT work. During edit, I entered the credentials and clicked the test button and received a success message. But, when I attempt to execute the script, I immediately get a login error:

Failed to run the task
Failed to execute the task script. Error #1326 - "Logon failure: unknown user name or bad password (0xFFF0)"

The status line at the bottom of the window has additional information: code = 8007052E

When I edit the script again, I receive a message on an early step: "The login information is not valid". I continue to the "Target archive" step and go to the "browse for location" dialog. I click "authentication" on the toolbar, and the previously entered credentials appear in the dialog. I click the test button and receive "connected successfully" again. Clearly, the credentials are entered and stored correctly. Just as clearly, they are not being used correctly by the scheduler.

The script has a pre-backup user command that executes a batch file. The batch file uses "net use d:" to log in to the remote folder, then deletes existing files, then logs out and deletes the attached drive. The pre-backup command has both command options checked:
) Do not perform operations until the command's execution is complete.
) Abort the operation if the user command fails.

This scheme works perfectly under the old script, both with 9.0 and with 2009. Under the 2009 script, the batch file is never executed. (The batch file records success or failure in a file. If it was executed, I would have results in a new file. The old file is untouched.)

I have several issues:
1) Why is my pre-backup batch file not executed with the new script, but is executed under the old script?

2) Why does the remote login work in the TI2009 login test, but fail when the script is executed?

3) Why do TI 9.0 scripts work with both 9.0 and 2009, but 2009 scripts will not work with 2009?

4) Why is there no ability to edit 9.0 scripts and/or convert 9.0 scripts to the format required by the 2009 script editor?

Although the script editor in version 9.0 was extremely clumsy, I am considering going back to it, as that version seems more competent, and I can at least edit scripts that work.

Update:
==========
Using a packet sniffer (Wireshark) I have discovered that no network activity to the NAS ever occurs with the new script. (Using the old script, I see where packets where logins occur)

What is the scheduler trying to do? Login to the source machine? The credentials are for the UNC of the remote machine! How can it claim there is a login failure to that machine when it never makes any attempt to login?

Hello Phillip,

Most probably, there is some issue with Acronis Scheduler service that is responsible for all tasks. So to fix if, I may suggest you to update Acronis Scheduler module:

• Download Acronis Scheduler which is a special utility to update the service using this link;
• Extract the downloaded and run install.bat. This utility will automatically update the service;

Check if the issue is resolved. If it's not, please proceed with the below steps:

• Reboot the machine;
• Recreate all tasks from scratch.

Please let me know if the issue still persists or if you have any additional questions, I'll be glad to help you.

Thank you.