Hello Tobias,
Storage on the filesystem has the advantage to use existing clustering raiding and hierachial storeage systems for storage and you dont have to implement those features in the database. The advantage would be documents can be found indepentendlly from the ERP-Sysem.
DB Advantages
All data (documents, folders, and metadata) is stored in the database.
Database is much better suited than file system to the administration of large amounts of data
Databese is limited to size 64 TB, then additional database needs to be installed
If there is a large number of write requests in your CM usage scenario, set up the CM repository in database mode. Since all documents are stored in the database, this avoids unintentional external manipulation of the data.
Another advantage of storing all data in the database is that the procedure for data backup and restore is easy since only the database needs to be backed up
File System Advantages
This is faster than the database option if you have large documents since there is no database data streaming. This also enables the size of the database to be controlled more easily since documents are stored in the file system.
File systems are not transactional, so this has restrictions and affects performance. If read and write operations take place for one document in the file system at the same time, these operations have to be coordinated by the repository manager. This happens by recording both write accesses and read accesses in the database. This affects performance.
Metadata (for example, locks or custom properties) can be lost if you edit or manipulate documents or folders directly in the file system. Only administrators should work in the file system, and they should only carry out mass operations such as copy and delete
For a scenario with write accesses, cannot ensure consistent data backup and restore. This is because changes to the folder structure in the file system could be made in the time between the two actions. This would lead to inconsistent data following the restore process. Consistent data backup and restore can therefore be ensured only if read accesses alone are taking place
There are CM repository managers can be set up in various modes i.e Persistence Mode to save the documents as follows:
1) DB Mode All data is stored in the database
2) DBFS Mode Metadata and folders are stored in the database, but documents are stored in the file system
3) FSDB Mode Folders and documents are stored in the file system, but metadata is stored in the database.
If you wish to change the settings you can do it but with some restrictions which follows as:change of the persistence mode is possible only from the DB mode to the DBFS mode. Changing from DB to FSDB, from FSDB to DB/DBFS, or from DBFS to DB/FSDB is not possible.
To change the mode if you wish with above restrictions
1. Make sure that enough free disk space is available to migrate the content from the database to the file system.
2. Change the configuration of the CM repository manager. In the Root Directory parameter, specify the path to the file system that the documents from the database are to be stored under. Change the entry in the Persistence Mode parameter from DB to DBFS.
3. Restart the application server.
4. Run the CM Store: Content Crawler report
Please check the follwoing notes on backup and restore:
Note 1000150 - Backup of KMC configuration
Note 1000351 - Restore of KMC Configuration Backup Archive.
Knowledge Management entire documentation can be found @
http://help.sap.com/SAPHELP_NW04S/helpdata/EN/62/468698a8e611d5993600508b6b8b11/frameset.htm
Thank you,
Shyam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.