Title: Quick Guide to Setup a Cross-Platform SAN - SupportConnect

Implementation StepsIP connectivity and name resolution among all servers in the Cross-Platform SAN isessential. To achieve this in many environments, update the IP hosts file on each serverparticipating in the Cross-Platform SAN, so that each server's name and IP address ispresent in each servers IP hosts file. The IP hosts file can be found in the followingfolders:Windows\winnt\system32\drivers\etcUNIX/etcon Solaris, HP, AIX, andTru64 machinesTest the connectivity by using the ping utility on each server, making sure you can pingeach Cross-Platform server-by-server name, not just their IP address.WindowsUNIX

WindowsAt the command prompt type:#ping UNIXOn Solaris, HP, AIX, andTru64 machines, at theconsole commandprompt, type:#ping Details are given in the following sections to configure your Cross-Platform SANservers.

UNIX Installation and ConfigurationFollow the steps listed below to install the SAN Option on a UNIX platform.1. Log on to the UNIX machine that will be used as the primaryserver.2. Run csetup. This script invokes sansetup, which guides youstep-by-step through the SAN configuration. When the systemprompts you for the primary server name, enter the name ofyour local server.3. The system will then prompt you for the number of distributedservers. Enter this number.4. The system will then prompt you for the distributed servernames, one at a time. Enter the names of all of the other UNIXservers that you want to use in the SAN loop.5. The system will now ask you to add the Windows primaryserver as the distributed server in the SAN. Enter the name ofthe Windows primary server configured in Step 2. Thisinformation will be saved in sanpeer.cfg, under the directory:\BrightStorEB\config6. At this point, SAN-related processes now start. There shouldbe two sanpeer processes, and one sanghost process on theprimary server.7. Complete the csetup to finish the changer configuration, andstart all of the BrightStor Enterprise Backup services. Allowthe system to initialize and inventory all of the libraries in theSAN loop.

8. After the primary server has initialized, run csetup on each ofthe distributed servers, one at a time. Make sure that the orderin which you enter the server names on the primary server isthe same on all of the distributed servers.If the number of distributed servers is large, you may copy thesanpeer.cfg file from the UNIX primary server to all of theUNIX distributed servers. This will ensure that the order ofUNIX distributed server names will be identical on all themembers.You will see only two sanpeer processes on the distributedservers. The sanghost process does not run on the distributedservers. After the SAN configuration is completed on thedistributed servers, continue with the library configuration (asperformed on the primary server), and then start the BrightStorEnterprise Backup processes on that server.Notes:• Before starting BrightStor Enterprise Backup on one server,make sure that all of the processes (on the previouslyconfigured server) are up and running, and that the serversees the devices properly.• In a Cross-Platform environment, the UNIX primary serveracts as the primary server. On Windows NT, the primaryserver acts as a distributed server to the UNIX primaryserver. To set up this configuration, from the sansetupprogram, you must answer yes to the following question inthe script:

We can add your NT primary server in a SAN environment to ourlist of UNIX Distributed Servers in a SAN environment. Pleasenote that the NT server must be a SAN NT primary server, not aSAN NT distributed server.Do you wish to add any SAN NT primary server at this time?[y,n,?,q] yWhat is the name of your SAN NT primary server? w2k_svrThis is your configuration.[MemberNames]## Primary Server ##server1=UXLEXUS_SC430server2=UXRX330server3=UXPathfinderserver4=NTHackie[EnterpriseSetup]Is your primary server, number of distributed servers, and thenames of your distributed servers correct? (y|n|q) yYour SAN setup has been configured.To configure your Windows server(s) on a Cross-PlatformSAN, follow the steps in the next section, “WindowsInstallation on a Cross-Platform”.

