Alex wrote:
Alex wrote:
The Sequoia tutorial/docs detail how to use clone, backup, and
restore commands to create a new backend behind a controller
containing the same data as an existing backend.
My situation is that I have a controller, with a single database
behind it, and I'd like to introduce another controller to my
cluster, with its own single database behind it, and make the data on
the new one be a copy of the first controller's database. What's the
best procedure to go about this?
Ah, jsut noticed section 6.6 of the management guide PDF, it mentions
the 'transfer' command for sending backups to another controller...
Can anyone give me a hint about why I'm getting the following message
when I try to transfer a dump I've made to another controller?
myDB(admin) > transfer dump backend1Dump 192.168.0.126:1090
Transferring dump backend1Dump to controller 192.168.0.126:1090...
can not transfer dumps on non-distributed virtual database
thanks,
Alex
lex
thanks,
Alex
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
