hello Judah
Am 22.06.2020 um 05:00 schrieb Judah Richardson:
On Sat, Jun 20, 2020 at 2:29 AM Guenther Alka <a...@hfg-gmuend.de> wrote:
Another option is to backup the current BE
How would I determine which one is current?
to the datapool via zfs send.
In napp-it, check menu Snapshots > Bootenvironment, at console beadm list
Look in the list for N=curreNt, R=Reboot. Normally you find one with NR
that is current and the one for next reboot.
If you create a napp-it replication job, it automatically shows only the
current BE as filesystem source together with all other regular filesystems.
This can be done continously via incremental send for ongoing backups.
If the system disk fails (or you want to replace), add a new disk,
install a default OS, import the datapool and restore the BE
What exactly are the commands for this?
via zfs
Use napp-it menu Jobs > Replicate > create then start the job. On first
run it replicates the whole filesystem, on next run only modified
datablock (incremental zfs send)
On console, create a snapshot of the current BE filesystem and use it
for a zfs send
Look at https://docs.oracle.com/cd/E36784_01/html/E36835/gbinw.html or
other basic ZFS manuals
send.
What would a command for this look like?
Could folks kindly be more specific and detailed in their replies, please?
A lot of these are just really generic and I'm not really sure how to
proceed based on them.
Then activate this BE and reboot to have the exact former OS
After you restored the BE filesystem via another replication job or zfs
send on the new installation use napp-it menu Snaps > Bootenvironment or
"beadm activate bename" to set a BE active for next reboot. In beadm
list you show the current marked with N and the activated one marked
with R (will become current after a Reboot).
installation restored.
Gea
@napp-it.org
_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
