Direkt zum Inhalt

Registry Backup with FileBackup

Thread needs solution

Hi to all,

I'm new here, so please be patient :-)

My problem occurs with TI2015 under WIN10 System.

 

What I'm trying to do:

Backup the windows registry by doing a FileBackup for C:\windows\system32\config .

In Options: Exclude Files  all hooks are deleted.

 

What I'm facing:

In the select-file-menu only the subdirectories in config-directory are listed, but not the discrete files.

Executing the backup with only the subdirectories selected the backup errors very soon with this

message:    \\?\C:\Windows\System32   fehlgeschlagen 

 

What I'm wondering about:

a) TrueImage is started as Admin with full access granted.

b) In DiskBackup of the system-disc  as well as  in PartitionBackup of the system-partition the system32\config  directory is enclosed with all files !  Both backups are running without any error.

c) With TI2016 under WIN7  is was no problem to do the requested backup. Never faced any problems.

d) Other programms to backup the registry (Erunt, RegBak) are running fine without problems.

 

Is there any idea what's wrong with me ????

 

Anhang Größe
acronis.png 58.39 KB
acronis2.png 52.2 KB
0 Users found this helpful

Hello Axel,

Have you tried this when you select C:\Windows\System32\ in the left window pane, and then just select the Config folder in the right window pane?

If I open the Config folder in the left pane, then I see very few files shown in the right pane and I cannot select files that are hidden, but selecting Config in the right pane results in all the hidden files being included in my backup.

If you are still getting an error taking this approach, then you may need to check that you don't have a VSS issue as these files are locked by Windows and VSS is needed in order to back them up.

This is what I see in my service_ log file (C:\ProgramData\Acronis\TrueImageHome\Logs) for doing the above backup.

ID Level Module Code Time Stamp Message
1 2 100 0 1458841324 Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2 2 100 2 1458841325 Operation config started manually.
3 2 100 0 1458841325 Operation description: Stage Description.
4 2 100 0 1458841327 Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
5 2 316 0 1458841327 Operation: Backup
6 2 100 11 1458841327 Priority changed to Low.
7 2 11 1008 1458841451 <bold>Create Backup Archive</bold><endl/><tabpoint value=30><indent value=4>From: <indent value=10><textcolor value="navyblue">C:\Windows\System32\config\ </textcolor></indent><indent value=4><endl/>To file: <indent value=10><textcolor value="navyblue">"config_full_b1_s1_v1.tib"</textcolor></indent><indent value=4><endl/>Compression: <indent value=10><textcolor value="navyblue">Normal</textcolor></indent><indent value=4><endl/></indent><endl/>
8 2 100 0 1458841453 Writing full version to file: config_full_b1_s1_v1.tib
9 2 100 0 1458841480 The following backups have been successfully created:<endl/>"H:\Test\config_full_b1_s1_v1.tib"
10 2 316 6 1458841484 Operation has succeeded.
11 2 103 0 1458841495 The e-mail notification has been successfully sent.
12 2 103 0 1458841497 Batch operation has completed successfully.
Anhang Größe
341920-126931.png 14.03 KB

Hi Steve,

thks for your response.

Selecting config folder in left or right window pane makes no difference.

 

VSS may be a promising idea .  At first sight this seems to be confirmed by the complete error message I found in the log:

„Access to file or folder refused. Process can not access the file, cause it is in use by another process“

(Translation from german, original english text surely will be different  :-)   )

But i have no idea, how to deal with that possible VSS problem.

The process ist set to manual start which obviously is the correct setting.  I did start the process manually and retried my backup but this

did not change a thing.

There is only one difference between your backup-log and the one created by my unsuccessful attempts  which may be relevant to my problem:

In your log the line: „Priority changed to low“   is followed by  „Create Backup Archive … “. 

In my log i see the line:  „Partition C : locking“  between  them.

Where is that coming from ?  Could this be the reason for everything ??

 

On the other hand:  no VSS-Issue should be the reason which prevents the display of the contents of config-folder in the selection window of TI !

This really points to an authorization problem. So i granted full access and admin rights to TI, i set UAC to lowest level  and i took the

ownership of complete system 32.  But nothing did help !?    

The problem is solved !

It appears only with 64-Bit system and 32-bit TrueImage.

In windows-64bit there is a folder called sysWOW64. I didn't take the time to learn the details, but this folder is used for 32-bit software with 64-bit exec. The content of sysWOW64 is very similar to the content of system32 but it's not completely  the same. In particular the folder syswow64/config has the same subdirectories as the folder system32/config but none of the dedicated files of system32/config ist present !

In the selection window of TI2015 the entry system32 in fact points to sysWOW64 !

Obviously this is an automatic routing by win-system because the 32-bit software TI2015 is executed under a 64-bit windows . This is a complete explanation for all observations given in the posting above.

Now it would be really nice to know, if there is a way to bypass this routing or is it really impossible to filebackup the registry with TI2015 ?  As far as I know, there is no special 64-Bit version of TrueImage.  So it should be the same with TI2016 and 64-Bit system. Anyone has the configuration to check ?   Should this be called a bug ???

 

Hello Axel, I am able to backup both the System32/Config and SysWOW64/Config folders using ATIH 2016 on my Windows 10 64-bit system with no errors.

Hello Steve,

thks for checking. Your result was surprising !  That's why I checked it with my system too.

And REALLY strange: on my system I face the same result with TI2016 as with TI2015: system32 -> syswow64 with no registry files ??!?!??!

Unfortunately the test-version of TI2016 overwrote my TI2015 instead of a parallel installation. I'm not amused now ! 

Hello Axel, I am sorry that the test version of ATIH 2016 has overwrote your 2015 installation, unfortunately this will always happen as the different versions share the same program directory structure.

I would recommend performing a clean install at this point assuming that you want to go back to using ATIH 2015 and not pay to upgrade to 2016.  For the clean install, remove the 2016 version normally, then run the Acronis Cleanup tool - there is a link to this in my signature below, before reinstalling 2015 again.  Doing this will remove all your backup tasks and history etc but you can recreate these by adding back in the image files - these may be added automatically if ATIH can detect them on the drive when they are stored but this will only happen on the first run of the program.

I am not able to test this further with ATIH 2015 as the only systems where I still have that version installed are running on 32-bit OS (Windows 7 or 10), so won't have the SysWOW64 folders on them.  My 64-bit systems are all on Windows 10 with ATIH 2016 and they work fine for this test.

Axel, you can submit a ticket about trial version of True Image 2016 at www.acronis.com/support/ during 30 days after you starting using the trial. There will be no updates for 2015 version and it hardly could be fixed, however you can get assistance with the latest release.

Regards,

Slava

Thanks for your hint, slava, but I am really fed up with that subject. There are several other ways to backup the registry, so this problem is not important to me. Maybe at a later date I will restart my investigation.

@Steve: unfortunately I didn't follow your advice ! 

I did an Acronis disc-restore instead. Being unconcentrated during that task I did SEVERAL mistakes one after another which resulted in 4 days of really hard work to bring my system up to an actual state again.   That's why that little acronis problem lost much of its significance :-)

 

Hello Axel, sorry to hear of the extra problems with the restore, hope all is working as you want now (and stays that way for you!).

Axel, just wanted to remind you that you can always get technical support for recovery issues both through live chat service and email. If you will need help with recovery issue in the future, do not hesitate to contact us at http://www.acronis.com/support. I recommend you using live chat service as a quicker way of getting assistance.