Sponsored Content
Full Discussion: Backup HP-UX
Operating Systems HP-UX Backup HP-UX Post 302628685 by sai_2507 on Tuesday 24th of April 2012 12:50:03 AM
Old 04-24-2012
Thanks methyl

Using commands mentioned above were really helpful in comparing the configurations before/after downtime.

Everything went well Smilie
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

regarding backup

hi i wanna know that is any such type of backup possible in Solaris or AIX that if my system crashes and i had to format the server.........then i shud be able to build the server with that backup only...........if so how thx (3 Replies)
Discussion started by: girish_shukla
3 Replies

2. UNIX for Dummies Questions & Answers

Backup

Dear All I have an HP 9000/800 UNIX machine , I have also Oracle applications 11i installed on it , we tried to take backup using fbackup command but it skipped some files ( was for database and the database was up and running ) but it took the other database files. I need to know also ,... (2 Replies)
Discussion started by: hisham.hamdy
2 Replies

3. UNIX for Dummies Questions & Answers

Check backup file size on backup tape

Hi, I performed backup on tape and I want to append more files to my previous backup on the same backup tape. But before I do that I need to know the backup file size of the first backup I performed so that I know the available size on the backup tape. Can someone help me what command I will use... (0 Replies)
Discussion started by: ayhanne
0 Replies

4. SCO

Backup to SCSI Tape Backup aborts

I am trying to make a full backup of my system using the cpio command. The Tape Unit is a SCSI DDS. The process started fine but after about 30 minutes, it just stopped and showed the following message: 1755 Signal 31 - Core dumped Any idea of what is causing this and how to fix it? ... (4 Replies)
Discussion started by: zionpc
4 Replies

5. UNIX for Advanced & Expert Users

Backup to CD ????? any one know how to do ???

hi, am trying to backup data on cd, cuz i don not have tape device....!!! i've rewritable CDROM, am using solaris 10 for x86 on vmware ..... how to make a backup data to a cd_rom againist to tape ? # ufsdump 0f cd_rom (1 Reply)
Discussion started by: sasame
1 Replies

6. AIX

backup

hi seniors today i took a backup using tar cmd in this i took two files for backup,backup was done succesfully but while viewing using tar -tvf ------- its showiing only one file at a time and i took backup in /etc/hosts,/etc/sen/nes (7 Replies)
Discussion started by: senmak
7 Replies

7. UNIX for Advanced & Expert Users

backup a file and keep every version of the backup

I am trying to backup my .bash_history and I want to keep every version of the backup. I am thinking to put one of these in my crontab. 0 0 * * 0,3 cat .bash_history > boo 0 0 * * 0,3 cp .bash_history boo I would like the backups to be called boo1, boo2, boo3, etc. I would like to keep... (7 Replies)
Discussion started by: cokedude
7 Replies

8. Shell Programming and Scripting

rsync backup mode(--backup) Are there any options to remove backup folders on successful deployment?

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

9. Shell Programming and Scripting

Help with Backup Shell Script for Network Device Configuration backup

HI all, im new to shell scripting. need your guidence for my script. i wrote one script and is attached here Im explaining the requirement of script. AIM: Shell script to run automatically as per scheduled and backup few network devices configurations. Script will contain a set of commands... (4 Replies)
Discussion started by: saichand1985
4 Replies
UNHIDE(8)						      System Manager's Manual							 UNHIDE(8)

