From owner-freebsd-current@FreeBSD.ORG Tue Aug 12 17:49:13 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 361E837B401 for ; Tue, 12 Aug 2003 17:49:13 -0700 (PDT) Received: from papoose.quick.com (papoose.quick.com [199.120.187.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B09543F93 for ; Tue, 12 Aug 2003 17:49:12 -0700 (PDT) (envelope-from jq@quick.com) Received: from quick.com (lili.chezq.com [199.120.187.254]) by papoose.quick.com (8.12.9/8.12.9) with ESMTP id h7D0n8BB068456 for ; Tue, 12 Aug 2003 20:49:09 -0400 (EDT) (envelope-from jq@quick.com) Date: Tue, 12 Aug 2003 20:49:05 -0400 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: James Quick To: freebsd-current@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.552) Subject: Questions about stability of snapshots and vinum in 5.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2003 00:49:13 -0000 My goal is to have a box, with 2 drives, each of which is identically configured. Slice 1, and Slice 2, will be smallish FreeBSD partitions 4-8 GB each. 1 will be treated as a production environment. The other will be used for building and testing new environments. The bulk of the space will be used for data. Each pair of production and test slices will be periodically mirrored to it's twin to provide a measure of fault tolerance. The box currently has one of the two new large drives installed, and 3 smaller aging (and ailing) drives. I was hoping to use vinum for all the rest, as it would give me far more flexibility. Based on recent posts it sounds like I should wait on that, and will leave enough unconfigured space at the top so that I can migrate from manually created partitions to vinum once I feel that geom+vinum have stabilized a bit. I am seeking feedback on the status of vinum, and whether the following plan makes sense as an upgrade plan for a host with a light load but whose downtime windows are short. I am curious if my planned use of snapshots is risky in 5.1, I have used them in under a much older 5.0 version with no problems, but a lot has changed. I have not migrated my data onto the first of these drive since I need to configure one, migrate from 2 old drives, then put in the second new drive before continuing. I also need to do as much of this work as possible without interruption. My plan is, to build out the first set of partitions, then create a queue of jobs for each disk controller: 1. create a snapshot on the destination drive. 2. use dump+restore or tar at a decent nice value, to copy from source to the new dest. 3. Then when I can shutdown production, and all the old data has completed a full (though aged) copy, get rid of the old mirrors. Use rsync to copy the changes to the destination. 4. Create snapshots on the new system volumes, boot into the new environment for testing. 5. If that goes well, swap out one of the old drives for the second new one, build out the OS copies, and copies of critical user data. 6. I can then get rid of, or fool around with the old disks at my leisure.