Arkeia Network Backup FAQ

Document version: 1.02 (built on 01/29/2003)

*** the three stars mark the answers updated from the Arkeia 4.2 FAQ
which is available at http://www.arkeia.com/arkeiafaq42.html

1. General

2. Concepts and Features

2.1. Arkeia Architecture and Terminology

2.2 Features

2.3 Database

3.1. General

3.2 Backup Server

3.3 Specific Hardware

3.4 Client Machine

1. General

2.1. Arkeia Architecture and Terminology

2.3 Database

3. Installation, Configuration and Maintenance




3.1. General



3.1.1. Which packages do I need to install?

*** Unlike the previous Arkeia 4.2 version, Arkeia 5 requires only a single package installation. For each platfrom the package contains all available components (server, client, interface). You can download the latest version of Arkeia for your platform @ http://www.arkeia.com/download.html

3.1.2. How do I install/upgrade Arkeia?

*** Depending on the OS platform, Arkeia offers 3 different installation package formats. To install them follow these examples: - rpm (Linux) rpm -Uvh arkeia-5.0.14.i386.rpm - tar.gz (Unix) gzip -d arkeia-5.0.14.tar.gz tar -tvf arkeia-5.0.14.tar cd arkeia-5.0.14 ./install - zip (Windows, Novell) unzip arkeia-5.0.14.zip chdir arkeia-5.0.14 run SETUP.EXE

3.1.3. How do I enter the Arkeia license key?

*** You enter the Arkeia license key(s) from the GUI: Administration -> Licenses After entering the Arkeia 5 license (product ARK50) the interface asks you to restart the GUI. You can check your license information (total number of clients, total number of flows, expiration date, ...) by selecting the ARK50 product.

3.1.4. How can I change the default installation location of Arkeia (Linux/Unix)?

*** The default installation directory is /opt/arkeia. To move Arkeia into another location you can set the new Arkeia 5 installation path in the file /etc/opt/arkeia/ARKEIA_DIR. Another way is to make a soft link from the new location to the default location (example: ln -s /arkeia /opt/arkeia).

3.1.5. How can I change the default installation location of Arkeia (Windows)?

*** The default installation directory of the Arkeia client for Windows is c:\Program Files\Arkeia\Arkeia. You can change this at installation time after uninstalling.

3.1.6. How can I implement Arkeia on a network running DHCP?

*** To configure a client machine managed by DHCP add the "VIRTUAL_HOSTNAME" variable in its arkeiad.cfg file. So the client declares to the backup server with the VNAME property added in rhost.lst file. Therefore all operations are made using the VNAME value and the hostname and IP address assigned by DHCP can change at any time.

3.1.7. How can I configure Arkeia to not use the FQDN hostname?

*** Unlike Arkeia 4.2, by default Arkeia 5 doesn't truncate the domain name from each machine name. To force Arkeia 5 to use the short hostname add in arkeiad.cfg file the variable STRIP_DOMAIN set to "1". Another way is to use the VIRTUAL_HOSTNAME variable in arkeiad.cfg file.

3.1.8. When multiple NICs, how do I assign Arkeia to one network card?

*** To tell Arkeia to use a secondary network interface, you should define a hosts.cfg file pointed by the NLP_HOSTFILE parameter in the arkeiad.cfg file. NLP_HOSTFILE specifies a host file which redefines the association between the IP address to use and the real hostname of the machine. Here an example where the main network is 192.168.20 and the backup network is 192.168.3: Name: backsuse.arkbackup.com Address: 192.168.3.8 Name: testsuse.knox.com Address: 192.168.20.8 Name: testslac.knox.com Address: 192.168.20.4 Name: backslac.arkbackup.com Address: 192.168.3.4 On both backup server (testsuse) and client (testslac) configure this: root@testXXXX:/opt/arkeia/arkeiad> grep NLP arkeiad.cfg NLP_HOSTFILE "/opt/arkeia/arkeiad/hosts.cfg" root@testXXXX:/opt/arkeia/arkeiad> cat hosts.cfg "192.168.3.8" "testsuse.knox.com" "192.168.3.4" "testslac.arkeia.com" root@testXXXX:/opt/arkeia/arkeiad> cat admin.cfg testsuse.knox.com If a machine cannot be found in "NLP_HOSTFILE" file, Arkeia will use the standard hostname resolution.

