07-15-2011
The recovery process heavily depends on the way you backed up your files.
Without a backup an undelete is not possible with the tools a shell script provides. The data your files contained may still be on your disk, but the inode entries are discarded.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We recently terminated a developer at my place of employment who created scripts on a windows server (that i do not have access to) that invoke FTP sessions on my UnixWare 7.1.1 servers.
I need to know the password that is being used. Does anyone know of a good password crack? (8 Replies)
Discussion started by: rm -r *
8 Replies
2. UNIX for Dummies Questions & Answers
Hi, I am new to unix and I set a password for a user and now I need to recover what that password was. Is there a way, where as root, I can view what a users passwords is?
Thanks,
Eric (2 Replies)
Discussion started by: ejbrever
2 Replies
3. Solaris
Hi all,
how i recovery the files when system is crash? (using crashdump concept)
regards
Krishna (1 Reply)
Discussion started by: murthy76
1 Replies
4. Solaris
Some thing happened to our solaris 10 ( sparc ) box and it is not coming up now.
These are some of the console messages :
I assume it is not able to find very basic system libraries so i need to tell it some how to find it under /lib:/usr/lib.
I booted it from the CD but now i... (4 Replies)
Discussion started by: rajwinder
4 Replies
5. AIX
I will be going for a DR test next month and have few concerns regarding restoring user vg's
System which will be restored is on P750 (AIX 6.1) and the DR hdwr is P570.
I do have bootable mksysb of the system and also have savevg (with no data) using "savevg -r -f " for the user volume... (5 Replies)
Discussion started by: mk8570
5 Replies
6. AIX
Hi,
I have to write a shell script for disk space recovery - We have been facing disk space shortage issues very often.
d=`df -k |awk '{print $5}' | egrep "" | cut -c-2`
if
then
echo "DISK SPACE STATUS :NOT OK" >> /backup/stats/healthcheck/SCP1_BLU_HCsummary_$dt.txt
else
echo "DISK... (3 Replies)
Discussion started by: vasukv
3 Replies
7. Shell Programming and Scripting
Hi all,
I'm a complete newbie to bash scripting, although I have some experience in programming. The thing is that I have a .dmg file on my mac which I protected with a password, and now I've forgotten it.
I remember the first few letters of the password and the characters that represent the... (4 Replies)
Discussion started by: sujay.jauhar
4 Replies
8. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Hi guys. My case study is about creating a script that includes password recovery whenever a user forgets... (1 Reply)
Discussion started by: jenimesh19
1 Replies
9. Shell Programming and Scripting
Hello All!
First post...
I am working on a script that is used to recover a crashed drive from an rsync backup.
I'm down to the place where I need to create all of the directories in /mnt where I will then mount each of the volumes and begin the restore process to each volume...
I have... (3 Replies)
Discussion started by: RogerBaran
3 Replies
10. Ubuntu
Is it possible to take incremental backup in Linux using tar command?
Please guide me.
Suppose I have a directory /data.
And want incremental backup.
What will be the incremental "tar" command syntax? (6 Replies)
Discussion started by: engineer2002
6 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)