You have a LiveUpdate Administrator (LUA) 2.x system that is running out of disk space on the volume where LUA is installed. You would like to modify or reconfigure LUA so that it stores content in a different folder or on a different volume. How can this be accomplished?
- Disk space exhaustion
- Desire to balance I/O load and content across multiple disk volumes
By default, LUA stores all content on the system volume - normally the C: drive.
If the default Distribution Center (DC) was initially used, it is possible to establish a DC on a remote server and delete the local clu-prod DC on the LUA server itself. Also, a small amount of LUA content - the folder used for temporary storage of downloaded definitions - can be redirected via Configuration > Preferences > Changing the specified "Temporary Directory" folder. In releases prior to LiveUpdate Administrator 2.3.2, there is no supported method for moving or redirecting the rest of the content. LUA 2.3.2 introduced the ability to move the Downloads / Manage Updates folder.
If it is not possible to upgrade to LUA 2.3.2, there are two workarounds that can be used to address this issue:
Reinstall LiveUpdate Administrator. During installation, you have the option to place the temporary download folder used by LUA somewhere other than the default location of C:\All Users\Application Data\Symantec\LiveUpdate Administrator\Downloads. Optionally, you can also install the product somewhere other than the default location of C:\Program Files\Symantec\LiveUpdate Administrator, which will also cause the folders associated with the Production and Test distribution centers to be installed in the new location.
Note: Since there is no supported method of exporting configuration specifics such as schedules, distribution centers, and selected products, it may be prudent to take note of these before reinstalling.
Configure folder(s) you wish to relocate as an NTFS mount point referencing another volume with sufficient space. Consult Microsoft documentation or technical support for additional information regarding the implementation of this technique.
Imported Document Id