05-21-2014
Hi,
we also use gtar as backup tool and were able to achieve a better performance/throughput with a larger blocking factor (eg '-b 1024').
Regards
This User Gave Thanks to -=XrAy=- For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
We have a gtar file and we are trying to untar the file with the option
gtar -xvzf <filename>
The gtar gets us till the end and throws the error message as highlighed below
mfcp/XFHFCD2.CPY
mfcp/XFHFCD3.CPY
mfcp/XFHFCD.CPY
gzip: stdin: unexpected end of file
gtar:... (1 Reply)
Discussion started by: ganga.dharan
1 Replies
2. UNIX for Dummies Questions & Answers
I am trying to write a very large file, 570 gb, to a tape using gtar like this :
gtar czxf /dev/rmt/1 ./*
I get a message:
off_t value 570635451556 too large (max=68719476735)
It is writing to tape, but will it be good?
Thanks (1 Reply)
Discussion started by: iancrozier
1 Replies
3. Shell Programming and Scripting
My data is something like shown below.
date1 date2 aaa bbbb ccccc
date3 date4 dddd eeeeeee ffffffffff ggggg hh
I want the output like this
date1date2 aaa eeeeee
I serached in the forum but didn't find the exact matching solution. Please help. (7 Replies)
Discussion started by: rdhanek
7 Replies
4. Solaris
Hi all,
will gtar zcvf command work in csh and tcsh shells? Becuase when i'm executing one script in bash and ksh, it's working fine. But it's not working in csh and tcsh shells. We have to run multiple scripts in tcsh, so we can not change the shell while executing these scripts. One of my... (2 Replies)
Discussion started by: raghu.iv85
2 Replies
5. Solaris
Hello All,
I am preparing a script to view or Extract contents of a tape drive using gtar.But facing a strange issue while trying to extract files using gtar.
If running script using sudo the getting the below error.
################
/usr/local/lib /usr/X11/lib /usr/X11R6/lib... (1 Reply)
Discussion started by: ajaincv
1 Replies
6. UNIX for Dummies Questions & Answers
Ok so once again im back with what is probably a beginner question although somewhat more complicated (for me) than the last.
Background:
A client has a daily backup which is carried out via rsync.
Due to this, when they move a file around that file is then coppied a second time.
On top of... (4 Replies)
Discussion started by: jeked
4 Replies
7. Shell Programming and Scripting
Hi Everyone,
we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment?
Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies
8. AIX
We are taking backup of our application data(cobol file system, AIX/unix) before and after EOD job runs. The data size is approximately 260 GB in biggest branch. To reduce the backup time, 5 parallel execution is scheduled through control-m which backups up the files in 5 different *.gz. The job... (8 Replies)
Discussion started by: Bharath_79
8 Replies
9. SCO
Hi All!
i am trying to copy files from a SCO Openserver 5.0.6 to a NAS Server using NFS. I have a cron job that takes 1.5 hours to run and most of the data is static. I would like to find a faster way. In the event I needed to running manually or avoid an issue with taking down the servers... (9 Replies)
Discussion started by: trolley
9 Replies
10. Shell Programming and Scripting
Hi all
I have a unix based firewall, which creates a daily backup file on the device.
I need a script to scp this file over to a remote server.
I can get this working daily using a basic script and a cron job.
However, I only want it to send the latest config back up file and currently... (4 Replies)
Discussion started by: jimmyzoom
4 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)