Kennisbank

Overview

This article provides step-by-step instructions for migrating Warden content filter policies, blacklists, whitelists, and Bayes training data between servers. Before beginning the migration process, ensure you have administrative privileges on both the source and destination environments.

Migrate Content Filter Policies, Blacklists, and Whitelists

Use the Policy Migrator interface to export configurations from a source server and import them into a destination server.

1. Navigate to Warden > Settings > Content Filter Settings > Policy Migrator.
2. Select the target users for migration.
3. Select Warden as the data source.
4. Click the Export button and save the generated XML file to your local workstation.
5. On the destination server, navigate to Warden > Settings > Content Filter Settings > Policy Migrator.
6. In the Policy Import section, click Browse, locate the exported XML file, and select it.
7. Click the Import button to apply the configurations to the destination server.

Migrate Bayes Training Data

Bayes training data is transferred between servers using the command-line interface. Ensure the Warden service is fully installed and operational on the destination server before proceeding with the import.

1. On the source server, export the Bayes database by executing the following command:

sa-learn -u amavis --backup > /tmp/amavis-bayes.db

2. Transfer the /tmp/amavis-bayes.db file to the destination server.
3. On the destination server, import the data into the Warden database by executing:

sa-learn -u amavis --restore /tmp/amavis-bayes.db

Troubleshooting and Common Issues

• Prolonged Import Times: Restoring large Bayes databases is a resource-intensive operation. A database containing approximately 2 million tokens typically requires two hours to complete.
• Service Dependency: If the restore command fails or returns an error, verify that the Warden service and all associated dependencies are correctly installed and running on the destination server before retrying.