05-14-2008
I am not an AIX admin, but Tar and Dump are reasonably alike across UNIXes.
Tar (the Tape ARchiver) was originally meant for writing multiple files to tape. By specifying a file as an output device, it can store several files in a single file (sometimes referred to as a 'tarball').
By compressing the resulting tarball with GZip, several files can be combined into a single, compressed archive.
Dump usually 'dumps' (backs up) the contents of a filesystem to a 'dumpfile'.
This means that all files included in the filesystem are included in the resulting dumpfile. Generally, an entire filesystem is restored in a single 'restore' command.
There are other ways to use dump (HP-UX has a wrapper script named fbackup), where dump performs (incremental) backups of sets of files.
The 'regular' version of tar, dump and restore are usually supplied with any UNIX distribution.
There is a GNU version of Tar that can perform in-line compression, incremental backups and other useful functions.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
For those with backup tapes (and I just bought and installed a Seagate one for my FreeBSD box) I want to know how to get the most out of each tape by placing multiple backups on each tape (potentially 20GB). Please correct me if I'm wrong:
First, retension the tape:
# mt retension
next, turn... (3 Replies)
Discussion started by: WIntellect
3 Replies
2. AIX
Currently am running the backup command for AIX 5L and see that the tape is rewinding after the completion of the back.
backup -0 -u -f /dev/rmt0 / >> $file 2>&1
What can I do to stop allow the backup to rew after the completion of this job? Any thoughts?
Thanks again. (2 Replies)
Discussion started by: justinburbridge
2 Replies
3. UNIX for Dummies Questions & Answers
Hello all, how would i go about verifying that a tape is backing up data correctly other than restoring the backup. for example, what command would i use to check the tape for errors? Any and all help is appreciated
-Coffee (0 Replies)
Discussion started by: coffeebrown
0 Replies
4. Solaris
My tape library is broken but backups still need to go on .I have 2 boxes running Solaris 10
Got SCSI tape drive attached to the DEV box ( my PROD Box has only fibre)
I want to take the prod backup from the DEV box using ufsdump. ie
/usr/sbin/ufsdump 0uvf DEV:/dev/rmt/1n... (2 Replies)
Discussion started by: Msororaji
2 Replies
5. AIX
Hi, I am currently looking at how we can optimize and speed up our backups here. I am just a beginner operator and our system admin hardly knows anything (long term interim).
There is this particular TAR backup of DB backups that for a 10.5Gb amount of files, it takes 5 hours to do the backup on... (6 Replies)
Discussion started by: Browser_ice
6 Replies
6. AIX
It may seam a bit odd that I ask this question.
After you have done your backups to tapes, do you verify the content of the tapes ?
- never
- sometimes
- always
The reason I am asking is that here in the office, all the backup procedures include verifying the content of the tapes (no... (5 Replies)
Discussion started by: Browser_ice
5 Replies
7. Solaris
I have a server/domain on a m5000 running Solaris 10. It is part of a cluster.
The other cluster member sees tape drives, but this one does not.
It is zoned correctly, and I can see the drives are binded in lputil.
The st.conf, and devlink.tab are identical.
ST.CONF: -
#
# Copyright... (1 Reply)
Discussion started by: pfwhufc
1 Replies
8. UNIX for Dummies Questions & Answers
Hello all. UNIX dummy here :p
Anyway I was trying to do a full backup of my work server SUN SPARC SERVER 1000 machine (yes we are actually using this dinosaur). I did the ufsdump comand and everything was fine until I got to the dumping of regular files. During the run I got the following... (7 Replies)
Discussion started by: hammerva
7 Replies
9. Solaris
First of all, great web site! I have been using it for a while but just registered today. It's been a great resource for me. Now, on to my issue.;)
I'm geographically separated from six (Sun v245s) development servers that I have been asked to backup and restore as development is done and... (11 Replies)
Discussion started by: ShawnD41
11 Replies
10. AIX
Hello,
I need to be able to encrypt LTO tapes that our AIX writes to for backups.
We have a tape library (IBM TS3100) that our AIX host uses to write to LTO6 tapes. We then take those tapes off-site and restore to another AIX system using a 3580-H6S LTO6 tape drive - this is a very simple... (3 Replies)
Discussion started by: c3rb3rus
3 Replies
LEARN ABOUT XFREE86
butc_logs
BUTC_LOGS(5) AFS File Reference BUTC_LOGS(5)
NAME
butc_logs - Message logs from the Tape Coordinator process
DESCRIPTION
The Backup System Tape Coordinator (butc) process generates two log files per device, one for error messages and one for actions.
Error Message Log
The TE_device_name file logs error messages generated by the Backup System Tape Coordinator that controls the tape device or backup data
file indicated by device_name.
As the Tape Coordinator initializes, it creates the file in ASCII format in the /var/lib/openafs/backup directory. If there is an existing
file, the Tape Coordinator renames it to TE_device_name.old>, overwriting the existing TE_device_name.old> file if it exists.
For a tape device, the Tape Coordinator derives the variable device_name portion of the filename from the device pathname listed in the
local /var/lib/openafs/backup/tapeconfig file, by stripping off the initial "/dev/" string and replacing any other slashes in the name with
underscores. For example, the filename for a device called /dev/rmt/4m is TE_rmt_4m. Similarly, for a backup data file the Tape Coordinator
strips off the initial slash ("/") and replaces any other slashes in the name with underscores. For example, the filename for a backup data
file called /var/tmp/FILE is TE_var_tmp_FILE.
The messages in the file describe the error and warning conditions the Tape Coordinator encounters as it operates. For instance, a message
can list the volumes that are inaccessible during a dump operation, or warn that the Tape Coordinator is overwriting a tape or backup data
file. The messages also appear in the /var/lib/openafs/backup/TL_device_name file, which traces most of the Tape Coordinator's actions.
Action Log
The TL_device_name file logs the actions performed by the Backup System Tape Coordinator that controls the tape device or backup data file
indicated by device_name. It also records the same error and warning messages written to the TE_device_name file.
As the Tape Coordinator initializes, it creates the file in ASCII format in the /var/lib/openafs/backup directory. If there is an existing
file, the Tape Coordinator renames it to TL_device_name.old, overwriting the existing TL_device_name.old file if it exists.
For a tape device, the Tape Coordinator derives the variable device_name portion of the filename from the device pathname listed in the
local /var/lib/openafs/backup/tapeconfig file, by stripping off the initial "/dev/" string and replacing any other slashes in the name with
underscores. For example, the filename for a device called /dev/rmt/4m is TL_rmt_4m. Similarly, for a backup data file the Tape Coordinator
strips off the initial slash ("/") and replaces any other slashes in the name with underscores. For example, the filename for a backup data
file called /var/tmp/FILE is TL_var_tmp_FILE.
SEE ALSO
tapeconfig(5), butc(8)
COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas
Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
OpenAFS 2012-03-26 BUTC_LOGS(5)