In general, when you setup a Citrix server if you select all the defaults then the access database file is created automatically on the first server in the farm. The other servers also use that database automatically. You only really need to do anything with the database if you want to compact it or back it up, or if you want to move it to another server.
Compacting the Access data store Servers hosting the data store have both a local host cache database file (Imalhc.mdb) and a data store database file (Mf20.mdb). Use dsmaint compactdb on both these files to compact them. Servers not hosting the data store have only the local host cache database file (Imalhc.mdb) that can be compacted occasionally to improve performance.
NOTE: The dsmaint compactdb command can be executed while the server is running, even so it is best to do this when there are no users logged on (eg on a weekend). Citrix recommends that the database be compacted on a regular basis, but exactly how regular depends on how busy your particular farm is.
Moving the Access data store At some time it may be decided to move the data store from the local Access database to a SQL server. How this is performed is discussed in the Citrix Document ID: CTX773628 (available from http://www.citrix.com). It is also possible that it may be desired to move the Access data store from one server to another server (for example, if the server currently hosting the data store needs to be brought down for maintenance for a period of time). This is done as follows:
Copy the backup database or the original database and the existing dsn file to the server that is to become the new host server. These files are MF20.mdb and MF20.dsn and are located in the directory %systemdrive%\program files\citrix\independent management architecture\
If you copy the existing MF20.dsn file, after copying it edit it with notepad and - if it has the old server name in it, change that line to point to the new server.
On all servers in the farm, execute dsmaint failover to point to the new host server. (NOTE: The IMA service must be running on these servers for the command to execute properly. You must do this before executing dsmaint config on the new host server as specified in the next step; otherwise the other servers in the farm will not be able to write to the database.
On the new host server, execute dsmaint config to point the IMA service to the newly created DSN file from Step 2. If no security was set on the Access database, use the default user account and password information (citrix/citrix).
If it is going to remain in the farm, change the original host server to its new role as an indirect server (it will now access the data store indirectly through the new host server) by running the Registry Editor (Regedt32.exe) and changing the value of the following registry key from Imaaccess.dll to Imaodbc.dll: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\DatabaseDriver
Stop and restart the IMA service on all farm servers.
When the IMA service on the new host server is running, stop and restart the IMA service on all of the other servers in the farm. IMPORTANT: Restarting the IMA service instead of rebooting might cause the SNMP service to Dr. Watson if SNMP is enabled. This error is benign but is generally an indication that SNMP has been installed on a server after a service pack has been installed.