1834827 Members
2553 Online
110070 Solutions
New Discussion

HP9000 fbackup error

 
Matthew K Bowman
New Member

HP9000 fbackup error

Hi,

A client of ours uses a HP9000 with HP-UX 11.0 to backup a Cobalt Qube 2 to a local tape drive attached to the HP. The backup works in general save for a problem with a couple of directories on the Qube (see example below)

The Qube is linked to the HP via NFS.

I don't believe its the Qube thats to blame, although I am wondering if SAMBA is part of the problem as its used as a fileserver and users SMB from Windows into the Qube.

fbackup(1301): resuming at file 143854
fbackup(3007): WARNING: File number 143874 (/qube/home/groups/bettelec/Bettis Electric Literature Letters/literature letters/Delaware.doc)
was active during attempt number 1
fbackup(1301): resuming at file 143874

backup(1301): resuming at file 143929
fbackup(3007): WARNING: File number 143932 (/qube/home/groups/bettelec/Dave Hoke Presentations/Hazardous.JPG)
was active during attempt number 1
fbackup(1301): resuming at file 143932

Any help would be most apprieciated. Thank you
3 REPLIES 3
Steven E. Protter
Exalted Contributor

Re: HP9000 fbackup error

The file is open and fbackup may or may not be getting a good or usable copy.

Database backups are usually no good with fbackup unless the database is down. Cold backup.

P
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Pramod_4
Trusted Contributor

Re: HP9000 fbackup error

You are trying to backup files which are in use.

If the files not being modified at the time of the backup then you should be good, those files are not going to be good otherwise.

Thanks,

Pramod
A. Clay Stephenson
Acclaimed Contributor

Re: HP9000 fbackup error

This is a normal occurance when backing up files that are in use. Fbackup detected that the file was modified while it was in the process of being backed up. This is only a warning and may or may not be serious. Only the applications developer would know. As has been indicated, any sort of database backup is useless unless the database is shutdown (cold backup) or provisions have been made for hotbackups. In your case the files do not appear to be database related. Fbackup will retry those busy files; the number of retries can be specified in your fbackup config file.
If it ain't broke, I can fix that.