none
Files in document library reverted to old version - with no versioning in library?? RRS feed

  • Question

  • I'm trying to get to the bottom of a very weird problem where a user claims to have been editing a file in a document library for a month or so, but now it's back to an old version. No versioning was turned on in the library, so my best guess was that actually they've been working on a copy of the file that lives somewhere else. For other reasons, their computer was recently rebuilt so any local copy will now be gone. But the user's manager also claims to have seen the file with data in it, accessed from Sharepoint on his own computer.

    None of this adds up, but if it's been edited from multiple places that means it's not just a stray local copy after all, and brings up the possibility that Sharepoint has actually lost the files. But even if it had, I'm not convinced that it would just go back to an old version (the same version at the time the file was uploaded in the first place). With no versioning in the library, it would have just disappeared.

    The user was not using Sharepoint Workspace.

    We've been struggling with getting stuff from backup but we did manage to get one from a couple of weeks ago which had the old versions; if SP had reverted it had already happened by then.

    I'm just not sure what to think. I'd love to know that it was not the system losing this data, because I'm the one trying to get more people to use Sharepoint. But the story 'I used Sharepoint to share my files, and I lost a month's work' is not going to help that :-( .  I'm relying on anecdotal evidence from my users 'I'm sure I saw it...' so this could be a wild goose chase anyway. But if anything is going on, I'd like to work out what to do about it.

    Thanks for any insight. I can't find any evidence that anyone else has seen this happen, which makes me think it probably didn't.

    Wednesday, May 29, 2013 12:56 PM

Answers

  • These situations are always tough.  I would agree, SharePoint is not going to just revert to a previous version of a document.  Without versioning turned on, this is highly unlikely if not impossible.  I'm thinking its more likely that someone uploaded an old copy and overwrote the previous one, or something.

    Do you have auditing turned on?  If not, I would turn this on.  Then at the very least you will get an audit trail of what is happening in the library and the document.  Also, it may benefit you to turn on versioning as well.  Versioning has its storage impacts, but it should provide some peace of mind that SP is keeping various versions and you can bring one of those back in the event users report this again.

    Good luck!


    Brandon Atkinson
    Blog: http://brandonatkinson.blogspot.com

    Wednesday, May 29, 2013 1:04 PM

All replies

  • These situations are always tough.  I would agree, SharePoint is not going to just revert to a previous version of a document.  Without versioning turned on, this is highly unlikely if not impossible.  I'm thinking its more likely that someone uploaded an old copy and overwrote the previous one, or something.

    Do you have auditing turned on?  If not, I would turn this on.  Then at the very least you will get an audit trail of what is happening in the library and the document.  Also, it may benefit you to turn on versioning as well.  Versioning has its storage impacts, but it should provide some peace of mind that SP is keeping various versions and you can bring one of those back in the event users report this again.

    Good luck!


    Brandon Atkinson
    Blog: http://brandonatkinson.blogspot.com

    Wednesday, May 29, 2013 1:04 PM
  • I have experienced this issue and witnessed this issue with the most version of SharePoint. A co-worker and I were working in the same document, one that I had just saved moments before they opened the file and the file they were displaying was from a version that was from a previous day and not the one I just had saved. I do not know what is causing the issue. Had I not noticed and she backed out of the document without saving, it would have overwritten that file and everything that had been put into the document would have been lost. Unfortunately that did happen later, so we have to fix our 40 plus page document. It could be tied to the local cached files causing an issue with the version being opened, but do not know.

     I very much believe the user could of had that issue. Again had I not seen this happen with my own eyes, I too would not believe it, but I have seen SharePoint do some things that are not easy to explain.

    Friday, February 14, 2020 3:01 PM