Patented Synchronous
Mirroring
Ease
of Use
Non-intrusive System Maintenance
Scalability and
Interoperability
Requirements
Patented Synchronous
Mirroring
synchronous
mirroring protects production Windows data by creating a second
copy on a connected Windows server, which can be used if the first
copy is damaged or becomes unavailable. It eliminates the need for
a shared disk and can be used to replicate your data for business
continuance. Through the use of a dedicated link, risks and
latency typically associated with public networks are avoided.
Co-StandbyServer AAdvanced supports standard LAN and also
Fiber connections, to enable you to mirror data across distances
up to 10 kilometers.
Ease of Use
Co-StandbyServer
AAdvanced is designed to minimize the administrative burden of
managing applications in branch office and departmental IT
departments. Key ease-of-use features include:
Wizard Deployment:
Wizard deployment using setup.exe ensures
that you can quickly and easily deploy Co-StandbyServer
AAdvanced in just a few minutes per server.
New GUI Interface
The Java Console provides you with more resource details than provided with previous versions of Co-StandbyServer, ensuring you can rapidly find and repair problems on the failed server.
The Java
Console provides a live state indicator for all managed objects
defined by a color status, shown right on the main screen for
all managed servers and resources across as many branch offices
and departments as you have protected. This allows you to see
what is happening as soon as it occurs, and respond to it more
quickly and precisely if action is required.
Operator Level Control
Three levels of user-access, including
administrator, operator and read-only access, simplify and
reduce the cost of your availability management. Operators can
view and control all objects in a domain, but cannot change
their definition. This ability to delegate daily operations to
operators frees up valuable administrator's time while still
maintaining administrative control.
Availability Tracking
Availability Tracking allows you to track
metrics for reporting and analysis, providing a comprehensive
picture of the health of your environment. Each resource group
defined by the administrator is tracked by cause, duration, date
and time of each downtime event, and is categorized as planned
or unplanned. Administrators can export this data to easily
report on the service levels that they have delivered, and to
measure the downtime associated with maintenance and other
planned activities versus actual failure.
Non-intrusive System
Maintenance
Routine systems
maintenance activities can now be performed during regular
business hours using Co-StandbyServer AAdvanced.
Proactively relocate an application from one server to another
while users continue to operate virtually uninterrupted and with
an absolute minimum of downtime. Improved application uptime
reduces operating expenses, reduces the stress on systems
administrators, and increases corporate
productivity.
Scalability and
Interoperability
Co-StandbyServer
AAdvanced can easily be upgraded to AAM with just the
change of a license key, to work with UNIX and Linux systems in
addition to Windows. All of these servers can be monitored and
managed from AAM's Java Console at the same time, dramatically
lowering the total cost of availability management. This
capability to scale up to UNIX and Linux is unique to 's
offering, and enables Windows to enter data centers without adding
extra cost and management overhead. In addition, it offers
customers running Windows in multiple branch offices the ability
to manage and control all of their resource availability, across
all sites and servers, using a single centralized team of expert
administrators.
Requirements
Co-StandbyServer NT:
Two
Intel-based servers. The hardware in each does not need to be
identical but it should be as similar in RAM, processor and disk
technology as possible.
30
MB of free space on the system hard disk for the Co-Standby Server
files on each server.
An
active/active configuration requires a minimum of two additional
disks (total of three) per server as seen by Windows NT Disk
Administrator.
An
active/passive configuration requires at least one additional disk
(total of two) per server as seen by Windows NT Disk
Administrator.
Co-StandbyServer 2000:
Two
Intel-based servers with 133 MHz or higher Pentium-compatible CPU.
256
MB of RAM recommended minimum (128 MB minimum supported; 8 GB
maximum).
Windows 2000 Server/Advanced Server
30
MB free disk space
Additional network cards in each
machine.