Date: Wed, 29 Oct 2014 13:13:17 -0600 From: "James R. Van Artsdalen" <james-freebsd-fs2@jrv.org> To: Johannes Totz <johannes@jo-t.de> Cc: freebsd-fs@freebsd.org Subject: Re: Snapshots and what not to snapshot Message-ID: <54513C4D.4010203@jrv.org> In-Reply-To: <m2raeh$9ek$2@ger.gmane.org> References: <alpine.BSF.2.00.1410120128570.6601@woozle.rinet.ru> <m2raeh$9ek$2@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/29/2014 12:08 PM, Johannes Totz wrote: > On 11/10/2014 22:38, Dmitry Morozovsky wrote: >> you have some tree of ZFS file systems, like >> >> pool/path/r >> pool/path/jails >> pool/path/jails/j1 >> pool/path/jails/j1/obj >> snapshots and ZFS replication is done against the ZFS namespace, not the unix namespace. Organize your filesystems in the ZFS tree based on how you want to replicate/snapshot them, then use the ZFS mountpoint property to put them in the unix namespace where you want them to appear. For example the basic approach I use for client systems is a ZFS namespace like POOL/UNIX for FreeBSD, POOL/BUSINESS for shared company data, POOL/BACKUP for client system backup blobs, POOL/REPLICANT for the replication workspace to use in keeping hot-spare servers updated, etc. Note that the root of the ZFS tree is empty, and that the root of the unix tree is elsewhere. I often keep more than one bootable unix system root in a pool (for maintenance). PS. Don't forget the zpool bootfs property.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54513C4D.4010203>