The Adaptiva OneSite Cache Migration Tool is designed to convert and copy content that is published in Adaptiva OneSite but cached in non-Adaptiva form (such as a ConfigMgr Distribution Point), into the local Adaptiva Client cache. This alleviates the need to download content a second time for use in the Adaptiva Peer-to-Peer network.
The Cache Migration Tool can convert and copy content from the following locations:
- ConfigMgr 2012/Current Branch distribution point
- 1E Nomad™ client cache
- ConfigMgr client cache
- Altiris™ Notification Servers, Altiris™ Package Servers, Altiris™ Clients
How It Works
When the Cache Migration Tool is executed on an Adaptiva client, the following steps are performed:
- The client java component (JAR file) is extracted and put into the external folder under the Adaptiva Client installation folder.
- The Adaptiva Client service is restarted.
- For each item in the cache a message is sent to the Adaptiva Server to see if that package is published in Adaptiva OneSite.
- The server responds with a message to either Convert (if the package is published in Adaptiva) or Abort. If the response is Convert, the content is converted and stored in the Adaptiva Client cache of the machine it is run on. If the response is Abort, the log file can be examined for the reason the content could not be migrated.
- After all packages have been checked, the client JAR file is removed from the external folder.
- The Adaptiva Client service is restarted.
- Approximately 1 minute after the client has restarted, the OneSitePreCacheClient component lets the Adaptiva Server know that the newly converted content is available from this client in the Adaptiva P2P network.
Prerequisites
- The Adaptiva Client must be installed on the machine where the Cache Migration Tool is executed, and enough disk space should be available to accommodate the content.
- The Cache Migration Tool should be executed with administrative rights.
Tool Location
The Adaptiva Cache Migration Tool is included in the Adaptiva OneSite download source, in the \Tools folder, and is named CacheMigrationTool.exe.
Using the Cache Migration Tool
The tool can be distributed via a ConfigMgr package with an associated program or executed via command line.
CacheMigrationTool.exe -<source> [-paramater1] [-parameter2]
Command Line Parameters
| Parameter | Description |
|---|---|
| Content Source | |
-dp2012 |
Used to migrate content from a Distribution Point where Adaptiva is connected to an ConfigMgr 2012/Current Branch site. |
-nomad |
Used to migrate content from a 1E Nomad™ client cache. |
-sccmclient |
Used to migrate content from a ConfigMgr client cache. |
-altirispackageserver |
Used to migrate content from an Altiris™ package server. |
-altirisclient |
Used to migrate content from an Altiris™ client. |
| Additional Parameters | |
-p2p <#> |
Used to replicate migrated content to other peers in the local office. The # value represents the number of clients where the content should be replicated. This parameter requires that a source parameter be used. Ex: |
-delete |
Used to delete migrated content from the source cache. NOTE: This option can only be used with the Ex: |
-regenerate |
Used to regenerate previously migrated content from all contents found and deletes an earlier generated copy. This parameter requires that a source parameter be used. NOTE: This option is generally not required and solves a specified case for fixing contents generated by the Cache Migration Tool prior to version 4.5.632. Ex: |
-revalidate |
Used to validate all existing content files in the Adaptiva Client cache. Once executed, the tool will verify the hash is correct for all content and remove any invalid or partial content. NOTE: This option can be run independently and does not require that a source parameter be used. Ex: |
Migrating from an Altiris™ Notification Server
Cache migration is now supported from Altiris™ Notification Servers, Altiris™ Package Servers, and Altiris™ Clients.
Contact Adaptiva support (support@adaptiva.com) to obtain an OBEX file that contains an automated workflow which will import all Altiris™ Software Releases into ConfigMgr Applications and automatically publish them in Adaptiva.
See the table above for the command line parameters used to migrate content from Altiris™ Package Servers and Altiris™ clients.
Logging
When the cache migration executes on a client, the following logs document the process:
| Log File | Location | Purpose |
|---|---|---|
| Client | ||
| CacheMigrationTool.log | %AdaptivaClientInstalPath%\Logs | Documents the execution activity of the Cache Migration Tool. |
| CacheMigrationClient.log | %AdaptivaClientInstallPath%\Logs\componentlogs | Tracks the activity of the Cache Migration Tool as it works with the local content. |
| Server | ||
| Adaptiva.log | %AdaptivaServerInstallPath%\Logs\ | Displays the communication from the client running the Cache Migration Tool as well as the validation of each item being migrated. |
Comments
0 comments
Article is closed for comments.