Hi Santosh I'll answer your questions below:
> 1. I was reading the documentation for distributed database on multiple > servers here > <http://www.orientechnologies.com/docs/last/orientdb.wiki/Distributed-Configuration.html>. > I see that we need to configure several files like > orientdb-dserver-config.xml, default-distributed-db-config.json and > hazelcast.xml. Are these changes to be made on one node or all the nodes ? > How do we operate the cluster ? Start one node at a time or is there a > script to start all the nodes in a cluster ? > distributed configuration is managed as follows: - when first node starts it reads default-distributed-db-config.json from single database directory or from /config; this will become the "official" network configuration for all the cluster - when other nodes start they ask for the configuration to the cluster network (default-distributed-db-config.json of the new node will be ignored) - orientdb-dserver-config.xml and hazelcast.xml are managed at single node level, so their content is not shared between nodes in the network - nodes can be started one at a time, but writing a simple script that starts multiple nodes is a trivial task If you are using Community Edition and you want to change the network (replication, sharding) configuration you have to restart all the nodes. With Enterprise Edition (see here http://www.orientechnologies.com/orientdb-enterprise/ ) you have a workbench that lets you configure replication and other parameters from a web console, without having to restart database nodes. > 2. For non-blocking backups, can we use san snapshot instead of LVM ? Can > we create a custom script to take an online non-blocking backup ? > > current backup.sh script uses LVM only, but you can edit the script and use SAN snapshot instead. The basic backup mechanism is straightforward: - freeze database - copy physical files (with LVM or Snapshot it will be a fast operation, while a physical copy can take a lot more time) - release database Luigi 2014-10-29 10:50 GMT+01:00 Santosh M <[email protected]>: > Hi, > > I am working on testing the operational suitability of OrientDB for one of > our major applications. I have been reading the documentation for a couple > of days to understand OrientDBs features and limitations. I have a couple > of question that I would like to clarify. I would highly appreciate it if > you could help me out : > > 1. I was reading the documentation for distributed database on multiple > servers here > <http://www.orientechnologies.com/docs/last/orientdb.wiki/Distributed-Configuration.html>. > I see that we need to configure several files like > orientdb-dserver-config.xml, default-distributed-db-config.json and > hazelcast.xml. Are these changes to be made on one node or all the nodes ? > How do we operate the cluster ? Start one node at a time or is there a > script to start all the nodes in a cluster ? > > 2. For non-blocking backups, can we use san snapshot instead of LVM ? Can > we create a custom script to take an online non-blocking backup ? > > Thanks in advance for your help. > > Regards, > Santosh Mathew > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
