Backup forum

jsblume · 2020-06-29 16:57:24

I'm having an odd problem with IDrive backing up MS Access 2016 databases. For any database file with a date modified after about 6/1/2020, IDrive attempts to back it up twice. It succeeds the first time and fails the second time.

Here are two lines from the 6/28/2020 backup log:

[SUCCESS] [06/28/2020 22:01:09] [[Full Backup][D:\Databases\MSAccess\AstuteData.accdb][Size: 3.25 MB]]
[ERROR] [06/28/2020 22:01:13] [[D01582158279000692765\D\Databases\MSAccess\AstuteData.accdb][Reason : update retained]]

I have been going round and round with IDrive support for almost two weeks now, with little headway. They've uploaded my log files, and they continue suggesting to me that I make sure MS Access is closed during the back up. It always is - I always make sure everything is closed before the scheduled back up happens.

Any suggestions would be greatly appreciated!

Thank you,

SteveA · 2020-06-29 22:08:33

Could there be anything else attached to the database? Excel for example, maybe from another computer?

jsblume · 2020-06-29 22:14:35

A good question, SteveA. Nothing else attaches to these database. They are 100% stand-alone specifically for documentation and/or local testing of ideas for clients.

A further interesting thing is that IDrive on my Win7 laptop will back up modified MS Access 2010 databases. It's my Win10 laptop with MS Access 2016, and the first occurrence of an error was 6/8/2020. Prior to that date, it was backing up fine.

SteveA · 2020-06-30 00:48:31

jsblume wrote:
first occurrence of an error was 6/8/2020. Prior to that date, it was backing up fine.

Does that happen to coincide with an update of the IDrive client software?

jsblume · 2020-07-02 18:51:12

I don't recall when IDrive last updated.

SteveA · 2020-07-02 20:45:22

I came across some anecdotal evidence around the Internet that there may be an issue with MS Access (not necessarily 2016) and Windows 10.

People have noticed that when they close MS Access, the process remains active in the Task Manager, requiring a forced close (End Task).

Could this be happening in your case? Have a look at the processes in Task Manager and see if MSACCESS.EXE is still running after you close the application.

jsblume · 2020-07-02 20:47:56

Thanks for that info! I hadn't heard that, but was beginning to suspect it. I'll test that tonight and get back to you.

jsblume · 2020-07-04 20:45:16

I did a reboot of my Win10 laptop before the next scheduled back up and didn't do anything with the laptop until after. I still had the same errors. I noticed that Office 2016 has a "Click-to-Run" service which is running on my Win10 laptop but not my Win7 laptop. I've stopped the service to see what will happen with tonight's backup.

SteveA · 2020-07-04 21:51:23

jsblume wrote:
I noticed that Office 2016 has a "Click-to-Run" service which is running on my Win10 laptop but not my Win7 laptop. I've stopped the service to see what will happen with tonight's backup.

That could be the culprit - it probably pre-loads recently used Office Applications to make it appear faster when you start them.

SteveA · 2020-07-04 21:54:13

On second thoughts, read this:

https://techtips.easyclou....nstall-it/

Click-to-Run provides update to the Office suite and is an important component of Microsoft Office it’s NOT advisable to uninstall it

jsblume · 2020-07-05 16:02:40

Thanks for that link! The service had restarted itself at some point and the backup failed again on those files. We'll see what happens tonight!

SteveA · 2020-07-22 21:53:34

Did you get any further with this issue?

jsblume · 2020-07-22 22:04:38

Thanks for checking up! I did disable the Microsoft Office Click-to-Run service, but it did not make a difference. IDrive has been unable to suggest anything new. I'm formulating a post for the Microsoft forum to see if they have any ideas.

I'm open to suggestions for a backup service other than IDrive. I like the program, but the support leaves a lot to be desired. I'm contemplating committing to OneDrive, but not sure yet if I want to do that.

SteveA · 2020-07-24 00:11:19

Have you tested that OneDrive can successfully back up the Access files?

I'm not familiar with any other online backup services - before IDrive I backed up to tape streamers

If you are prepared to persevere with IDrive, you could try setting up a scheduled task that ZIPs up your databases into an archive that is then picked up by IDrive during its backup.

Having a two stage backup regime might seem a bit clunky, but its normal practice with SQL Server databases, which can't be reliably backed up as flat files. You'd also have an advantage of an online copy of your files for quicker restores.

Backup forum

Announcement

#1 2020-06-29 16:57:24

IDrive and MS Access

#2 2020-06-29 22:08:33

Re: IDrive and MS Access

#3 2020-06-29 22:14:35

Re: IDrive and MS Access

#4 2020-06-30 00:48:31

Re: IDrive and MS Access

jsblume wrote:

#5 2020-07-02 18:51:12

Re: IDrive and MS Access

#6 2020-07-02 20:45:22

Re: IDrive and MS Access

#7 2020-07-02 20:47:56

Re: IDrive and MS Access

#8 2020-07-04 20:45:16

Re: IDrive and MS Access

#9 2020-07-04 21:51:23

Re: IDrive and MS Access

jsblume wrote:

#10 2020-07-04 21:54:13

Re: IDrive and MS Access

#11 2020-07-05 16:02:40

Re: IDrive and MS Access

#12 2020-07-22 21:53:34

Re: IDrive and MS Access

#13 2020-07-22 22:04:38

Re: IDrive and MS Access

#14 2020-07-24 00:11:19

Re: IDrive and MS Access

Board footer