3.1.9. How do I backup across a firewall?

*** These are the core steps to configure Arkeia with a firewall. a) Allow connections on port 617 from the client to the backup server b) Allow connections on port 617 from the backup server to the client c) By default, the file /opt/arkeia/arkeiad/auth_ARKFS.cfg on client and backup server should read: ARKFS.* ALLOW * * You will find additionnal information (PORT range configuration, ssh configuration), in the User Manual, Chapter 1, section 3 "Configuring Arkeia to work from behing a firewall".

3.1.10. How to use different TCP port numbers with Arkeia?

*** By default the Arkeia processes are listen on the TCP port number 617. With Arkeia 5 you can set different port numbers between several machines. Note that the current port number is listed in the rhost.lst file in the PORT property. - To change the TCP port number on a machine: Delete the current arkboot configuration: /opt/arkeiad/bin/arkeiad remove Add in the /opt/arkeia/arkeiad/arkeid.cfg file the "PORT_NUMBER" parameter with the new TCP port number as in this example: root@testsuse:/opt/arkeia/arkeiad> grep PORT_NUMBER arkeiad.cfg PORT_NUMBER "637" Restart arkeiad: /opt/arkeiad/bin/arkeiad start - To specify on each client machine that the backup server uses a specific port number, add the new value in the admin.cfg file like in this example: root@testslac:/opt/arkeia/arkeiad> cat admin.cfg testsuse.knox.com:637

3.2 Backup Server



3.2.1. How do I configure the Arkeia Backup Server?

*** Please reference the Arkeia User Manual for complete instructions on how to configure the Arkeia backup server. For the quickest way to configure your first Arkeia backup using a standalone drive, ensure your OS detects your backup devices, and reference the instructions in the Arkeia Quickstart Guide. Complete the library configuration with the help of the User Manual, Chapter 10, Advanced Hardware.

3.2.2. Should I allocate a dedicated SCSI Host Adapter for my backup device?

Yes, Arkeia recommends you allocate a dedicated SCSI Host Adapter for your backup devices. You will gain the best performances with Arkeia and you will prevent SCSI bus access conflicts between the tape drive(s) and other devices.

3.2.3. Why does the library unit have to be configured in Random Access mode?

The Random Access mode means that Arkeia can order the library hardware to change the tapes (sometimes called SCSI or Changer mode). The reverse mode often called Sequential means that the library hardware itself will change automatically the tape when it becomes full. Check the documentation provided with your library to set it in Random Access mode.

3.2.4a. Is my backup hardware detected by the OS (Linux)?

*** On Linux check the dmesg output for lines in the form of: Vendor: QUALSTAR Model: TLS-4480 Rev: 2.12 Type: Medium Changer ANSI SCSI revision: 02 Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 8 Vendor: SONY Model: SDX-500C Rev: 0108 Type: Sequential-Access ANSI SCSI revision: 02 Attached scsi tape st0 at scsi1, channel 0, id 1, lun 0

3.2.4b. Is my backup hardware detected by the OS (Solaris)?

