SBG Replication
Updated: 21 May 2010 | 11 comments
This issue has been solved. See solution.
Hi, we currently have setup an SBG 8.0 appliance and we have another in the test environment. Both are setup to be Control Centers and we'll be moving one to a Disaster Recovery Site. We need to make sure that the logs will be replicated between the appliances. I've checked the admin guide and can't fully grasp the concept.
Do I replicate the CC/Scanner from one to the other by adding the scanner only?
discussion Filed Under:
Comments
...
Anyway, I went in and tried to add the other server to the first one.
I'm getting an error message:
"Cannot find an Agent that is running.Please check the specified host, and that the Agent will allow connections from this IP address."
The agent if that's the 2nd machine is currently configured to accept all connections and I've tried pinging that host succesfully. I'm accessing both servers from a remote console far from the servers.
“Your most unhappy customers are your greatest source of learning.”
Oh, one more thing
Someone encountered the same error and he tried reinstalling and got it fixed.
If I tried resetting the configurations, will it also remove the upgrade?
“Your most unhappy customers are your greatest source of learning.”
Hi, not sure if I understand
Hi,
not sure if I understand what you're trying to do here. If you mean attaching the same scanners to two Control Centers that will not work. Scanners can only be added only one Control Center.
If not, please provide more details.
Thanks,
Federico
I have 2 SBG servers. I've
I have 2 SBG servers. I've configured them seperately so they both have a scanner and a control center. I want to get them to communicate so that the logs, database, and policies of one will be sent to the other and vice-versa so that it can be managed from either control centers. And we're planning on adding a third.
“Your most unhappy customers are your greatest source of learning.”
Hi, I'm afraid that's not a
Hi,
I'm afraid that's not a current feature of the product.
Regards,
Federico
Thanks fferaboli. Change of
Thanks fferaboli.
Change of plans, just put one machine on standby and the other will be for production use. I'm not sure if having 2 SBG appliances working on a single domain would work. They'll be connected to different email servers belonging to a cluster.
Does the scanner contain the database or is it just that - a scanner.
“Your most unhappy customers are your greatest source of learning.”
Hi, I understand you have 2
Hi,
I understand you have 2 SBG boxes (both are scanner + control center at the moment).
There's not active passive feature at the moment and there's no way to have 2 control centers talking to the same scanner.
Going back to first post, one solution to the logging question can be to use remote logging vis Syslog. You can configure SBG to send all your logs to a host that will collect everything that is generated by each of the SBG appliances when running and you don't need to replicate anything this way (this is for logs).
If you want to have one appliance running and the other as a spare with same configuration, you then need to do backups on SBG 1 and restore it on SBG 2. You can even schedule regular backups on SBG.
Another option is to have both appliances running separately (and maybe still doing scheduled backups).
Hope this helps,
Federico
When doing the restore, will
When doing the restore, will that just add on to the existing logs and not replace the one in the target machine?
I'm thinking of using cron and ftp right now.
“Your most unhappy customers are your greatest source of learning.”
Hi, by restoring you replace
Hi,
by restoring you replace the data in the target machine.
Regards,
Federico
Marked the best answer as a
Marked the best answer as a solution. Moving on to the ideas section. :D
“Your most unhappy customers are your greatest source of learning.”
I've had problems restoring a CC to a box in new address space
Just a heads up. Test your recovery processes.
Would you like to reply?
Login or Register to post your comment.