fbackup from one mt point to another server

[boomer_2]

Hi guys,
Can i take fbackup from server1 say /tmp folder and put it in /backup of another server2..if yes then how, what is the syntax for it ?

Thankx in advance

[Jollyjet]

Hi,

The man page say's clearly that you can take a fbackup only to tape the other way is that you can use tar and zip it and move to other system or you can have mirror of the server.

[Steven Schweda · Accepted solution]

> The man page say's clearly that you can
> take a fbackup only to tape

You mean like this?:

DESCRIPTION
fbackup combines features of dump and ftio to provide a flexible,
high-speed file system backup mechanism (see dump(1M) and ftio(1)).
fbackup selectively transfers files to an output device. For each
file transferred, the file's contents and all the relevant information
necessary to restore it to an equivalent state are copied to the
output device. The output device can be a raw magnetic tape drive
(for example, a DLT tape drive), the standard output, a rewritable
magneto-optical disk, or a file.


How do _you_ interpret "or a file"?

Note that it's good in a pipeline, too:

-f device device specifies the name of an output file. If the
name of the file is -, fbackup writes to the standard
output. [...]


Thus, any previous "tar" pipeline experience
should be good here, too. (And for your
final examination, ...)


td176> uname -a
HP-UX td176 B.11.23 U ia64 1928826293 unlimited-user license

Check your own system's info.

[SANTOSH S. MHASKAR]

Hi,

As per my understanding,

U want to backup of /tmp dir of server1 to
backup location /backup on server2 using
fbackup.

Try this on server1,

# fbackup -v -f server2:/backup/server1_tmp.bkp -i /tmp

-Santosh

[boomer_2]

Hi Santosh,
After trying ur command My fbackup process went into loop and kept me asking for raw device file...
Have u tried it on ur server first???

[SANTOSH S. MHASKAR]

Hi,

I have not tried on across servers but on
same machine u can specify backup device as
a filesystem file.

I think my solution will not work in remote devices, see (man fbackup), it says Only
magnetic tapes can be remote devices.

-----------
There is slightly different behavior if remote devices
are used. A device on the remote machine can be
specified in the form machine:device. fbackup creates
a server process from /usr/sbin/rmt on the remote
machine to access the tape device. If /usr/sbin/rmt
does not exist on the remote system, fbackup creates a
server process from /etc/rmt on the remote machine to
access the tape device. Only magnetic tapes can be
remote devices. When remote DDS tape devices are used,

Hewlett-Packard Company - 5 - HP-UX Release 11i: November 2000

fbackup(1M) fbackup(1M)

the fast search marks capability is not used.
-----------------------------------


-Santosh

[Bill Hassell]

fbackup can send data to a remote system only when:

1. the remote system is also HP-UX
2. the remote system allows resmh from the local system
3. the destination is a tape (and not a file)

You can use remsh redirection and a pipe with fbackup and dd (just like other backup tools) -- not a production quality solution however.

[Steven Schweda]

> fbackup can send data to a remote system
> only when:
>
> 1. the remote system is also HP-UX
> 2. the remote system allows resmh from the
> local system
> 3. the destination is a tape (and not a
> file)

Not without some help, perhaps, but is there
any reason that a simple pipeline with
rsh/remsh wouldn't work as well as with, say,
"tar"? For example, leaving out compression,
possible "( cd xxx ; [...] )" activity, and
other frills:

fbackup -f - [...] | \
remsh remote_host ' cat > dest_file '