Sponsored Content
Full Discussion: Backup HP-UX
Operating Systems HP-UX Backup HP-UX Post 302625775 by methyl on Wednesday 18th of April 2012 09:18:46 AM
Old 04-18-2012
Look in the directory /etc/rc.config.d , sort by modification date and save anything which has changed since HP-UX was installed . The main Network Configuration file is called netconf , but there will be more depending on what network hardware you have installed.

Other network-related files to save are:
/etc/hosts
/etc/inetd.conf
/etc/nsswitch.conf
/etc/ntp.conf
/etc/resolv.conf
/etc/services
# Everything in the directory
/etc/mail

Again, sort /etc by modification date and and look for files which have changed since the system was installed (particularly files with extension .conf).



Save a copy of /etc/mnttab (the list of current mounted filesystems) for comparision.

As for the full backup, as well as making an Ignite backup as advised you may need to backup other filesystems which are excluded from the Ignite backup.
How do you normally back your system up?
 

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
DOWNTIMED(8)						      System Manager's Manual						      DOWNTIMED(8)

NAME
downtimed - system downtime monitoring and reporting daemon SYNOPSIS
downtimed [-D] [-d datadir] [-l log] [-p pidfile] [-S] [-s sleep] downtimed -v DESCRIPTION
The downtimed daemon waits in the background, frequently updating a time stamp file on the disk. If the daemon is killed with a signal associated with a normal system shutdown procedure, it will record the shutdown time on the disk. When the daemon is restarted during the next boot process, it will report how long the system was down and whether it was properly shut down or crashed. The downtime report is output to the system log or to a specified log file. Also a record is appended to the downtime database. OPTIONS
-D Do not create nor update the downtime database. -d datadir The directory where the time stamp files as well as the downtime database are located. The default directory is determined at com- pile time. -l log Logging destination. If the argument contains a slash (/) it is interpreted to be a path name to a log file, which will be created if it does not exist already. Otherwise it is interpreted as a syslog facility name. The default logging destination is "daemon" which means that the messages are written to syslog with the daemon facility code. -p pidfile The location of the file which keeps track of the process ID of the running daemon process. The system default location is deter- mined at compile time. -S Normally fsync(2) is performed after each update of the time stamp. This option disables the fsync(2). It reduces the load on the disk system but makes the downtime measurement less reliable. This option is not available on all systems. -s sleep Defines how long to sleep between each update of the on-disk time stamp file. More frequent updates result in more accurate downtime reporting in the case of a system crash. Less frequent updates decrease the amount of disk writes performed. The default is to sleep 15 seconds between eacch update. If you are using a flash memory based SSD or other disk which has limited amount of write cycles per block, it might be a good idea to set the sleep time to a higher value to prolong the lifetime of the storage device. -v Display the program version number, copyright message and the default settings. SIGNALS
SIGHUP Close and re-open the output log. Use in case you want to rotate the log file. SIGTERM and SIGINT Terminate gracefully. These signals signify that a graceful system shutdown is in process. EXIT STATUS
The daemon exits 0 on success, and >0 if an error occurs. SEE ALSO
downtimes(1), syslog.conf(5), http://dist.epipe.com/downtimed/ BUGS
The reporting accuracy in case of a system crash depends on how often the time stamp is updated. Finding out the system startup time is very operating system specific. If the program does not have specific code to support your operat- ing system, it assumes that the system started when the daemon started. Reporting is inaccurate if the system clock changes during system downtime or startup process. Daylight saving time changes have no effect as all calculations are done using UTC. COPYRIGHT
Copyright (C) 2009-2011 EPIPE Communications. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBU- TORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE- MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABIL- ITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as represent- ing official policies, either expressed or implied, of EPIPE Communications. version 0.5 2011-03-02 DOWNTIMED(8)
All times are GMT -4. The time now is 10:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy