IBM CMOD Cache Filesystems - Revision history

Jderrick: Changed title. /* Too late, I already deleted files from my CMOD cache filesystem. Help! */

2021-10-27T17:36:47Z

Changed title. Too late, I already deleted files from my CMOD cache filesystem. Help!

← Older revision		Revision as of 17:36, 27 October 2021
Line 37:		Line 37:
	The simple answer is that CMOD does the best it can to remove data that no longer meets the retention requirements specified in the Application Group configuration to reduce the amount of data in the cache to the goal - which is 80% full (with 20% free) by default, but it can be modified with the <code> -n</code> and <code> -x</code> parameters to the [[arsmaint]] command.		The simple answer is that CMOD does the best it can to remove data that no longer meets the retention requirements specified in the Application Group configuration to reduce the amount of data in the cache to the goal - which is 80% full (with 20% free) by default, but it can be modified with the <code> -n</code> and <code> -x</code> parameters to the [[arsmaint]] command.

	== ~~Too late,~~ I ~~already~~ deleted files from my CMOD ~~cache~~ filesystem. Help!==		== I deleted files from my CMOD Cache filesystem. Help!==
	If you have a backup of your cache data in your enterprise backup system, you can probably recover the missing data. Contact a company that provides [https://cmod.cloud/professionalservices/ Professional Services for CMOD] for assistance in recovering data. They have tools to help you restore and verify the contents of your cache, or to pull data from secondary storage back into the CMOD cache.		If you have a backup of your cache data in your enterprise backup system, you can probably recover the missing data. Contact a company that provides [https://cmod.cloud/professionalservices/ Professional Services for CMOD] for assistance in recovering data. They have tools to help you restore and verify the contents of your cache, or to pull data from secondary storage back into the CMOD cache.

Jderrick: /* Can I delete files in the cache manually? */

2021-10-27T14:56:11Z

Can I delete files in the cache manually?

← Older revision		Revision as of 14:56, 27 October 2021
Line 32:		Line 32:

	== Can I delete files in the cache manually? ==		== Can I delete files in the cache manually? ==
	NO! The cache is only to be managed with the [[arsmaint]] utility! The structure of the OnDemand Cache Filesystem is complex, and deleting files or directories inside the Content Manager OnDemand cache could lead to documents becoming unavailable to end users, and potentially irrecoverable data loss.		NO! The cache is only to be managed with the [[arsmaint]] utility! The structure of the OnDemand Cache Filesystem is complex, and deleting files or directories inside the Content Manager OnDemand cache could lead to documents becoming unavailable to end users, and potentially irrecoverable data loss. You should be running cache expiration regularly.

			== How does CMOD Cache Expiration work? ==
			The simple answer is that CMOD does the best it can to remove data that no longer meets the retention requirements specified in the Application Group configuration to reduce the amount of data in the cache to the goal - which is 80% full (with 20% free) by default, but it can be modified with the <code> -n</code> and <code> -x</code> parameters to the [[arsmaint]] command.

	== Too late, I already deleted files from my CMOD cache filesystem. Help!==		== Too late, I already deleted files from my CMOD cache filesystem. Help!==

Jderrick: /* How do I add more cache filesystems? */

2021-10-27T14:52:22Z

How do I add more cache filesystems?

← Older revision		Revision as of 14:52, 27 October 2021
Line 41:		Line 41:

	== How do I add more cache filesystems? ==		== How do I add more cache filesystems? ==
	Ask your System Administrator or Storage Management team to add an additional cache filesystem to your server (create /arscache/cache03... cache04, etc.) and simply add that filesystem as an entry in the CMOD cache configuration file, normally ars.cache. If you have more than one Content Manager OnDemand instance configured on your IBM CMOD server, then you’ll need to edit the file specified by SRVR_SM_CONFIG in the instance definition in your [[ars.ini]] configuration file.		Ask your System Administrator or Storage Management team to add an additional cache filesystem to your server (create /arscache/cache03... cache04, etc.) and simply add that filesystem as an entry in the CMOD cache configuration file, normally ars.cache. If you have more than one Content Manager OnDemand instance configured on your IBM CMOD server, then you’ll need to edit the file specified by SRVR_SM_CONFIG in the instance definition in your [[ars.ini]] configuration file. But if you already have multiple OnDemand Caches, then you can simply choose to expand the filesystems you already have.

			== Which cache do I expand? ==
			If you have multiple CMOD Cache Filesystems, and you're running low on space, you can simply add more storage to ONE of your caches, instead of adding space to ''each'' IBM Content Manager OnDemand cache filesystem. OnDemand allocates data to the cache filesystem with the largest number of free 'blocks' when loading data.

	== Can I remove a cache filesystem? ==		== Can I remove a cache filesystem? ==

Jderrick: Many minor updates, refreshed links.

2021-09-29T15:03:50Z

Many minor updates, refreshed links.

Jderrick: /* How do I add more cache filesystems? */

2020-10-27T00:41:52Z

How do I add more cache filesystems?

← Older revision		Revision as of 00:41, 27 October 2020
Line 41:		Line 41:

	== How do I add more cache filesystems? ==		== How do I add more cache filesystems? ==
	~~Simply~~ add an entry to the CMOD ars.cache ~~configuration file~~. If you have more than one Content Manager OnDemand instance configured on your IBM CMOD server, then you’ll need to edit the file specified by SRVR_SM_CONFIG in the instance definition in your [[ars.ini]] configuration file.		Ask your System Administrator or Storage Management team to add an additional cache filesystem to your server (create /arscache/cache03... cache04, etc.) and simply add that filesystem as an entry in the CMOD cache configuration file, normally ars.cache. If you have more than one Content Manager OnDemand instance configured on your IBM CMOD server, then you’ll need to edit the file specified by SRVR_SM_CONFIG in the instance definition in your [[ars.ini]] configuration file.

	== Can I remove a cache filesystem? ==		== Can I remove a cache filesystem? ==

Jderrick: Many small updates and changes.

2020-03-09T23:12:45Z

Many small updates and changes.

Jderrick: Minor changes.

2020-03-09T22:59:37Z

Minor changes.

← Older revision		Revision as of 22:59, 9 March 2020
Line 4:		Line 4:

	==What is the IBM CMOD Cache filesystem?==		==What is the IBM CMOD Cache filesystem?==
	The ~~CMOD~~ cache filesystem, often named “arscache” is a pool of storage on your ~~IBM CMOD~~ server that Content Manager OnDemand uses to store documents for fast loading or retrieval. ~~IBM CMOD~~ Application Groups are configured by default to load data into the cache filesystem, and migrate it to secondary storage at a later time. Migrating the data from the CMOD cache to secondary storage doesn’t delete it - the caches are kept at 80% by default, to help make retrievals for end users faster. One of the easiest ways to tune the OnDemand Cache performance on large Content Manager OnDemand installations is to increase this number to over 95%.		The OnDemand cache filesystem, often named “arscache” is a pool of storage on your server that Content Manager OnDemand uses to store documents for fast loading or retrieval. Application Groups are configured by default to load data into the cache filesystem, and migrate it to secondary storage at a later time. Migrating the data from the CMOD cache to secondary storage doesn’t delete it - the caches are kept at 80% by default, to help make retrievals for end users faster. One of the easiest ways to tune the OnDemand Cache performance on large Content Manager OnDemand installations is to increase this number to over 95%.

	== Where do I configure the behavior of the CMOD cache? ==		== Where do I configure the behavior of the CMOD cache? ==

Jderrick: A few minor fixes.

2019-07-02T17:16:38Z

A few minor fixes.

← Older revision		Revision as of 17:16, 2 July 2019
Line 13:		Line 13:

	==How does the cache get filled?==		==How does the cache get filled?==
	As you load data into IBM Content Manager OnDemand, data is placed into the caches for fast access. The only exception to this rule is if you choose not to load Application Group data to the cache at all - which is generally reserved for situations where documents need to be archived for legal or regulatory reasons, but are rarely, if ever, accessed.		As you load data into IBM Content Manager OnDemand, data is placed into the caches for fast access. The only exception to this rule is if you choose not to load Application Group data to the cache at all, and send them directly to secondary storage - which is generally reserved for situations where documents need to be archived for legal or regulatory reasons, but are rarely, if ever, accessed.

	If you have more than one cache filesytem, IBM CMOD chooses the cache with the most free space, ~~by absolute storage, (not as a percentage)~~ and puts ~~its~~ compressed objects there.		If you have more than one cache filesytem, IBM CMOD chooses the cache with the most free space, and puts the compressed objects generated by the load there.

	==How does the cache get emptied?==		==How does the cache get emptied?==
	You can reduce the amount of data in the cache filesystems with the [[arsmaint]] command. You will want to migrate any data with the <code> arsmaint -m </code> command first, then the <code>arsmaint -c</code> command. ~~Give plenty of time for~~ the ~~migration~~ to ~~complete before starting the deletion of data from the cache~~.		You can reduce the amount of data in the cache filesystems with the [[arsmaint]] command. You will want to migrate any data with the <code>arsmaint -m </code> command first, then run the <code>arsmaint -c</code> command to delete eligible items from the cache. You can combine both options in the same command (<code>arsmaint -mc </code>) to perform both tasks.

	== What is cache expiration? ==		== What is cache expiration? ==
	CMOD Cache expiration is the process by which OnDemand reduces the amount of data inside the caches, in order to make room for new data that is loaded into your Content Manager OnDemand server. It does this by removing data that has already been migrated to secondary storage, starting with the oldest documents first, until the filesystems are approximately 80% full. You can visit the [[arsmaint]] page to find out more about how you can clear data from the IBM CMOD cache filesystem.		CMOD Cache expiration is the process by which OnDemand reduces the amount of data inside the caches, in order to make room for new data that is loaded into your Content Manager OnDemand server. It does this by removing data that has already been migrated to secondary storage or is eligible for expiration, starting with the oldest documents first, until the filesystems are approximately 80% full by default. As mentioned above, on large IBM CMOD servers that have multiple terabytes of cache, adjusting the minimum and maximum parameters makes optimal use of your expensive cache filesystems. You can visit the [[arsmaint]] page to find out more about how you can clear data from the IBM CMOD cache filesystem.

	==What is cache optimization?==		==What is cache optimization?==
	Storage is expensive and finite. In order to make the most out of the storage space you have in your IBM CMOD Cache filesystems, you should try to store more of the data that users are actually accessing, for the period of time that they’re interested in them. You can optimize the cache contents ~~(so that it contains the majority of data people request) and for size,~~ so that you’re using precisely enough disk to perform the required retrievals, and to load new data.		Storage is expensive and finite. In order to make the most out of the storage space you have in your IBM CMOD Cache filesystems, you should try to store more of the data that users are actually accessing, for the period of time that they’re interested in them. You can optimize the cache contents so that you’re using precisely enough disk to perform the required retrievals and to have enough space to load new data. An optimized cache contains only the data people are accessing. Unfortunately, there's no built-in tool for performing the Content Manager OnDemand Cache.

	==How can I optimize the IBM CMOD Cache?==		==How can I optimize the IBM CMOD Cache?==

Jderrick: Clarified cache performance suggestion.

2019-07-02T16:52:34Z

Clarified cache performance suggestion.

← Older revision		Revision as of 16:52, 2 July 2019
Line 4:		Line 4:

	==What is the IBM CMOD Cache filesystem?==		==What is the IBM CMOD Cache filesystem?==
	The CMOD cache filesystem, often named “arscache” is a pool of storage on your IBM CMOD server that Content Manager OnDemand uses to store documents for fast loading or retrieval. IBM CMOD Application Groups are configured by default to load data into the cache filesystem, and migrate it to secondary storage at a later time. Migrating the data from the CMOD cache to secondary storage doesn’t delete it - the caches are kept at 80% by default, to help make retrievals for end users faster. One of the easiest ways to tune the OnDemand Cache performance is to increase this number to ~~90 or~~ 95%.		The CMOD cache filesystem, often named “arscache” is a pool of storage on your IBM CMOD server that Content Manager OnDemand uses to store documents for fast loading or retrieval. IBM CMOD Application Groups are configured by default to load data into the cache filesystem, and migrate it to secondary storage at a later time. Migrating the data from the CMOD cache to secondary storage doesn’t delete it - the caches are kept at 80% by default, to help make retrievals for end users faster. One of the easiest ways to tune the OnDemand Cache performance on large Content Manager OnDemand installations is to increase this number to over 95%.

	== Where do I configure the behavior of the CMOD cache? ==		== Where do I configure the behavior of the CMOD cache? ==

Jderrick: Inserted diagram: Configuring IBM CMOD Cache behavior

2019-07-02T00:47:23Z

Inserted diagram: Configuring IBM CMOD Cache behavior

← Older revision		Revision as of 00:47, 2 July 2019
Line 10:		Line 10:

	===Diagram: Configuring IBM CMOD Cache behavior===		===Diagram: Configuring IBM CMOD Cache behavior===
			[[File:CacheConfiguration.png\|720px]]

	==How does the cache get filled?==		==How does the cache get filled?==
	As you load data into IBM Content Manager OnDemand, data is placed into the caches for fast access. The only exception to this rule is if you choose not to load Application Group data to the cache at all - which is generally reserved for situations where documents need to be archived for legal or regulatory reasons, but are rarely, if ever, accessed.		As you load data into IBM Content Manager OnDemand, data is placed into the caches for fast access. The only exception to this rule is if you choose not to load Application Group data to the cache at all - which is generally reserved for situations where documents need to be archived for legal or regulatory reasons, but are rarely, if ever, accessed.

← Older revision		Revision as of 15:03, 29 September 2021
Line 15:		Line 15:
	As you load data into IBM Content Manager OnDemand, data is placed into the caches for fast access by end users. The only exception to this rule is if you choose not to load Application Group data to the cache at all, and send them directly to secondary storage - which is generally reserved for situations where documents need to be archived for legal or regulatory reasons, but are rarely, if ever, accessed.		As you load data into IBM Content Manager OnDemand, data is placed into the caches for fast access by end users. The only exception to this rule is if you choose not to load Application Group data to the cache at all, and send them directly to secondary storage - which is generally reserved for situations where documents need to be archived for legal or regulatory reasons, but are rarely, if ever, accessed.

	If you have more than one cache filesytem, ~~IBM CMOD~~ chooses the cache with the most free space, and puts the compressed objects generated by the load there.		If you have more than one cache filesytem, OnDemand chooses the cache with the most free space, and puts the compressed objects generated by the load there.

	==How does the cache get emptied?==		==How does the cache get emptied?==
Line 21:		Line 21:

	== What is cache expiration? ==		== What is cache expiration? ==
	CMOD Cache expiration is the process by which OnDemand reduces the amount of data inside the caches, in order to make room for new data that is loaded into your Content Manager OnDemand server. It does this by removing data that has already been migrated to secondary storage or is eligible for expiration, starting with the oldest documents first, until the filesystems are approximately 80% full by default. As mentioned above, on large IBM CMOD servers that have multiple terabytes of cache, adjusting the minimum and maximum parameters makes optimal use of ~~your~~ expensive cache ~~filesystems~~. The only reason to maintain ~~a terabyte or more~~ of free space in your cache is to ensure there is room to load incoming files if data can't be written to secondary storage for some reason. You can visit the [[arsmaint]] page to find out more about how you can create free space in the IBM CMOD cache filesystem.		CMOD Cache expiration is the process by which OnDemand reduces the amount of data inside the caches, in order to make room for new data that is loaded into your Content Manager OnDemand server. It does this by removing data that has already been migrated to secondary storage or is otherwise eligible for expiration - starting with the oldest documents first - until the filesystems are approximately 80% full by default. As mentioned above, on large IBM CMOD servers that have multiple terabytes of cache, adjusting the minimum and maximum parameters makes optimal use of the expensive storage that the CMOD cache is built with. The only reason to maintain an excessive amount of free space in your cache is to ensure there is room to load incoming files if data can't be written to secondary storage for some reason. You can visit the [[arsmaint]] page to find out more about how you can create free space in the IBM CMOD cache filesystem.

	==What is cache optimization?==		==What is cache optimization?==
	~~Storage~~ is expensive and finite. In order to make the most out of the ~~storage~~ space you have in your IBM CMOD Cache filesystems, you ~~should try to~~ store more of the data that users are actually accessing, for the period of time that ~~they’re interested in~~ them. ~~You can~~ optimize the cache contents so that you’re using precisely ~~enough~~ disk to perform the required retrievals ~~and to~~ have enough space to load new data. An optimized cache contains only the data people are accessing. Unfortunately, there's no built-in tool for performing the Content Manager OnDemand Cache, but [https://cmod.cloud/ibm-cmod-cache-optimization/ CMOD Cache optimization] is offered as a service by IBM ~~Business Partners~~.		Fast and reliable storage is expensive and finite. In order to make the most out of the space you have in your IBM CMOD Cache filesystems, you must store more of the data that users are actually accessing, but only for the period of time that they are actually accessing them. It's possible to optimize the cache contents so that you’re using precisely the amount of disk necessary to quickly perform the required retrievals, but still have enough space to load new data. An optimized cache contains only the data people are accessing. Unfortunately, there's no built-in tool for performing the Content Manager OnDemand Cache, but [https://cmod.cloud/ibm-cmod-cache-optimization/ CMOD Cache optimization] is offered as a service by companies that specialize in [https://TenaciousConsulting.com IBM CMOD Professional Services].

	==How can I optimize the IBM CMOD Cache?==		==How can I optimize the IBM CMOD Cache?==
	If your IBM CMOD Cache Filesystems are large (~~over~~ 1 terabyte) then the default setting for the <code>arsmaint -c </code> will leave 20% - 200 gigabytes of empty cache. If you have multiple 1TB cache filesytems, and you only load 20GB per day, you could have a huge amount of wasted space in your caches. You can adjust this number with the <code>-m </code> and <code>-n </code> options for [[arsmaint]] to set new maximum and minimum caches sizes during cache expiration.		If your IBM CMOD Cache Filesystems are large (for example, 1 terabyte / 1000 gigabytes) then the default setting for the <code>arsmaint -c </code> will leave 20% - 200 gigabytes of empty cache. If you have multiple 1TB cache filesytems, and you only load 20GB per day, you could have a huge amount of wasted space in your caches. You can adjust this number with the <code>-n </code> and <code>-x </code> options for [[arsmaint]] to set new maximum and minimum caches sizes during cache expiration.

	The other ways to tune the cache filesystems are to ~~analyse~~ the patterns of retrievals of Application Group data, and change the cache retention to match actual end user usage, and to use data from your load and retrieval patterns to determine your optimal cache size.		The other ways to tune the cache filesystems are to analyze the patterns of retrievals of Application Group data, and change the cache retention to match actual end user usage, and to use data from your load and retrieval patterns to determine your optimal cache size.

	== Can I delete files in the cache manually? ==		== Can I delete files in the cache manually? ==
	NO! The cache is only to be managed with the [[arsmaint]] utility! The structure of the Cache Filesystem is complex, and deleting files or directories inside the Content Manager OnDemand cache could lead to documents becoming unavailable to end users, and potentially irrecoverable data loss.		NO! The cache is only to be managed with the [[arsmaint]] utility! The structure of the OnDemand Cache Filesystem is complex, and deleting files or directories inside the Content Manager OnDemand cache could lead to documents becoming unavailable to end users, and potentially irrecoverable data loss.

	== Too late, I already deleted files from my CMOD cache filesystem. Help!==		== Too late, I already deleted files from my CMOD cache filesystem. Help!==
	If you have a backup of your cache data in your enterprise backup system, you can probably recover the missing data. ~~You can contact~~ [https://~~Tenacious~~.~~Consulting Tenacious Consulting~~] for assistance. They have tools to help you restore and verify the contents of your cache, or to pull data from secondary storage back into the CMOD cache.		If you have a backup of your cache data in your enterprise backup system, you can probably recover the missing data. Contact a company that provides [https://cmod.cloud/professionalservices/ Professional Services for CMOD] for assistance in recovering data. They have tools to help you restore and verify the contents of your cache, or to pull data from secondary storage back into the CMOD cache.

	== What are the retr and migr directories? ==		== What are the retr and migr directories? ==
Line 47:		Line 47:

	== Can I balance the data in the cache filesystem? ==		== Can I balance the data in the cache filesystem? ==
	Content Manager OnDemand automatically balances the amount of data in caches by placing new CMOD object files in the cache with the most free space, measured in blocks of free space in the filesystem. If you have a large number of cache filesystems with dramatically different utilization, you ~~may~~ have a configuration issue that needs to be corrected.		Content Manager OnDemand automatically balances the amount of data in caches by placing new CMOD object files in the cache with the most free space, measured in blocks of free space in the filesystem. If you have a large number of cache filesystems with dramatically different utilization, you probably have a configuration issue that needs to be corrected.

	== Related Articles ==		== Related Articles ==

← Older revision		Revision as of 23:12, 9 March 2020
Line 13:		Line 13:

	==How does the cache get filled?==		==How does the cache get filled?==
	As you load data into IBM Content Manager OnDemand, data is placed into the caches for fast access. The only exception to this rule is if you choose not to load Application Group data to the cache at all, and send them directly to secondary storage - which is generally reserved for situations where documents need to be archived for legal or regulatory reasons, but are rarely, if ever, accessed.		As you load data into IBM Content Manager OnDemand, data is placed into the caches for fast access by end users. The only exception to this rule is if you choose not to load Application Group data to the cache at all, and send them directly to secondary storage - which is generally reserved for situations where documents need to be archived for legal or regulatory reasons, but are rarely, if ever, accessed.

	If you have more than one cache filesytem, IBM CMOD chooses the cache with the most free space, and puts the compressed objects generated by the load there.		If you have more than one cache filesytem, IBM CMOD chooses the cache with the most free space, and puts the compressed objects generated by the load there.

	==How does the cache get emptied?==		==How does the cache get emptied?==
	You can reduce the amount of data in the cache filesystems with the [[arsmaint]] command. You will want to migrate any data with the <code>arsmaint -m </code> command first, then run the <code>arsmaint -c</code> command to delete eligible items from the cache. You can combine both options in the same command (<code>arsmaint -mc </code>) to perform both tasks.		You can reduce the amount of data in the cache filesystems with the [[arsmaint]] command. You will want to migrate any data with the <code>arsmaint -m </code> command first, then run the <code>arsmaint -c</code> command to delete eligible items from the cache. You can combine both options in the same command <code>arsmaint -mc </code> to perform both tasks. While it's possible to run both cache migration and expiration at the same time in two different processes, it's not recommended.

	== What is cache expiration? ==		== What is cache expiration? ==
	CMOD Cache expiration is the process by which OnDemand reduces the amount of data inside the caches, in order to make room for new data that is loaded into your Content Manager OnDemand server. It does this by removing data that has already been migrated to secondary storage or is eligible for expiration, starting with the oldest documents first, until the filesystems are approximately 80% full by default. As mentioned above, on large IBM CMOD servers that have multiple terabytes of cache, adjusting the minimum and maximum parameters makes optimal use of your expensive cache filesystems. You can visit the [[arsmaint]] page to find out more about how you can ~~clear data from~~ the IBM CMOD cache filesystem.		CMOD Cache expiration is the process by which OnDemand reduces the amount of data inside the caches, in order to make room for new data that is loaded into your Content Manager OnDemand server. It does this by removing data that has already been migrated to secondary storage or is eligible for expiration, starting with the oldest documents first, until the filesystems are approximately 80% full by default. As mentioned above, on large IBM CMOD servers that have multiple terabytes of cache, adjusting the minimum and maximum parameters makes optimal use of your expensive cache filesystems. The only reason to maintain a terabyte or more of free space in your cache is to ensure there is room to load incoming files if data can't be written to secondary storage for some reason. You can visit the [[arsmaint]] page to find out more about how you can create free space in the IBM CMOD cache filesystem.

	==What is cache optimization?==		==What is cache optimization?==
	Storage is expensive and finite. In order to make the most out of the storage space you have in your IBM CMOD Cache filesystems, you should try to store more of the data that users are actually accessing, for the period of time that they’re interested in them. You can optimize the cache contents so that you’re using precisely enough disk to perform the required retrievals and to have enough space to load new data. An optimized cache contains only the data people are accessing. Unfortunately, there's no built-in tool for performing the Content Manager OnDemand Cache.		Storage is expensive and finite. In order to make the most out of the storage space you have in your IBM CMOD Cache filesystems, you should try to store more of the data that users are actually accessing, for the period of time that they’re interested in them. You can optimize the cache contents so that you’re using precisely enough disk to perform the required retrievals and to have enough space to load new data. An optimized cache contains only the data people are accessing. Unfortunately, there's no built-in tool for performing the Content Manager OnDemand Cache, but [https://cmod.cloud/ibm-cmod-cache-optimization/ CMOD Cache optimization] is offered as a service by IBM Business Partners.

	==How can I optimize the IBM CMOD Cache?==		==How can I optimize the IBM CMOD Cache?==
	If your IBM CMOD Cache Filesystems are large (over 1 ~~terbyte~~) then the default setting for the <code>arsmaint -c </code> will leave 20% - 200 gigabytes of empty cache. If you have multiple 1TB cache filesytems, and you only load 20GB per day, you could have a huge amount of wasted space in your caches. You can adjust this number with the <code>-m </code> and <code>-n </code> options for [[arsmaint]] to set new maximum and minimum caches sizes during cache expiration.		If your IBM CMOD Cache Filesystems are large (over 1 terabyte) then the default setting for the <code>arsmaint -c </code> will leave 20% - 200 gigabytes of empty cache. If you have multiple 1TB cache filesytems, and you only load 20GB per day, you could have a huge amount of wasted space in your caches. You can adjust this number with the <code>-m </code> and <code>-n </code> options for [[arsmaint]] to set new maximum and minimum caches sizes during cache expiration.

	The other ways to tune the cache filesystems are to analyse the patterns of retrievals of Application Group data, and change the cache retention to match actual end user usage, and to use data from your load and retrieval patterns to determine your optimal cache size~~. If you need help optimizing your cache filesystem, visit [https://CMOD.cloud/ibm-cmod-cache-optimization CMOD Cloud’s Cache Optimization page]~~.		The other ways to tune the cache filesystems are to analyse the patterns of retrievals of Application Group data, and change the cache retention to match actual end user usage, and to use data from your load and retrieval patterns to determine your optimal cache size.

	== Can I delete files in the cache manually? ==		== Can I delete files in the cache manually? ==
	NO! The cache is only to be managed ~~withthe~~ [[arsmaint]] utility ~~to reduce~~ the ~~amount of data stored in your cache filesystems~~, and ~~make space for new documents in~~ the cache.		NO! The cache is only to be managed with the [[arsmaint]] utility! The structure of the Cache Filesystem is complex, and deleting files or directories inside the Content Manager OnDemand cache could lead to documents becoming unavailable to end users, and potentially irrecoverable data loss.

	== Too late, I already deleted files from my CMOD cache filesystem. Help!==		== Too late, I already deleted files from my CMOD cache filesystem. Help!==
Line 47:		Line 47:

	== Can I balance the data in the cache filesystem? ==		== Can I balance the data in the cache filesystem? ==
	Content Manager OnDemand automatically balances the amount of data in caches by placing new CMOD object files in the cache with the most free space, measured in blocks of free space in the filesystem. If you have a large number of cache filesystems with dramatically different utilization, ~~see this article on [https://CMOD.cloud/cache-consolidation Cache Consiolidation]~~.		Content Manager OnDemand automatically balances the amount of data in caches by placing new CMOD object files in the cache with the most free space, measured in blocks of free space in the filesystem. If you have a large number of cache filesystems with dramatically different utilization, you may have a configuration issue that needs to be corrected.

	== Related Articles ==		== Related Articles ==