07-17-2014
Quote:
Originally Posted by
shyam2j
'dd' was in my mind, but concern was wiping the OS completely and shutting down server after it.
In AIX you do not need to wipe the OS completely. If you overwrite the first GB (or thereabouts) of the rootvgs hdisk device(s) with hexadecimal zeroes you will destroy the VGDA and upon reboot the VG will not be recognizable any more by the OS. This will prevent data recovery with "normal" measures offered by the OS, but it will perhaps not prevent specialized laboratories doing some "extreme" data recovery.
You will have to decide if you want to prevent only "normal" people from getting anything or if you need to even fool the NSA (which probably had your data even before you from tapping the wires ;-)) ).
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a .sh script which was running fine on all the UNIX Servers (AIX, SunSolaris). The script requires two mandatory parameters and many optional parameters. Now at a different client place who are on a Windows Server, when I try to execute the script through MKS Toolkit, there are couple of... (5 Replies)
Discussion started by: madhunk
5 Replies
2. Fedora
Hi,
Is it possible to install Linux on an AIX server?
Is there any doc available with anyone for installation? Please help. (1 Reply)
Discussion started by: dwiravi
1 Replies
3. AIX
Hi,
I am a newbie to AIX. We have 2 AIX5.3 servers in our environment, I need to transfer some files in Binary mode from one server to another and some files in ASCII mode from one server to another server. Could you please help me as to how I need to do that?
Thanks,
Rakesh (4 Replies)
Discussion started by: rakeshc.apps
4 Replies
4. AIX
Guy's
AIX Monitoring Tool - under preparing .....
I'm working to make and prepare tool to monitor AIX system and my idea it's based on the following outputs
I want command to give me shout outpous about the following ...
CPU load
Memory load
Used load
Number of... (5 Replies)
Discussion started by: Mr.AIX
5 Replies
5. Red Hat
Hi,
Can anyone help me on migration the print server from AIX to RHEL 4?
Appreciate your help? (1 Reply)
Discussion started by: brby07
1 Replies
6. AIX
Hi,
I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error:
# mount 128.127.11.121:/aix /to_be_del
mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper
failure - RPC: 1832-008 Timed out
mount: retrying... (1 Reply)
Discussion started by: victorcheung
1 Replies
7. HP-UX
Hi,
Please suggest wipe tool for hp-ux. (2 Replies)
Discussion started by: manoj.solaris
2 Replies
8. AIX
Hello everybody,
Please let me know if there are any free C profiling tool for AIX environment
Thanks in advance (0 Replies)
Discussion started by: SteAlma
0 Replies
9. AIX
Hi,
is any one using nagios monitoring solution on AIX ? if yes, is it supported on AIX 7.1 TL 03 as well ?
I tried to search online and unix.com , could not find it.
Thank you (5 Replies)
Discussion started by: aaron8667
5 Replies
10. AIX
Hi folks,
How can i configure an AIX LDAP client to authenticate against an Linux Openldap server over TLS/SSL?
It works like a charm without TLS/SSL.
i would like to have SSL encrypted communication for ldap (secldapclntd) and ldapsearch etc. while accepting every kind of certificate/CA.... (6 Replies)
Discussion started by: paco699
6 Replies
LEARN ABOUT DEBIAN
bup-damage
bup-damage(1) General Commands Manual bup-damage(1)
NAME
bup-damage - randomly destroy blocks of a file
SYNOPSIS
bup damage [-n count] [-s maxsize] [--percent pct] [-S seed] [--equal]
DESCRIPTION
Use bup damage to deliberately destroy blocks in a .pack or .idx file (from .bup/objects/pack) to test the recovery features of bup-fsck(1)
or other programs.
THIS PROGRAM IS EXTREMELY DANGEROUS AND WILL DESTROY YOUR DATA
bup damage is primarily useful for automated or manual tests of data recovery tools, to reassure yourself that the tools actually work.
OPTIONS
-n, --num=numblocks
the number of separate blocks to damage in each file (default 10). Note that it's possible for more than one damaged segment to
fall in the same bup-fsck(1) recovery block, so you might not damage as many recovery blocks as you expect. If this is a problem,
use --equal.
-s, --size=maxblocksize
the maximum size, in bytes, of each damaged block (default 1 unless --percent is specified). Note that because of the way bup-
fsck(1) works, a multi-byte block could fall on the boundary between two recovery blocks, and thus damaging two separate recovery
blocks. In small files, it's also possible for a damaged block to be larger than a recovery block. If these issues might be a
problem, you should use the default damage size of one byte.
--percent=maxblockpercent
the maximum size, in percent of the original file, of each damaged block. If both --size and --percent are given, the maximum block
size is the minimum of the two restrictions. You can use this to ensure that a given block will never damage more than one or two
git-fsck(1) recovery blocks.
-S, --seed=randomseed
seed the random number generator with the given value. If you use this option, your tests will be repeatable, since the damaged
block offsets, sizes, and contents will be the same every time. By default, the random numbers are different every time (so you can
run tests in a loop and repeatedly test with different damage each time).
--equal
instead of choosing random offsets for each damaged block, space the blocks equally throughout the file, starting at offset 0. If
you also choose a correct maximum block size, this can guarantee that any given damage block never damages more than one git-fsck(1)
recovery block. (This is also guaranteed if you use -s 1.)
EXAMPLE
# make a backup in case things go horribly wrong
cp -a ~/.bup/objects/pack ~/bup-packs.bak
# generate recovery blocks for all packs
bup fsck -g
# deliberately damage the packs
bup damage -n 10 -s 1 -S 0 ~/.bup/objects/pack/*.{pack,idx}
# recover from the damage
bup fsck -r
SEE ALSO
bup-fsck(1), par2(1)
BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown- bup-damage(1)