*** On Solaris check the dmesg for lines in the form: Mar 21 16:24:42 pod unix: /pci@1f,0/pci@1/scsi@1/st@3,0 (st3): Mar 21 16:24:42 pod Mar 21 16:24:42 pod unix: st3 at glm0: Mar 21 16:24:42 pod unix: target 3 lun 0 Mar 21 16:24:42 pod unix: st3 is /pci@1f,0/pci@1/scsi@1/st@3,0 Mar 21 16:24:52 pod unix: sst1: found Changer device at tgt2, lun0 Mar 21 16:24:52 pod unix: sst1: Vendor/Product ID =3D3D SPECTRA 215 Mar 21 16:24:52 pod unix: sst1 at glm0: Mar 21 16:24:52 pod unix: target 2 lun 0 Mar 21 16:24:52 pod unix: sst1 is /pci@1f,0/pci@1/scsi@1/sst@2,0 An entry in /dev should point to the right devices in /devices: lrwxrwxrwx 1 root other 45 Mar 21 16:24 /dev/rmt/0hb -> ../../devices/pci@1f,0/pci@1/scsi@1/st@3,0:hb lrwxrwxrwx 1 root root 50 Mar 21 16:43 /dev/rsst2 -> ../devices/pci@1f,0/pci@1/scsi@1/sst@2,0:character

3.2.4c. Is my backup hardware detected by Arkeia? (arkdetect)

*** Check for attached tape libraries and tape drives from the GUI Main Menu > Hardware Menu > Detect Or run the "arkdetect" utility.

3.2.5. Do I have to configure my tape drive?

*** The arkdetect feature helps to find the specific information on setting up the tape drive. You declare your tape drive(s) from the "Hardware -> Drives" menu. The rewind device should point to a unix device detected by the OS. In addition you have to associate your tape drive into a drivepack.

3.2.6. How do I configure my library?

*** The arkdetect feature helps to find the specific information on setting up the library medium changer. From the "Hardware -> Libraries" menu create your library configuration: - Select the Type which matches your library license. - Declare the control device which points to the medium changer. - Attach the tape drive(s) using the "Manage drives" menu. - Assign your Arkeia tapes to a slot using the "Manage slots" menu.

3.2.7. How do I configure a cleaning tape in a library?

*** - Under the GUI > Hardware > Tapes section, create a cleaning tape. - Under the GUI > Hardware > Libraries section, assign the cleaning tape to a slot.

3.2.8. How do I configure a library on Solaris?

Arkeia for Solaris needs the sst pass-thru driver to control the library changer device. The sst driver package is provided at http://www.arkeia.com/download.html: sst32.tar contains the driver for Solaris 2.6 and 7 booting in 32 bits mode. sst64.tar contains the driver for Solaris 7 and 8 booting in 64 bits mode. Each package contains the installation instructions in "installsst.txt" file. Between the 32 bits and 64 bits architectures, the main difference is the installation directory: /usr/kernel/drv/ for the 32 bits driver /usr/kernel/drv/sparcv9/ for the 64 bits driver

3.2.9. How do I configure Arkeia on Solaris Multi-Processor machine?

A problem with the Architecture of the Sun Solaris Operating system can result in performance bottlenecks on large Sun systems running Arkeia Server. A Sun patch is available which lifts the single mutex restriction. (patch number 103734 for Solaris 2.5.1). This patch should be applied to SUN machines that have four or more CPUs and are running Arkeia server. In conjunction with this patch a setting needs to be made in Arkeia.prf to make use of the multiple message queues: "ARK_NB_QDLG" "n" The value of n will need tuning to see at what point optimum performance is obtained. A good starting point is to set the value to the number of available flows.

3.2.10a. How do I backup the Arkeia Database?

*** Save the Arkeia database using a dedicated backup. Select the sysinfo:/dbase plugin and perform a backup on a DEDICATED TAPE which includes the database configuration and the index of the backup server. - the configuration (backup_server_name!sysinfo:/dbase/f3) - the index (backup_server_name!sysinfo:/dbase/o3dbtree/backup_server_name) You can save on a regular tape the client indexes: - backup_server_name!sysinfo:/dbase/o3dbtree/client_name).

3.2.10b. How do I restore the Arkeia Database?

*** To restore the index of a client machine from the GUI, select the backup_server_name!sysinfo:/dbase/o3dbtree/client_name item. To restore the backup server configuration and its index you need the disaster recovery feature.

3.2.11. Do I have to change the i-node configuration for the Index Database?

In most cases, if the disk space is enough to hold the database, then the i-node number is enough. But, if you have a server which contains lot of directories with few files you may have to change the i-node configuration for your index database. Arkeia requires 4 inodes per directory: - 2 for the directory itself - 1 for o3cpnt - 1 for a lock file Note: some file systems, like Reiser FS, accept an infinite number of i-nodes.

3.2.12. How should I prepare my disk partition for the Index Database?

The Index Database size requires between 1% and 3% of the saved data depending of the backup history. Arkeia considers that the following disk space are enough: 100 MB for 10 GB of data to save 4 GB for 400 GB of data to save 10 GB for 1 TB of data to save

3.2.13. How do I define and configure a backup policy?

*** The best way to understand how to build a backup policy with Arkeia is to reference the Arkeia 5 User Manual, Chapter 8, Periodic Backup.

3.2.14. How do I configure the E-mail notification?

To receive an email notification when Arkeia needs a new tape or a backup is finished: - set the "Use emails" field in the backup definition, - configure the "Email" address field for the user which owns the backup (in User Management screen).

3.2.15. How do I personalize the e-mail notification?

*** Add the variable ARK_MAILCMD in the file server.prf. The default value is: ARK_MAILCMD "cat %F | mail -s %S %T" At execution time the template is replaced by something like: cat /opt/arkeia/server/dbase/f3tmp/arkrst3e1b4228/ark.jl2 |\ mail -s 'Arkeia backup report' 'backupadmin@your.domain.net' the percent (%) macros will be replaced by Arkeia as following: - %F: a temporary file containing the body message - %S: the subject (you cannot replace it at this stage) - %T: the recipient ("To:" field) as specified in the email field of the user screen.

3.2.16. How do I force Arkeia to use a specific tape?

Arkeia will choose a tape in the tape pool assigned to the backup. By default, you cannot designate which tape will be used. But, there are three ways to force Arkeia to use a specific tape. - Standalone drive: load the drive with the Arkeia tape you want to use. Make sure this tape has been recycled. - Library: place only the tapes which you want Arkeia to use in the library slots. Make sure to remove any unwanted tapes from the library slots. - Periodic backup: A more complex solution is to configure a periodic backup per day. For each periodic backup, assign a unique tape pool containing only one tape.

3.2.17. Can I force Arkeia to use whatever tape which is in the drive?

If you prefer that Arkeia overwrites a previous backup, rather than backing up nothing, you can set it up so that it overwrites data and labels tapes automatically. Case 1 - On a new non labeled tape: Arkeia will back up without problem if the Arkeia tape definition was never used. It would be better that you label the tape before using it. Case 2 - On a recycled Arkeia tape: Arkeia will back up on recycled tape with its original label (e.g. if Arkeia plans to back up with Daily Tape4 while there is the Recycled Daily Tape3 in the drive, Arkeia will backup on Daily Tape3). Case 3 - On a valid Arkeia tape: you must recycle the Arkeia tape before running the backup (case 2). You can automate the recycle operation by configuring a command before backup which will perform arkc commands similar to these: to read the tape label : arkc -drive -read -D name=ArkDrive (assume it returns tpname=Daily Tape 3) to recycle the tape : arkc -tape -recycle -D name=[Daily Tape 3] Please note: before implementing such a backup policy, remember that you may erase a wrong tape.

3.2.18. How do I assign a tape to another pool?

You can move a tape to another pool only if this tape is "Free". From "Tapes management" or the "Tapes in pool" screen, select tape(s) and press the "Modify tape(s)" button. Select the pool section, and assign the tape to the desired tape pool. Finally refresh the "tapes" screen to verify the change.

3.2.19. Never delete the o3dbtree/o3_cpnt file

