04-14-2005
Sounds like you did a sequential ufsdump - which is a lot faster than an interactive ufsrestore (Where the tape heads are jumping around more based on yor selection criteria (e.g add/extract)). During an Solaris interactive restore, you generally just select the file(s) you require restoring from the filesystem (e.g a config file like /etc/hosts), although you can just select (add) everything and carry on with the restore. (if you have selected a ufsrestore ivf, the verbose option will also slow things down)
For a simple clean backup, I usually take a complete UFS level 0 dump; something like this ...
to dump ...
mt -f /dev/rmt/0 rewind # rewind the tape
for i in `/ /var /opt /export/home /opt/{filesystem} /opt/{filesystem}`
do
ufsdump 0f /dev/rmt/0n $i
echo "Completed ufs dump level 0 of $i ... "
done
echo "backup completed ... "
mt -f /dev/rmt/0 rewind
mt -f /dev/rmt/0 offline # eject the tape
Then try restoring the whole filesystem as follows with a similar script/set of commands ...
use mt -f /dev/rmt/0 fsf or bsf to move to the markers on the tape and when your happy you have the correct filesystem, complete a ufsrestore 0f /dev/rmt/0n (no rewind) to your filesystem. Should be quicker?
If you want to be even more fancy (in terms of potentially dealing with less data to backup), you could take incremental backups, which means you will only have to backup data that has changed from the last ufsdump date. Restores can get a bit tricky and messy though.
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. UNIX for Dummies Questions & Answers
I am running RH 7.1 and i am always remotely logged in working on a database. I got php and mysql running and then as the each week goes my rsh, or secure telnet, and any other remote session slows to become extremly choppy. If i am at teh box my i am fine the computer is not bogged down at all,... (5 Replies)
Discussion started by: macdonto
5 Replies
3. 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
4. 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
5. 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
6. AIX
Hello,
Some background so you can see what I'm trying to do on AIX:
In Windows its possible to partition a single hard drive into 2 separate logical paritions which may appear as a C and a D drive. It is then possible to to use 3rd party software such as Power Quest Drive Image to create a... (3 Replies)
Discussion started by: quickfirststep
3 Replies
7. 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
8. 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
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. Red Hat
This will be covered elsewhere im sure but i just cant seem to find my exact issue.
I want to backup my systems using tar, command is:
tar -cjpf /backup /bin /etc /home /opt /root /sbin /usr /var /bootWhen i include the / directory it also tar's the /lib /sys /proc /dev filesystems too (and... (8 Replies)
Discussion started by: Tommyk
8 Replies
tz(4) Kernel Interfaces Manual tz(4)
Name
tz - SCSI magnetic tape interface
Syntax
VAX NCR 5380:
adapter uba0 at nexus?
controller scsi0 at uba0 csr 0x200c0080 vector szintr
tape tz0 at scsi0 drive 0
VAX DEC SII:
adapter ibus0 at nexus?
controller sii0 at ibus? vector sii_intr
tape tz0 at sii0 drive 0
RISC DEC SII:
adapter ibus0 at nexus?
controller sii0 at ibus? vector sii_intr
tape tz0 at sii0 drive 0
RISC DEC KZQ:
adapter uba0 at nexus?
controller kzq0 at ibus? csr 0761300vector sii_intr
tape tz0 at kzq0 drive 0
RISC NCR ASC:
adapter ibus0 at nexus?
controller asc0 at ibus? vector ascintr
tape tz0 at asc0 drive 0
Description
The SCSI tape driver provides a standard tape drive interface as described in This is a driver for any Digital SCSI tape device.
For the TZK10 QIC format tape drive, the densities supported are QIC-24 (read only) block size of 512 byte blocks, QIC-120, and QIC-150
read/write block size of 512 byte blocks, and QIC-320 read/write block size of 1024 byte blocks. With QIC format style tapes all reads and
writes must be in multiple of the block size. This is a requirement of fixed block tape drives because record boundaries are not pre-
served. The QIC densities are selected using the following special device names:
QIC-24 Fixed block size.
QIC-120 Fixed block size.
QIC-150 Fixed block size.
QIC-320 Fixed block size.
With all fixed block tape devices a of a file to the tape must be padded out. An example of this is a of which has a size of approximately
3800 bytes.
dd if=/etc/gettytab of=/dev/rmt0h bs=10k conv=sync
or
dd if=/etc/gettytab of=/dev/rmt0l bs=512 conv=sync
The option of pads the output to block size.
This driver also supports n-buffered reads and writes to the raw tape interface (used with streaming tape drives). See for further
details.
Tape Support
TZ30, TZK50, TLZ04, TSZ05, TKZ08, TZK10
Diagnostics
All diagnostic messages are sent to the error logger subsystem.
Files
See Also
mtio(4), nbuf(4), SCSI(4), MAKEDEV(8), uerf(8), tapex(8)
Guide to the Error Logger
tz(4)