Skip to main content

Can Acronis use a different user credential to do backup?

Thread solved

HI. I'm running Acronis true imagine 2019 Build 18100 (home user). I have it installed on my desktop PC (Win10) and use it to back up two local drives no issues. Recently I got a new (used) laptop (win10). I've shared the C drive on the laptop and have it mounted as a network drive "L:" on my desktop. I'm trying to setup a backup of this network drive. Basically the whole C: drive on the laptop.

I can setup the back up, but when it runs it gets to some system or other protected file (i.e. /program files/winapps, etc..) and stops with an error. Note: some of these protected system files/folders I can't even get to as a local admin on the laptop. If I run the backup manually I can simply "skip all" and the backup will proceed to the end. But I'd like to schedule this overnight. Currently I just get a set of emails about "waiting for user input" if I try.

When I look at the backups for the local drives on the desktop these same folders exist are are backed up no problem. So locally Acronis overrides any permission problems.

I have the same user "jim" and password "1234" on both my desktop and laptop. What I was thinking might work was to create a new user "backup_dude" on the laptop and place him in the backup group. I'm thinking since the backup group is allowed to ignore all security permission on files/folders this might get around it. To do this when I run Acronis I would need to be able to become, or access the network drive as this backup_dude. I see no way to set a login/password in Acronis.  I have no desire to be logged into my desktop as "backup_dude". I'm not sure what non-admin features I may loose.

So does anyone have any thoughts on this?

Thanks

Jim M.

1 Users found this helpful

Jim, sorry but you are making a basic mistake here in trying to backup your whole laptop C: drive from a different computer via a network drive mapping!

First issue:  the laptop C: drive user will never be the same as your other computer user regardless of being given the same user name!  All Windows users are actually unique to the system where they are created, so user jim will never have the required authorities to access hidden / system files on the laptop when coming from the other computer.

Next issue: any backup you create using a network drive mapping will be of Files & Folders only and will never be usable as a means of recovering the laptop to a bootable Windows OS state - this is because a Disks & Partitions backup image is required for that type of recovery, where all hidden / system locked files such as the Windows Registry are captured using Microsoft VSS snapshot methods, plus required boot partition data is included (Windows BCD etc).

The only option that you may be able to use here is to create the Acronis bootable rescue media on the computer where ATI 2019 is installed, then test whether this will work with the laptop and if it does, create an offline backup using that media.  The alternative is to install ATI 2019 on the laptop, assuming you have a license to do so, then create backups directly there.

Steve,

Thanks for the quick response. Yeah, OK you confirmed what I suspected. I was trying to "cheat" by using my desktop to do a full disk backup on my laptop. I figured there might be issues. And there are. Oh well. The laptop is really just a secondary machine for camping/vacations. I'm setting it up to look as much like my desktop as practical. I've setup a sync program for the main folders my wife and I use between the two machines.

I've been using Acronis for a good 10-12 years now. The only reason I still use it is a convenient to keep all my pictures and music backed up vs the old days of coping everything to CD's/DVD's. And when I just replaced both hard disks with SSD's I just did a "bare metal" recovery and was up an running quickly. Now that I think of it I have 2-3 old versions laying around. Maybe I'll install one of those on the laptop since I only need basic backup features.

Thanks again.

Jim M.