We had a server A which hosted all our databases. This was coming to end of life so we built a new LN server M and copied the data to it. We also a built a backup server N which was acting as a replicant. Server A was decomissioned and switched off.A year down the line, someone had the wisdom to switch on server A to find out what it was. It was left switched on for several days until I found out; I finally switched it off and physically removed it.
But some weeks later some databases were showing records that had been previously deleted; they were mysteriously resurrected.
I am not sure whether it is server A that had replicated with M (on being switched on after a year) or if server N is not replicating correctly with M.
Subject: Data coming back
My guess is that it’s Server A that replicated documents back into the live databases.
You should be able to see that by looking at the document properties, at the created/modified dates on the first tab.
The original created/modifed date shows when the document is first created, lines 3 and 4 show when the document were added or modified ‘in this file’, and modified by whom. You’ll probably see ServerA listed there.
Subject: RE: Data coming back
Indeed. The root of the “problem” is that the corresponding deletion stubs would have been purged months ago, so rather than having “A” see the documents in question as things to delete (which it would if “M” still had the deletion stubs), “M” sees them as documents it doesn’t have yet.