It keeps the same name, that's why it must be unique.
Emmanuel
Anthony J. Biacco wrote:
For the unique naming..what happens if I used the "transfer backend"
command to transfer a backend from one controller to another? How would
it get named in the other controller?
-Tony
---------------------------
Manager, IT Operations
Format Dynamics, Inc.
303-573-1800x27
[EMAIL PROTECTED]
http://www.formatdynamics.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emmanuel Cecchet
Sent: Wednesday, April 16, 2008 4:40 PM
To: Sequoia general mailing list
Subject: Re: [Sequoia] clone config, naming question
Tony,
1. Am I correct in assuming that if I use the "clone" command in the
console to duplicate a backend config to a new backend, that that
config is active only in memory? So if I restarted the controller, the
new backend would then be missing, if I didn't go in the virtual
databases config xml file and put the new backend config in there?
Yes, this is correct but you can also save a controller configuration
through the console (just make sure you reload that config when you
restart the controller).
2. Am I correct in assuming from the docs that every backend must have
a unique name? e.g. in a 2-controller 2-backend setup, backend #1 must
have a different name in controller #2 than controller #1, e.g.
db-01-01 in controller #1 and db-01-02 in controller #2, even though
they're the same backend?
Yes, as backends can be transferred from one controller to another, it
is necessary to be able to identify them globally.
Best regards,
Emmanuel
--
Emmanuel Cecchet - Research scientist
EPFL - LABOS/DSLAB - IN.N 317
Phone: +41-21-693-7558
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
