Manual updates

For Satellites with low-bandwidth network links, Manual Software Repository Cache updates allow you to pre-populate the Software Repository Cache at installation time. You can also configure refreshes for an existing cache. The Software Repository Cache is populated by an out-of-band method, such as by cutting CDs of the required packages and shipping them to the Satellite. To perform manual updates, use the SA DCML Exchange Tool (DET) to copy existing packages from an SA core or use the Staging Utility to perform the update. See Creating software repository cache manual updates and Staging files to a software repository cache.

When configured for manual updates, a Software Repository Cache does not communicate with upstream Software Repository Caches or the Core’s Software Repository until you initiate an update. The Satellite considers its own Software Repository Cache as authoritative.

If the caching policy is manual update and you request an on-demand software update, the Software Repository Cache will raise a wordbot.unableToCacheFile exception.

Even if you have configured a Software Repository as on-demand update, you can apply a manual update regardless of its update policy.

When applying manual updates in a Satellite installation with multiple Software Repository Caches, you must apply the update to each Software Repository Cache in the Satellite. Otherwise, when performing operations that retrieve files from the Cache (for example, when installing software on a server in the affected Satellite), you may get the wordbot.unableToCache file error.