Backup Clients of Different Platforms

The Backup server can back up clients from a variety of platforms. This section provides configuration tips for configuring clients to enable them to back up to the Backup server.

To use clients of a different operating system than that of your Backup server, you must purchase and enable the appropriate ClientPak. See "How Backup Enforces Client Licensing " for information about ClientPaks and how the Backup server checks each client before it allows backup to begin.

Support for 64-bit filesystems exists for clients that run Solaris 2.6, AIX 4.2, and HP-UX 10.20. You can archive, backup, browse, and recover files larger than two gigabytes for clients of Solaris 2.6, AIX 4.2, and HP-UX 10.20. If your clients are not 64-bit capable, you can browse files larger than 2 gigabytes, but you cannot recover them.

UNIX Clients

On all Backup clients for UNIX, you must manually update and verify the following files:

• The /etc/hosts file must contain the Internet address of the Backup client and the Backup server, unless you use DNS or Network Information System (NIS), for example:

127.0.0.1 				localhost			loopback
137.69.8.1 				server			server.companyname.com
137.69.8.2 				client 			client.companyname.com

Backup does not automatically configure and update the /etc/hosts file. You must manually edit the file and verify that the information in this file is accurate. Do not delete or comment out the entry for the localhost loopback.

• During SunOS and Solaris client software installation, if you accepted the default directory when installing the Backup executables, the default directory should already be in your executable path. If you specify a different directory, add the directory to your executable path for root or Backup users.

  The executable path is set in the PATH environment variable. Adding the directory containing the Backup executables to your executable path allows execution of Backup commands without entering the full pathname. For example, you enter nwbackup instead of /usr/bin/nsr/nwbackup.

Windows NT Clients

On Backup clients for Windows NT, you must manually update and verify the following files:

• The %SYSTEMROOT%\SYSTEM32\DRIVERS\ETC\HOSTS file must contain the Internet address of the Backup client and the Backup server, unless you are using DNS or Windows Internet Naming Service (WINS). The HOSTS file is a simple ASCII text file with one line for each Internet Protocol (IP) address. The IP address is the first entry on the line followed by the hostname and all aliases for each machine. For example:

  127.0.0.1 localhost loopback 137.69.8.1 server server.companyname.com 137.69.8.2 client client.companyname.com

  Your %SYSTEMROOT%\SYSTEM32\DRIVERS\ETC directory should contain a sample HOSTS file that gives details about adding entries to the HOSTS file. Do not delete or comment out the entry for localhost loopback.

  If you are using DNS or WINS, verify that the DNS or WINS server has entries for both the Backup client and the Backup server.

• The SERVERS file is typically in C:\WIN32APP\NSR\RES. Backup uses the contents of this file to control who has the right to request a program to be executed on this client.

  If you want this client to back up to other Backup servers, you must add the names of the additional Backup servers to this file. One server name per line.

  If you want other clients to be able to perform directed recovers to this client, you will need to add their names to the \nsr\res\servers file. One client name per line.

  If you want to allow any Backup server to back up this Backup client, delete the SERVERS file.

  After you save your changes, you must restart the Backup Remote Exec Service to make your changes take effect.

  To allow any Backup server to back up this Backup client, delete the SERVERS file.

• The Backup client for Windows NT must have the latest service pack from Microsoft applied.

• Make sure that the following services are running:

  • Backup Remote Exec Service (nsrexecd.exe)

  • Backup Portmapper Service (also known as portmap.exe)

    Backup Portmapper Service is an optional service for Backup clients. To enable this service, start it before Backup Remote Exec Service.

Windows 95 Clients

On Windows 95 clients, you must manually edit and verify the following files accordingly:

• The HOSTS file, typically found in C:\WINDOWS, must contain the Internet address of the Backup client and the Backup server, unless you are using DNS or WINS. The HOSTS file is a simple ASCII text file with one line for each IP address. The IP address is the first entry on the line followed by the hostname and all aliases for each machine, for example:

  127.0.0.1 localhost loopback 137.69.8.1 server server.companyname.com 137.69.8.2 client client.companyname.com

• Your Windows 95 directory, typically C:\WINDOWS, should contain a sample HOSTS file, named HOST.SAM, that gives details about adding entries to an actual HOSTS file. Do not delete or comment out the entry for localhost loopback.

  If you are using DNS or WINS, verify that this DNS or WINS server has entries for both the Backup client and the Backup server.

• The SERVERS file is in C:\PROGRAM FILES\LEGATO\NSR\RES. Backup uses the contents of this file to control who has the right to request a program to be executed on this client.

  If you want this client to back up to other Backup servers, you must add the names of the additional Backup servers to this file. One server name per line.

  If you want other clients to be able to perform directed recovers to this client, you will need to add their names to the \nsr\res\servers file. One client name per line.

  If you want to allow any Backup server to back up this Backup client, delete the SERVERS file.

  After you save your changes, you must restart the Backup Remote Exec Service to make your changes take effect.

  To allow any Backup server to back up this Backup client, delete the SERVERS file.

• The Windows 95 client must have the latest service pack from Microsoft applied.

• Make sure that the Backup Scheduled Backup (wtcpschd.exe) is running. Put a copy of Backup Scheduled Backup in the Startup folder to enable scheduled backup to run automatically.

NetWare Clients

On NetWare clients, you must manually update and verify the following files accordingly:

• The SYS:ETC\HOSTS file must contain the internet address of the Backup client and the Backup server. The HOSTS file is a simple ASCII text file with one line for each IP address. The IP address is the first entry on the line followed by the hostname and all aliases for each machine. The HOSTS file should also contain an entry for localhost, for example:

  127.0.0.1 localhost loopback 137.69.8.1 server server.companyname.com 137.69.8.2 client client.companyname.com

  ---

  Caution -

  The TCP/IP hostname and the NetWare server name must be identical for the Backup for NetWare client. In the previous example, the NetWare server name replaces the value represented by "client."

  ---

• TCP/IP must be loaded and bound correctly in the AUTOEXEC.NCF, for example:

  Load and bind TCP/IP before Backup is installed, or some configuration files are not properly updated.

• Other files that affect Backup operation on a TCP/IP network and that are automatically configured during the Backup installation are SYS:ETC\RPCUSERS, SYS:ETC\SERVICES, SYS:ETC\RPC, SYS:ETC\GATEWAYS, SYS:ETC\NET\NETWARE\SERVICES, and RPCNET.CFG, typically found in SYS:NSR.

  Other RPC-based products can also use many of these files, so they might already exist on a client before you install Backup. If the files exist, Backup does not overwrite these files during installation. In most cases, files provided by other RPC-based software work with Backup.

Macintosh Clients

A Macintosh client must meet the following requirements:

• Macintosh System Software Release 7.1, 7.5.1, or 7.5.2 is installed.

• MacTCP Release 2.0.6 is installed.

• MacTCP has Ethernet selected (not EtherTalk).

• Domain Name Services (DNS) are available to the Macintosh. You need to manually configure DNS correctly.

  The domain name and the IP address must match the information in the /etc/resolv.conf file on the DNS server. The /etc/resolv.conf file points your machine to the correct name server. If there is no resolv.conf file, the resolver uses the nameserver on the local machine, for example:

  domain companyname.com nameserver 137.69.8.2

• The TCP, DNS, and UDP utilities are available for use on the Macintosh. It is advisable to also have the ping utility available for troubleshooting.

• You must specify the fully qualified name of the Backup server on the Macintosh client.