fbackup(1517): /net not backed up - 'n' option (NFS) not specified
fbackup(3203): volume 1 has been used 0 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/c0t3d0BEST
fbackup(3003): normal EOT
fbackup(3316): enter '^[yY]' when volume 2 is ready on
/dev/rmt/c0t3d0BEST,
or '^[nN]' to discontinue:
fbackup(3004): writer aborting
fbackup(1002): Backup did not complete : Reader or Writer process exit
Not a terminal
stty: : Not a typewriter
Not a terminal
stty: : Not a typewriter


my understanind is that the tape storage was full and the system watns
another tape and since this is coming from a cron entry then naturally
it fails.

am i right?

also, i wanted to rectify the issue by selecting the filesystems to be
backuped up, however, in my script, i only have

"fbackup -f /dev/rmt/c0t3d0BEST -i /"

how to achieve so? by replacing / with the list of filesystems to be
backed up?

thanks

yls177 <yls177@hotmail.com> wrote:
> fbackup(1517): /net not backed up - 'n' option (NFS) not specified
> fbackup(3203): volume 1 has been used 0 time(s)
> fbackup(3024): writing volume 1 to the output file /dev/rmt/c0t3d0BEST
> fbackup(3003): normal EOT
> fbackup(3316): enter '^[yY]' when volume 2 is ready on
> /dev/rmt/c0t3d0BEST,
> or '^[nN]' to discontinue:
> fbackup(3004): writer aborting
> fbackup(1002): Backup did not complete : Reader or Writer process exit
> Not a terminal
> stty: : Not a typewriter
> Not a terminal
> stty: : Not a typewriter
>
> my understanind is that the tape storage was full and the system watns
> another tape and since this is coming from a cron entry then naturally
> it fails.
>
> am i right?

Yes

> also, i wanted to rectify the issue by selecting the filesystems to be
> backuped up, however, in my script, i only have
>
> "fbackup -f /dev/rmt/c0t3d0BEST -i /"
>
> how to achieve so? by replacing / with the list of filesystems to be
> backed up?

If you include "/", you also include all filesystems below "/". So if
you only want to backup "/", but not the filesystems below it, then you
have to specifically exclude those other filesystems. This is easiest
with the "-g graphfile" option, where graphfile is a file which contains
the includes and excludes, i.e.

graphfile:
==========
i /
e /mnt1
....
e /mntx

See the fbackup(1M) manual page for details.

Frank Slootweg <this@ddress.is.invalid> wrote in message news:<40e01458$0$208$cd19a363@news.wanadoo.nl>...
> yls177 <yls177@hotmail.com> wrote:
> > fbackup(1517): /net not backed up - 'n' option (NFS) not specified
> > fbackup(3203): volume 1 has been used 0 time(s)
> > fbackup(3024): writing volume 1 to the output file /dev/rmt/c0t3d0BEST
> > fbackup(3003): normal EOT
> > fbackup(3316): enter '^[yY]' when volume 2 is ready on
> > /dev/rmt/c0t3d0BEST,
> > or '^[nN]' to discontinue:
> > fbackup(3004): writer aborting
> > fbackup(1002): Backup did not complete : Reader or Writer process exit
> > Not a terminal
> > stty: : Not a typewriter
> > Not a terminal
> > stty: : Not a typewriter
> >
> > my understanind is that the tape storage was full and the system watns
> > another tape and since this is coming from a cron entry then naturally
> > it fails.
> >
> > am i right?
>
> Yes
>
> > also, i wanted to rectify the issue by selecting the filesystems to be
> > backuped up, however, in my script, i only have
> >
> > "fbackup -f /dev/rmt/c0t3d0BEST -i /"
> >
> > how to achieve so? by replacing / with the list of filesystems to be
> > backed up?
>
> If you include "/", you also include all filesystems below "/". So if
> you only want to backup "/", but not the filesystems below it, then you
> have to specifically exclude those other filesystems. This is easiest
> with the "-g graphfile" option, where graphfile is a file which contains
> the includes and excludes, i.e.
>
> graphfile:
> ==========
> i /
> e /mnt1
> ...
> e /mntx
>
> See the fbackup(1M) manual page for details.




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"
2) also, how about the owner/ermission of this file?
3) i got the entries of "backupfile" from bdf command. any concerns?
4) any idea how to check whether the entries in "backupfile" space is
enough for the tape device?

