[OpenIndiana-discuss] What is the recommended way to back up root pool?
What is the recommended approach to back up a zfs root pool? For other pools I use zfs send/receive and/or rsync-based methods. The zfs root pool is different since it contains multiple filesystems, with the filesystem for one one BE being mounted at a time: % zfs list -r -t filesystem rpool NAMEUSED AVAIL REFER MOUNTPOINT rpool 79.7G 377G50K /rpool rpool/ROOT 29.5G 377G31K legacy rpool/ROOT/openindiana 15.8M 377G 3.15G / rpool/ROOT/openindiana-1 38.9M 377G 5.97G / rpool/ROOT/openindiana-2 40.6M 377G 11.3G / rpool/ROOT/openindiana-2-backup-1 124K 377G 10.5G / rpool/ROOT/openindiana-3 48.4M 377G 13.2G / rpool/ROOT/openindiana-3-backup-176K 377G 11.4G / rpool/ROOT/openindiana-3-backup-245K 377G 11.5G / rpool/ROOT/openindiana-3-backup-3 123K 377G 11.9G / rpool/ROOT/openindiana-3-backup-444K 377G 12.1G / rpool/ROOT/openindiana-4 20.1M 377G 18.8G / rpool/ROOT/openindiana-4-backup-195K 377G 13.3G / rpool/ROOT/openindiana-4-backup-2 156K 377G 18.8G / rpool/ROOT/openindiana-5 17.5M 377G 18.9G / rpool/ROOT/openindiana-6 29.4G 377G 17.6G / rpool/export121M 377G32K /export rpool/export/home 121M 377G32K /export/home This means that there are multiple filesystems which would need to be backed up in order to save a replica of the pool. At the moment I am using rsync-based backup of only selected filesystems. It is not clear to me where configuration due to utilities like 'ipadm' and 'dladm' is stored, but I am pretty sure it is to files under the /etc directory. What is recommended/common practice for backing up the root pool? Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
for home or for office? for office, I don't back up root pool. it's considered disposible and reproducible via reinstall. (that plus config management) for home, you can zfs send it somewhere to a file if you want, or you can tar it up since that's probably easier to restore individual files after an oops. I do the latter. Then you could reinstall from golden image and restore the files you need. On Wed, Oct 28, 2015 at 7:24 PM, Bob Friesenhahn < bfrie...@simple.dallas.tx.us> wrote: > What is the recommended approach to back up a zfs root pool? > > For other pools I use zfs send/receive and/or rsync-based methods. > > The zfs root pool is different since it contains multiple filesystems, > with the filesystem for one one BE being mounted at a time: > > % zfs list -r -t filesystem rpool > NAMEUSED AVAIL REFER MOUNTPOINT > rpool 79.7G 377G50K /rpool > rpool/ROOT 29.5G 377G31K legacy > rpool/ROOT/openindiana 15.8M 377G 3.15G / > rpool/ROOT/openindiana-1 38.9M 377G 5.97G / > rpool/ROOT/openindiana-2 40.6M 377G 11.3G / > rpool/ROOT/openindiana-2-backup-1 124K 377G 10.5G / > rpool/ROOT/openindiana-3 48.4M 377G 13.2G / > rpool/ROOT/openindiana-3-backup-176K 377G 11.4G / > rpool/ROOT/openindiana-3-backup-245K 377G 11.5G / > rpool/ROOT/openindiana-3-backup-3 123K 377G 11.9G / > rpool/ROOT/openindiana-3-backup-444K 377G 12.1G / > rpool/ROOT/openindiana-4 20.1M 377G 18.8G / > rpool/ROOT/openindiana-4-backup-195K 377G 13.3G / > rpool/ROOT/openindiana-4-backup-2 156K 377G 18.8G / > rpool/ROOT/openindiana-5 17.5M 377G 18.9G / > rpool/ROOT/openindiana-6 29.4G 377G 17.6G / > rpool/export121M 377G32K /export > rpool/export/home 121M 377G32K /export/home > > This means that there are multiple filesystems which would need to be > backed up in order to save a replica of the pool. > > At the moment I am using rsync-based backup of only selected filesystems. > > It is not clear to me where configuration due to utilities like 'ipadm' > and 'dladm' is stored, but I am pretty sure it is to files under the /etc > directory. > > What is recommended/common practice for backing up the root pool? > > Bob > -- > Bob Friesenhahn > bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
At home, I do nothing for rpools. I dont even mirror them and I havent even written out a process for recovery. I assume I can just reinstall and re-import any custom xml files for smf that i have archived. for work, i have automation to rebuild rpools but i dont back them up. Here is one thought. Use snapshots on your rpool, synchronize one or more mirrors once per day on a rotation basis. once complete, split the mirror. I would nail the boot device in the LSI config using alt-b. this command sequence might be hidden depending on the version of firmware on your controller. make sure you are install the grub boot blocks too. I havent tested this and the one time i actually tried to split a mirror the system crashed. It might be worth exploring though. j. On 10/28/15 4:24 PM, Bob Friesenhahn wrote: What is the recommended approach to back up a zfs root pool? For other pools I use zfs send/receive and/or rsync-based methods. The zfs root pool is different since it contains multiple filesystems, with the filesystem for one one BE being mounted at a time: % zfs list -r -t filesystem rpool NAMEUSED AVAIL REFER MOUNTPOINT rpool 79.7G 377G50K /rpool rpool/ROOT 29.5G 377G31K legacy rpool/ROOT/openindiana 15.8M 377G 3.15G / rpool/ROOT/openindiana-1 38.9M 377G 5.97G / rpool/ROOT/openindiana-2 40.6M 377G 11.3G / rpool/ROOT/openindiana-2-backup-1 124K 377G 10.5G / rpool/ROOT/openindiana-3 48.4M 377G 13.2G / rpool/ROOT/openindiana-3-backup-176K 377G 11.4G / rpool/ROOT/openindiana-3-backup-245K 377G 11.5G / rpool/ROOT/openindiana-3-backup-3 123K 377G 11.9G / rpool/ROOT/openindiana-3-backup-444K 377G 12.1G / rpool/ROOT/openindiana-4 20.1M 377G 18.8G / rpool/ROOT/openindiana-4-backup-195K 377G 13.3G / rpool/ROOT/openindiana-4-backup-2 156K 377G 18.8G / rpool/ROOT/openindiana-5 17.5M 377G 18.9G / rpool/ROOT/openindiana-6 29.4G 377G 17.6G / rpool/export121M 377G32K /export rpool/export/home 121M 377G32K /export/home This means that there are multiple filesystems which would need to be backed up in order to save a replica of the pool. At the moment I am using rsync-based backup of only selected filesystems. It is not clear to me where configuration due to utilities like 'ipadm' and 'dladm' is stored, but I am pretty sure it is to files under the /etc directory. What is recommended/common practice for backing up the root pool? Bob ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
zfs split may also be undocumented depending on your distribution. j. On 10/28/15 5:08 PM, jason matthews wrote: At home, I do nothing for rpools. I dont even mirror them and I havent even written out a process for recovery. I assume I can just reinstall and re-import any custom xml files for smf that i have archived. for work, i have automation to rebuild rpools but i dont back them up. Here is one thought. Use snapshots on your rpool, synchronize one or more mirrors once per day on a rotation basis. once complete, split the mirror. I would nail the boot device in the LSI config using alt-b. this command sequence might be hidden depending on the version of firmware on your controller. make sure you are install the grub boot blocks too. I havent tested this and the one time i actually tried to split a mirror the system crashed. It might be worth exploring though. j. On 10/28/15 4:24 PM, Bob Friesenhahn wrote: What is the recommended approach to back up a zfs root pool? For other pools I use zfs send/receive and/or rsync-based methods. The zfs root pool is different since it contains multiple filesystems, with the filesystem for one one BE being mounted at a time: % zfs list -r -t filesystem rpool NAMEUSED AVAIL REFER MOUNTPOINT rpool 79.7G 377G50K /rpool rpool/ROOT 29.5G 377G31K legacy rpool/ROOT/openindiana 15.8M 377G 3.15G / rpool/ROOT/openindiana-1 38.9M 377G 5.97G / rpool/ROOT/openindiana-2 40.6M 377G 11.3G / rpool/ROOT/openindiana-2-backup-1 124K 377G 10.5G / rpool/ROOT/openindiana-3 48.4M 377G 13.2G / rpool/ROOT/openindiana-3-backup-176K 377G 11.4G / rpool/ROOT/openindiana-3-backup-245K 377G 11.5G / rpool/ROOT/openindiana-3-backup-3 123K 377G 11.9G / rpool/ROOT/openindiana-3-backup-444K 377G 12.1G / rpool/ROOT/openindiana-4 20.1M 377G 18.8G / rpool/ROOT/openindiana-4-backup-195K 377G 13.3G / rpool/ROOT/openindiana-4-backup-2 156K 377G 18.8G / rpool/ROOT/openindiana-5 17.5M 377G 18.9G / rpool/ROOT/openindiana-6 29.4G 377G 17.6G / rpool/export121M 377G32K /export rpool/export/home 121M 377G32K /export/home This means that there are multiple filesystems which would need to be backed up in order to save a replica of the pool. At the moment I am using rsync-based backup of only selected filesystems. It is not clear to me where configuration due to utilities like 'ipadm' and 'dladm' is stored, but I am pretty sure it is to files under the /etc directory. What is recommended/common practice for backing up the root pool? Bob ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
never mind, zfs split doesnt work on rpools. j. On 10/28/15 5:08 PM, jason matthews wrote: zfs split may also be undocumented depending on your distribution. j. On 10/28/15 5:08 PM, jason matthews wrote: At home, I do nothing for rpools. I dont even mirror them and I havent even written out a process for recovery. I assume I can just reinstall and re-import any custom xml files for smf that i have archived. for work, i have automation to rebuild rpools but i dont back them up. Here is one thought. Use snapshots on your rpool, synchronize one or more mirrors once per day on a rotation basis. once complete, split the mirror. I would nail the boot device in the LSI config using alt-b. this command sequence might be hidden depending on the version of firmware on your controller. make sure you are install the grub boot blocks too. I havent tested this and the one time i actually tried to split a mirror the system crashed. It might be worth exploring though. j. On 10/28/15 4:24 PM, Bob Friesenhahn wrote: What is the recommended approach to back up a zfs root pool? For other pools I use zfs send/receive and/or rsync-based methods. The zfs root pool is different since it contains multiple filesystems, with the filesystem for one one BE being mounted at a time: % zfs list -r -t filesystem rpool NAMEUSED AVAIL REFER MOUNTPOINT rpool 79.7G 377G50K /rpool rpool/ROOT 29.5G 377G31K legacy rpool/ROOT/openindiana 15.8M 377G 3.15G / rpool/ROOT/openindiana-1 38.9M 377G 5.97G / rpool/ROOT/openindiana-2 40.6M 377G 11.3G / rpool/ROOT/openindiana-2-backup-1 124K 377G 10.5G / rpool/ROOT/openindiana-3 48.4M 377G 13.2G / rpool/ROOT/openindiana-3-backup-176K 377G 11.4G / rpool/ROOT/openindiana-3-backup-245K 377G 11.5G / rpool/ROOT/openindiana-3-backup-3 123K 377G 11.9G / rpool/ROOT/openindiana-3-backup-444K 377G 12.1G / rpool/ROOT/openindiana-4 20.1M 377G 18.8G / rpool/ROOT/openindiana-4-backup-195K 377G 13.3G / rpool/ROOT/openindiana-4-backup-2 156K 377G 18.8G / rpool/ROOT/openindiana-5 17.5M 377G 18.9G / rpool/ROOT/openindiana-6 29.4G 377G 17.6G / rpool/export121M 377G32K /export rpool/export/home 121M 377G32K /export/home This means that there are multiple filesystems which would need to be backed up in order to save a replica of the pool. At the moment I am using rsync-based backup of only selected filesystems. It is not clear to me where configuration due to utilities like 'ipadm' and 'dladm' is stored, but I am pretty sure it is to files under the /etc directory. What is recommended/common practice for backing up the root pool? Bob ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On Wed, 28 Oct 2015, Doug Hughes wrote: for home or for office? for office, I don't back up root pool. it's considered disposible and reproducible via reinstall. (that plus config management) for home, you can zfs send it somewhere to a file if you want, or you can tar it up since that's probably easier to restore individual files after an oops. I do the latter. Then you could reinstall from golden image and restore the files you need. Assume that this is for a network server with advanced network configuration settings, ssh config, zones, etc. If was the same as a standard OS install without subsequent configuration, then backing up would not be so important. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On Wed, 28 Oct 2015, jason matthews wrote: never mind, zfs split doesnt work on rpools. 'zpool offline -t pool device', 'dd' device image, 'zpool online pool device' would work but it would be a stupid backup and extremely slow if the disk is large. If the other disk failed during this procedure, then the system would panic. Some resilvering would be required when the device is placed back on line. It is not clear to me where persistent configuration is stored. For example, 'ipadm' accesses a service via "/etc/svc/volatile/ipadm/ipmgmt_door". I was thinking that the configuration data is stored in /etc/svc/volatile/ipadm/aobjmap.conf but evidence suggests that this data is used when the ipmgmtd daemon is restarted. If one restores a system based on a partial file backup (e.g. /etc), what files need to be restored to restore the persistent network configuration? The manual page does not say. Zfs configuration is easy due to zfs import/export and 'zfs history'. However, one must still remember which pools should be imported (if they are remote). Doing a zfs send of the current boot environment (ignoring all others) still seems easiest. This still misses any filesystems outside of the boot environment. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
Go old school. Use dd to manually mirror two or more identical drives. Apply boot blocks. Nail the boot device in Lsi or bios. J. Sent from my iPhone > On Oct 28, 2015, at 5:59 PM, Bob Friesenhahn > wrote: > >> On Wed, 28 Oct 2015, Doug Hughes wrote: >> >> for home or for office? >> for office, I don't back up root pool. it's considered disposible and >> reproducible via reinstall. (that plus config management) >> for home, you can zfs send it somewhere to a file if you want, or you can >> tar it up since that's probably easier to restore individual files after an >> oops. I do the latter. Then you could reinstall from golden image and >> restore the files you need. > > Assume that this is for a network server with advanced network configuration > settings, ssh config, zones, etc. > > If was the same as a standard OS install without subsequent configuration, > then backing up would not be so important. > > Bob > -- > Bob Friesenhahn > bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
I'd put that in my config mgmt system (or installer) Sent from my android device. -Original Message- From: Bob Friesenhahn To: Discussion list for OpenIndiana Sent: Wed, 28 Oct 2015 21:00 Subject: Re: [OpenIndiana-discuss] What is the recommended way to back up root pool? On Wed, 28 Oct 2015, Doug Hughes wrote: > for home or for office? > for office, I don't back up root pool. it's considered disposible and > reproducible via reinstall. (that plus config management) > for home, you can zfs send it somewhere to a file if you want, or you can > tar it up since that's probably easier to restore individual files after an > oops. I do the latter. Then you could reinstall from golden image and > restore the files you need. Assume that this is for a network server with advanced network configuration settings, ssh config, zones, etc. If was the same as a standard OS install without subsequent configuration, then backing up would not be so important. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
Bob Friesenhahn wrote: What is the recommended approach to back up a zfs root pool? For other pools I use zfs send/receive and/or rsync-based methods. The zfs root pool is different since it contains multiple filesystems, with the filesystem for one one BE being mounted at a time: This means that there are multiple filesystems which would need to be backed up in order to save a replica of the pool. At the moment I am using rsync-based backup of only selected filesystems. If you don't intend reverting to older BEs (they are probably useless after a while anyway), remove them. I have always used zfs send/receive to back up the root pool. -- Ian. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On Wed, Oct 28, 2015 at 5:59 PM, Bob Friesenhahn < bfrie...@simple.dallas.tx.us> wrote: > Assume that this is for a network server with advanced network > configuration settings, ssh config, zones, etc. > > If was the same as a standard OS install without subsequent configuration, > then backing up would not be so important. In ye olden days, or on FreeBSD, I'd probably back up /etc (and, on BSD, /usr/local/etc) with rsync and assume that would capture the configuration. With SMF, which is opaque about its config file locations, I suspect that wouldn't do it. I think the service configuration settings are scattered around the filesystem, with some of it under /lib. -- D. Brodbeck System Administrator, Linguistics University of Washington GPG key fingerprint: 0DB7 4B50 8910 DBC5 B510 79C4 3970 2BC3 2078 D875 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On Fri, 6 Nov 2015, David Brodbeck wrote: In ye olden days, or on FreeBSD, I'd probably back up /etc (and, on BSD, /usr/local/etc) with rsync and assume that would capture the configuration. With SMF, which is opaque about its config file locations, I suspect that wouldn't do it. I think the service configuration settings are scattered around the filesystem, with some of it under /lib. Probably the subject line should have been "What is the recommended way to restore configuration from the root pool"? It seems easy enough to back up the root pool (via filesystem or zfs send) but restoring the desired parts on top of a freshly installed root pool (perhaps based on a fresher OS release) is not so clear. For example, how does one restore persistent networking configuration (links, bridges, IP interfaces)? Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On 11/ 6/15 03:27 PM, Bob Friesenhahn wrote: Probably the subject line should have been "What is the recommended way to restore configuration from the root pool"? It seems easy enough to back up the root pool (via filesystem or zfs send) but restoring the desired parts on top of a freshly installed root pool (perhaps based on a fresher OS release) is not so clear. For example, how does one restore persistent networking configuration (links, bridges, IP interfaces)? Bob I think it is a great topic of discussion. As much as I love working with Solaris and Solaris based distro's, its far from perfect. The last thing I ever thought I would do was to speak highly of AIX, the Unix with the equivalent of the Windows registry (ODM database), but AIX has a way to back up and restore an existing (configured) system to a new/blank disk. (Scope) creeping out further, can any of the *BSD's or Lunux distro's do a full system restore to blank disk? Jerry ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On Fri, Nov 6, 2015 at 3:39 PM, Jerry Kemp wrote: > (Scope) creeping out further, can any of the *BSD's or Lunux distro's do a > full system restore to blank disk? I've usually done it by booting from a LiveCD, and doing the restore from there. I think this is probably the ideal method. Another method is to do a minimal OS install in a small partition, then do the restore into a new root partition, and reboot into it. Finally, because of the way UNIX handles open files, you can frequently get away with restoring over top of the running OS in single-user mode, as long as it's a closely related version to what's on the backup. I've successfully done this with FreeBSD, on a hosted VM where I couldn't easily boot from an arbitrary image. -- D. Brodbeck System Administrator, Linguistics University of Washington GPG key fingerprint: 0DB7 4B50 8910 DBC5 B510 79C4 3970 2BC3 2078 D875 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
In regard to: Re: [OpenIndiana-discuss] What is the recommended way to back...: The last thing I ever thought I would do was to speak highly of AIX, the Unix with the equivalent of the Windows registry (ODM database), but AIX has a way to back up and restore an existing (configured) system to a new/blank disk. Same, but I totally agree that 'mksysb' is one of things where AIX has one up on the competition. And mksysb has existed for 20+ years... Mention "bootable tape" to a junior admin these days and watch the expression on their face... (Scope) creeping out further, can any of the *BSD's or Lunux distro's do a full system restore to blank disk? The commercial, enterprise backup solution my workplace uses for Windows & Linux ostensibly supports bare metal recovery (BMR), but I've vowed to never even attempt it. Just MHO, but automated installation (jumpstart, kickstart, etc.) + rigorous use of a configuration management system (puppet, ansible, chef, etc.) is the way to go for OS config. It's probably both faster and (almost certainly) safer to do that for OS config than to try recover the entire OS over the top of an install. We do back up the OS, for the one offs or the potential for stuff that someone configures outside of a configuration management system, but I would never use traditional OS backups for a BMR. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On Fri, Nov 6, 2015 at 4:05 PM, Tim Mooney wrote: > Just MHO, but automated installation (jumpstart, kickstart, etc.) + > rigorous use of a configuration management system (puppet, ansible, > chef, etc.) is the way to go for OS config. It's probably both faster > and (almost certainly) safer to do that for OS config than to try > recover the entire OS over the top of an install. > I agree -- it's how I do things at work -- but I have to admit I wouldn't set up and maintain a puppet server just for a home fileserver. ;) -- D. Brodbeck System Administrator, Linguistics University of Washington GPG key fingerprint: 0DB7 4B50 8910 DBC5 B510 79C4 3970 2BC3 2078 D875 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
In message , David Brodbeck writes: >set up and maintain a puppet server just for a home fileserver. ;) Any tarsnap success or fail stories on this M/L? I recently heard their plug on the BSD Now podcasts with Illumos' Brown mafia members and it seems geared toward home fileservers. John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
I hadn't heard of tarsnap before, but I've been using one of the other cloud-based backup services and have been pretty happy with the convenience. I actually have occasionally used it while traveling just as a way to retrieve files I needed off computers that were back home and inaccessible. The initial backup for a machine takes a while if you have a lot of data. Some services offer an option where you can mail in a hard disk to seed the backup and avoid doing a full backup via the wire. Data caps are also something to keep in mind; they're coming to a lot of us soon in the US, since monopoly cable carriers are starting to enforce them. On Sat, Nov 7, 2015 at 2:38 PM, John D Groenveld wrote: > In message < > cahhaouaf9yub2gugudy09eqtche6j5gqypsn57+gsspetvn...@mail.gmail.com> > , David Brodbeck writes: > >set up and maintain a puppet server just for a home fileserver. ;) > > Any tarsnap success or fail stories on this M/L? > > I recently heard their plug on the BSD Now podcasts with > Illumos' Brown mafia members and it seems geared toward > home fileservers. > > John > groenv...@acm.org > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > -- D. Brodbeck System Administrator, Linguistics University of Washington GPG key fingerprint: 0DB7 4B50 8910 DBC5 B510 79C4 3970 2BC3 2078 D875 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
In message , David Brodbeck writes: >I hadn't heard of tarsnap before, but I've been using one of the other >cloud-based backup services and have been pretty happy with the >convenience. I actually have occasionally used it while traveling just as I read some complaints when Code42 EOLd their OpenSolaris CrashPlan client and so figured tarsnap might be relevant here. >a way to retrieve files I needed off computers that were back home and >inaccessible. The OP might appreciate more details. >The initial backup for a machine takes a while if you have a lot of data. >Some services offer an option where you can mail in a hard disk to seed the >backup and avoid doing a full backup via the wire. Data caps are also >something to keep in mind; they're coming to a lot of us soon in the US, >since monopoly cable carriers are starting to enforce them. Fortunately my locality offers some competition, but incrementals are more efficient which is a win every way you look at it (so long as its restorable.) John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On Mon, Nov 9, 2015 at 11:59 AM, John D Groenveld wrote: > The OP might appreciate more details. > Eh, I didn't want to seem like I was shilling, especially shilling a service that was in direct competition with an OSS system you already mentioned. Anyway, based on earlier comments I'm pretty sure the OP isn't interested in, or in a position to, pay for a subscription service. > > >The initial backup for a machine takes a while if you have a lot of data. > >Some services offer an option where you can mail in a hard disk to seed > the > >backup and avoid doing a full backup via the wire. Data caps are also > >something to keep in mind; they're coming to a lot of us soon in the US, > >since monopoly cable carriers are starting to enforce them. > > Fortunately my locality offers some competition, but incrementals > are more efficient which is a win every way you look at it (so > long as its restorable.) > > John > groenv...@acm.org > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > -- D. Brodbeck System Administrator, Linguistics University of Washington GPG key fingerprint: 0DB7 4B50 8910 DBC5 B510 79C4 3970 2BC3 2078 D875 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On Mon, 9 Nov 2015, David Brodbeck wrote: Anyway, based on earlier comments I'm pretty sure the OP isn't interested in, or in a position to, pay for a subscription service. OP == "Original Poster"? If I am the OP, then my interest is in the best way to preserve and restore root pool configuration (and some user data) in case the OS needs to be installed with the same or a very similar OS from scratch. In this case it is not normally necessary or desirable to restore operating system binaries, but portable configuration (e.g. from an OpenSolaris or Illumos-based system) needs to be restored in a safe way. If the root pool is not restored as a full replica (e.g. from zfs send stream), then it is necessary to use a package manager to install former required packages and apply any previous local configuration. Are people who are backing up their root pools backing it up as a full replica image, or are they only capturing configuration data? If one was to use an off-site backup like 'tarsnap', how would it be used to restore a root pool? Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
In message , Bob Friesenhahn writes: >Are people who are backing up their root pools backing it up as a >full replica image, or are they only capturing configuration data? Something like Oracle's zonep2vchk -c would be useful for dumping your GZ's configs if you're not capturing that info some other way. http://docs.oracle.com/cd/E53394_01/html/E54752/gpohk.html#scrolltoc> John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On Mon, 9 Nov 2015, John D Groenveld wrote: Something like Oracle's zonep2vchk -c would be useful for dumping your GZ's configs if you're not capturing that info some other way. http://docs.oracle.com/cd/E53394_01/html/E54752/gpohk.html#scrolltoc> Interesting. It would be nice to have a tool which can show all of the added, deleted, and changed files (minus junk like log files) vs the OS footprint installed by the package manager. Sort of like 'zfs diff' but with knowledge of what the files are. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
On Mon, Nov 9, 2015 at 1:47 PM, Bob Friesenhahn < bfrie...@simple.dallas.tx.us> wrote: > On Mon, 9 Nov 2015, David Brodbeck wrote: > >> >> Anyway, based on earlier comments I'm pretty sure the OP isn't interested >> in, or in a position to, pay for a subscription service. >> > > OP == "Original Poster"? > > If I am the OP, then my interest is in the best way to preserve and > restore root pool configuration (and some user data) in case the OS needs > to be installed with the same or a very similar OS from scratch. In this > case it is not normally necessary or desirable to restore operating system > binaries, but portable configuration (e.g. from an OpenSolaris or > Illumos-based system) needs to be restored in a safe way. > Ah, sorry. I got two threads conflated in my head. Time to up my morning coffee intake, I guess! -- D. Brodbeck System Administrator, Linguistics University of Washington GPG key fingerprint: 0DB7 4B50 8910 DBC5 B510 79C4 3970 2BC3 2078 D875 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
In message , Bob Friesenhahn writes: >It seems easy enough to back up the root pool (via filesystem or zfs >send) but restoring the desired parts on top of a freshly installed >root pool (perhaps based on a fresher OS release) is not so clear. >For example, how does one restore persistent networking configuration >(links, bridges, IP interfaces)? The received snapshot of your BE retains that information so you shouldn't have many problem so long as its just rpool spindle failures. 1. Reinstall OS from installation media. 2. Boot 3. # zfs create rpool/restore 4. # zfs receive -vF -d rpool/restore < rpool-snapshot.zfs 5. # zfs rename rpool/restore/ROOT/mybe rpool/ROOT/mybe 6. zfs rename any other filesystems or vols you want to retain from your rpool-snapshot 7. munge /rpool/boot/grub/menu.lst with rpool/restore/boot/grub/menu.lst 8. # beadm activate mybe My WAG is things fail when NICs or other devices are missing on your restored hardware but I can't test right now to see how badly. John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
Bob Friesenhahn wrote: OP == "Original Poster"? If I am the OP, then my interest is in the best way to preserve and restore root pool configuration (and some user data) in case the OS needs to be installed with the same or a very similar OS from scratch. In this case it is not normally necessary or desirable to restore operating system binaries, but portable configuration (e.g. from an OpenSolaris or Illumos-based system) needs to be restored in a safe way. If the root pool is not restored as a full replica (e.g. from zfs send stream), then it is necessary to use a package manager to install former required packages and apply any previous local configuration. Are people who are backing up their root pools backing it up as a full replica image, or are they only capturing configuration data? If one was to use an off-site backup like 'tarsnap', how would it be used to restore a root pool? I use a two level backup/DR strategy. 1) Replicate the entire pool so a system can be rebuilt "as is" if something goes horribly wrong. 2) Make /etc a mercurial repository and push it to another host. This allows me to track file changes and quickly recover if I stuff something up. -- Ian. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
Ian Collins писал 11.11.2015 07:43: 2) Make /etc a mercurial repository and push it to another host. This allows me to track file changes and quickly recover if I stuff something up. Have you looked at fsvs? It also tries to preserve permissions. We have backup/fsvs in OI Hipster repository. I haven't used it actively on Solaris/illumos systems, but it works rather good on our Linux servers. --- System Administrator of Southern Federal University Computer Center ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What is the recommended way to back up root pool?
Alexander Pyhalov wrote: Ian Collins писал 11.11.2015 07:43: 2) Make /etc a mercurial repository and push it to another host. This allows me to track file changes and quickly recover if I stuff something up. Have you looked at fsvs? It also tries to preserve permissions. We have backup/fsvs in OI Hipster repository. I haven't used it actively on Solaris/illumos systems, but it works rather good on our Linux servers. I haven't, no. I prefer the distributed model used by mercurial or git to Subversion. -- Ian. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
