Advantage of db storage area:
1. One backup backs it up all, at restore no sync between any storage and db is not necessary (and not possible)
2. I have seen performance tests that show slight performance gains with small objects
Disadvantage:
The database usually gets VERY large bringing with it all sorts of operational problems.
I have yet to see a customer that uses the db storage area for the majority of documents... sometimes they store a limited set (e.g. templates,forms) there
Advantage File Storage
1. Wide range of options to choose from
2. Simple to configure/manage
Disadvantage:
Can run out of sync with the database.
At restore time you should really know what you are doing.
Security might be a problem in critical environments as you can access the share with an appropriate user and delete or encrypt it with some ransom
My personal preference for storage (our milage may vary) is object based storage in aligned mode like ICOS, ECS or HCP.
Kind regards,
Gerold
Kind regards,
------------------------------
Gerold Krommer
------------------------------
Original Message:
Sent: Tue February 07, 2023 10:47 PM
From: Dhandy Yusuf Sahyadi
Subject: Migrating Large Document Number between Object Store Using FDM
Thank RUTH Hildebrand-Lund for giving a clear explanation regarding to my case.
Do you have any technical paper/publication regarding pro-cons of using Database Storage Area vs File Storage Area?
And also how to perform backup & recovery procedure using File Storage Area?
Thank you,
Dhandy Yusuf Sahyadi
------------------------------
Dhandy Yusuf Sahyadi
Original Message:
Sent: Tue January 17, 2023 09:25 AM
From: RUTH Hildebrand-Lund
Subject: Migrating Large Document Number between Object Store Using FDM
Dhandy
Assuming you are on a reasonably current version of FileNet, you don't actually need to create a new object store to resolve your issue. Instead, use the sweep capability in ACCE to move the existing content to a different storage area.
The sweep will run in the background, so your object store stays usable throughout the process.
At a high-level, here's the suggested procedure
- Add a new storage area & policy to the object store that uses the storage you want to use going forward.
- Update your document classes to use the new storage policy....that way all new ingest will go to the new storage areas rather than database storage
- Use the bulk move option in the Sweep to move your existing content from database storage to the new storage areas
- Once the move is complete, reorg your database to reclaim space
As with all things, please try this out in a non-production environment first.
More information on performing bulk actions with sweep is available here: Handling bulk processing with sweeps. I'm also attaching a presentation on the capability.
------------------------------
RUTH Hildebrand-Lund
rhildebr@us.ibm.com
Original Message:
Sent: Mon January 16, 2023 12:25 AM
From: Dhandy Yusuf Sahyadi
Subject: Migrating Large Document Number between Object Store Using FDM
Hi,
I'm planning to migrate a large number of documents (approx. 600k in total) from the existing Object Store to newly created Object Store on Ms.SQL Server.
The default Storage Areas set on current/existing Object Store is just using Default Database Storage. So the database size for this OS is growing bigger.
So we need to create a new object store that using both default database storage and filestorage area.
I hope I can achieve that and migrate those documents through FileNet Deployment Manager. Is there any limitation regarding of this case?
Or any insight on other alternatives that can be done to achieve the proper solution.
Thanks,
Dhandy
------------------------------
Dhandy Yusuf Sahyadi
------------------------------