The tar command is not really a backup solution in the same way
ufsdump is. tar makes a copy of all of the files. ufsdump looks
at which files are modified and only copies those files when you do an
incremental dump. Both commands could have issues when you are
copying data from an active file system.
Tar will copy everything under the specified directory unless you
manually exclude something. ufsdump has the built-in ability to skip
files that have not changed since the last incremental dump.
With regard to question 1, restoring depends on the state
of the system as a whole and how it got to this state.
Assuming you have a tar file of the zonepath, you can untar
that to recreate the zonepath. You also need to get the zone
configuration into the right state. If that is gone, you'll need a
backup of more than just the zonepath. You'll need the zone
configuration information. You have to get the zone created
and into the installed state. You can do that in Solaris Express
using the 'attach -F' option. (This command will be available in the
upcoming S10 update release as well.) But, if the tar file is out of
sync with the global zone, the zone might not boot or run correcty.
You really need a backup of the whole system.
With regard to using the tar command on the non-global zone to restore
beginning from /, this probably wouldn't work. If you have to restore
because the zone data is gone for some reason, is the zone in the
configured or installed state? You can't log in to the zone until it is
running. Being in a running zone and overwriting all of the files could
cause various sorts of trouble. You also have the same issues for the
tar file being in sync with the global zone. And, you have to be sure
nothing from any inherited pkg dirs is in the tar file.
This message posted from opensolaris.org
zones-discuss mailing list