Tag Info

New answers tagged

0

I would recommend you to check below mysql guide for adding server to existing replication http://dev.mysql.com/doc/refman/5.7/en/replication-howto-additionalslaves.html


3

A better option is to not disable the ISTG at all and let the KCC do it's thing within the confines that you define within Active Directory Sites and Services. Based on your comments above, you have no reason to disable the ISTG. This is what I would recommend. Disable the "Bridge All Site Links" option in Sites and Services. This will prevent two ...


1

XtreemFS seems to be the thing you want to achieve. You can probably do pretty much the same things with CephFS.


0

Try DRBD. This is not filesystem, but blockdevice. From http://lwn.net/Articles/329543/ Protocol A: Writes are considered to complete as soon as the local disk writes have completed, and the data packet has been placed in the send queue for the peers. In case of a node failure, data loss may occur because the data to be written to remote node disk ...


1

Gluster would solve the problem you have because it can hold the locks, propagate changes - delete the file on all other nodes, but it may add additional latency that can be a problem for a webserver. The next alternative is DRBD+OCFS2 or GFS, but that's probably more complex as with gluster you are using the underlying filesystem - it doesn't operate at the ...


1

GlusterFS is hard to deploy. For web data, file sync level like Unison is much easier to deploy and maintenance. DRBD is a perfect solution for keep data sync at block level. But you have to format them to special format like OCFS2 or something similar.


-1

You can set up 3 database servers and import start-up database into 3 servers, Please configure your insert and update application so that it writes on other servers (its mechanism is so easy) then you have mirrored exactly on other server...


1

This could easily turn into either opinion-based or "minimal understanding required" to be honest. Since this isn't a one size fits all thing. It will depend on your environment, options at your disposable, downtime allowed (which you stated), size of environment, IP network provisioning and overlap if any, and many other factors. However, given your ...


1

Depends on source of your data. If data you want to sync is generated somewhere else (developers workstation, etc) and only distributed to clients via those 3 servers, I would recommend to push the data to each of three servers via rsync, or some CI tool like Jenkins, keeping the files on local disks of each server. If the data is generated and served by ...


0

SQL Server Migration Assistant (SSMA) for MySQL lets you quickly convert MySQL database schemas to SQL Server or SQL Azure schemas, upload the resulting schemas into SQL Server or SQL Azure, and migrate data from MySQL to SQL Server or SQL Azure. You can use this small app and guide on msdn. Get started here : ...



Top 50 recent answers are included