Sponsored Content
Operating Systems HP-UX HP-UX Full System Backup with fbackup Post 302456554 by methyl on Friday 24th of September 2010 02:10:22 PM
Old 09-24-2010
vbe is right. "fbackup" is not enough.

I would also like to add that "fbackup" in common with many of the unix feebies such as "dump" does not deal with large files (above 2Gb). It is also not accepted as a backup by HP support.


If you want to be able to recover from a system disc failure you should first make an Ignite backup and repeat that backup every time you make a significant change to the system configuration. Don't forget to record the current root password against that backup.

Then also use proper backup software (e.g. HP Omniback aka. Data Protector) to back up every file bearing in mind that "files" backups do not back up the Operating System properly - hence the Insight backup.

Don't forget to quiesce filesystems before you run a backup. In the basic case this mean stopping any databases and ensuring that no files are open. There are techniques available to keep database engines such as Oracle running during a backup.

It is advisible to rehearse and document the restore again-and-again to an expendable computer until you are confident that the restore works. If you are meticulous in your Insight backups or /dev/vg00 you may just need to bring /etc/passwd up to date before restoring the individual filesystems from the secondary backup.


Dealing with "fbackup" or "dump" process which go onto a continuation tape needs technical knowledge and planning. Imho you need to break the backup down into separate tapes by careful sizing and planning. i.e. Make each tape a separate backup operation containing one or more distinct disc partitions and don't let the backup software ask for a continuatation tape.
Imho. The best technique is to place each filesystem backup onto a separate tape partition and then use "mt" commands to navigate the tape. This is not necessary with HP Omniback because it recognises different mountpoints.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Backup using fbackup

Dear All, We have Universe database on HP-UX Servers, when we take back on DDS3 it completes around 48 Gb data on just one tape. As per DDS media specs it can hold upto 24 GB compressed data. How it is managing more than double data..? (3 Replies)
Discussion started by: Kashif Raees
3 Replies

2. UNIX for Dummies Questions & Answers

Full System Backup / Cloning HPUX

I am new to UNIX and need help in cloning a HPUX 10.2 Ace 5, can anybody please guide me in making a full system backup. Real Chess (0 Replies)
Discussion started by: real-chess
0 Replies

3. Linux

full system backup script

Please help. I am new to linux. I wrote a script to run the backup on lunix machine but the job gave me an error. I am using Linux 2.6.14.3. Below is the sample of my script can anyone tell me where went wrong? Thanks in advance. #!/bin/sh dat=$(date +%d%b%y)... (5 Replies)
Discussion started by: clement
5 Replies

4. UNIX for Dummies Questions & Answers

System full backup to tape

hi, Recently, I had receive one system. it's run on the unix tru64 server. I looking some log files when i know don't work few months age system backup to tape. Below error: INFO:Tape backups to tape tape0 starting for backup list: slot2:/disk4 Backup Command Variable... (0 Replies)
Discussion started by: Tlg13team
0 Replies

5. Solaris

full system backup

I have unix server with OS 5.8 ,,, I tried ufsdump 0ua -f /dev/rmt/0 / to perform full system backup on tape but I failed could any one give a procedure for full system backup on solaris machine using tapes??? (1 Reply)
Discussion started by: mm00123
1 Replies

6. UNIX for Dummies Questions & Answers

Full System Backup Sco 5.0.5

I would like to know if I can do a full system back up on my Unix Sco openserver 5.0.5 Machine. If so, What is the syntax to do this or where can I find this information at? Also, is it possible to make this tape bootable so that I can easily do a full system restore? Any information on... (2 Replies)
Discussion started by: nellenodrog
2 Replies

7. HP-UX

Backup Script using fbackup command Help Needed.

Hi Friends, I'm new to unix, I have the below script which takes regular backup. Now if fbackup fails I get the below messages in my log as fbackup(3047): could not open output file /dev/rmt/0m fbackup(3019): would you like to enter a new output file? fbackup(3004): writer aborting... (4 Replies)
Discussion started by: avik.nandi
4 Replies

8. UNIX for Advanced & Expert Users

how to make a full system backup excluding data and restoring it to a new system

