








                    Citrix
                    WinView
                    Application Notes



                    ArcServer
                    by: Cheyenne





                    This application note is
                    for informational use only
                    and Citrix makes no
                    representations or
                    warranties with respect to
                    the contents or use of
                    this document or of any of
                    third-party products
                    discussed within.







Aug 25, 1994



Citrix Systems
210 University Drive
Suite 700
Coral Springs, FL 33071
(305)755-0559
FAX: (305)341-6880


Overview
--------

     This application note discusses the use of the Cheyenne
ArcServer product (referred to as ArcServer) with the Citrix
WinView Application Server (referred to as WinView) product.
ArcServer is backup system that is capable of backing up a wide
variety of machines and operating systems, including WinView.
ArcServer consists of three parts.  The first part is the NLM
server part.  This runs on a Novell file server that has a
SCSI tape drive in it that ArcServer supports.  The second part
is the ArcServer Manager for Windows.  This allows you to
control the backup/restore processes on ArcServer.  The Windows
Manager must run on a standard DOS/Windows system.  It will not
run under Windows on Winview due to the ArcServer Manager's
dependency on Cheyenne's version of NWIPXSPX.DLL.  The third part
of the ArcServer setup consits of a variety of ArcServer Agents.
There is a different agent for each operating system type.  The
agent you can use to backup/restore to a WinView server is
ArcServer's FS_AGENT.EXE (Full Screen OS/2 Agent).  This program
runs on the WinView server and allows the ArcServer Manager to
control backups and restores to the WinView server.

        ArcServer is capable of backing up both FAT and/or HPFS
partitions from your WinView hard disk to tape.  This product
will allow you to backup and restore your WinView systems over
a network to a tape drive on a Novell file server.  This allows
you to protect your data and setups from problems such as
hardware failure and the like.

     The intended audience for this document is a engineer who has
had hands on experience with WinView, NetWare, and the ArcServer
products.

     The scenarios described in this document have been thoroughly
tested by Citrix and Citrix believes you should have no problems
using ArcServer with WinView if you  follow carefully the information
and steps in this document.  Other variations to the scenarios
described in this document may in fact work fine, however they
have not specifically been tested by Citrix.  In order to maximize
your chance for success, you should use the specified revision
levels of all software products described in this document and
stay within the bounds of the features and functions described in
this document.

     Please note that this application note document is a living
document and will be modified as new information and versions of
the software described herein become available.  Make sure you
have the latest version of this document before you begin.  The
latest version is always available in the Citrix Forum on
CompuServe.


Requirements
------------

     To use ArcServer with a WinView application server you will need
to have the following:

     Software Requirements
          - Citrix WinView 2.2x or higher
          - Cheyenne ArcServer 5.01 or higher
          - Novell NetWare 3.11, 3.12 or 4.01
          - Standard MS DOS 6.x or higher and Windows 3.1 or higher

     Hardware Requirements
          - WinView server
               > 486DX-25 CPU or larger
               > 12 meg memory or more
               > NetWare supported network adapter
          - NetWare file server
               > SCSI Adapter supported by Cheyenne ArcServer
               > SCSI Tape Drive(s) supported by ArcServer
               >NetWare supported network adapter
          - DOS/Windows client (for running ArcServer Manager)
               >NetWare supported network adapter


Configuration Notes
-------------------
     A single Administrator class user should be configured to run the
FS_AGENT.EXE program on the WinView server.  Only one of these logins
should be active at a time, so set the user login limit for this user
to "1".  Make sure to set a password for this user, so as to prevent
unauthorized access.  Make sure this user has access to all files and
directories.

Make sure all users are logged off of the Citrix WinView server
that you intend to backup or restore to.  If you do not, you may have users
with open files that will not get backed up or restored over.  This will
cause your backup or restore to be invalid.  Any backup procedure can not
access files that are open by another user on a Citrix WinView server.
On a WinView server, you can restrict login times for users using the
CONFIG PROFILE utility.  However, it will not log out users that are logged
in all ready.  To do that you will have to use the LOGOUT *.* command to
logout those users.  A simple command file (*.CMD) can make the task simple
for you.  Make sure you have a procedure for doing this to make sure all
users are logged off of both WinView and Novell file servers that you want
to backup or restore to.  BE SURE TO EXEMPT THE WinView ADMINISTRATIVE
LOGIN USED FOR RUNNING THE "FS_AGENT.EXE" PROGRAM.  If you set it to log out
along with the rest you will not be able to get back in to do the backup!
This admin login should be the ONLY login with this privilege.

     ArcServer can backup and restore to both FAT and HPFS partitions
on you hard disk.  Keep in mind however that while FAT can be backed up
and restored to HPFS with no problem, the reverse is not always true.
HPFS has extended attributes and can long file names other than the
standard XXXXXXXX.YYY, 8.3 format you find on FAT partitions.  While
ArcServer will restore a HPFS backup to a FAT drive, you will loose
all extended attributes as well as any files that have long names.  From
this viewpoint you might want to do everything HPFS or everything FAT
so as to avoid any problems.  (Remember that if you install WinView on
a FAT partition you loose all the WinView Security benefits.  These are
only available on an HPFS partition.)  If you go with HPFS you can also
make your Novell file server support HPFS by adding OS/2 namespace.
See your Novell manuals on how to do this.

     When using HPFS, you have all the benifits of WinView security using
WinView's CONFIG ACCESS function.  However, this information will NOT be
backed up when you backup your HPFS partition.  To backup this information
so that you do not loose your security settings you must use BACKACL and
RESACL.  To backup your security settings type:
        BACKACL c:\ c:\cdisk.acl /s /file /dir
This will save the security settings for all files "/file" in all directories
"/dir" in all subdirectories "/s" in the file "c:\cdisk.acl".  You can
then just backup the "cdisk.acl" file as you would any other standard
file.  You must do this for each HPFS drive that you have that you wish
to save the security settings for.  Make sure that each file gets backed
up to tape along with the rest of the disk.  Its recommended that the name
you use represent the name of the disk or directory that it is saving the
security attributes for.  Such as "CDISK.ACL" holds the security settings
for the "C" disk drive, etc, etc.  To restore this information use RESACL.
Simply type:
        RESACL c:\cdisk.acl c:
This will restore the WinView security settings to the restored copy.  Make
sure you restore your data FIRST, and then run RESACL otherwise the restore
will remove the ACL settings on your files and directories.  (NOTE: RESACL
will NOT restore the ACLs to any file that is currently open.  You may find
that you have to boot off the WinView installation disks and ESC to a
command prompt to run the RESACL command.  This way NO files will be
opened on the hard disk and all the ACLs will be able to restore.  This
is particularly true with the WinView boot drive.)

For more information on BACKACL and RESACL see your WinView manuals and
readmes or type "BACKACL /?" or "RESACL /?" for the help.


Installation
------------

        The first part of the ArcServer installation consists of installing
the ArcServer supported SCSI adapter and SCSI tape drive into your Novell
file server.  The next part is to run the ArcServer Windows installation
program from your DOS/Windows client (NOT from WinView).  This will setup
the ArcServer Manager program on your DOS/Windows client and the ArcServer
NLMs on your Novell file server.  (Remember you'll need a SUPERVISOR login
on your Novell file server to run the ArcServer Manager).  Follow the
Cheyenne ArcServer installation manuals to install these parts.

        Once you have setup the ArcServer server on the Novell file
server (Say that 3 times fast) and the ArcServer Windows Manager on
your DOS/Windows client, you can then setup the OS/2 agent on WinView.
To do this do the following:

        1.  Using WinView's CONFIG PROFILE utility, create a new user
            in the CITRIX group called FSAGENT.  Go into FSAGENT's
            profile and make sure you have the following settings:
                Auto Disconnect login: "Sustain sessions on disconnect"
                   First user program: "C:\USR\FSAGENT\FS_AGENT.EXE"
                                       (Note: C: is the WinView boot drive)
                          Class level: "Administrator"
                  NetWare auto-login : "Disable"
                         Logins (max): "1"
                 Virtual memory (max): "10000"

             Under the "Options" menu you can then change FSAGENT's
             password to whatever password you would like.  After
             setting the password, be sure to hit F4 to save all
             your settings for FSAGENT.

        2.   Login to the Novell file server that you installed
             ArcServer on.  Change into the \ARCSERVER\AGENT
             directory.  There you will find a file called
             "FS_AGENT.EXE".  Copy this file into the user FSAGENT's
             home directory.  This should be something like
             "C:\USR\FSAGENT\", where C: is the WinView boot drive.

        3.   Next, from an OS/2 prompt type in the following command:
                CONFIG NETNAME /ADDRESS
             This will give you the network loop and address for the
             WinView server.  You will need this to refer to the
             system in the ArcServer Windows Manager.

        4.   Finally to do a backup or restore, verify that all users
             are logged out and all files closed (Or at least the ones
             that you intend to backup/restore).  Then run a WinView
             Login and log in FSAGENT.  FSAGENT should login to the
             WinView server and start up the FS_AGENT.EXE program.
             Now you can use the ArcServer Windows Manager to backup
             or restore to this WinView server.  If you wish, you
             may hit ALT-TAB at the FS_AGENT.EXE screen to create
             a new OS/2 session under FSAGENT's login and type
             "DISCONN", then hit return.  This will disconnect FSAGENT
             from your screen into the background.  It will continue
             to run and you may reconnect it to your screen by typing
             CONNECT FSAGENT.* or by re-logging in as FSAGENT.

Compatibility
-------------

     There are no known hardware or software incompatibilities when using
ArcServer with WinView at this time.  When selecting the SCSI adapter and
tape drive, be sure to select one that is compatible with ArcServer.


Diagnosing Problems
-------------------
     If it seems that the ArcServer Windows Manager can not see your
WinView server, it is likely that you have:
                A.  Not installed or setup Cheyenne ArcServe correctly.
                B.  Do not have the correct network address for the
                    WinView server.  (Run CONFIG NETNAME /ADDRESS)
                C.  Have a network cable or router problem.
                D.  Do not have the Network setup correctly in WinView.
Please verify that all these are correct and double check them.  Try using
ArcServer to backup or restore to another system or DOS client on your
network to see if it can access it correctly.  If that works then your
problem is probably B. or D., if it does not then it is probably A. or
C.