Windows Installation on a Cross-Platform SANThe BrightStor Enterprise Backup SAN Option for NT/2000/2003 must be used withBrightStor Enterprise Backup.The BrightStor Enterprise Backup Tape Library Option for NT/2000/2003 must be run ona computer with Windows NT4 with SP6a, Windows 2000 server, or Advanced Serverwith SP1. Follow the steps listed below.1. Install BrightStor Enterprise Backup for Windows NT/2000/2003 on each of theWindows servers participating in the Cross-Platform SAN.2. Install the Tape Library Option (TLO) on each Windows server participating inthe Cross-Platform SAN. Configure your Tape Library on the Windows server you planto be the primary Windows server.3. Install the SAN Option for Windows NT/2000/2003 on each of the Windowsservers participating in the Cross-Platform SAN. After all of the Windows servers havethe SAN Option installed, you can go to any of the Windows servers and run the SANOption Configuration.A. If any of the Windows servers do not display in the AvailableServers list, you can add the missing servers by clicking onthe Add Servers button. Select a desired server, and thenclick OK. The server should then appear in the AvailableServers list.B. You must first choose a Windows primary server. Select theserver you want to make the Windows primary from the rightpane, and then click the Make Primary button.C. Select each remaining Windows server from the right pane, andassign them as distributed servers under the Windows primaryserver. Selecting the Windows server from the right pane,highlighting the Windows Primary on the left side, and thenclicking the Assign Distributed button.4. Refer to the chapter “Installing and Configuring the SAN Option on a UNIXplatform” for information on how to install and configuring the UNIX SAN servers.5. After the SAN Option for Solaris, HP, AIX, and Tru64 are installed andconfigured on all of your UNIX servers, run the SAN Configuration Utility from yourWindows primary server.A. To add a UNIX server, from the BrightStor Enterprise BackupSAN Configuration window, click Add Servers.

The Add Servers dialog appears. For example:B. In the Server Name field, enter the name of your UNIX primaryserver, and in the Server Type group box, click the UNIX radiobutton.Select your Server Name from the list, and click OK. TheBrightStor Enterprise Backup SAN Configuration window reappears,with the primary server now appearing in the right pane.

C. Repeat Steps A and B to add additional servers.D. Define the UNIX primary server as the Cross-Platform primaryserver by highlighting the UNIX primary server in the right pane,and clicking on the Make Primary button.When you click Make Primary, the s UNIX primary server nowappears in the left pane.

F. Repeat Step D and E to assign the remaining UNIX distributedserver(s). When you are finished, you window should appearsimilar to the following:G. Highlight your primary Windows server, and drag and drop it onthe top of UNIX primary server. For example:

The final configuration should look like a tree structure containingall of the UNIX (Solaris, HP, AIX, and Tru64) servers andWindows servers. The UNIX primary server is now configured asthe Cross-Platform primary server.The UNIX primary server is treated as the Cross-Platform primaryserver that will handle the inventory, initialization, andmanagement of the tape device(s).All UNIX distributed servers and the Windows primary serverwill act as distributed servers under the Cross-Platform primaryserver. Windows distributed servers will continue to act asWindows distributed servers under the Windows primary.6. Launch BrightStor Enterprise Backup for Solaris, HP, AIX, and/or Tru64 on theCross-Platform UNIX primary server.

Notes:7. After the Cross-Platform primary server has fully initialized the shared tapelibrary (the slot information is displayed in the Device Manager), you can start BrightStorEnterprise Backup on the remaining UNIX distributed servers and the Windows primaryserver, one at a time.8. After BrightStor Enterprise Backup is started on the Windows primary server,you can start BrightStor Enterprise Backup on the Windows distributed servers.• BrightStor Enterprise Backup Cross-Platform Manager cannot beinstalled on the same Windows machine that has BrightStorARCserve Backup Version 9 Cross-Platform Manager installed.For example, if you use Windows server “A” to installBrightStor ARCserve Backup Version 9 (including SAN Optionand Cross-Platform Manager), instead of using the same server“A” to install BrightStor Enterprise Backup, Tape Library andSAN Option, you need to find another server to install theseapplications.• Make sure there is no activity taking place on the shared tapelibrary before starting a UNIX distributed or Windows primaryserver.• Make sure all of the UNIX distributed servers are added andassigned as Cross-Platform UNIX distributed servers in theWindows SAN Option Configuration Utility.• If “camediad” is ever restarted on the UNIX primary server,“camediad” on ALL distributed UNIX servers must be restarted.Also, the Tape Engine on the primary Windows server anddistributed Windows server(s) must be restarted as well.• All UNIX and Windows servers must have BrightStor EnterpriseBackup, Tape Library Option, and the SAN Option installed.

General Information for Windows NT/2000/2003• If a shared device is participating in a RAID configuration,it will be automatically removed from that configurationwhen it is configured as a Cross-Platform device. Anylocal devices participating in RAID configurations willremain intact.• If a shared Tape Library is configured as a virtual library,this configuration needs to be removed before configuringthe library in a Cross-Platform SAN. Please refer to theBrightStor Enterprise Backup Tape Library Option ReleaseNotes for virtual library support.• Only one active Windows primary server can be physicallyattached to the same SAN. In the event that a primaryWindows server is no longer available, a distributed servercan be removed from its primary Windows server by rightclicking on the distributed Windows server and selectingthe option Force to Remove.• Please be sure to run \Device Configuration\TLO Setup toconfigure your shared tape library before you assign thenew primary through the SAN Configuration Utility.