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?
Jack_son_Asked:
Who is Participating?
 
jessc7Commented:
I know this is for 2007, but it appears that it might not be possible without resorting to the DB backup:

http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/78175a66-9598-4c28-9b0e-938ab376da97/

Maybe someone else has an idea.
0
 
jessc7Commented:
Have you checked the User and Site Collection Recycle Bins? Or has the document been deleted there as well?
0
 
Jack_son_Author Commented:
i didnt see it there. i think he overwrote the document.

I can pull from backup but it does take longer.
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

 
jessc7Commented:
Another potential easy answer - was versioning turned on?
0
 
Jack_son_Author Commented:
yes unfortunately versioning is off
0
 
Jack_son_Author Commented:
would versioning help with this situation in the future?
0
 
jessc7Commented:
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.
0
 
Jack_son_Author Commented:
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
0
 
jessc7Commented:
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).
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.