Hi, In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way : - Make a full system backup excluding the user file system (this... (7 Replies)
Discussion started by: pagaille
7 Replies

9. UNIX for Advanced & Expert Users

Grub - how to boot a copy of Linux (full system backup)

Hi All, I have successfully backup & restore (using tar) one of my Debian Lenny Servers. On the restore server (standby machine), everytime i have to erase the disk & extract the tar backup. I want to extract the tar on the running restore server on a directory for e.g /systembackup-01,... (11 Replies)
Discussion started by: coolatt
11 Replies

10. Solaris

Help - Chosing backup way (full system + zones)

Hello i am new on Solaris, and i need to migrate my old AIX 5.3 to Solaris 11.2 Now i have all apps working fine but i have the backup cause i was reading and i have not idea about what method must i choose. Btw on AIX i had a mksysb backup to restore all system and obviously another backups to... (4 Replies)
Discussion started by: thorin666
4 Replies
BACKUP_VOLINFO(8)					       AFS Command Reference						 BACKUP_VOLINFO(8)

NAME
       backup_volinfo - Displays a volume's dump history from the Backup Database

SYNOPSIS
       backup volinfo -volume <volume name> [-localauth]
	   [-cell <cell name>] [-help]

       backup voli -v <volume name>
	   [-l] [-c <cell name>] [-h]

DESCRIPTION
       The backup volinfo command displays a dump history of the specified volume, reporting information such as the date on which the volume was
       dumped and the tapes that contain it. Include the ".backup" extension on the volume name if the backup version of the volume was dumped.

OPTIONS
       -volume <volume name>
	   Names the volume for which to display the dump history. Include the ".backup" or ".readonly" extension if the backup or read-only
	   version of the volume was dumped.

       -localauth
	   Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to
	   the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more
	   details, see backup(8).

       -cell <cell name>
	   Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8).

       -help
	   Prints the online help for this command. All other valid options are ignored.

OUTPUT
       The output includes a line for each Backup Database dump record that mentions the specified volume, order from most to least recent. The
       output for each record appears in a table with six columns:

       dumpID
	   The dump ID of the dump that includes the volume.

       lvl The depth in the dump hierarchy of the dump level at which the volume was dumped. A value of 0 indicates a full dump. A value of 1 or
	   greater indicates an incremental dump made at the specified depth in the dump hierarchy.

       parentid
	   The dump ID of the dump's parent dump. A value of 0 indicates a full dump, which has no parent; in this case, the value in the "lvl"
	   column is also 0.

       creation date
	   The date and time at which the Backup System started the dump operation that created the dump.

       clone date
	   For a backup or read-only volume, the time at which it was cloned from its read/write source. For a read/write volume, the same as the
	   value in the "creation date" field.

       tape name
	   The name of the tape containing the dump: either the permanent tape name, or an AFS tape name in the format
	   volume_set_name.dump_level_name.tape_index where volume_set_name is the name of the volume set associated with the initial dump in the
	   dump set of which this tape is a part; dump_level_name is the name of the dump level at which the initial dump was backed up;
	   tape_index is the ordinal of the tape in the dump set. Either type of name can be followed by a dump ID in parentheses; if it appears,
	   it is the dump ID of the initial dump in the dump set to which this appended dump belongs.

EXAMPLES
       The following example shows part of the dump history of the Backup volume "user.smith.backup":

	  % backup volinfo -volume user.smith.backup
	  DumpID    lvl parentID  creation date    clone date	    tape name
	  924600000 1	924427600 04/20/1999 05:20 04/20/1999 05:01 user_incr_2 (924514392)
	  924514392 1	924427600 04/19/1999 05:33 04/19/1999 05:08 user_incr_2
	  924427600 0		0 04/18/1999 05:26 04/18/1999 04:58 user_full_6
	      .     .	   .	     .	     .	     .	    .	      .
	      .     .	   .	     .	     .	     .	    .	      .

PRIVILEGE REQUIRED
       None

SEE ALSO
       backup(8), backup_dumpinfo(8), backup_volrestore(8)

COPYRIGHT
       IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

       This documentation is covered by the IBM Public License Version 1.0.  It was converted from HTML to POD by software written by Chas
       Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

OpenAFS 							    2012-03-26							 BACKUP_VOLINFO(8)
All times are GMT -4. The time now is 10:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy