backuprestore cache on C drive keeps increasing in size

[thegary]

Since upgrading to the newest version.

There is a file in user prefs ( think it was backuprestore) keeps getting bigger and bigger.

Ate up a 112 GB of my C drive.  Found it and deleted it. But its starting to grow again.

Gary

 

[walt.farrell]

36 minutes ago, thegary said:

think it was backuprestore

It would help to know its exact name, and the file path leading to it.

[thegary]

9 minutes ago, walt.farrell said:

It would help to know its exact name, and the file path leading to it.

c:\users\name\appdata\roaming\affinity\common\designer\2.0\temp

The File was in here. I deleted it his this morning. Not there now. This is a new .2.30 thing.

Gary

[Dan C]

Thanks for your report @thegary!

Unfortunately however, we're a little unsure which exact file you're referring to - as our team aren't aware of any file called 'backuprestore' that the Affinity app creates.

12 hours ago, thegary said:

c:\users\name\appdata\roaming\affinity\common\designer\2.0\temp

The File was in here.

Equally, I don't believe the path you have provided is a valid Affinity path,  as you have provided both 'common' and 'designer' in the same path. As far as I'm aware, the common and designer folders are always separate.

For example, the following are both valid Affinity paths, but as can be seen the Designer and Common folders are not within one another, as you've mentioned:

C:\Users\[username]\AppData\Roaming\Affinity\Common\2.0

C:\Users\[username]\AppData\Roaming\Affinity\Designer\2.0\temp

____

We suspect you may be referring to the 'PersonaBackstore.dat' file, found in the Designer/2.0/temp folder I've mentioned above. This file is designed to grow with temporary data, and should be automatically cleared periodically by the Affinity app.

During the 2.1 release cycle, we changed the location that certain Affinity files are saved in when using the EXE versions from the %UserProfile% folder to the %AppData% folder. It's possible that during this process, and incorrect link was made on your PC, causing the app to be unable to clear this file.

Our devs have confirmed it's perfectly safe to delete this file from the temp folder, as the Affinity app should then recreate this file, which it should be able to periodically clear as expected.

Therefore as you've already deleted this file, you should find this issue does not return - assuming we've correctly understood the specific file you're referring to here.

I hope this helps!

[thegary]

3 hours ago, Dan C said:

Thanks for your report @thegary!

Unfortunately however, we're a little unsure which exact file you're referring to - as our team aren't aware of any file called 'backuprestore' that the Affinity app creates.

Equally, I don't believe the path you have provided is a valid Affinity path,  as you have provided both 'common' and 'designer' in the same path. As far as I'm aware, the common and designer folders are always separate.

For example, the following are both valid Affinity paths, but as can be seen the Designer and Common folders are not within one another, as you've mentioned:

C:\Users\[username]\AppData\Roaming\Affinity\Common\2.0

C:\Users\[username]\AppData\Roaming\Affinity\Designer\2.0\temp

____

We suspect you may be referring to the 'PersonaBackstore.dat' file, found in the Designer/2.0/temp folder I've mentioned above. This file is designed to grow with temporary data, and should be automatically cleared periodically by the Affinity app.

During the 2.1 release cycle, we changed the location that certain Affinity files are saved in when using the EXE versions from the %UserProfile% folder to the %AppData% folder. It's possible that during this process, and incorrect link was made on your PC, causing the app to be unable to clear this file.

Our devs have confirmed it's perfectly safe to delete this file from the temp folder, as the Affinity app should then recreate this file, which it should be able to periodically clear as expected.

Therefore as you've already deleted this file, you should find this issue does not return - assuming we've correctly understood the specific file you're referring to here.

I hope this helps!

@Dan C

Thanks for you reply. That was the file. Thank you for confirming. Was trying to remember the path. Not quite right. 

Good to know the directory is safe to remove..

 

Thanks again.

Gary