04-17-2008
why need to mirror disk if we had backups ?
hi.. newbie here, just wonder why there is a need for mirroring in some servers whereby we already had backups by cron jobs ?
10 More Discussions You Might Find Interesting
1. HP-UX
Being somewhat extremely new to Unix, I have just had a system crash
One of my Volume Groups has crashed
However, this Volume Group is actually mirrored
How do I switch to use the mirrored copy?
Any assistance greatly appreciated
Thanks (1 Reply)
Discussion started by: cobdeng
1 Replies
2. Solaris
Hi,
need some help.
I’m new to solaris and trying to find out how to mirror a data disk (not the root disk).
In AIX it is easy but with solaris 5.8 I don’t find my way even with the SUN docs (disk/suide is installed).
What is behind is I want to migrate a disk from 1 storage system to... (7 Replies)
Discussion started by: ccTester
7 Replies
3. Solaris
Is it possible to create a Mirror with zfs ??
I'm experimented user with Solstice Disk suite.
Or Sun Volume manager or veritas volume manager.
But, i would like switch from Disksuite to Zfs.
All my mirrored disks. (1 Reply)
Discussion started by: simquest
1 Replies
4. Solaris
Hi,
I want to know if one disk is failed in mirror in solaris and system is booted from another disk, is it possible to find out from which disk system is booted at command level? (1 Reply)
Discussion started by: manoj.solaris
1 Replies
5. Filesystems, Disks and Memory
I have a SUN 440 running Solaris 8 that is generating funny errors on /dev/dsk/c1t0d0 and I would like to dupe the drive(the non offending drives are removed for this process), swap it with the dupe and reboot. From what I have read, the process seems simple:
dd if=/dev/dsk/c1t0d0... (1 Reply)
Discussion started by: hardyj
1 Replies
6. Solaris
Hi all
I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =)
At the last code, is the step i wish to do. Please help to check and correct me if got any wrong.
root@leo # format </dev/null
Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies
7. Solaris
Long time Linux, relatively new to Solaris.
Currently I have a Solaris 9 machine which has a mirrored root disk. We will be running some tests on this machine, and when those tests are done we want to restore it to "pre-test" status.
What I would like to do is break the mirror, pull the first... (2 Replies)
Discussion started by: brianr
2 Replies
8. AIX
Hi Admins,
I am new into aix.I was surfing aix pages and reading how to replace failed mirror disks.I read in one of the posts that we have to reboot the server to replace the disk. actually i was a HPUX admin and many times replaced root mirror disk online.Ofcourse it was hot swappable.
... (2 Replies)
Discussion started by: newaix
2 Replies
9. AIX
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies
10. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 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)