on 2009 Nov 16 4:39 PM
Can I use High Availability of SQL Anywhere, with a single copy of db files, shared between server on a NAS?
I need something like this to prevent hard failures with on downtime of my site.
Request clarification before answering.
When the .db
file is already open by a server process, attempting to start another with the same database file gives the following error:
A database server with that name has already started
Even if you set the server name to something different you then get:
Resource temporarily unavailable
since the file is locked by the first server process.
If you're looking for a fail-over solution, you might want to take a look at database mirroring.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ben, maybe Veritas Cluster Server does what I'm thinking... Please, look at this: http://dcx.sybase.com/index.html#1101en/dbadmin_en11/da-highavailability-s-3835111.html
@Zote: The "mirroring mode" you choose determines how aggressively SQL Anywhere will behave during the commit: guarantee that the commit is performed on the mirror before responding to the client, or don't bother waiting for an acknowledgment, or [something even sloppier]. I've never met anyone who's used anything other than Door Number One, called "synchronous". See "Choosing a database mirroring mode" in the Help.
User | Count |
---|---|
74 | |
30 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.