Folks, My understanding is that there is a way to create a zfs "checkpoint" before doing any system upgrade or installing a new software. If there is a problem, one can simply rollback to the stable checkpoint. I am familiar with snapshots and clones. However, I am not clear on how to manage checkpoints. I would appreciate your help in how I can create, destroy and roll back to a checkpoint, and how I can list all the checkpoints. Thank you in advance for your help. Regards, Peter -- This message posted from opensolaris.org
On 08 November, 2010 - Peter Taps sent me these 0,7K bytes:> Folks, > > My understanding is that there is a way to create a zfs "checkpoint" > before doing any system upgrade or installing a new software. If > there is a problem, one can simply rollback to the stable checkpoint. > > I am familiar with snapshots and clones. However, I am not clear on > how to manage checkpoints. I would appreciate your help in how I can > create, destroy and roll back to a checkpoint, and how I can list all > the checkpoints.You probably refer to snapshots, as ZFS does not have checkpoints (and is pretty much the same as a snapshot). /Tomas -- Tomas ?gren, stric at acc.umu.se, http://www.acc.umu.se/~stric/ |- Student at Computing Science, University of Ume? `- Sysadmin at {cs,acc}.umu.se
Actually he likely means Boot Environments. On OpenSolaris or Solaris 11 you would use the pkg/ beadm commands. Previous Solaris used Live Upgrade. See the documentation for IPS. -- bdha On Nov 9, 2010, at 2:56, Tomas ?gren <stric at acc.umu.se> wrote:> On 08 November, 2010 - Peter Taps sent me these 0,7K bytes: > >> Folks, >> >> My understanding is that there is a way to create a zfs "checkpoint" >> before doing any system upgrade or installing a new software. If >> there is a problem, one can simply rollback to the stable checkpoint. >> >> I am familiar with snapshots and clones. However, I am not clear on >> how to manage checkpoints. I would appreciate your help in how I can >> create, destroy and roll back to a checkpoint, and how I can list all >> the checkpoints. > > You probably refer to snapshots, as ZFS does not have checkpoints (and > is pretty much the same as a snapshot). > > /Tomas > -- > Tomas ?gren, stric at acc.umu.se, http://www.acc.umu.se/~stric/ > |- Student at Computing Science, University of Ume? > `- Sysadmin at {cs,acc}.umu.se > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
On 11/ 9/10 01:47 AM, Peter Taps wrote:> My understanding is that there is a way to create a zfs "checkpoint" before doing any system upgrade or installing a new software. If there is a problem, one can simply rollback to the stable checkpoint. > > I am familiar with snapshots and clones. However, I am not clear on how to manage checkpoints. I would appreciate your help in how I can create, destroy and roll back to a checkpoint, and how I can list all the checkpoints. >Boot environments are managed with beadm http://dlc.sun.com/osol/docs/content/dev/snapupgrade/create.html
I think you maybe wanting the same kind of thing that NexentaStor does when it upgrade - takes snapshot and marks it a checkpoint in case the upgrade fails - right? I think you may have to snap then clone from that and use beadm thought it''s something you should play with... --- W. A. Khushil Dep - khushil.dep at gmail.com - 07905374843 Visit my blog at http://www.khushil.com/ On 9 November 2010 14:43, Oscar del Rio <delrio at mie.utoronto.ca> wrote:> On 11/ 9/10 01:47 AM, Peter Taps wrote: > >> My understanding is that there is a way to create a zfs "checkpoint" >> before doing any system upgrade or installing a new software. If there is a >> problem, one can simply rollback to the stable checkpoint. >> >> I am familiar with snapshots and clones. However, I am not clear on how to >> manage checkpoints. I would appreciate your help in how I can create, >> destroy and roll back to a checkpoint, and how I can list all the >> checkpoints. >> >> > Boot environments are managed with beadm > http://dlc.sun.com/osol/docs/content/dev/snapupgrade/create.html > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20101109/1c0f44f1/attachment.html>
Thank you all for your help. Looks like "beadm" is the utility I was looking for. When I run "beadm list," it gives me the complete list and indicates which one is currently active. It doesn''t tell me which one is the "default" boot. Can I assume that whatever is "active" is also the "default?" Regards, Peter -- This message posted from opensolaris.org
* Peter Taps (ptrtap at yahoo.com) wrote:> Thank you all for your help. Looks like "beadm" is the utility I was > looking for. > > When I run "beadm list," it gives me the complete list and indicates > which one is currently active. It doesn''t tell me which one is the > "default" boot. Can I assume that whatever is "active" is also the > "default?"As outlined in beadm(1M): beadm list [-a | -ds] [-H] [beName] Lists information about the existing boot environment named beName, or lists information for all boot environ- ments if beName is not provided. The Active field indi- cates whether the boot environment is active now, represented by N; active on reboot, represented by R; or SunOS 5.11 Last change: 21 Jul 2010 3 System Administration Commands beadm(1M) both, represented by NR. Cheers, -- Glenn
On Nov 9, 2010, at 11:24 AM, Peter Taps wrote:> Thank you all for your help. Looks like "beadm" is the utility I was looking for.On NexentaStor, the NMC command is "setup appliance checkpoint" :-) There is also a GUI form for managing the checkpoints. This works similar to the way beadm works, but is easier. -- richard