Documents / Spreadsheets rolling back to blank

[kb.stellent]

Hello,

We have community server and document server installed.
There were a number of times when a few of the spreadsheets and documents we've been editing for quite some time just suddenly goes back to a blank page.

Sample scenario:
1.Create spreadsheet.
2. Share to other users.
3. Users use and edit on this sheet.
4. After ~8 days of use, the first thing we see in the morning is a blank version of that spreadsheet with NO revision history.

It happened:
a. Randomly on spreadsheets and documents.
b. ~5 shared documents, ~3 in common documents, ~1 personal document (not shared)
c. Number of days being used before going blank is random as well.
d. Daily back-up is inconvenient as we have more than 30 documents being used regularly,

[Maxim]

Hello kb.stellent!
Please give us more info!
Specify what OS you're using on server?
What OnlyOffice installation you've installed (Docker or not)?

[kb.stellent]

Server:
Windows Server 2012 R2 Datacenter 64-bit (6.3, Build 9600)

OnlyOffice Version 8.7.0 installed manually.

[Maxim]

Hello kb.stellent!
One more important question - while editing the file every user closed the tab in the browser? The edited file can be saved at the moment when the last session is closed.

[kb.stellent]

Hello Maxim,

No, not every user closed the tab while editing. Our users are constantly editing documents/spreadsheets.

Do you mean to say that for every user to save a document, no other user has to be viewing/editing it?
I'm not sure if that's what you mean because it contradicts collaborated editing which is supported by the following tooltip:


Which saving while other have it opened on there browsers, works for us most everytime.

[Maxim]

Hello kb.stellent!

Do you mean to say that for every user to save a document, no other user has to be viewing/editing it?

No, i mean that the file, while editing, keeps in cache of Document Server and "collecting" all changes into the file which is ready be saved in storage (in Community Server for example). The signal for Document Server when the file is ready to be saved is closing last browser's tab, Document Server "understands" that file is not opened anywhere and "collects" it into the file from cache and put the ready-to-use file into the storage.
Now we are trying to reproduce your issue.

[mus]

I wish there was a feature to "flush" the document server cache - for example by explicitly saving the file on any of the concurrent browsers - because what if a user keeps the tab open on their laptop, then goes on holiday? I suddenly don't have a current version! We are using the fast edit mode, and a user getting lost in browser tabs is of course a frequent issue.