Salta al contenuto principale

Acronis Creating Empty Directory

Thread needs solution

I have 3 backup jobs:

- MOOSE Daily
- MOOSE Full
- MOOSE Network

They create the files in directories with the following names:

- MOOSE_Daily
- MOOSE_Full
- MOOSE_Network

However, Acronis creates another directory occasionally.

- Moose_Differential

For example, it created one on 12/20/2018 7:41 AM.

I deleted it and it created another one on 12/29/2018 12:31 AM.

It doesn't seem to correspond to when one of the 3 backups are running.

I did a search of all files on my C drive for the text string "Moose_Differential" and didn't find any.

I searched the registry for it and didn't find it.

I may have at one time had a backup job that used this, but it would have been deleted...

It's just an empty directory, but it bugs me.

Any ideas on how I can track down what is creating this?

0 Users found this helpful

I would expect that there is still some reference to this empty directory held in the Acronis Database or associated files used by the same.

The official solution here would be to blow away the Database by either renaming or deleting the folder then let ATI start again.  All Acronis Services then Processes need to be ended to be able to do this due to locks held.

Another option that you can try is to look at the files in the C:\ProgramData\Acronis\TrueImageHome\Database folder - leave the actual .DB database file alone, but check the contents of the various .OPT files shown in the folder.  You can open these with a normal Text editor such as Notepad as they are XML files.  Look for any that may reference your problem folder and remove those you find.

Thanks Steve!

I found 2 .opt files with references to the Moose_Differential folder in them.

I also found that Archives.db contained that text.

If I use the official solution and rename the database folder will I have to define my jobs and everything again, or will it just recreate the folder itself?

 

NOTE: I have 242 .opt files.  Is that normal?

If I use the official solution and rename the database folder will I have to define my jobs and everything again, or will it just recreate the folder itself?

If you rename the database folder, it will not affect your backup tasks other than you will lose their history information until you either run the jobs again or perform a validation for the jobs.  The database folder will be recreated but the actual .db will be 'empty' until new information is used to populate it again.