mnesia

I created a Mnesia database / Schema on machine1. The node was named mypl@machine1. I then moved all files to machine2, because machine1 broke down. Everything runs fine as long as the code is running with the name "mypl@machine1". Obviously this is somewhat confugsing, because it is now running on machine2. If I start Erlang with the node name "mypl@machine2" the Mnesia Database appears being empty. How do I rename the node in a Mnesia Database from machine1 to machine2? archaelus I don't think this can be done online on a single node(anyone?), but it is possible to do via a backup/restore in

I'm an erlang and mnesia newbie.. How do I add a new disc_only_copies node to an mnesia database that already has a schema? Thanks archaelus Start your new node ( b@node ) erl -sname b -mnesia dir '"/path/to/storage"' -s mnesia . This starts a new ram_copies node called b@node . On your original node ( a@node ), at the erlang prompt execute mnesia:change_config(extra_db_nodes, ['b@node']). This will cause the original node to connect b to the mnesia cluster. At this point, b@node has joined the cluster but only has a copy of the schema. To make new the node b@node capable of storing disc

Some places state 2GB period. Some places state it depends up the number of nodes. Quite large if your question is "what's the storage capacity of an mnesia database made up of a huge number of disc_only_copies tables" - you're largely limited by available disk space. An easier question to answer is what's the maximum capacity of a single mnesia table of different types. ram_copies tables are limited by available memory. disc_copies tables are limited by their dets backend ( Hakan Mattsson on Mnesia ) - this limit is 4Gb of data at the moment. So the simple answer is that simple disc_copies