11-13-2002
thanks livinfree,
I am doing the bare bones system, (on a duplicate machine) and unpacking the backups.
Is there some reason that the boot manager area is not backed up or damaged with the "tar" method as opposed to the "find" method? Both backup methods are done at the init 1 level.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I'm trying to set up a stanard sh script that will find all the files that have been changed within the last day and then tar them up.
I think the command line should be something like :
find /home/bob -atime +0 -exec \ tar cvf /home/bob/files.tar {}\;
Help please ...
Thanx (3 Replies)
Discussion started by: ianf
3 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I've got dozens of tar's with two files in each one,
live_access_log & live_error_log (one tar for each day, backups).
The probelm is i need to match a pattern in all of the archive_access_log files and output the line to a seperate file (All_access.log).
I.e. I need to get details... (21 Replies)
Discussion started by: tom123
21 Replies
3. Solaris
Hi all,
I would like to know what would happen if the tape (media) is not placed on the drive and a tar command is executed to backup on the tape.
My problem is that tar command hanged for multiple days instead of throwing the error,
Is it valid behaviour?
I was unable to test the... (4 Replies)
Discussion started by: jmsathish
4 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
4 files are returned when i issue 'find . -mtime -1 -type f -ls'.
./ora_475244.aud
./ora_671958.aud
./ora_934052.aud
./ora_934050.aud
However, when I issued the below command:
tar -cvf test.tar `find . -mtime -1 -type f`, the tar file only contains the 1st file -... (2 Replies)
Discussion started by: ahSher
2 Replies
5. Shell Programming and Scripting
find . -type f -name "*.sql" -print|xargs perl -i -pe 's/pattern/replaced/g'
this is simple logic to find and replace in multiple files & folders
Hope this helps.
Thanks
Zaheer (0 Replies)
Discussion started by: Zaheer.mic
0 Replies
6. Shell Programming and Scripting
Hello people!
I would like to create one script following this stage
I have one directory with 100 files
File001
File002
...
File100
(This is the format of content of the 100 files)
2012/03/10 12:56:50:221875936 1292800448912 12345 0x00 0x04 0
then I have one... (0 Replies)
Discussion started by: Abv_mx81
0 Replies
7. Shell Programming and Scripting
Need to
1. archive all the files in a directory from the previous month into a tar/gz file, ignoring all already archived 'tar.gz' files
2. Check created .tar.gz file isnt corrupted and has all the required files in it. and then remove the original files.
I am using a function to get the... (1 Reply)
Discussion started by: Prev
1 Replies
8. AIX
This thread is about using tar & other compression utilities on AIX ;
1. Find out which version of tar you are using
thanks to bakunin
>what $(which tar)
/usr/bin/tar:
61 1.14 src/bos/usr/ccs/lib/libc/__threads_init.c, libcthrd, bos53 0 7/11/00 12:04:14
10 ... (21 Replies)
Discussion started by: filosophizer
21 Replies
9. Solaris
I've a tape contains a corrupt tar file. I'm using Unix SunOS 5.5.1. So when I run this command : dd if=/dev/rmt/0 of=/tmp/outputfile.tar
I get this error message :
warning /pci@1f, 0/pci@1/pci@1/sunw, isptwo@4/st@4,0 (sty): Error for command : read Error Level: Fatal Requested... (2 Replies)
Discussion started by: akaderb
2 Replies
LEARN ABOUT DEBIAN
bup-fsck
bup-fsck(1) General Commands Manual bup-fsck(1)
NAME
bup-fsck - verify or repair a bup repository
SYNOPSIS
bup fsck [-r] [-g] [-v] [--quick] [-j jobs] [--par2-ok] [--disable-par2] [filenames...]
DESCRIPTION
bup fsck is a tool for validating bup repositories in the same way that git fsck validates git repositories.
It can also generate and/or use "recovery blocks" using the par2(1) tool (if you have it installed). This allows you to recover from dam-
aged blocks covering up to 5% of your .pack files.
In a normal backup system, damaged blocks are less important, because there tends to be enough data duplicated between backup sets that a
single damaged backup set is non-critical. In a deduplicating backup system like bup, however, no block is ever stored more than once,
even if it is used in every single backup. If that block were to be unrecoverable, all your backup sets would be damaged at once. Thus,
it's important to be able to verify the integrity of your backups and recover from disk errors if they occur.
WARNING: bup fsck's recovery features are not available unless you have the free par2(1) package installed on your bup server.
WARNING: bup fsck obviously cannot recover from a complete disk failure. If your backups are important, you need to carefully consider
redundancy (such as using RAID for multi-disk redundancy, or making off-site backups for site redundancy).
OPTIONS
-r, --repair
attempt to repair any damaged packs using existing recovery blocks. (Requires par2(1).)
-g, --generate
generate recovery blocks for any packs that don't already have them. (Requires par2(1).)
-v, --verbose
increase verbosity (can be used more than once).
--quick
don't run a full git verify-pack on each pack file; instead just check the final checksum. This can cause a significant speedup
with no obvious decrease in reliability. However, you may want to avoid this option if you're paranoid. Has no effect on packs
that already have recovery information.
-j, --jobs=numjobs
maximum number of pack verifications to run at a time. The optimal value for this option depends how fast your CPU can verify packs
vs. your disk throughput. If you run too many jobs at once, your disk will get saturated by seeking back and forth between files
and performance will actually decrease, even if numjobs is less than the number of CPU cores on your system. You can experiment
with this option to find the optimal value.
--par2-ok
immediately return 0 if par2(1) is installed and working, or 1 otherwise. Do not actually check anything.
--disable-par2
pretend that par2(1) is not installed, and ignore all recovery blocks.
EXAMPLE
# generate recovery blocks for all packs that don't
# have them
bup fsck -g
# generate recovery blocks for a particular pack
bup fsck -g ~/.bup/objects/pack/153a1420cb1c8*.pack
# check all packs for correctness (can be very slow!)
bup fsck
# check all packs for correctness and recover any
# damaged ones
bup fsck -r
# check a particular pack for correctness and recover
# it if damaged
bup fsck -r ~/.bup/objects/pack/153a1420cb1c8*.pack
# check if recovery blocks are available on this system
if bup fsck --par2-ok; then
echo "par2 is ok"
fi
SEE ALSO
bup-damage(1), fsck(1), git-fsck(1)
BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown- bup-fsck(1)