We have SAP Content Server - and it must be highly available (protect against the failure of iron on the same server). What are the possible options?
Can anyone have success story on this subject?
Someone deploy such HA solution?
Our environment: 2 identical host, Windows, local to each host drives, database MaxDB.
Actually, the question revolve around high-availability database MaxDB.
Here are some options:
Failover Cluster
A failover cluster consists of a primary and a backup instance on different hosts, bothof which access shared data and logs. In the event of failure, a switchover is madefrom the primary instance to the backup instance. Processing can then continue asnormal.
This option does not suit us - there is no shared storage, only local.
Standby Database
A standby database is a copy of the primary database. Log shipping keeps thestandby database up-to-date. The log backups are regularly imported from theprimary instance.If you experience problems with the primary database, you can start operating thestandby database immediately, and continue working without significant downtime.
The most suitable option, but there is no clear description of how it works.
Note to 952 783 - FAQ: MaxDB high availability (http://www.saptechies.com/faq-maxdb-high-availability/) says that in MaxDB replication can be configured through the "script-based shadow database solution" or through third-party software developers, for example DBShadow from Libelle.
Hot Standby Database
A hot standby system consists of a master component and one or more standbycomponents. The hot standby system behaves like a normal database instance. Thestandby components must run on separate hosts.Hot standby often uses switchover software to transfer control to the standbyinstance.
Advantage - automation, but also requires a shared disk array - does not fit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.