thanks

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.

Frank Slootweg <this@ddress.is.invalid> wrote in message news:<40e569d7$0$136$1b2cd167@news.wanadoo.nl>...
> 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.


stty: : Not a typewriter
fbackup(1004): session begins on Sat Jul 10 23:46:27 2004
fbackup(3203): volume 1 has been used 1 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/mydevice
fbackup(1102): WARNING: unable to stat file
/var/spool/sockets/pwgr/client2569
fbackup(1102): WARNING: unable to stat file
/var/spool/sockets/pwgr/client2691
fbackup(1102): WARNING: unable to stat file
/var/spool/sockets/pwgr/client2924
fbackup(1102): WARNING: unable to stat file
/var/spool/sockets/pwgr/client3021
fbackup(1102): WARNING: unable to stat file
/var/spool/sockets/pwgr/client3212
fbackup(1102): WARNING: unable to stat file
/var/spool/sockets/pwgr/client3290
fbackup(1102): WARNING: unable to stat file
/var/spool/sockets/pwgr/client3365
fbackup(3005): WARNING: file number 93507 was NOT backed up
fbackup(3005): WARNING: file number 93508 was NOT backed up
fbackup(3005): WARNING: file number 93510 was NOT backed up
fbackup(3005): WARNING: file number 93512 was NOT backed up
fbackup(3005): WARNING: file number 93513 was NOT backed up
fbackup(3005): WARNING: file number 93514 was NOT backed up
fbackup(3005): WARNING: file number 93515 was NOT backed up
fbackup(1030): warnings encountered during backup
fbackup(3055): total file blocks read for backup: 77878219
fbackup(3056): total blocks written to output file /dev/rmt/mydevice:
78224868
Not a terminal
stty: : Not a typewriter
Not a terminal
stty: : Not a typewriter


my graphfile is the same as the above except that i have "e /".
however, what does the above warning indicates?

yls177 <yls177@hotmail.com> wrote:
[deleted]
> stty: : Not a typewriter
> fbackup(1004): session begins on Sat Jul 10 23:46:27 2004
> fbackup(3203): volume 1 has been used 1 time(s)
> fbackup(3024): writing volume 1 to the output file /dev/rmt/mydevice
> fbackup(1102): WARNING: unable to stat file
> /var/spool/sockets/pwgr/client2569
> fbackup(1102): WARNING: unable to stat file
> /var/spool/sockets/pwgr/client2691
> fbackup(1102): WARNING: unable to stat file
> /var/spool/sockets/pwgr/client2924
> fbackup(1102): WARNING: unable to stat file
> /var/spool/sockets/pwgr/client3021
> fbackup(1102): WARNING: unable to stat file
> /var/spool/sockets/pwgr/client3212
> fbackup(1102): WARNING: unable to stat file
> /var/spool/sockets/pwgr/client3290
> fbackup(1102): WARNING: unable to stat file
> /var/spool/sockets/pwgr/client3365
> fbackup(3005): WARNING: file number 93507 was NOT backed up
> fbackup(3005): WARNING: file number 93508 was NOT backed up
> fbackup(3005): WARNING: file number 93510 was NOT backed up
> fbackup(3005): WARNING: file number 93512 was NOT backed up
> fbackup(3005): WARNING: file number 93513 was NOT backed up
> fbackup(3005): WARNING: file number 93514 was NOT backed up
> fbackup(3005): WARNING: file number 93515 was NOT backed up
> fbackup(1030): warnings encountered during backup
> fbackup(3055): total file blocks read for backup: 77878219
> fbackup(3056): total blocks written to output file /dev/rmt/mydevice:
> 78224868
> Not a terminal
> stty: : Not a typewriter
> Not a terminal
> stty: : Not a typewriter
>
> my graphfile is the same as the above except that i have "e /".
> however, what does the above warning indicates?

The "fbackup(1102): WARNING: unable to stat file" *warning* (not
error) means that fbackup could not do a stat(2) system call on the
named 'file' (probably a socket in this case). That normally means that
the 'file' was present when fbackup collected the list of files to be
backed up, but when it actually gets to backing up the file, it is no
longer there. The "fbackup(3005): WARNING: file number ..... was NOT
backed up" *warning* just says that the file was not backed up (because
it could not be stat(2)-ed/found.

