Versions Compared

Old Version 20

changes.mady.by.user Paul Ruvin

Saved on

compared with

New Version Current

changes.mady.by.user Paul Ruvin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

If there is a request to move DualShield Replication cluster to a new set of servers, the best approach would be to Clone just one dualshield/mysql node server in the cluster using the instructions as written here...

How to move DualShield to a new machine with the same Windows OS System Type

Then create a new replication cluster using the DualShield Assistant tool to clone from the new server and set up of the current environment and then restore to the new environment and from that create a new replication cluster. 

However, this may not be 100% straightforward as there are a couple of factors to consider, such as the size of the audit log table , eg

...

Expand
titleRemove Superflous Bin Log Files...

Binary log files (often referred to as binlogs) in MySQL are a record of all changes made to the database. They are essential for replication, backups, and recovery purposes. Binlogs track events such as:

  • Data modifications (e.g., INSERT, UPDATE, DELETE statements)
  • Table and database schema changes (e.g., CREATE, ALTER statements)

MySQL uses binlogs to propagate changes from a master database to one or more slave databases in a replication setup. The slaves read and apply the binlogs from the master to stay synchronized.

Over time the the amount of bin log files increase and therefore so does the size of the file they are stored in.  This will take up hard drive space plus, this will significantly slow the process if you are cloning the system as the more bin log files there are, the more that have to be copied during the cloning process.

Therefore there is some house keeping that needs to be done to ensure the older bin log files get deleted.


Expand
titleModify the das.ini file to housekeep automatically.......
  • expire_logs_days
    • You can control how long binary logs are kept by setting the expire_logs_days parameter in the MySQL configuration file
    • To do this go to  C:\Program Files\Deepnet DualShield\mysql
    • Edit the das.ini file in elevated Notepad or Notepad++
    • Add an entry under [mysqld] for example expire_logs_days = 30

    • This will ensure that logs over 30 days old will be deleted.  You can set a different amount of days, but we recommend at least 30 to ensure no loss of data.
    • Remeber to Save the das.ini file
    • Restart the MySQL(Dual) service

Expand
titleUse a MySQL query to manually purge binlogs...
    •  Log into MySQL Console in command prompt (refer to Login to MySql console)
    • Use the following query... show binary logs;

    • Use the following query... PURGE BINARY LOGS BEFORE NOW() - INTERVAL 30 DAY;

    • Logs over 30 days old will be deleted right away.  You can set a different amount of days, but we recommend at least 30 to ensure no loss of data.
    • Use the following query... show binary logs;

    • You can see that the number of bin log files has been greatly reduced. * 
    • *Please note the screenshots were taken from a test server with a low amount of bin log files to start with so in this example it was reduced to 7 days, but most likely you will see more bin log files if reduced to 30 days as recommended.





Begin the Initial Clone

Please do the following to move a  DualShield Server from the current VM to a new one.

Expand
titleClone One Machine from the Current Environment...
Include Page
How to move DualShield to a new machine with the same Windows OS System Type
How to move DualShield to a new machine with the same Windows OS System Type
Clone One Machine from the Current Environment


Prepare to Create a New Replication Cluster

Before you begin the process the master and slave configurations from the former cluster must be removed,

1) Stop the DualShied Server service on the new machine,


Image Added


2) Open a command prompt and change directory to C:\Program Files\Deepnet DualShield\mysql\bin

Log into MySQL console , and stop the slave service:

Code Block
languagesql
themeEmacs
mysql -u root -p

(Enter your password at prompt)

mysql> stop slave;

3)  Reset master and slave on both servers.  This will clear the replication configuration and status information from the previous cluster.

Code Block
themeEmacs
mysql> reset master; 
mysql> reset slave;

4) Stop the MySQL(Dual) Service

Image Added

5) Launch Notepad in Admin mode and open the das.ini file in C:\Program Files\Deepnet DualShield\mysql

6) Delete all existing replication server configuration details from the das.ini file.

Image Added

7) Download DualShield Assistant from here:  DualShield Assistant v2.5 

8) Install DualShield Assistant on Source and Target machines (In other words the new machine running DualShield and the other machines In your new environment you wish DualShield Server to be deployed to)


Create New Replication Cluster using DualShield Assistant

1) Follow Cloning DualShield to clone DualShield and MySQL server and deploy to another new hosting server 

2) Once the clone is complete follow Setting up Replication to setup replication between the two servers.

3) If you wish to add additional servers please follow steps 1 and 2 again and repeat until you have replication set up on all the servers you need.