X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=115-188-33-81.jetstream.xtra.co.nz;
X-Received: from [10.0.0.168] (115-188-33-81.jetstream.xtra.co.nz [115.188.33.81])
by netwin.co.nz (SurgeMail 7.3f) with ESMTP (TLS) id 3964951-1391920
for <surgemail-list@netwin.co.nz>; Mon, 04 Dec 2017 11:19:11 +0000
X-Return-Path: surgemail-support
Subject: Re: [SurgeMail List] server hardware upgrade and migration question
To: surgemail-list@netwin.co.nz
References: <43A37C30-9CF0-4B38-B71D-9BC7E4A5EB78@wilkes.com>
From: surgemail-support
Message-ID: <c6dc1353-b364-f17d-f355-1064432b43c4@netwinsite.com>
Date: Tue, 5 Dec 2017 00:19:06 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <43A37C30-9CF0-4B38-B71D-9BC7E4A5EB78@wilkes.com>
Content-Language: en-US
X-Authenticated-User: surgemail-support
X-Rcpt-To: <surgemail-list@netwin.co.nz>
X-SpamDetect: : 0.000000
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=0 Stars=0 Good=0 Friend=2 Surbl=0 Catch=0 r=0 ip=115.188.33.81
X-IP-stats: Incoming Last 0, First 0, in=1, out=0, spam=0 ip=115.188.33.81
List-Unsubscribe: <mailto:surgemail-list-leave@netwin.co.nz?subject=unsubscribe>
X-Mailing-List: surgemail-list@netwin.co.nz
List-ID: <surgemail-list@netwin.co.nz>
Precedence: bulk
Reply-To: surgemail-list@netwin.co.nz
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Yes, should be good, do a resync and a resync_prune on the master
first to be sure the mirror is in sync.
ChrisP.
On 4/12/2017 7:42 p.m., John Wilkes
wrote:
I want to migrate my server to new hardware. If I copy the current server’s /usr/local/surgemail and /etc/surgemail.ini to the new hardware, and I copy /var/surgemail from my mirror to the new server hardware, will I have any problems?
The reason I want to do this is that the current server hardware is ancient and slow, and /var/surgemail is quite large. The mirror is running on new, faster hardware, and it will be much easier and faster to copy /var/surgemail from it instead of the current server.
I prefer to do the migration by copying files instead of turning the mirror into the server, installing a new mirror on new hardware, and doing a resync. But copying the server’s /var/surgemail will be slow and tedious, so I want to copy the mirror’s /var/surgemail to the new server instead.
If /var/surgemail is exactly the same on server and mirror, I think this migration method should work. Is there any reason that it won’t?
Thanks!
John
--
I'd really appreciate it if you could take a moment to
like us on FaceBook, thanks heaps! ChrisP.