I would imagine now you would start managing large database file backups vs IFS backups.
Now what does your nightly DB backup window look like ?
It's interesting that one of the strengths and great weaknesses of tools like MS Sharepoint is that they store all documents in the database.
Larger DB backup, less file backup or larger file backup less DB backup. I suppose either has merits.
In the case of Sharepoint there are 3rd party apps that allow the files to be stripped from the DBs back to the file system.
Personally rather than starting to dump blobs into the database, I would look at alternate object management methods on the IFS. We had one customer who was creating a new profile each month to mirror the year/month that docs were stored.
Or an better answer is probably to move the file objects to a SAN or NAS storage device.
Interestingly there's already a project on the docket at the customer Joel was talking about to move the docs to SAN. They just haven't done it yet.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 5
date: Fri, 17 May 2013 22:41:07 -0400
from: Bdietz400 <bdietz400@xxxxxxxxx>
subject: Re: massive document storage in the IFS - how to handle Mimix
Joe, have you seen any differences in the amount of storage each record takes?
I can understand the benefits you see with access, and such. Any differences with saves, other than SAVSECDTA?
--
Bryan
midrange.com
