Cisco Cisco Prime Network Registrar 8.1 문제 해결 가이드
Chapter 4 Operations
Resynchronizing a Slave
• 17
The replication start coordinates of the log file, displayed in
MASTER_LOG_POS=
3.3.2 Copying the Production Executive Dump File to the Backup Executive
Before you execute the resync_slave.sh script, copy the Production Executive dump file that
was created when you executed the resync_master.sh script to the Backup Executive server.
To copy the MySQL database dump file from the Production Executive, follow these steps.
To copy the MySQL database dump file from the Production Executive, follow these steps.
1
Log into the Backup Executive server as incadmin user and change directory to
/opt/incontrol/etc/support.
>cd /opt/incontrol/etc/support
2
Execute the secure copy command, specifying the full pathname of the Production
Executive dump file.
> scp incadmin@<host_IP_address>:/opt/incontrol/etc/support/<dump_filename>.
For example:
>scp incadmin@192.168.196.45:/opt/incontrol/etc/support/dbforrepl.sql .
incadmin@192.168.196.45's password:
dbforrepl.sql
100% 391KB 391.2KB/s 00:00
3.3.3 Reloading the Dump File and Setting Coordinates
To reload the Production Executive dump file on the Backup Executive and set the log file
coordinates, execute the resync_slave.sh script. When completed, the script displays
instructions on the next steps you need to take to complete the resynchronization process.
resync_slave.sh accepts the following parameters:
resync_slave.sh accepts the following parameters:
Parameter
Required
Description
-d <dump_filename>
Yes
Defines the name of the MySQL database dump
file.
-h <host_IP_address>
Yes
Defines the IP address of the Active Master server.
-l <log_filename>
Yes
Defines the name of the MySQL database log file, as
defined in the
MASTER_LOG_FILE=
statement.
-s <log_coordinate>
Yes
Defines the starting point coordinate in the log file
where replication begins, as defined in
the
MASTER_LOG_POS=
statement.