Bump Bump Bump .... Anyone?????

[jsmwalker]

Not a problem, run the service as the administrator, however if the issue is because the administrator does not have permission on the NAS box, then i'd recommend either creating an exact duplicate on the NAS box (Same username/password) or create the exact user on the Windows box and grant it login as service rights and then run the LMB Service as this.

Which way is better for you depends on your network setup and security requirements.

J

[mherde]

BUMP! I am using the latest version of logmein backup 3.0.783 and am running into this exact problem. when a scheduled backup tries to run on a mapped drive it says "unable to access source drive" I have all the correct credentials in place. the only way to get the backup to run is to do it manually. If someone can please find a fix for this it would be awesome. so far none of the previous suggestions have worked.

[tntmiskit]

Yes, this is a major pain and has occurred long enough I would have thought LMI could have created a fix by now for a paid product but I may have found a work around using suggestions listed in this topic.

I’ve only tested this for one day, though.  So my disclaimer is, this isn’t proven yet.

To keep this simple, I’ll discuss the local Administrator account.

This is also with both server console sessions logged in.

Let’s say you have two servers.

Both Windows servers default with a local Administrator account.

Make sure the local Administrator account password is the same for both servers.

Set the following services to run as the local Administrator (.\Administrator) and set the password.

“LogMeIn Backup Maintenance Service”

“LogMeIn Backup Storage PC Service”

“LogMeIn Backup VSS Service”

“LogMeIn Maintenance Service”

Restart the above services.

Using the LogMeIn backup console, configure the backup set to the time you want it to backup.

Figure out what Windows Schedule Task was created by this set and open the properties of this backup set (will be labeled “LogMeIn Backup#”).  C:\Windows\Tasks\

Set the “Run As:” user to the local hostname\Administrator

(Where “hostname” is the name of your server.)

Set the password for the local Administrator user.

Apply the changes to the Windows scheduled task.

Close the LMI backup console and wait for the scheduled task to run.

If you edit the backup set using the LogMeIn Backup console, it will default the Windows scheduled task for that backup set and you will need to reconfigure the hostname\username and password again.

This worked for my servers.
The backup set testing process also ran and completed.

If you restore the data to a directory on your remote server, you’ll see your data did get backed up.

I tested this by simply creating a new text file on the primary server which did appear on my remote backup server after the restore.

As a further step (I didn’t do this) you could also map the network drive using the local administrator via the “connect using a different username” option.

[DrummerJoe]

I am surprised LogMeIn hasn't weighed in on this as it is still a problem over 1 year later.

I was able to solve it by doing something similar to tntmiskit although not all of the changes were necessary. Just changing the credentials for the scheduled task in Control Panel to the administrator username and password for our domain solved the problem.

[Birol2010]

I had have problem about mapped drivers backup scheduledly. I tried a lot of way to solve this. At the end I found a solution. I setted my backup set from logmein backup then go to the task scheduler in windows.

I founded logmein backup scheduler in there and double click it to open it's setting dialog box. in the dialog box you will see security option section. in there you should see run this as SYSTEM account. You should change this to administrator account. after then it works. But dont forget to change this account to adminsitorator after when you make modificaition in backup set from logmein backup.

[isosceles]

Thank You for posting your result. It helped me "workaround" an issue I was having where logmein would not run on a new 2008r2 Remote Desktop Server (Terminal Server). I was able to use a win7pro box to connect to some mapped drives and backup the data.

Thank You.

[4320]

thx for this workaround.  Seems to work on an old XP box used as a backup source for NAS networked drives.  Surprised that this has not been fixed or made it into the KB.