08-01-2005
tnk!!!
I'am sorry but i'am not expert could you help me plse ?????
i must back this system it is correct the following ???
command df : result
nifsunwrk:/export/home/netdemo> df
/ (/dev/dsk/c1t0d0s0 ): 222268 blocks 378150 files
/proc (/proc ): 0 blocks 29949 files
/dev/fd (fd ): 0 blocks 0 files
/etc/mnttab (mnttab ): 0 blocks 0 files
/var/run (swap ):13709216 blocks 888212 files
/tmp (swap ):13709216 blocks 888212 files
/nif (/dev/md/dsk/d3 ):18467950 blocks 2920674 files
/opt (/dev/dsk/c1t0d0s4 ): 4666888 blocks 559042 files
/usr/local (/dev/md/dsk/d0 ): 5008048 blocks 604001 files
/export/home (/dev/md/dsk/d1 ): 3173910 blocks 636026 files
/export/home/netdemo(/dev/md/dsk/d6 ):36032940 blocks 4210866 files
/usr/local/repository(/dev/md/dsk/d2 ): 1079510 blocks 2177913 files
/nica/nif/data/arclogs(/dev/md/dsk/d5 ): 8883238 blocks 640643 files
/nica/nif/nifw/debug(/dev/md/dsk/d4 ):10304804 blocks 641998 files
/export/home/netdemo/source(nifxwrk:/u/netdemo): 281032 blocks 172973 files
/export/home/netdemo/aixver(nifxver:/home/neticon/last): 1067040 blocks 822287 files
/export/home/netdemo/aixv55(nifxver:/home/neticon/v55/last): 417824 blocks 821554 files
to backup the entire system i lunch the command :
ufsdump 0cfu /expbck/bcksunver/c1t0d0s0 /dev/rdsk/c0t0d0s0
ufsdump 0cfu /expbck/bcksunver/d3 /dev/rdsk/d3
ufsdump 0cfu /expbck/bcksunver/c1t0d0s4 /dev/rdsk/c1t0d0s4
ufsdump 0cfu /expbck/bcksunver/d0 /dev/rdsk/d0
ufsdump 0cfu /expbck/bcksunver/d1 /dev/rdsk/d1
ufsdump 0cfu /expbck/bcksunver/d6 /dev/rdsk/d6
ufsdump 0cfu /expbck/bcksunver/d2 /dev/rdsk/d2
ufsdump 0cfu /expbck/bcksunver/d5 /dev/rdsk/d5
ufsdump 0cfu /expbck/bcksunver/d4 /dev/rdsk/d4
is correct ??? i'am sure that a have the complete system backup ???
if my system crash i have an a valid backup to restore the environment ???
tnk.....
Sorry for my bad english :-(((((
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I backed up a unix database using
"tar -cvf /dev/rmt1 -N 800 /*"
Normally I would restore this using
"tar -xvf /dev/rmt1 -N 800"
This is reporting an error about
"not enough memory"
I have done a new test backup and restore using the same commands and they work.
ANY IDEAS ? (2 Replies)
Discussion started by: Ross.Goodman
2 Replies
2. 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
3. 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
4. AIX
system is not booting ... i want to restore from mksysb backup. (2 Replies)
Discussion started by: AIXlearner
2 Replies
5. Shell Programming and Scripting
hi people i am in need of some assistance here hoping to star a linux course in january to wanted to get some experiance before starting so got a hold of some old assessments from a mate at college so just working through them in my spare time for the past 8 weeks or so and this is the final ? that... (2 Replies)
Discussion started by: boabbyrab
2 Replies
6. Shell Programming and Scripting
Hello everybody,
i am trying to make a script in UNIX to backup some compressed files to a tape drive. The thing is that i cannot use cpio command because some of these files are greater than 2GB. so i think the only solution left is backup command.
to restore the files i should use the... (6 Replies)
Discussion started by: omonoiatis9
6 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. Solaris
hi,
my requirement goes something like this:
In current setup, we have SPARC server running Solaris10 5/08. Out of 3 HDD available, 2 HDD (other than root) were zpool-ed and 3 zones were created.
Now, we have bought a new server with similar H/W config and planning to move the zones... (1 Reply)
Discussion started by: EmbedUX
1 Replies
9. 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
10. AIX
I have some old directories and files that I which to archive off. I have created archive using -p option with /usr/sbin/backup to a file. If I then do a du -g on the original directory and the archive differ as I'd expect due to using the p flag to compress the files < 2gb as part of the backup.
... (1 Reply)
Discussion started by: gefa
1 Replies
i2o_bs(7D) Devices i2o_bs(7D)
NAME
i2o_bs - Block Storage OSM for I2O
SYNOPSIS
disk@local target id#:a through u
disk@local target id#:a through u raw
DESCRIPTION
The I2O Block Storage OSM abstraction (BSA, which also is referred to as block storage class) layer is the primary interface that Solaris
operating environments use to access block storage devices. A block storage device provides random access to a permanent storage medium.
The i2o_bs device driver uses I2O Block Storage class messages to control the block device; and provides the same functionality (ioctls,
for example) that is present in the Solaris device driver like 'cmdk, dadk' on x86 for disk. The maximum size disk supported by i2o_bs is
the same as what is available on x86.
The i2o_bs is currently implemented version 1.5 of Intelligent IO specification.
The block files access the disk using the system's normal buffering mechanism and are read and written without regard to physical disk
records. There is also a "raw" interface that provides for direct transmission between the disk and the user's read or write buffer. A
single read or write call usually results in one I/O operation; raw I/O is therefore considerably more efficient when many bytes are
transmitted. The names of the block files are found in /dev/dsk; the names of the raw files are found in /dev/rdsk.
I2O associates each block storage device with a unique ID called a local target id that is assigned by I2O hardware. This information can
be acquired by the block storage OSM through I2O Block Storage class messages. For Block Storage OSM, nodes are created in
/devices/pci#/pci# which include the local target ID as one component of device name that the node refers to. However the /dev names and
the names in /dev/dsk and /dev/rdsk do not encode the local target id in any part of the name.
For example, you might have the following:
/devices/ /dev/dsk name
---------------------------------------------------------------
/devices/pci@0,0/pci101e,0@10,1/disk@10:a /dev/dsk/c1d0s0
I/O requests to the disk must have an offset and transfer length that is a multiple of 512 bytes or the driver returns an EINVAL error.
Slice 0 is normally used for the root file system on a disk, slice 1 is used as a paging area (for example, swap), and slice 2 for backing
up the entire fdisk partition for Solaris software. Other slices may be used for usr file systems or system reserved area.
Fdisk partition 0 is to access the entire disk and is generally used by the fdisk(1M) program.
FILES
/dev/dsk/cndn[s|p]n block device
/dev/rdsk/cndn[s|p]n raw device
where:
cn controller n
dn instance number
sn UNIX system slice n (0-15)
pn fdisk partition(0)
/kernel/drv/i2o_bs i2o_bs driver
/kernel/drv/i2o_bs.conf Configuration file
ATTRIBUTES
See attributes(5)
for descriptions of the following attributes:
+-----------------------------+-----------------------------+
|ATTRIBUTE TYPE |ATTRIBUTE VALUE
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
SEE ALSO
fdisk(1M), format(1M)mount(1M),lseek(2), read(2), write(2), readdir(3C), vfstab(4), acct.h(3HEAD), attributes(5), dkio(7I)
SunOS 5.10 21 Jul 1998 i2o_bs(7D)