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
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
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
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
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
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
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
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
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
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
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(1M) backup(1M)
NAME
backup - backup or archive file system
SYNOPSIS
[-archive]
DESCRIPTION
The command uses find(1) and cpio(1) to save a archive of all files that have been modified since the modification time of on the default
tape drive should be invoked periodically to ensure adequate file backup.
The option suppresses warning messages regarding optional access control list entries. backup(1M) does not backup optional access control
list entries in a file's access control list (see acl(5)). Normally, a warning message is printed for each file having optional access
control list entries.
The option causes backup to save all files, regardless of their modification date, and then update using touch(1).
prompts you to mount a new tape and continue if there is no more room on the current tape. Note that this prompting does not occur if you
are running from cron(1M).
The option causes to start a file system consistency check (without correction) after the backup is complete. For correct results, it is
important that the system be effectively single-user while is running, especially if is allowed to automatically fix whatever inconsisten-
cies it finds. does not ensure that the system is single-user.
You can edit to customize it for your system. Several local values are used that can be customized:
specifies which directories to back up recursively (usually
meaning all directories);
file name where start and finish times, block counts, and error messages
are logged;
file name whose date is the date of the last archive;
file name that is checked by
to remind the next person who logs in to change the backup tape;
file name where start and finish times and
output is logged.
You may want to make other changes, such as whether or not does automatic correction (according to its arguments), where output is
directed, other information logging, etc.
In all cases, the output from is a normal archive file (or volume) which can be read using with the option.
File Recovery
creates archive tapes with all files and directories specified relative to the root directory. When recovering files from an archive tape
created by you should be in the root directory and specify the directory path names for recovered files relative to the root directory When
specifying the directory path name for file recovery by do not precede the leading directory name with a slash. If you prefer, you can
also use with a option to determine how files and directories are named on the archive tape before attempting recovery.
WARNINGS
Refer to in cpio(1).
When runs out of tape, it sends an error to standard error and demands a new special file name from
To continue, rewind the tape, mount the new tape, type the name of the new special file at the system console, and press
If is being run unattended from cron(1M) and the tape runs out, terminates, leaving the process still waiting. Kill this process when you
return.
FILES
parameterized file names
SEE ALSO
cpio(1), find(1), touch(1), cron(1M), fbackup(1M), frecover(1M), fsck(1M), acl(5).
backup(1M)