SAPDB standy - minimal delay

Hello,

I'm comparing a few scenarios for a new server configuration where data
availability is important.
A solution based on SAN is not possible because to expensive. Thus I
need to find a way to keep a less powerfull standby SAPDB server as
updated as possible

SAPDB documentation notes "You can use pipes to transport the data
backup. You can transport log backups with ftp, or copy them with an
exported file system (such as NFS or a shared file system)."

Question 1: pipe data backups: Does this mean piping the data file? How
does this work?
Question 2: export log backups with NFS. Suppose the main server goes
down somewhere in the middle of transfering the log backups, Will the
standby server start with these 'incomplete' log backups? Suppose it
does work, does this mean I can have a realtime synchronised backup
server or is there a catch somewhere?
Question 3: Using NDB (network block device) or some kind alike on the
partitions where the datafiles and logfiles are stored to keep the 2
servers synchronised. Is that sufficient to start the standby server?
Anybody experience with a configuration alike? 


An indirectly related question: is NAS an alternative? Will the database
suffer performance issues when the data- and log files are stored on a
NAS devices using NFS? I know it depends on the activity level, but does
anybody have a configuration like this one and what are your
experiences?


Thanks in advance,

Cheers,

Filip Sergeys



-- 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* 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/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx