Fab's AutoBackup 6 Pro - a must have tool for techs

Hello,
I have just released a new version. I am trying to kill a bug that seems to happen when writing Outlook PST/OST files settings in the registry. I have made some changes in this piece of code and while doing tests, I found out that Exchange ActiveSync accounts were not fully supported: some registry values (paths) were not updated when restoring a backup or transferring files from an user profile to another. By the way, I have never been able to reproduce the issue myself. I hope, the changes I made have already solved this problem.
 
Hello and happy new year,
I have released a new version that brings some new features and fixes.

Here is the full change log:

Added:
- Ability to send the job log via email when using the user interface. Previously, this was possible only in command line mode. Select the option from the actions after job drop down menu.
- Included user's manual in the updater tool. On next update, user's manual will be downloadable with it.
- Now, when using Nirsoft tools stored within Fab's AutoBackup folder, the variable %AutoBackupRoot% (meaning Fab's AutoBackup's root folder) is used instead of %AutoBackupDrive% (meaning Fab's AutoBackup drive letter). This way, the program is always able to find them even if the path has changed.


Fixed:
- Changed the default timeout delay while copying a file from 10 seconds to 30 seconds. Also, the transferred size is monitored instead of the progress bar position. This avoids time out events on large files (several Giga Bytes) while they are in fact being copied.
- Some texts remained in white event when text branding was set up in the "[BRANDING]" section of "autobackup.ini" configuration file. This caused invisible labels in the job log window when the background color was set to white.
- The name of the file being copied comes back to the user interface even if it is small sized. This was designed to save processor resources while copying small files. Beside this, the program looked frozen while processing such files. This has finally low impact on global performance so, user experience has been preferred here.
- In the latest Windows 10, in "My documents", there are hidden symbolic links (like shortcuts but look and feel like real folders in Windows) to "My Pictures", "My Music" and "My Videos". Because of this, when using Fab's AutoBackup 6 Pro within a Windows PE like, these folders could get copied twice. For example, "My Pictures" is backed up using the usual "My pictures" item and another time with My documents item because of the "My Pictures" symbolic link in it. Now, Fab's AutoBackup 6 is designed to ignore anything that is under a path like "X:UsersProfileNameDocumentsMy music". There was the same issue for public documents and the symbolic links inside this folder.
 
Hi,
The old Restore/Transfer Outlook issue came back with the Fab's AutoBackup 6 release two days ago. This time, I have been able to reproduce the issue. It happened when restoring / transferring Outlook OST files configured with an IMAP account and there was no Microsoft Office installed on the target computer. So, I have just released Fab's AutoBackup 6 Pro 6.7.6213.53894 that fixes the problem.

Just use your updater or go to your shop account at https://store.fpnet.fr to get the update.

Cheers

Edit: If you got the 6.7.6213.44569 then throw it to the trash bin because Outlook Backup is broken in it. Get 6.7.6213.53894 instead
 
Last edited:
A Question. We have been doing more and more backups & restores to and from network shares in the shop. It mostly seems to work ok, and puts the data on our backup share where we keep it for 30 days in one go, as opposed to copying from an external drive.

Is this practice going to get me in trouble at some point? I seem to remember it not being the recommended procedure...
 
A Question. We have been doing more and more backups & restores to and from network shares in the shop. It mostly seems to work ok, and puts the data on our backup share where we keep it for 30 days in one go, as opposed to copying from an external drive.

Is this practice going to get me in trouble at some point? I seem to remember it not being the recommended procedure...
Hi,
There is no problem doing this. Just backup to a full network path (UNC) instead of a network mapped drive and it is fine.
 
Hello,
I have released a new version with a lot of fixes.

Software : Fab's AutoBackup 6 Pro
Version : 6.8.0.30498
Date : 02/07/2017
Added :
- All the Fab's AutoBackup executables are now digitally signed. Hopefully, this will avoid false positives from anti-malware programs.
- The duplicate files are now put at the end of the copy file list when the program is set to ask what to do with them (the default setting). This way, all the files are almost copied when the prompt message asking how to handle duplicates pops up.

Changed/Fixed :
- Blocking error message related to Unicode characters on some computers. This has been fixed by reverting to an older development software version.
- Display glitches on some disabled items.
- Error messages and unable to restore when there are a huge amount of data of additional folders in the backup.
- Windows Live 2009 Contacts were backed up / transferred instead of the good ones when it had been upgraded to Windows Live 2011/2012.
- The command line builder tool allowed saving a backup/restore script if the backup location was not specified.
- The backup/restore process started anyway even if the backup location was not specified in command line mode.
- The program tried to export the saved network credentials even if processing another user profile (Nirsoft NetPassView cannot work in this case).
- Installed printers list could not be exported from a pulled drive.

I hope that the "No mapping for the Unicode character exists in the target multi-byte code page" error message did not show up too many times as the program was just unusable in this case. This happens on some machines (not mine, that would be too easy to fix!). Obviously, this is a known and unfixed Delphi bug since some years (I would say 4 or 5!). I had to revert my Delphi development software to an older version that has not this problem. I guess Fab's AutoBackup 7 will be written in another language I will have to learn at the same time since I am fed up with editors that leave bugs in their software.

As usual, you can use the updater tool to download this release or get it from your store's account.
 
Hello,
I have released an emergency fix for Fab's AutoBackup 6 / 6 Pro.

Software : Fab's AutoBackup 6 Pro
Version : 6.8.0.30513
Fixed :
- All the registry exports were in a wrong character encoding (UTF8 instead of Unicode). This resulted in impossible registry imports when restoring. Files were here but not settings. For example, Outlook files are well restored but the profile was not. Please update to this version and destroy any V6.8.0.30498 you have in production environment.

This happened while trying to figure out what was wrong with Unicode mapping character error message in previous versions.

As usual, you can use the updater tool to download this release or get it from your store's account.
 
FYI, just tried to update mine from within the program and it failed the credentials check. Logged into my account and the credentials are correct, so I downloaded it from the Download link, which worked fine. Thanks for your constant maintenance of a terrific program, Fab.
 
FYI, just tried to update mine from within the program and it failed the credentials check. Logged into my account and the credentials are correct, so I downloaded it from the Download link, which worked fine. Thanks for your constant maintenance of a terrific program, Fab.
This may come from a database serveur address change on the last friday. This may be some cache problem.
I do not have any problem with the updater so, I guess this issue will disappear with a little time.
 
All the registry exports were in a wrong character encoding (UTF8 instead of Unicode). This resulted in impossible registry imports when restoring.

Are there likely to be many impacts from this on folks not using Outlook? I used the problem version last week for what was pretty much a "Favorites and Shortcuts" move, but I didn't test it hard after the restore. The source system is still available/repurposed without cleaning so I can re-do the migration if important.
 
Are there likely to be many impacts from this on folks not using Outlook? I used the problem version last week for what was pretty much a "Favorites and Shortcuts" move, but I didn't test it hard after the restore. The source system is still available/repurposed without cleaning so I can re-do the migration if important.
Here are the affected items:
- Internet Explorer settings (proxy, security zones)
- Windows mail accounts
- Windows live mail accounts
- Outlook Express identities and accounts
- IncrediMail identities and accounts
- Network drives connections
- IntelliType settings
- IntelliPoint settings
- Outlook profiles
- Outlook auto complete cache

As you can see, this was a major issue so it definitely needed an emergency release.
About existing backups, If the source systems are not available anymore, backups can be converted: all the .reg files in the backup have to be edited in Windows Note Pad and In the "save as" dialog, select Unicode encoding instead of UTF8 and overwrite the existing files.
 
Back
Top