On Fri, 10 Nov 2017, at 00:02, Nic Bernstein wrote:
> Bron,
> Thanks for the response. Your solution has pointed us towards the
> proper approach. We are using ZFS, so would be performing ZFS
> send/receive replication rather than "mv", to move the filesystems.
> Our typical approach for this
Bron,
Thanks for the response. Your solution has pointed us towards the
proper approach. We are using ZFS, so would be performing ZFS
send/receive replication rather than "mv", to move the filesystems. Our
typical approach for this sort of thing, then, would be:
* Create a filesystem snaps
Hi Nic,
Sorry I didn't get back to answering you on this the other day!
So... this one is kinda tricky, because everything is going to be on
"spool", but here's how I would do it.
Before:
/mnt/smalldisk/conf -> meta files only
/mnt/bigdisk/spool -> all email right now
Stage 1: splitting:
/mnt/
Thanks much to you both for your comments and suggestions. We had
already considered creating a temporary "staging" partition and
shuffling mailboxes around, as Michael discussed, but have the same
reservations about it. Since we're dealing with nearly 6TB of data,
most of it old, this schem
Hi,
Quoting Reinaldo Gil Lima de Carvalho :
I think that singleinstancestore (message hard links) will not survive when
moving from one partition to the other and storage total size will increase
significantly.
thanks for the hint. This was not a problem while migration to the
meta-data pa
I think that singleinstancestore (message hard links) will not survive when
moving from one partition to the other and storage total size will increase
significantly.
Reinaldo Gil Lima de Carvalho
2017-11-03 12:22 GMT-03:00 Michael Menge :
> Hi Nic,
>
> Quoting Nic Bernstein :
>
> Friends,
>> I
Hi Nic,
Quoting Nic Bernstein :
Friends,
I have a client with Cyrus 2.5.10 installed. Last year we migrated
their old 2.3.18 system to 2.5.10, with an eye towards an eventual
move to 3.0.x. Based on Bron's most excellent email of last year,
([Subject: Cyrus database and file usage data]
Friends,
I have a client with Cyrus 2.5.10 installed. Last year we migrated
their old 2.3.18 system to 2.5.10, with an eye towards an eventual move
to 3.0.x. Based on Bron's most excellent email of last year, ([Subject:
Cyrus database and file usage data] from Cyrus Devel of 8 January 2016)
