fbackup files in use

[Lisa Mauer]

If I am using fbackup through Sam - is there a log file that lists if files were not backed because they were in use?

If doing a full system backup and you have processes running, those executables will not be backed up correct?

[TwoProc · Accepted solution]

Incorrect,

Those files (unlike Windows) will be read just fine. Even open database files will be read just fine. BUT! That doesn't mean that database files which have activity will be any good, because you won't know what state the files were in for each part that was backed up during the procedure.

However, as far as your executables question goes, they'll be backed up fine.

[Torsten.]

Not really. There is no access violation like in the "other, colorful" OS world.

Problem could be changing files while backup - you change a file after it is already on tape and another before it is written to the tape.
fbackup is the basic tool for data backups - you should stop your application while you do a fbackup. prefered solution for the OS is ignite.

[Steven E. Protter]

Shalom Lisa,

You aren't doing a full system backup anyway.

You can't restore your system to bootable status with an fbackup backup.

fbackup can not back up open, changing files effectively. If you have an Oracle database and you put it in backup mode, then you can do it.

A full backup strategy consists of the following:

1) Regular ignite make_tape_recovery or make_net_recovery backups.
2) Backup of normal files, which fbackup can help with if the files aren't changing. If not, you need a better tool like Veritas Netbackup or Data Protector 5.X
3) Some of these tapes should go outside your business for disaster recovery purposes.

SEP

[James R. Ferguson]

Hi Lisa:

Be aware that 'fbackup' is designed to work while files are inuse. 'fbackup' attempts to insure a good copy of a file is placed on tape by comparing the timestamp of the file at the end of the copy to the timestamp of the file seen at the beginning of the transfer. If these do not match, 'fbackup' marks the file as "bad" and retries the copy. The retry ('maxretries') default is five (5) and can be defined in the 'config' file associated with 'fbackup' See the manpages for 'fbackp(1M)' for more information.

http://www.docs.hp.com/en/B2355-60127/fbackup.1M.html

Regards!

...JRF...

[Lisa Mauer]

Thanks!!!

Does SAM have a log of the files that could not be backed up? I could not find a log at all, but the fbackup is not completed yet...

[TwoProc]

If there are files that couldn't be backed up (I really don't believe you will find ANY, and if you do find some, it will be dead symbolic links, OR *disk problems*), they would likely show in /var/sam/log/samlog or one of the other files in that same directory.

[Bill Hassell]

Most all of the files marked as "not backed up" do not exist. They were temp files present when fbackup started but were removed before fbackup got to them. So they weren't backed up. Such is the nature of a busy system. The pathname to the file (and the filenames) will usually confirm the temporary nature of these files. The only way to prevent the error messages is to backup in single user mode (not really practical).

[Timothy P. Jackson]

Hi Lisa,

If you configure your fbackup to mail you when it is completed, the email will show you all the files that it had problems backing up. This is done in the "Set Additional Parameters..." when you create the automated backup. It is very good tool and I look at them every day to see if any of my production files are not being backed up.

An fbackup is only as good as your make recovery. As it was mentioned above, you cannot do a complete system restore from it.

Give the email a try, I think it's what you are looking for.

Tim

[Michael Steele_2]

SAM uses /usr/sam/lbin/br_backup when using fbackup and /var/sam/logs.