NAME
unhide -- forensic tool to find hidden processes SYNOPSIS
unhide [OPTIONS] TEST_LIST DESCRIPTION
unhide is a forensic tool to find processes hidden by rootkits, Linux kernel modules or by other techniques. It detects hidden processes using six techniques. OPTIONS
-f Write a log file (unhide.log) in the current directory. -h Display help -m Do more checks. As of 2010-11-21 version, this option has only effect for the procfs, procall, checkopendir and checkchdir tests. Implies -v -r Use alternate version of sysinfo check in standard tests -V Show version and exit -v Be verbose, display warning message (default : don't display). This option may be repeated more than once. TEST_LIST The checks to do consist of one or more of the following tests. The standard tests are the aggregation of one or more elementary test(s). Standard tests : The brute technique consists of bruteforcing the all process IDs. This technique is only available on Linux 2.6 kernels. The proc technique consists of comparing /proc with the output of /bin/ps. The procall technique combinates proc and procfs tests. This technique is only available on Linux 2.6 kernels. The procfs technique consists of comparing information gathered from /bin/ps with information gathered by walking in the procfs. With -m option, this test makes more checks, see checkchdir test. This technique is only available on Linux 2.6 kernels. The quick technique combines the proc, procfs and sys techniques in a quick way. It's about 20 times faster but may give more false posi- tives. This technique is only available on Linux 2.6 kernels. The reverse technique consists of verifying that all threads seen by ps are also seen in procfs and by system calls. It is intended to ver- ify that a rootkit has not killed a security tool (IDS or other) and make ps showing a fake process instead. This technique is only available on Linux 2.6 kernels. The sys technique consists of comparing information gathered from /bin/ps with information gathered from system calls. Elementary tests : The checkbrute technique consists of bruteforcing the all process IDs. This technique is only available on Linux 2.6 kernels. The checkchdir technique consists of comparing information gathered from /bin/ps with information gathered by making chdir() in the procfs. With the -m option, it also verify that the thread appears in its "leader process" threads list. This technique is only available on Linux 2.6 kernels. The checkgetaffinity technique consists of comparing information gathered from /bin/ps with the result of call to the sched_getaffinity() system function. This technique is only available on Linux 2.6 kernels. The checkgetparam technique consists of comparing information gathered from /bin/ps with the result of call to the sched_getparam() system function. This technique is only available on Linux 2.6 kernels. The checkgetpgid technique consists of comparing information gathered from /bin/ps with the result of call to the getpgid() system func- tion. This technique is only available on Linux 2.6 kernels. The checkgetprio technique consists of comparing information gathered from /bin/ps with the result of call to the getpriority() system function. This technique is only available on Linux 2.6 kernels. The checkRRgetinterval technique consists of comparing information gathered from /bin/ps with the result of call to the sched_rr_get_inter- val() system function. This technique is only available on Linux 2.6 kernels. The checkgetsched technique consists of comparing information gathered from /bin/ps with the result of call to the sched_getscheduler() system function. This technique is only available on Linux 2.6 kernels. The checkgetsid technique consists of comparing information gathered from /bin/ps with the result of call to the getsid() system function. This technique is only available on Linux 2.6 kernels. The checkkill technique consists of comparing information gathered from /bin/ps with the result of call to the kill() system function. Note : no process is really killed by this test. This technique is only available on Linux 2.6 kernels. The checknoprocps technique consists of comparing the result of the call to each of the system functions. No comparison is done against /proc or the output of ps. This technique is only available on Linux 2.6 kernels. The checkopendir technique consists of comparing information gathered from /bin/ps with information gathered by making opendir() in the procfs. This technique is only available on Linux 2.6 kernels. The checkproc technique consists of comparing /proc with the output of /bin/ps. This technique is only available on Linux 2.6 kernels. The checkquick technique combines the proc, procfs and sys techniques in a quick way. It's about 20 times faster but may give more false positives. This technique is only available on Linux 2.6 kernels. The checkreaddir technique consists of comparing information gathered from /bin/ps with information gathered by making readdir() in /proc and /proc/pid/task. This technique is only available on Linux 2.6 kernels. The checkreverse technique consists of verifying that all threads seen by ps are also seen in procfs and by system calls. It is intended to verify that a rootkit has not killed a security tool (IDS or other) and make ps showing a fake process instead. This technique is only available on Linux 2.6 kernels. The checksysinfo technique consists of comparing the number of process seen by /bin/ps with information obtained from sysinfo() system call. This technique is only available on Linux 2.6 kernels. The checksysinfo2 technique is an alternate version of checksysinfo test. It might (or not) work better on kernel patched for RT, preempt or latency and with kernel that don't use the standard scheduler. It's also invoked by standard tests when using the -r option This technique is only available on Linux 2.6 kernels. Exit status: 0 if OK, 1 if a hidden or fake thread is found. BUGS
Report unhide bugs on the bug tracker on sourceforge (http://sourceforge.net/projects/unhide/) SEE ALSO
unhide-tcp (8). AUTHOR
This manual page was written by Francois Marier francois@debian.org and Patrick Gouin. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foun- dation. LICENSE
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Administration commands October 2010 UNHIDE(8)
All times are GMT -4. The time now is 04:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy