Deletion of the BLOB cache files and sub-folders commences.ĭeleting the sub-folders and files isn’t an instantaneous operation, though. You go into the file system, find your BLOB cache folder (by default, C:\blobCache), open it up, select all files and sub-folders contained within, and press the key on your keyboard. Let’s say that you decided to manually clear the BLOB cache for a sizable publishing site collection that is heavily trafficked. This risk may be small for sites that see little traffic or are relatively small, but the risk grows with increasing request volume and site collection size.
Jumping in and simply deleting files without stopping requests to the affected site collection (or rather, the web application/applications servicing the site collection) risks sending you down the road to (further) cache corruption. Just delete all of the files in the target BLOB cache folder (as specified in the web.config) and you should be good to go, right?
If the aforementioned flush mechanisms simply aren’t working for you, you’re probably staring down the barrel of a manual BLOB cache flush. This solution utilizes a different mechanism for flushing, but the net effect produced is the same as for the out-of-the-box (OOTB) mechanism: all BLOB-cached files for the associated site collection are deleted from the file system, and the three BLOB cache tracking files for each affected web application (IIS site) are reset.įor more information on the internals of the BLOB Cache, the flush process, and the files I just mentioned, see my previous post entitled We Drift Deeper Into the Sound … as the (BLOB Cache) Flush Comes. If a site collection is extended to multiple web applications, only one web application’s BLOB cache is affected by this operation.Īlternatively, my MOSS 2007 Farm-Wide BLOB Cache Flushing Solution (screenshot shown on the right) can be used to clear the BLOB cache folders associated with a target site collection across all servers in a farm and across all web applications (zones) serving up the site collection. When a flush is executed in this fashion, it affects only the server to which the postback occurs and only the web application through which the request is directed. Executing a flush is as simple as checking the supplied checkbox and clicking the OK button at the bottom of the page. This option (circled in red on the page shown to the right) is exposed through the Site collection object cache menu item on a publishing site’s Site Collection Administration menu.
When corruption does occur or a cache flush is desired for any reason, the built-in “Disk Based Cache Reset” option is typically adequate for flushing the BLOB cache on a single server and single web application zone. In my experience, the answer is “no.” The MOSS BLOB cache generally requires little maintenance and attention beyond ensuring that it has enough disk space to properly store the objects it fetches from the lists within the content databases housing your publishing site collections.
Is BLOB Cache Corruption a Common Problem? The MOSS Binary Large Object (BLOB) cache, or disk-based cache, is no different. Configure use of passwords for operating system drives.It’s a fact of life when dealing with many caching systems: for all the benefits they provide, they occasionally become corrupt or require some form of intervention to ensure healthy ongoing operation. Configure TPM startup key and PIN: Required/Allowed Configure TPM startup PIN: Required/Allowed Note that if you do not enable this policy setting, options in the "Require additional authentication at startup" policy might not be available on such devices.
When the Windows Recovery Environment is not enabled and this policy is not enabled, you cannot turn on BitLocker on a device that uses the Windows touch keyboard. If this policy is not enabled, the Windows Recovery Environment must be enabled on tablets to support the entry of the BitLocker recovery password. If you enable this policy setting, devices must have an alternative means of pre-boot input (such as an attached USB keyboard). The Windows touch keyboard (such as that used by tablets) isn't available in the pre-boot environment where BitLocker requires additional information such as a PIN or Password. This policy setting allows users to turn on authentication options that require user input from the pre-boot environment, even if the platform lacks pre-boot input capability. Chinese (Traditional, Hong Kong S.A.R.)Įnable use of BitLocker authentication requiring preboot keyboard input on slates.Español (España, alfabetización internacional)