Scheduled Backups Continually Fail

Hello!
Have the following setup:

1- Server running Windows 2000 Server, fully updated

2 - Acronis TI Server 8, Build 1018

3 - Maxtor 250GB External USB/Firewire Drive connected to a networked PC and shared, Mapped from the server as E:

4 - Full backups of the Server's Raid Data drives and C: drive are done daily, in 700 MB files, along with a weekly backup of C: to the Acronis Secure Zone.

In earlier builds (700's I believe) automatic scheduling of the backup jobs worked perfectly.

Somewhere along the line of newer builds, the scheduled jobs to E: began to fail, but run perfectly when scheduling is removed and they are started manually. Only the Scheduled Secure Zone Backup continues to work.

This would seem to indicate that the scheduling function has a problem with the Networked E: drive.

Any suggestions would be appreciated!

Thanks!

 

Hello NAL44,

Thank you for choosing Acronis Server Disk Backup Software.

Please be aware that we do not recommend scheduling a task for the image creation on a mapped drive, since mapped drives are accessible only when a user you scheduled this particular task under is logged in. If this user is currently logged off a mapped drive is not accessible for Acronis True Image and therefore can not be used to save an image. Please read this FAQ article for more details.

Instead of using mapped drive(s) we recommend you to enter the full UNC path to the shared folder\drive you want to save your images to.

If you have any further questions concerning Acronis software, please feel free to submit a request for technical support or post any of them on this forum. We will certainly try to help you in resolving any issues.

Thank you.
--
Alexey Popov

 

Thanks for your reply, Alexey!

Checked the FAQ you referenced, but I don't feel it applies.

All backup functions are run and initiated directly from the server to a machine dedicated to hosting the mapped external backup drive - this machine runs 24x7, so the user under which the mapped drive runs is always logged in - the same is true of the server.

I tested scheduling on Saturday using an existing saved backup profile - starting the job with "run now" works fine - editing the job and adding a day/time, for example 15 minutes into the future, results in a failure.

Under Power Options on the "hosting machine", Standby, Hibernation, and Turn off Disk Drives are all set to NEVER, and the "Require password on resume from Standby" is checked, so a password must be entered to get by the login screen that results from the settings above, BUT the login screen notes that the user is still "logged in". Could this affect the scheduled job but not the "run now" job?

Thanks!

PS - Just tested the UNC Scheduled method again - it fails on automatic, but runs fine when I select Run Now.

PPS - Unchecked the "Require User Password when returning from Standby box and tried the automatic UNC test again - it's running. So it seems, even though Standy is set to NEVER, having the Require Password box checked causes the backup to fail ON BOTH MAPPED AND UNC Paths EVEN THOUGH the User is listed as Logged In.

I will test further on the other jobs and post results.

Thanks!