User modified (shortened) a field which affected most of their documents. Would it be possible to restore only the database files and use the current volumes. It would save time if they don't have to restore 800 GB of images.
Question
Question
Answer
Document metadata is stored only in the SQL database, so restoring volumes is not necessary to recover this information. What you do have to consider is that if you restore your database to that point in time without restoring the volumes, there's potential for inconsistencies. For instance, if a document was deleted your SQL restore will undo the delete from the index but the pages won't exist on the volume, or if a document was moved between volumes the database will point to the old location (where it no longer resides). Of course, if there were no changes on a particular volume since the field shortening you don't need to restore that volume.
Replies
Considering the metadata information and titles are in the database, it seems like a reasonable idea.
I do not now how well this will work however, since the backup and the current volumes may not line up (say, the database doesn't know about 200 files). That is one of the risks you may run into.
Anyone else have a comment on this?
To follow up on this. Is there a way to pick template information to restore? Say, restore a template's settings, and the metadata associated with it, without having to restore the entire database?
There's no one step operation for this, but you could theoretically copy specific items into SQL on the backend. I would be VERY careful about this though, and needless to say it's not a supported procedure.
Is there somewhere in the documentation that explains what SQL tables relate to templates, the metadata inside of them, etc?
There were no volume changes. The customer made a field change, then realized it affected all previous documents. Restoring the database alone resolved it.