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) we used a tiered layout for the storage: The main categories are:
Now the client is ready to take the dive into v3.0, and I'm trying to figure out how to put "archive" operation in effect. I have read the documentation (hell, I wrote most of it) and understand the settings, but what I cannot quite wrap my brain around is this: There is already all of this data sitting in all of these data partitions (we use a total of 34 separate partitions each for data & metadata) so how do I make the transition to separate archive partitions, since all that data is on the "slow" drives? Can I just reassign all of the current data partitions to archivedata partitions, define the new set of "Hot" data partitions on the Fast pool, and let 'er rip, or what? I promise, if you tell me, I'll write it up as real documentation. :-) Cheers, -nic -- Nic Bernstein nic@xxxxxxxxxxx Onlight, Inc. www.onlight.com 6525 W Bluemound Road, Suite 24 v. 414.272.4477 Milwaukee, Wisconsin 53213-4073 |
begin:vcard fn:Nic Bernstein n:Bernstein;Nic org:Onlight, Inc. adr:Suite 24;;6525 W Bluemound Road;Milwaukee;WI;53213-4073;USA email;internet:nic@xxxxxxxxxxx title:VP Operations tel;work:414-272-4477 x204 tel;cell:414-807-1734 url:http://www.onlight.com/ version:2.1 end:vcard
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus