yls177 <yls177@hotmail.com> wrote:
[deleted]
> fbackup -f /dev/rmt/mydevice -g backupfile
>
> my backupfile is as follows
> i /
> i /stand
> i /var
> i /usr
> e /usr/sap/trans
> e /usr/sap/put
> e /usr/sap/sid
> e /tmp_trans
> e /tmp
> i /sapmnt/sid
> i /sap_interface
> i /oracle/stage/817_64
> i /oracle/stage/816_64
> i /oracle/sid
> i /oracle/sid/sapreorg
> i /oracle/sid/sapdata6
> i /oracle/sid/sapdata5
> i /oracle/sid/sapdata4
> i /oracle/sid/sapdata3
> i /oracle/sid/sapdata2
> i /oracle/sid/sapdata1
> i /oracle/sid/saparch
> i /oracle/sid/origlogB
> i /oracle/sid/origlogA
> i /oracle/sid/mirrlogB
> i /oracle/sid/mirrlogA
> i /oracle/805_64
> i /opt
> e /old_kernel
> e /home
>
> 1) must the name of the -g filename be "graphfile"? cos here, i
> changed to "backupfile"

No, you can have any name. Note however that an incremental backup
will refer to the absolute pathname of the graphfile, so you will have
to use the same pathname for the full and incremental backups.

> 2) also, how about the owner/ermission of this file?

As long as the user which invokes fbackup, normally root, can read it,
then it should be OK.

> 3) i got the entries of "backupfile" from bdf command. any concerns?

Yes, that is the right way (or the mount command, etc.).

> 4) any idea how to check whether the entries in "backupfile" space is
> enough for the tape device?

No because (hardware) data compression is dependent on the actual
data, you can not know in advance how much will fit on a tape. For some
fbackup versions (for 11.X?) there is some fbackup option which makes
fbackup report the total size of the backup *after* it is finished. You
can use that, together with an estimate of the compression factor (start
with 1, i.e. no compression) and the native mode (i.e. uncompressed)
capacity of the tape in question, to try to get as much as possible on
the tape.