*** Never delete the /opt/arkeia/server/dbase/o3dbtree/o3_cpnt file to fix a license issue as you did with Arkeia 4.2. Use the arkmvhost and arkrmhost commands instead. Since Arkeia 5 the o3dbtree/o3_cpnt file contains the history of the hostname changes. If you suppress this file Arkeia will not restore the files backed up from an old machine name.

3.2.20. How do I move the Index Database to a new location?

*** To move the Index Database to a new location make a tar copy of the o3dbtree directory. Next, in /opt/arkeia/server/dbase directory create a soft link from o3dbtree to the new location. Ensure your new directory contains the .ARK_NOBACKUP file

3.2.21. How do I migrate the backup server to a new machine?

*** To move your backup server onto a new machine without losing your configuration and history, make a tar copy of the /opt/arkeia directory then reinstall Arkeia on the new machine. If the hostname of the new backup server changes, use the arkmvhost command to update the Arkeia database with the new hostname. Verify that the tape drive and library devices don't change on the new machine. Finally change the admin.cfg file on each client machine to reflect the new backup server name.

3.2.22. How do I change the hostname of the backup server?

*** Do not remove the o3dbtree/o3_cpnt file. Use the arkmvhost command to update the Arkeia database with the new host name of the backup server (configuration and index).

3.2.23. How do I rename a machine and preserve its license token?

*** Do not remove the o3dbtree/o3_cpnt file. Use the arkmvhost command to update the Arkeia database with the new hostname of the client machine (configuration and index).

3.2.24. How do I retire a machine to reuse its license token?

*** Do not remove the o3dbtree/o3_cpnt file. Use the arkrmhost command to suppress a client machine.

3.3 Specific Hardware



3.3.1. How do I setup the HP Surestore DAT 24x6 on Solaris?

There is an option switch on the DAT 24X6 autoloader and HP1553 (older) autoloader. For the external autoloader: Solaris recommends setting the value to "5". Arkeia requires this value to be set to "7". For the internal autoloader: You will need to open the case and manually set your DIP switch settings. SWITCH 1: ON SWITCH 2: ON SWITCH 3: ON SWITCH 4: OFF For details please examine this Answer http://support.arkeia.com/cgi-bin/arkeia.cfg/php/enduser/std_adp.php?p_faqid=79

3.3.2. How do I Configure an AIT Drive on Linux?

*** Arkeia 5 manages both the variable and the default 512 fixed tape block size for the AIT drives. Unlike version 4.2, there is no longer a need to force the AIT tape block size to variable. But if you migrate a v4.2 backup server configured with variable block size, to enable Arkeia 5 to read the v4.2 tapes, you have either to apply the 3.3.6 FAQ or to report the configuration (SET_BLKSIZE) in this file: - /opt/arkeia/server/dbase/f3drv/drvtypes.lst ITEM { "NAME" "STD_AIT" "FORM_FACTOR" "EXB" "SET_BLKSIZE" "0" } ITEM { "NAME" "AIT_AUTOLOADER" "FORM_FACTOR" "EXB" "DONT_UNLOAD" "1" "SET_BLKSIZE" "0" } Note: The AIT_AUTOLOADER drive type is used only if the AIT2 drive is attached to a Sony AIT Auloloader. To take into account this change, you have to stop/restart Arkeia (both the interface and arkeiad).

3.3.3. How do I Configure an AIT drive on Solaris?

