Source Address connection: http://bbs.chinaunix.net/thread-3650691-1-1.html
Ask:
There are currently 2 servers Trackerserver+storage and storage that need to migrate to 2 new server environments and migrate the data in Fastdfs.
And the points to be noted
For:
Upgrade the original system to v3.05 and then hang the new machine under the original cluster as the new storage server for the existing group
Fastdfs can automatically complete an existing file synchronization.
Reply 6# Guliny
Fastdfs the problem of the whole migration of cluster. If the new and old IP address one by one corresponds, and is the same, it is very simple, directly copy the data directory to the past.
IP is not the same, it will be more troublesome. If you use the V4 custom server ID feature, it is easier to directly tracker the IP and ID mapping file on the storage_ids.conf Modify it well.
If you use the IP address as the server identity, then you need to modify the data directory of tracker and storage several files, the old IP to adjust to the new IP. Note that there is one under the storage Data directory. The first hidden file also needs to be modified. In addition, you need to rename the sync location record filename with the suffix of Mark's IP address and port. The Cluster service will not start until all the files have been adjusted.
List of files that need to be adjusted on the tracker server: Data/storage_groups_new.dat Data/storage_servers_new.dat Data/storage_sync_timestamp.dat
List of files Storage server needs to adjust: Data/.data_init_flag Data/sync/${ip_addr}_${port}.mark: This type of file, you need to adjust the IP address in the file name. |