Error in Fbackup

[Francis Oliva]

Hi all,

I need your help. Please see below error:

#######
Insert a LTO-ULTRIUM2 tape with label 20070201_chippydb FS at /dev/rmt/1m:

Press enter when ready :
fbackup(1421): no history is available for graph file /home/chpyoper/bin/backup_ fs.g (below level 0)
fbackup(1004): session begins on Thu Feb 1 14:26:14 2007
fbackup(1702): out of virtual memory
fbackup(3055): total file blocks read for backup: 0
fbackup(3056): total blocks written to output file : 0
Backup Finished Successfully at Thu Feb 1 14:29:11 EAT 2007 ...:
####

Can you please advice me what to do? Thanks in advance

[Fabian Briseño]

Hello and welcome to the forums francis.

Can you please check your /var/adm/syslog.log file to see if there are more error messages? and display them here

[Fabian Briseño]

What version OS are you using.

what command are you using to make fbackup.

also check this

The utility set comprised of fbackup and frecover was originally
designed for use on systems equipped with not more than one gigabyte
of total file system storage. Although the utilities have no
programming limitations that restrict users to this size, complete
backups and recoveries of substantially larger systems can cause a
large amount of system activity due to the amount of virtual memory
(swap space) used to store the indices. Users who want to use these
utilities, but are noticing poor system-wide performance due to the
size of the backup, are encouraged to back up their systems in
multiple smaller sessions, rather than attempting to back up the
entire system at one time.

[Mridul Shrivastava]

These kind of messages comes when you try to backup very big data ( about 200GB)
It not so much of an issue backing up that amount of information in general. The
fbackup utility will create an INDEX of what it is about to backup, so this can
take up considerable amount of virtual memory depending on how many files you
have.
Basically you have one of three options.
1. Break up the backup - do one lvol at a time.
2. Use tar (a lot less elegant) but does not have the INDEX problem.
3. Increase the value of maxdsiz and see how you go.

[Francis Oliva]

Hi all ,

thanks for the info. Here is the requested info:
#########
Feb 1 17:25:38 chippydb sshd[166]: Failed password for oracle from 10.226.132.140 port 39770 ssh2
Feb 1 17:26:38 chippydb above message repeats 2 times
Feb 1 17:26:38 chippydb sshd[327]: Failed password for oracle from 10.226.132.140 port 40727 ssh2
Feb 1 17:26:52 chippydb sshd[357]: Accepted keyboard-interactive/pam for ptrlprod from 10.225.33.85 port 4771 ssh2
Feb 1 17:26:38 chippydb sshd[327]: error: PAM: Authentication failed for oracle from lightapp2
Feb 1 17:26:52 chippydb above message repeats 2 times
chippydb root:/var/adm/syslog> uname -a
HP-UX chippydb B.11.11 U 9000/800 3527244391 unlimited-user license
chippydb root:/var/adm/syslog>
##########

Can you please tell me to procedure how to increase the step #3? thanks again

[Mridul Shrivastava]

This has to be done using SAM and you have to reboot the server to make it effective.. So downtime is required..

SAM ==> Kernel configuration and then go to tunables and select this parameter and then increase the value...