*** On Solaris 2.4 and higher, to enable the st driver to manage the AIT drive with a variable tape block size, apply the configuration recommended by Sony in the "UNIX Configuration Guide v2.xx 7/25/2001". The /kernel/drv/st.conf file should contain these lines: tape-config-list=3D "SONY TSL-A500C", "Sony AIT2 8mm Autoloader", "SONY_AIT", "SONY SDX-500C", "Sony AIT2 8mm", "SONY_AIT", "SONY TSL-A400C", "Sony AIT1 8mm Autoloader", "SONY_AIT", "SONY SDX-400C", "Sony AIT1 8mm", "SONY_AIT", "SONY TSL-A300C", "Sony AIT1 8mm Autoloader", "SONY_AIT", "SONY SDX-300C", "Sony AIT1 8mm", "SONY_AIT"; <- notice the semi-colon! /*---- (4 spaces between SONY and SDX)*/ SONY_AIT = 1, 0x36, 0, 0xd679, 4, 0x00, 0x00, 0x00, 0x00,0; The tape-config-list requires the entry which matches the inquiry string returned by your particular AIT model.

3.3.4. How do I Configure an HP LTO Ultrium drive on Linux?

*** The Ultrium LTO works better when configured with a fixed tape block size of 1024 (the default is variable block size on HP models). By default Arkeia 5 for Linux configures the tape block size to 1024. This is done in the file /opt/arkeia/server/dbase/f3drv/drvtypes.lst with the SET_BLKSIZE property into the LTO drive type as following: ITEM { "NAME" "LTO" "FORM_FACTOR" "LTO" "TIME_BEFORE_CLEAN" "40" "SET_BLKSIZE" "1024" } If you migrate from a v4.2 server where you didn't apply the Arkeia recommendation to fix the tape block size for the HP LTO Ultrium drive, Arkeia 5 will not read your v4.2 tapes. To enable Arkeia 5 to read LTO tape written with a variable tape block size change the SET_BLKSIZE property to "0" in the drvtypes.lst file and restart Arkeia (both the graphic interface and arkeiad). See also the FAQ 3.3.6

3.3.5. How do I Configure an LTO Ultrium drive on Solaris?

Set the LTO Ultrium drive to a fixed block size value of 1024. For example, here is the setting of the /kernel/drv/st.conf file for an HP LTO Ultrium drive (the significant values are 1024 and 0xd638): tape-config-list = "HP Ultrium", "HP Ultrium", "ULTRIUM", (there are 6 significant spaces between HP and Ultrium here) ULTRIUM = 1,0x36,1024,0xd638,4,0x00,0x00,0x00,0x40,3; name="st" class="scsi" target=X lun=0; (where X is the SCSI target address of the device you have attached.) Reboot the system as following: # reboot -- -r Make sure you include the -r switch, so that Solaris will redo the hardware detection.

3.3.6. How to manage the Tapes after changing the tape block size?

*** After changing the tape block size (from fixed to variable or the reverse), Arkeia cannot restore tapes made by using the original tape block size, although it can read the labels. So we need a procedure to manage both tapes (old and new tape block size). After changing the tape block size configuration, delete all free tapes. Re-create the tapes with a new basename and re-label them to be sure Arkeia can work with these tapes. If the Arkeia restoration asks for an old tape (just check the name), come back to the old configuration, stop and restart the Arkeia GUI and perform the restoration.

3.4 Client Machine



3.4.1. How do I exclude directories during backup?

*** There are two ways to exclude a directory from being backed up: Solution 1: Add a file named .ARK_NOBACKUP on Unix based file system, or NOBACKUP.ARK on DOS based file system in the directory you want to exclude. Note that for backward compatibility Arkeia 5 still recognizes the old 4.2 names (e.g. .OPB_NOBACKUP and NOBACKUP.OPB). Solution 2: Add an exclusion filter in the tree option screen. Example of exclusion filter: To exclude the directory "netscape/cache" => (^.*/netscape/cache.*$) To exclude two directories ("netscape/cache" and "netscape/xover-cache") => (^.*/netscape/cache.*$)|(^.*/netscape/xover-cache.*$)

3.4.2. How do I backup network file systems (NFS, SAMBA)?

By default, Arkeia does not backup NFS files. To force Arkeia to backup Network File System, select the 'All file systems' option on the Savepack option screen in the File System Allowed entry field. The 'All file systems' option is only available with the Arkeia Professional version.

