04-08-2005
you should also think about the number...
theses numbers are only (exept 0) logical numbers for the administrator.
if you take your level 0 backup the whole system is backuped....
if you take your level 3 backup the changes will be saved, so if you backup a new level 3 the changes since level 0 will be saved again BUT if you would take level 4 the changes since the level 3 backup will be changed
ufsdump 0vuf /dev/rmt/0 --> whole backup
mt fsf 1 --> forward one tapestamp
ufsdump 3vuf /dev/rmt/0n --> backup changes since 0 to unrewind tape
mt fsf 2 --> forward two tapestamps
ufsdump 5vuf /dev/rmt/0n --> backup changes since 3 ....
...
..
.
ufsdump 4vuf /dev/rmt/0n --> backup changes since 3 but the 5 will be ignored and changes will also be stored....
with the -u option the system updates you /etc/dumpdates to manage the dump-levels
greetings pressy
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Eh... what the title says. :) (8 Replies)
Discussion started by: PSC
8 Replies
2. UNIX for Dummies Questions & Answers
hi
i would like to backup my OS
what is the exact command to do?
beside backup to tapes can i back up to a directory in another server?
will the command be the same?
thanks. :confused: (4 Replies)
Discussion started by: legato
4 Replies
3. UNIX for Advanced & Expert Users
Hi,
I' using a sun solaris server, I would like to known if there is the possibility to control how many space is free on a tape and how I can delete a single file on a tape.
Thanks
DOMENICO (3 Replies)
Discussion started by: Minguccio75
3 Replies
4. UNIX for Dummies Questions & Answers
Hi there: I'm new here
Can anyone help me:
I have DS15 Alpha server : Unix 5.1B
Now i need to connect a DLVT VS80 1U Rackmount Tape Drive unit.
What is the exact comman to mount the DLTape IV??
How do i make backuo @ copy file to the tape?
Thanx to all (0 Replies)
Discussion started by: ayzeayem
0 Replies
5. SCO
when I do a tape status /dev/rStp0 I get the following on a new tape and I have tried several:
Status : ready beginning-of-tape
soft errors : 0
hard errors: 2
underruns: 5
My BackupEdge has stopped backing up my system because it asks for a new volume yet my total system data is under 20... (5 Replies)
Discussion started by: psytropic
5 Replies
6. Filesystems, Disks and Memory
I've starting playing with a tape drive for the first time. Its a new one, an IBM Ultrium LTO 4. After initially copying a file to the tape with tar cvf /dev/st0 /root/dummy, all subsequent files appended take an increasing amount of time with tar rvf /dev/st0 /root/dummyX. Is it normal for each... (2 Replies)
Discussion started by: jeriryan87
2 Replies
7. Solaris
hi, was wondering if there is a problem with the patches, and if we wish to restore everything back to square one, how should we go about using ufsrestore from a DAT tape of ufsdump backup data ? (1 Reply)
Discussion started by: Exposure
1 Replies
8. Solaris
hi friends, i am trying to patch a solaris 9 server. However i need to do a ufsdump backup before any patching. There is no hardware port for connecting the tape drive. Any other ways to do a ufsdump ? :wall: (2 Replies)
Discussion started by: Exposure
2 Replies
9. Solaris
Experts,
Before patching am advised to take backup :
so am going with:
ufsdump -0uf /dev/rmt0 / ---> to take the whole / bkp to tape.
some servers have /var in diff slice, In this case whether i need to take backup of /var also in tape?
ufsdump -ouf /dev/rmt0 /var ---> to take... (3 Replies)
Discussion started by: fizan
3 Replies
10. AIX
I am trying to use this command to eject the tape
mt -f /dev/rmt/0 unload
but it gives me error
mt -f /dev/rmt/0 unload
mt: 0511-575 unload is not a recognized subcommand.
Usage: mt Subcommand
Valid subcommands are:
weof
eof
fsf
bsf
... (5 Replies)
Discussion started by: filosophizer
5 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)