Messaging Gateway

Hi there,

currently we have one BGW server wich is running as Scanner and control center at once.  This appliance is currently our productive system and is faulty. The database seems to be messed up. We can't fix it. The DB is nearly 30GB and Backup/Restore is not working. It gives us always the error "not enough" space.
And in fact there is not enough space. I have tried the clean up steps, given in the admin guide but this made 2GBs and we need nearly 60GB.

So we decided to rebuild the whole BGW concept now with a seprate control center and a separate Scanner.  This constallation is working.

But the problem are the Personal Good and Bad Sender lists. These lists are still on the faulty server.

My question is how can I export them to the new Control center.
I have found on the faulty server in the folder "/data/scanner/etc" a file called: user_pref.xml. This file seems to contain the whole lists.
Can I just copy this file to the new control center? For this I need the root rights. Support seems not have enough rights to do it.
Or are there any other ways to export these lists? 

Thanks in advance

In order to see the End User Settings you have to export the table from Mysql.

1. Login to the CLI as support.
2. Run the command "cd /opt/Symantec/Brightmail/mysql/bin"
3. Run the command "./mysqldump -h127.0.0.1 -ubrightmailuser -p`cat /data/etc/.brightmailuser` brightmail settings_user_pref > /tmp/userprefdump.sql"
4. Use WinSCP and the support account to pull the file off the system.

This looks like only the "export" part, how could it be "import" back to the new system?

Hey Guys,

There currently isn't any supported method to achieve this.  My advice would be to work with Support to get this database back into a position you can work with, then run a database backup and restore on the new appliance configured identically(including version, IP's, hostnames etc.)

Support should be able to help determine what tables in the database are taking up all this space and help clean it up.  Had you already tried deleting all the reporting and log data being stored?  This is most likely where the problem is...  Even after doing this you may need to optimize the database to free up the space, again Support should be able to help with this.

Kevin