Sponsored Content
Full Discussion: Need ur Help!!!
Special Forums IP Networking Need ur Help!!! Post 14908 by JammerFSU on Thursday 7th of February 2002 05:52:03 PM
Old 02-07-2002
I would problably tar the directories up that contained the data I needed on the remote server to a diskfile and then compress the diskfile and see how big the file was. It may be that your compressed file is less thanr 1/2 the size of the origional file.

For example:

Let's say my data was in /usr2/data

I would use the following command:

tar -cvf mydata /usr2/data

This command will tar all the files together that are in /usr2/data and place them in a diskfile called mydata.

Then compress the file mydata

compress mydata


Transfer the file mydata.Z over to your other server either via ftp or rcp or copy the file off to tape or diskette and UPS or FED-EX the data to your other site.

Load the file mydata.Z onto your other server and place in a directory that has enough free space to accomodate the file uncompressed.

Uncompress the file

uncompress mydata.Z

The extract the data from the file mydata


tar xvf mydata


This will place the data back into the directory /usr2/data on your remote server.

Aside from compressing the files down your best bet.. if you have to transfer that amount of data on a daily basis, it may warrant having an internet connection available full time.

T1 !!!!!! =)
 
XRLOGIN(1)						      General Commands Manual							XRLOGIN(1)

NAME
xrlogin - start an xterm that uses ssh (or optionally rlogin or telnet) to connect to a remote host SYNOPSIS
xrlogin [-l username] [-rlogin|-telnet] [xterm options] remote-host DESCRIPTION
Xrlogin opens an xterm window and runs ssh, rlogin or telnet to login to a remote host. Xrlogin automatically passes the -name argument to xterm with a value of "xterm-hostname" where hostname is the name of the remote host. This allows the user to specify resources in their server's resource manager which are specific to xterms from a given host. For example, this feature can be used to make all xterm windows to a given remote host be the same color or use a specific font or start up in a spe- cific place on the screen. Xrsh(1) passes the same string so they are compatible in this regard. Xrlogin specifies that the default title for the new xterm will be "hostname" where hostname is the name of the remote host. This and the -name argument above can be overridden with xterm-options on the command line. One could also use xrlogin's sister command xrsh(1) to open a window to a remote host. In the case of xrsh, the xterm would run on the remote host and use X as the connection protocol while xrlogin would run the xterm on the local host and use rlogin or telnet as the con- nection protocol. See xrsh(1) for a discussion of the merits of each scheme. OPTIONS
-l username When not using -telnet, use username as the id to login to the remote host. -rlogin Use the rlogin protocol to open the connection. In general rlogin is preferred because it can be configured to not prompt the user for a password. Rlogin also automatically propagates window size change signals (SIGWINCH) to the remote host so that applications running there will learn of a new window size. -telnet Use the -telnet protocol to open the connection. Use of telnet provided mostly for hosts that don't support rlogin. COMMON PROBLEMS
Make sure that the local host is specified in the .rhosts file on the remote host or in the remote hosts /etc/hosts.equiv file. See rlogin(1) for more information. EXAMPLES
xrlogin -bg red yoda Start a local red xterm which connects to the remote host yoda using rlogin. xrlogin -telnet c70 Open a local xterm which connects to the remote host c70 using telnet. SEE ALSO
xrsh(1), rlogin(1), telnet(1) AUTHOR
James J. Dempsey <jjd@jjd.com> and Stephen Gildea <gildea@intouchsys.com>. X Version 11 Release 6 XRLOGIN(1)
All times are GMT -4. The time now is 02:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy