HomeProductsServicesDownloadSupportNewsPartnersPurchaseContact

BUY
TRY
? Questions

I am very content with the software. You are to be commended for a job well done! 
Jim Restucci, Senior VP
Axcess Internet Services
 

PRODUCT  INFORMATION
Product Sheet
Client Testimonials
Get a Quotation
Reviews and Awards
Readers Choice Awards
White Papers
ROI Calculator
Modus Powered Solutions
The Modus Technology
Modus Blockade Solutions
Modus Manuals
   

The power
of Modus.

The reliability
of Dell.

2 wires to plug.

   

I did not think it was possible to have such an effective spam fighting solution that requires minimum amounts of administration in a single package. Vircom has set the standard for fighting the SPAM battle.
Rudolph Kornter
Infotech EDV-Systeme Gmbh

 

   
   
Clustered E-mail Security Solution

Modus Blockade is a cluster of Modus anti-spam solutions specifically designed for robustness and scalability. Whether you need high performance messaging systems, scalable configurations, redundant setups or failover options as part of your disaster recovery plan, Modus Blockade is the e-mail server and / or gateway-based security package you are looking for.

Use a Modus Blockade:

  • In high-performance / large scale networks

  • For high availability / failover options

  • For your contingency / disaster recovery plan

Features

  • Centralized quarantine reports

  • Shared user settings

  • Highly scalable

  • Compatible with clustered databases and servers

  • Various configurations available



 

A Modus Blockade with gateway configuration is deployed either to protect large scale environments or to add robustness and redundancy to existing networks. No matter how many nodes are needed, the Modus Blockade shares user settings through a single or a clustered database for maximal efficiency and performance. The quarantine is also centralized, making the Blockade operate exactly like a single gateway protection for end users.

As an entry-level deployment, a two-node Blockade can be operated without a load balancer, using the round-robin feature of the DNS server. One of the nodes can also host the database and user settings, which will be shared with the other node.

A typical Blockade will include a load balancer to ensure that traffic and CPU usage in each node is as well-balanced as possible. A separate database will also be added, to ensure proper performance.

An advanced setup will feature redundancy at each level of the process. Load balancers, databases and servers will all be doubled to ensure high availability and failover options in case one or more components fail or malfunction.

An advanced setup for large scale operations will be the same, except that elements composing the e-mail network will all be arrays of components for ultimate performance and availability.

A Modus Blockade with server configuration is used as a primary e-mail service, either for redundancy or for large scale networks. A server-based Blockade includes all perimeter and specific protection plus advanced e-mail delivery and management features. Server-based Blockades rely on one or more databases for quarantine management and user settings as well as a storage area network (SAN).

As an entry-level deployment, a two-node Blockade can be operated without a load balancer, using the round-robin feature of the DNS server.

A typical server-based Blockade will include a load balancer to ensure that traffic and CPU usage in each node is as well-balanced as possible.

An advanced setup will feature redundancy at each level of the process. Load balancers, databases and SANs will all be doubled to ensure high availability and failover options in case one or more components fail or malfunction.

An advanced setup for large scale operations will be the same, except that elements composing the e-mail network will all be clustered for ultimate performance and availability.

Furthermore, server-based Blockades can be used as part of a disaster recovery plan (DRP). In this case, the nodes are separated over two different geographical locations and do not operate simultaneously. Node number 1 will be the main server, while node number 2 will be immediately available in case of a failure. Both nodes maintain synchronized via mirroring and use their own database and SAN.

ABOUT SAV25      USER AGREEMENT   PRIVACY POLICY   CONTACT US                                                                           
SAV25 Data Systems
appropriate solutions
Copyright ©1999-2005 SAV25 DATA SYSTEMS. All Rights Reserved   
All Product names, trademarks, trade names, service marks and logos included in this site are the property of their respective companies and/or affiliate companies.
For best viewing, use Opera 8.02 or higher or Internet Explorer 6.X or Firefox 1.X at 800X600 resolution