HELP – can't make archival backup copy of Affinity files!

[Rumpelstilzchen]

Dear Affinity software engineers,

 

If I open a Affinity file and make a new file via "save as", no archive bit is placed for the file document in window’s file manager "explorer".

 

To tag this archive bit is crucial for making daily archival backup copies of my changed or newly created files.

 

Therefore, all "save as" Affinity files are missing in my archival backup. If some damages happens, all these files are lost forever.

 

Hence, I beg you to fix this problem as soon as possible, please.

 

My OP: Windows 11

My Affinity version: 2.2.0

 

Kind regards

[GarryP]

On Windows 10, I’ve just done a quick test in V2 and neither the original “Save” file nor the “Save As” file have the archival flag set, whereas they both do in V1.
I hope it’s just my quick/bad testing that is at fault here as this is quite worrying otherwise.

[anto]

2 hours ago, GarryP said:

the archival flag set, whereas they both do in V1.

what do you mean, what "archival flag"?

[walt.farrell]

47 minutes ago, anto said:

what do you mean, what "archival flag"?

 

It's used by some backup applications to indicate that the file is new or changed, and should be backed-up.

[walt.farrell]

3 hours ago, GarryP said:

On Windows 10, I’ve just done a quick test in V2 and neither the original “Save” file nor the “Save As” file have the archival flag set,

I see that, too, for Save/Save-As. Exporting seems to set it properly, though.

Possibly a bug that crept in with the new file-locking implementation?

[AlainP]

I don't see this problem here on my Win 11 system. Maybe I'm not looking at the right place...

[walt.farrell]

22 minutes ago, AlainP said:

I don't see this problem here on my Win 11 system. Maybe I'm not looking at the right place...

Have you:

1. Saved a native Affinity file, and then
2. In File Explorer, selected the file, right-clicked and chosen Properties, then clicked on Advanced?

[AlainP]

Exactly what I did. Here's a file I worked on this morning in Affinity Photo.

 

[walt.farrell]

16 minutes ago, AlainP said:

Exactly what I did. Here's a file I worked on this morning in Affinity Photo.

And you've updated Photo to 2.2.0? 

If so, did you install via the MSIX- or EXE-based installer?

[AlainP]

2.2.0 Release versions, MSIX installers.

[walt.farrell]

27 minutes ago, AlainP said:

2.2.0 Release versions, MSIX installers.

Interesting. I've tried it with 2.2.0, and both the MSIX and EXE installers. I wonder what's different between your system and mine (or Garry's or Rumpelstilzchen's).

[AlainP]

It's getting weirder.... now all files I create in any Affinity app don't have that flag turned on anymore.... and I just do what I did this morning.... 

More research.... I think I found out why it was working this morning and not now. This morning I saved the files and reopened them minutes later to do some more work on them. 

What I found out is that when I save the file the first time the archival bit is not set. And when you reopen it and save it again it's then set correctly.

[walt.farrell]

I installed 2.1.1, and the Archive bit is properly set by that release. So it looks like it's a new problem in 2.2.0 on Windows.

[Andreas CH]

Ich verwende Windows 11 und Affinity Suite in der Version 2.2.0.
Bei mir wird das Archiv-Bit gesetzt.

Auch mit der Beta 2.2.1 wird das Bit gesetzt.

I use Windows 11 and Affinity Suite in version 2.2.0.
For me, the archive bit is set.

The bit is also set with Beta 2.2.1.

[carl123]

Archive bit also not setting here in 2.2 beta or 2.2.1 beta on Windows 11. Exe versions.

Also tested one of my overnight backup routines and files are not backed up

2.1 release works correctly. (Fortunately, I had not got around to updating that version as yet and still use it for important stuff)

This is one of those problems that companies may not notice for a while but when they do... someone in the IT department is getting fired

 

 

 

[GarryP]

Here’s a bit more detail from my end.

Windows 10 Home – 22H2 – 19045.3516 – Updated a few days ago and no updates listed as pending.
Designer 2.2.0.2005 – installed via MSIX from Serif Store.

(In the below workflow: Des = Designer; Exp: Windows Explorer.)

Des: Launch application.
Des: Create new HD-sized landscape document.
Des: Add rectangle shape.
Des: Save document to my user root folder (testing archive flag.afdesign).
Exp: Check Archive Flag for file – It’s not set.
Des: Close document.
Exp: Check Archive Flag for file – It’s not set.
Des: Open recent – open the same document.
Des: Add ellipse shape.
Des: Save document.
Exp: Check Archive Flag for file – It’s not set.
Des: Close document.
Exp: Check Archive Flag for file – It’s not set.
Des: Open recent – open the same document.
Des: Save As – with new filename to my user root folder (testing archive flag2.afdesign).
Exp: Check Archive Flag for both files – It’s not set.
Des: Close document.
Exp: Check Archive Flag for both files – It’s not set.
Des: Close application.
Exp: Check Archive Flag for both files – It’s not set.

Basically, at no point is the Archive Flag set. (I’ve not checked this with Publisher or Photo.)

(Virus/Security is via Windows Defender and backups are ‘processed’* via the standard “Backup using File History” functionality provided by Windows.)

* Even though this is set to be done automatically every day I have to force this to happen every week or two just to make sure that it gets done, for some reason that escapes me. I don’t know if this is relevant but thought I’d mention it anyway.

[Sean P]

Hi Rumpelstilzchen,

Thanks for letting us know - I can confirm that I have reproduced this issue and it has now been passed along to development.

[Affinity Info Bot]

The issue "Windows "File is ready for archiving" flag is not getting set File > Save or Save As" (REF: AF-637) has been fixed by the developers in internal build "2.2.1.2063".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

[Rumpelstilzchen]

Wow, thank you so much for your great help! When I first discovered the missing archive bits, I was shocked to know, I worked without any "safety net".