New answers tagged replication
Turns out the solution was simply to lower the SCSI ID for the assigned DR LUN from 255 to 254.
It looks like you are running into the issue described in this KB Article: FIX: A column that uses the DATETIME data type does not replicate to an Oracle subscriber by using a transactional replication in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012 Apply the appropriate Cumulative Update or Service Pack and see if that alleviates your ...
As Sandor said, this cannot be done with standard MySQL replication. It can be done if you use a third-party / external replication mechanism. A few products that I'm aware of: Continuent Tungsten Replicator SymmetricDS Both are open source and freely available. Another option would be to migrate to a MySQL cluster. Some options: MySQL Carrier ...
No. That would require A to be slave to both B and C, which is not possible. A-›B->C->A not recommended either.
The mechanism for controlling replication of passwords to a Read-Only Domain Controller (RoDC) is through Password Replication Policy (PRP). Passwords are the only part of the Domain partition of the Active Directory (AD) database that is selectively replicated to RoDC's. All the rest of the objects and attributes will be replicated. PRP is based on ...
I will answer the question, but you probably won't like how broad the answers are. There have been books written about what you're asking. No one is going to give you a step-by-step. First, regarding the DHCP, I was able to build a simple one on a VM. But, I need to have multiple subnets, each in a different VLAN (different departments of the company). ...
this might help you: dd if=/dev/sda of=/dev/sdb dd command can copy disk in raw format. It will copy partition table and bootloader and all partitions within this disk. if=/dev/sda : Input disk (source) of=/dev/sdb : Output disk (destination)
You can try to create md device in RAID1 mode where the read operations are issued to the faster device preferably mdadm --create --verbose /dev/md0 --level=mirror --raid-devices=2 --write-mostly /dev/sdb1 /dev/sdc1 where the device /dev/sdb is slower for reading (e.g. SATA drive) while the /dev/sdc is performing better (e.g. SSD drive). The ...
What you are looking for is called bcache: http://bcache.evilpiepirate.org/ It writes and reads from the faster device, while periodically writing to the slower one
Once you have your both servers synced, with replicated paused, use : PURGE MASTER LOGS BEFORE now() on both server. This will reset the binary log on both servers (and remove the old files). Make sure to check the file name and position with : SHOW MASTER STATUS Then, you'll need to reset the position with (on both servers) : CHANGE MASTER TO ...
Top 50 recent answers are included