Virtual TapeServer 6.04.04 for NonStop Servers Supplemental Installation Guide

Enabling Instant DR and AutoCopy | 19
4. Set up and edit the /home/bill/.rhosts file to define aliases for the IP addresses. Perform
this step on the destination server for each source VTS server.
a. At the command prompt, log in.
b. Become root:
su -
c. Create the /home/bill/.rhosts file.
d. Enter chown bill /home/bill/.rhosts to change the ownership of the file to bill.
e. Enter chmod 600 /home/bill/.rhosts to set the privileges to read and write for bill.
f. Open the /home/bill/.rhosts file for editing using a text editor, such as vi.
g. Scroll down to the last line in the file.
h. Add the name of all other VTS servers in this file. For example, on the Los Angeles
VTS server, enter boston.
i. Save and exit the file.
5. If the VTS server’s eth1 port is on a different subnet than eth0, you must add a static
route that will persist after reboot. To add a persistent static route, complete these steps:
a. Create a file named route-interfaceX in the /etc/sysconfig/network-scripts/
directory, where interface is the interface name and X is the interface number. Create
a separate file for each of the available interfaces. For example:
/etc/sysconfig/network-scripts/route-eth0
/etc/sysconfig/network-scripts/route-eth1
b. In each file, add the following entries to specify the gateway, netmask, and IP
address:
GATEWAYN=gateway_addr
NETMASKN=netmask
ADDRESSN=IP_addr
where N defines the route entry number and should be the same on all of the entities.
Example:
GATEWAY0=192.168.1.1
NETMASK0=255.255.255.0
ADDRESS0=10.10.10.0
GATEWAY1=192.168.1.1
NETMASK1=255.255.255.0
ADDRESS1=20.20.20.2
6. Set up and authorize secure shell (SSH) if you are configuring VTS for AutoCopy or if you
wish to secure communication for Instant DR.
a. At the command prompt, become bill:
su - bill
b. Export the SSH socket by entering this command:
ssh-agent