3.4.3. How do I setup compression with Arkeia?

*** By default, the compression is activated. By using the Arkeia GUI from the "Savepack Option" or "Tree Option" screens, you can set the desired compression type allowed (LZ1 or LZ3_3, LZ1 only, LZ3_3 only), or you can disable the compression with the "No compression" choice. On client side, you can change the default compression algorithm (LZ1) by defining the "PREFERRED_COMPRESION" variable in the file /opt/arkeia/arkeiad/arkfs.cfg. Also on the client machine, you can tune the compression type according to filename extention by editing in /opt/arkeia/arkeiad/arkfs directory the files: lzrw1.ext, lzrw3_3.txt and nocompr.txt

3.4.4. How do I setup up encryption with Arkeia?

*** A special license key is required to use the encryption feature of Arkeia. The choice of an encryption algorithm (DES, Blowfish, None, ...) is made with the GUI in "Savapack or Tree options" window. On the client machine, the keys for encryption are stored in a "key file" using this syntax: DES "[Des Encryption Key]" FISH "[Blowfish Encryption Key]" - to encrypt a directory DIR (but not its subdirectories) create the "key file" $DIR/.cryptkey.opb. If this file is empty the global "key file" /opt/arkeia/arkeiad/arkfs/.cryptkey.opb will be used. Note that the "key file" $DIR/.cryptkey.opb itself is not backed up by Arkeia - to encrypt a whole directory tree (itself and its subdirectories) configure the "/opt/arkeia/arkeiad/arkfs/cryptree.opb" file with the list of directory trees to encrypt. Each entry is associated with a "key file" like this: "/home" "/opt/arkeia/arkeiad/arkfs/encryt_home.keys" - On Windows or Novell machines replace the ".cryptkey.opb" unix filename by "cryptkey.opb" filename.

3.4.5. How do I backup/restore the MS Windows system information?

                
 
                ***
                
                The Windows System plug-in for Arkeia 5 allows you to backup four distinct 
                parts of the systems information:
                
                1) Windows Registry
                2) Windows Active Directory
                3) Windows Certificates
                4) Windows Event Logs
                
                Please reference the Arkeia 5 User Manual section: Appendix 4, Microsoft 
                Windows Backup.
                
                3.4.6. How do I uninstall the MS Windows client? 

                

                ***
                
                There are two ways to uninstall the MS Windows client.
                
                Solution 1: The normal way to uninstall the Arkeia 5 client software for
                Windows 2000/XP is :
                
                Start Menu -> Programs ->  Arkeia -> uninstall Arkeia
                
                Solution 2:  If the uninstall program doesn't work you have to do it 
                manually as following:
                
                1. From control panel Services Stop "Arkeia Service" (arkeiad)
                or execute C:\Program Files\Arkeia\Arkeia\bin\arkboot -stop
                
                2. Remove the "Knox Network Service" service with this command:
                C:\Program Files\Arkeia\Arkeia\bin\arkboot -remove
                
                3. Remove the directory C:\Program Files\Arkeia
                
                4. Remove the Arkeia uninstall program C:\WINNT\arkuinst.exe
                5. Remove the entries "Arkeia" in Start Menu -> Programs:
                
                C:\Documents and Settings\Administrator\Start Menu\Programs\Arkeia
                C:\Documents and Settings\All Users\Start Menu\Programs\Arkeia
                
                6. Remove the entry in the registry HKEY_LOCAL_MACHINE\SOFTWARE
                
                HKEY_LOCAL_MACHINE\SOFTWARE\ Arkeia
                HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\CurrentVersion\Uninstall\ARKEIA
                
                7. Remove the entries in the registry HKEY_LOCAL_MACHINE\SYSTEM
                
                HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\Eventlog\Application\Arkeia
                HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\arkboot
                (if it exists: this entry should have been removed by the point 2)
                
                8. Then restart the machine.