The Mobility Connector database is named mobility. The default user for accessing the Mobility Connector database is datasync_user.
Database maintenance activities for the Mobility Connector database ensure satisfactory performance for mobile device users.
The Mobility Connector database is a PostgreSQL database. As with any database, the Mobility Connector database requires regular maintenance in order to perform reliably. If you are new to managing a PostgreSQL database, see Routine Database Maintenance Tasks
on the PostgreSQL Documentation Web site for assistance.
Most items synchronize automatically from GroupWise mailboxes to the Mobility Connector database. As a result, they are readily available when users want to manually synchronize the contents of specific folders. Over time, older items must be cleaned up on a regular basis to prevent degradation in Mobility Connector synchronization performance.
By default, the Mobility Connector automatically cleans up outdated items from the Mobility Connector database between midnight and 6:00 a.m. every day. It cycles through all users and all folders once each day. It checks the user-selected settings for each mobile device to determine the maximum age after which users no longer want items retained on their mobile devices.
You can adjust the time period during which the Mobility Connector performs nightly maintenance, and you can turn off nightly maintenance, if necessary.
In Synchronizer Web Admin, click the Mobility Connector to display the Mobility Connector Configuration page.
Click
.To adjust the time when nightly maintenance occurs:
Locate the following lines:
<databaseMaintenanceStartHour>0</databaseMaintenanceStartHour> <databaseMaintenanceStopHour>6</databaseMaintenanceStopHour>
Using the 24-hour clock, change the start hour and stop hour as needed for your Synchronizer system.
(Optional) To turn off nightly maintenance:
Locate the following line:
<databaseMaintenance>1</databaseMaintenance>
Change 1 to 0.
IMPORTANT:This is not recommended. Without nightly maintenance, items accumulate in the Mobility Connector database indefinitely and reduce Mobility Connector performance over time.
Click
.Click
on the menu bar to return to the main Synchronizer Web Admin page.In a terminal window, restart the Synchronizer services:
rcdatasync restart
(Conditional) If the Mobility Connector is not configured to restart automatically along with the Synchronizer services:
In the
column for the Mobility Connector, click ( ) to stop the Mobility Connector.Click (
) to start the Mobility Connector with the new nightly maintenance settings in effect.You can see what the Mobility Connector is doing as it performs its nightly maintenance by searching for MaintenanceMonitor in the Mobility Connector log file:
/var/log/datasync/default.pipeline1.mobility-AppInterface.log
If logging is set to Debug, the Mobility Connector logs each item that it deletes. This can result in a very large log file. Without the Debug log level, the Mobility Connector lists the users as it performs nightly maintenance for them. For more information about log levels, see Controlling Connector Logging
in Connector and User Management
in the Novell Data Synchronizer System Administration Guide.