Hi, Can you define a little more what is meant by "...a suitable memory management system and a cluster solution..."
Can you explain the layout of the cluster? Does it need shared storage where alle instances actually act upon the same datafiles? Or can it use network raid1 to have a copy of the data on both systems, and if so: is it sufficiant to only have the logfile replicated or do the datafiles also need to be in raid? How is the failover managed. Does it need something like heardbeat or does the standbyserver automatically take over when master goes down? The reason for my inquiry is that we are about to go into production with maxdb and a home grown hotstandy solution. Maybe it is worth waiting a little longer and see what this can do. thanx and greetings, Filip Sergeys On Fri, 2004-03-05 at 11:32, Montag, Marina wrote: > > Hi Jan, > Hot Standby can be used from MaxDB Version 7.5.00.08. > The documentation on Hot Standby Systems and their administration will be available > on the MaxDB documentation page (http://www.mysql.com/products/maxdb/docs.html) > within 2 weeks, approximately. Production is being made right now. > Meanwhile I can send you an extract of the relevant paragraphs in the Database > Manager CLI documentation: > > Setting Up a Hot Standby System > > Use > You set up a hot standby [Extern] system to increase the availability [Extern] of > your database system. > For this, you need a suitable memory management system and a cluster solution. Refer > to the manufacturer's documentation > for information about the setup of a memory management system and cluster > configuration. > > Prerequisites > * Master and standby components use the same hardware platforms (memory, type and > number of processors). > * All data paths and files (run directory, volumes, trace files, and so on) used in > the configuration correspond to the master and standby components. > * The same database software version is installed on all computers. > * All computers are activated. > * The X server runs on all computers. > * The user who sets up the hot standby system has administrator rights on all > computers. > > Procedure > ... > 1. Create the database instance > 2. Transfer the database instance to OFFLINE state > 3. Configure a master component > 4. Transfer the database instance to ONLINE state > 5. Define a new standby component > > Savepoints are not possible when setting up a new standby component. > > 6. Transfer the standby component to STANDBY state > > Result > The hot standby system is set up. To add further standby components, repeat the > procedure from step 5. > To change database parameters, address the master component of the hot standby > system with the usual commands. > The changes are automatically transferred to all standby components. > See also: > Example > Database Administration documentation: Special Database Parameters > > > Overview of the DBM Commands for Setting Up a Hot Standby System > > Querying Hot Standby Parameters > hss_getnodes > Addressing a Standby Component > hss_execute > Defining an Additional Standby Component > hss_addstandby > Removing a Standby Component > hss_removestandby > Configuring a Master Component > hss_enable > > Requesting Hot Standby Parameters > > Use > You request the hot standby parameter values. The system displays which server in > the cluster is the current master > component (CURRENT_NODE). > > Prerequisites > You have the server authorizations ParamRead, ParamCheckWrite or ParamFull. > > Syntax > hss_getnodes > > Reply > The system displays the information about the hot standby system. > > Example > hss_getnodes > OK > HS_STORAGE_DLL libhsscopy > OFFICIAL_NODE hotel_official > CURRENT_NODE genua > HS_NODE_001 genua > HS_NODE_002 parma > > See also: > Example: How to Set Up a Hot Standby System > Database Administration documentation: Special Database Parameters > > > Addressing a Standby Component > > Use > You send a Database Manager command to a standby component using the master > component. > > Generally, Database Manager commands should not be transferred directly to standby > components but to the cluster instead. > The cluster software forwards the commands to the master component. The master > component executes the commands and, > if necessary, synchronizes the standby components. > > Prerequisites > You have the required server authorizations. > > Syntax > hss_execute <hs_node_nnn> <dbm_command> > > hs_node_nnn Server name/address of standby component nnn > dbm_command Database Manager command > > Reply > The system displays an OK message. > > Example > To request the status of the standby component parma, use the following command: > hss_execute parma db_state > > > Defining an Additional Standby Component > > Use > You define an additional standby component for the hot standby system. > > Prerequisites > * You are connected to the hot standby [Extern] system via the master component in > the Database Manager CLI. > * The hot standby system is in the ONLINE operational state. > * All data paths and files (run directory, volumes, trace files, and so on) of the > standby component to be added > must correspond to those of the master component. > * You have the server authorization ParamFull. > > Syntax > hss_addstandby <hs_node_nnn> login=<user>,<password> [path=<dependent _path>] > [delay=<hs_delay_time_nnn>] > > hs_node_nnn Server name/address of standby component nnn > user Operating system user on the standby server must have administrator > rights for the server. > dependent_path Installation path of the database software on the standby > server. > If you do not enter a path, the version of database software used > will be that which corresponds to the > database software version of the master component. > hs_delay_time_nnn > Time delay in seconds for the > recovery of log entries by the standby component nnn. > > Reply > The system displays an OK message. > > > Removing a Standby Component > > Use > You remove a standby component from the hot standby system. > > Prerequisites > * You are connected to the hot standby system via the master component in the > Database Manager CLI. > * You have the server authorization ParamFull. > > Syntax > hss_removestandby <hs_node_nnn> > > hs_node_nnn Server name/address of standby component nnn > > Reply > The system displays an OK message. > > > Configuring a Master Component > > Use > You configure the master component for a hot standby system. > > Prerequisites > * The operational state [Extern] of the database instance is OFFLINE. > * You have the server authorization ParamFull. > > Syntax > hss_enable lib=<hs_storage_dll> node=<official_node> > > hs_storage_dll Name of the library required for controlling the memory > management system. > official_node Official name of the database within the cluster system. > This name is defined by the system administrator. > > Reply > The system displays an OK message. > > Example: How to Set Up a Hot Standby System > You need to set up a hot standby system called HOTELDB with the master component > GENUA and standby component PARMA. > The operating system user DAVID with password BLUE is recognized on the server > GENUA. The hot standby system should be > addressed with the name HOTEL_OFFICIAL. The operating system user ANNA with password > MAY is recognized on the server PARMA. > The installation path of the database software on this server is C:\Program > Files\sdb\7500. > > > Establish a connection to the official node HOTEL_OFFICIAL: > dbmcli -n HOTEL_OFFICIAL > Generate the database instance HOTELDB: > db_create HOTELDB DBM,DBM DAVID,BLUE > ... > Set up the hot standby system: > db_offline > hss_enable node=HOTEL_OFFICIAL lib=LIBHSSCOPY > db_online > hss_addstandby PARMA login=ANNA,MAY path="C:\Program Files\sdb\7500" > db_standby PARMA > > Sorry for the inconvenience. > Best regards > Marina > > Marina Montag > MaxDB Team > SAP Labs Berlin > > > -----Original Message----- > From: Jan Suchanek [mailto:[EMAIL PROTECTED] > Sent: Donnerstag, 4. M�rz 2004 09:13 > To: [EMAIL PROTECTED] > Subject: Hot Standby with MAXDB > > > Hello, > > is it possible to use the hot standby feature with MaxDB (Version 7.5)? > I found quit confusing information... the the windows Database Manager > client has some dialogs to enable hot standby, but there is no > documentation for this feature and the feature list on the MaxDB web > site tell you that hot standby will come soon (in some of the next > versions). So what can I believe now? ;-) > > Greetings, Jan Suchanek > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* * System Engineer, Verzekeringen NV * * www.verzekeringen.be * * Oostkaai 23 B-2170 Merksem * * 03/6416673 - 0477/340942 * *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
