12-26-2007
for ufsrestore you need a running system... ufsdump and ufsrestore ist not a good way for "bare metal restore". flash archive is! cause you are no expert listen to the advices given...
zfs with snapshots is nice for data volumes but (for the lack of zfs boot) not for the root volume!
for installing the dump on "bare metal" you need a boot server to via network and a whole lot of knowledge. for a flasharchive you just need the archive and a solaris dvd to boot from!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
Here is what I am trying to do.
We have an old Enterprise 250 which we want to phase out. So plan is to move everything running on the 250 to an unused Sun Fire V280R.
Here is what I decided to do:
1. Fresh Solaris 8 install on Sun 280R (disk0). Configure network and install... (1 Reply)
Discussion started by: mshafi
1 Replies
2. Solaris
Hi.... everyone could help me to understand how to do a backup of my servers .. operating systems is sun solaris 8 .
I have some question about ....
1) Is better backup phisical disk or partition ???
i sow the command is ufsdump 0cfu /expbck/bcksunver/c0t0d0s5 dev/dsk/c0t0d0s5 to... (4 Replies)
Discussion started by: tt155
4 Replies
3. AIX
I have several H80 machines, all with AIX 4.3.3. On these machines I have mksysb running for rootvg backups and savevg for non-rootvg backups.
I'm trying to get a list of files on the tapes, but I can't seem to do it with tar for the mksysb images. I keep getting the directory checksum errors?... (3 Replies)
Discussion started by: uXion
3 Replies
4. HP-UX
Hello!
i have a blank harddrive and a complete tape backup of the workstation.
the backup is made with F-Backup.
Now my question is:
how can i restore my workstation?
thanks for every idea!
paul tittel
hup-si (3 Replies)
Discussion started by: paultittel
3 Replies
5. Solaris
Hi men,
I'm testing for my backup&restore job with ZFS.
My server have two disks. I wanna do backup&restore job like ufsdump utility:
Disk0 is rpool(root zpool) and disk1 (backup zpool) will be stored full backup replicates. When rpool zpool have problem, i can "boot cdrom -s" and use my... (5 Replies)
Discussion started by: tien86
5 Replies
6. Emergency UNIX and Linux Support
Hi,
Currently I have 2 servers. 1 is already installed with RHEL4(withmyapplications) and the other one is still brand new.
My question is, is it possible to use DD command to backup the whole harddrive for the RHEL4 server and restore it to the new brand server so that I do not have to... (3 Replies)
Discussion started by: flekzout
3 Replies
7. AIX
Hi experts, i got a question.
i have a production server with two Volume Group(VG) which are rootvg and datavg. Both of these VGs are 256 PP SIZE.
On Disaster Recovery Server (DR server) contains two empty hardisks for restoring rootvg and datavg from production server. This two hardisks are... (7 Replies)
Discussion started by: polar
7 Replies
8. Red Hat
Hi,
I need to back up a RH file system (96G).
The files are oracle .dbf format some of which are 5G in size.
I know that tar has got a size restriction of 2G so I cannot use this.
Can anyone recommend an alternative way of backuping up this FS?
I have been looking at dump but this... (6 Replies)
Discussion started by: Duffs22
6 Replies
9. AIX
I run a backup sucessfully:
find . | backup -ivqf/dev/rmt0
I want to make sure I can restore, so I change to a test directory and try this:
restore -rvqf /dev/rmt0
However, we fail with this error:
New volume on /dev/rmt0:
Cluster size is 51200 bytes (100 blocks).
The volume number is... (3 Replies)
Discussion started by: landog
3 Replies
10. UNIX and Linux Applications
The problematic directory is the following:
/root/.cache/deja-dup
This directory grows until my "/" is full and then the restoring activity fails.
I already tried to create a symbolic link with origin another partition where I have more space. However during the restoring activity ... (4 Replies)
Discussion started by: puertas12
4 Replies
LEARN ABOUT OPENSOLARIS
native
native(5) Standards, Environments, and Macros native(5)
NAME
native - native branded zone
DESCRIPTION
The native brand uses the branded zones framework described in brands(5) to run zones installed with the same software as is installed in
the global zone. The system software must always be in sync with the global zone when using a native brand.
SUB-COMMANDS
The following native brand-specific subcommand options are supported in zoneadm(1M).
attach [-u] [-b patchid]...
For native zones, zoneadm checks package and patch levels on the machine to which the zone is to be attached. If the packages/patches
that the zone depends on from the global zone are different (have different revision numbers) from the dependent packages/patches on
the source machine, zoneadm reports these conflicts and does not perform the attach. If the destination system has only newer dependent
packages/patches (higher revision numbers) than those on the source system, you can use the -u option to update the attached zone to
match the -revision packages and patches that exist on the new system. With -u, as in the default behavior, zoneadm does not perform an
attach if outdated packages/patches are found on the target system.
For native zones, one or more -b options can be used to specify a patch ID for a patch installed in the zone. These patches will be
backed out before the zone is attached or, if -u was also specified, updated.
install [-a archive] | [-d path] [-p] [-s] [-u] [-v] [-b patchid]...
The native brand installer supports installing the zone from either the software already installed on the system or from an image of an
installed system running the same release. This can be a full flash archive (see flash_archive(4)) or a cpio(1) or pax(1) "xustar" ar-
chive. The cpio archive be compressed with gzip or bzip2. The image can also be a level 0 ufsdump(1M), a path to the top-level of a
system's root tree, or a pre-existing zone path.
With no options the zone is installed using same software as is running the global zone.
To install the zone from a system image either the -a or -d is required. Either the -u or -p option is also required in this case.
-a archive
The path to a flash_archive(4), cpio(1), or pax(1) "xustar" archive, or a level0 ufsdump(1M), of an installed system. cpio archives
may be compressed using gzip or bzip2.
-b patchid
One or more -b options can be used to specify a patch ID for a patch installed in the system image. These patches will be backed
out during the installation process.
-d path
The path to the root directory of an installed system. If path is a hyphen (-), the zonepath is presumed to be already populated
with the system image.
-p
Preserve the system configuration after installing the zone.
-s
Install silently.
-u
Run sys-unconfig(1M) on the zone after installing it.
-v
Verbose output from the install process.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWzoneu |
+-----------------------------+-----------------------------+
|Interface Stability |Uncommitted |
+-----------------------------+-----------------------------+
SEE ALSO
cpio(1), pax(1), zlogin(1), zonename(1), sys-unconfig(1M), ufsdump(1M), zoneadm(1M), zonecfg(1M), flash_archive(4), attributes(5),
brands(5), privileges(5), zones(5), lx_systrace(7D)
SunOS 5.11 13 Feb 2009 native(5)