Perhaps others can comment on what the *specific* files/directory,
i.e. /var/spool/sockets/pwgr/client*, are/is used for.

The "stty: : Not a typewriter" and "Not a terminal" errors are not
directly related to fbackup. Apparently your backup script tries some
terminal operations (perhaps by an implicitly referenced .profile file),
and since the script runs from cron(1M), there is no terminal
(association).

"Frank Slootweg" <this@ddress.is.invalid> wrote in message
news:40f24ce8$0$221$4a441750@news.wanadoo.nl...
> yls177 <yls177@hotmail.com> wrote:
[deleted]

>
> Perhaps others can comment on what the *specific* files/directory,
> i.e. /var/spool/sockets/pwgr/client*, are/is used for.
>

The pwgr daemon is used for Password Lookups, and utilizes UNIX sockets for
communication.
From pwgrd(1M) manpage:
"When the corresponding routine in libc is called,
a request is issued to pwgrd via a Unix domain
socket connection."

These messages in an fbackup log are not something to be concerned about -
as Frank mentioned, the "files" (sockets) were present when fbackup(1M)
compiled it's list of files to be backed up, but were gone (as is the nature
of sockets) when the actual backup was attempted...

Hope that helps...

--
Steve Hamilton
Beechglen Development, Inc.
Email: steveh_NOSPAM@beechglen.com

"Steve Hamilton" <steveh@NOSPAM.beechglen.com> wrote in message news:<mCwIc.13136$1F6.6468@fe37.usenetserver.com>. ..
> "Frank Slootweg" <this@ddress.is.invalid> wrote in message
> news:40f24ce8$0$221$4a441750@news.wanadoo.nl...
> > yls177 <yls177@hotmail.com> wrote:
> [deleted]
>
> >
> > Perhaps others can comment on what the *specific* files/directory,
> > i.e. /var/spool/sockets/pwgr/client*, are/is used for.
> >
>
> The pwgr daemon is used for Password Lookups, and utilizes UNIX sockets for
> communication.
> From pwgrd(1M) manpage:
> "When the corresponding routine in libc is called,
> a request is issued to pwgrd via a Unix domain
> socket connection."
>
> These messages in an fbackup log are not something to be concerned about -
> as Frank mentioned, the "files" (sockets) were present when fbackup(1M)
> compiled it's list of files to be backed up, but were gone (as is the nature
> of sockets) when the actual backup was attempted...
>
> Hope that helps...



thanks guys!

yls177@hotmail.com (yls177) wrote in message news:<c06e4d68.0407121716.3ff08132@posting.google. com>...
> "Steve Hamilton" <steveh@NOSPAM.beechglen.com> wrote in message news:<mCwIc.13136$1F6.6468@fe37.usenetserver.com>. ..
> > "Frank Slootweg" <this@ddress.is.invalid> wrote in message
> > news:40f24ce8$0$221$4a441750@news.wanadoo.nl...
> > > yls177 <yls177@hotmail.com> wrote:
> > [deleted]
> >
> > >
> > > Perhaps others can comment on what the *specific* files/directory,
> > > i.e. /var/spool/sockets/pwgr/client*, are/is used for.
> > >
> >
> > The pwgr daemon is used for Password Lookups, and utilizes UNIX sockets for
> > communication.
> > From pwgrd(1M) manpage:
> > "When the corresponding routine in libc is called,
> > a request is issued to pwgrd via a Unix domain
> > socket connection."
> >
> > These messages in an fbackup log are not something to be concerned about -
> > as Frank mentioned, the "files" (sockets) were present when fbackup(1M)
> > compiled it's list of files to be backed up, but were gone (as is the nature
> > of sockets) when the actual backup was attempted...
> >
> > Hope that helps...
>
>
>
> thanks guys!




e /
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


my concern is with the "e /" will i be missing important information.
if i put in "i /", basically, i will be taking the whole thing.
however, i can put a series of "e filsystem" so that the whole of /
will not be taken?

yls177 <yls177@hotmail.com> wrote:
[deleted]

> e /
> 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
>
>
> my concern is with the "e /" will i be missing important information.
> if i put in "i /", basically, i will be taking the whole thing.
> however, i can put a series of "e filsystem" so that the whole of /
> will not be taken?

Yes, i.e. "i /" and then exclude ("e ...") anything you do not
need/want, not only filesystems, but also individual directories and/or
files.