SharePoint 2010 recover document
If someone overrights a document, is there an easy way to recover the old document or is just going thru the sql database the easiest way?
jessc7
Have you checked the User and Site Collection Recycle Bins? Or has the document been deleted there as well?
ASKER
i didnt see it there. i think he overwrote the document.
I can pull from backup but it does take longer.
I can pull from backup but it does take longer.
Another potential easy answer - was versioning turned on?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes unfortunately versioning is off
ASKER
would versioning help with this situation in the future?
Yes, when overwriting a file in a library with versioning turned on, SharePoint will just create another version. In this scenario, you would have been able to recover a previous version as the newest version, and been fine.
ASKER
ok, thanks; as for common practices, is enabling this for all sites common / best practice? It would have definitely saved me a lot of time in this case
I don't believe it is enabled by default, as it can increase storage space in SQL dramatically on a large deployment. However, if you understand that each version of a document takes up storage space, you can plan adequately. If you enable versioning, it makes sense to limit the number of versions allowed within the corresponding library. I have used 3 - 5 versions as a rule of thumb, unless requirements dictate otherwise.
In the past I have created versioning where it was needed to have a historical view, or that I had experienced a similar scenario as you, where certain high priority content had been overwritten. If it was low priority content, it would be given a low SLA of recovery (DB recovery or other methods if possible), or maybe not an SLA at all (no recovery, only recreate).
In the past I have created versioning where it was needed to have a historical view, or that I had experienced a similar scenario as you, where certain high priority content had been overwritten. If it was low priority content, it would be given a low SLA of recovery (DB recovery or other methods if possible), or maybe not an SLA at all (no recovery, only recreate).