# $Id: readme_vms_cli.txt,v 1.9 2007/02/28 08:34:21 miraculix Exp $


Readme for SEP sesam VMS Backup Client SBC for the Backup System
SEP sesam

Copyright 2006 SEP AG, Germany 83629 Weyarn, Ziegelstr. 1 (C) 


This readme describes the steps to install SEP sesam VMS Backup Client
on Open VMS 7.x and 8.x Alpha.
         
There are two specific packages:

Kit sbc_vms_v2_0.zip with VMS-Client 1.6.x for VMS 7.1 and 7.2.
Kit sbc_vms_v3_2.zip with VMS-Client 1.7.x for VMS 7.3 and 8.x with ODS-2 and ODS-5 Support.

The client is supported since SEP sesam Server Version 3.0.

Important: The client kit sbc_vms_v#_#.zip should only be unzipped using VMS-UNZIP! 
      Other Zip/Unzip programs do not correctly create the required file properties.

unzip.exe for HP OpenVMS Alpha is available under
http://h71000.www7.hp.com/freeware/freeware60/000tools/alpha_images/unzip.exe
         


Work on the VMS-client
========================

The VMS-client Kit sbc_vms_v#_#.zip is provided in VMS ZIP Format.

It is imperative that the Kit is unzipped into VMS using the VMS UNZIP Tool, 
to prevent the loss of important data required by the VMS backup tool.

Once unzipped SEPsesam020.A/B or SEPsesam032.A/B Savesets are installed 
using VMS Install commands.


Procedure
============== 

1. TCP/IP configuration

   The SEPsesam Server must be configured in TCP/IP.
   For all proxies the identical names must be entered as for the Host 
   entries. Aliases will not be recognized.

   Host und Proxy Entries

   Enter the Host Names, in the event no Bind Service is used:
    ucx set host {name} /addr={IP-Adresse} /alias="{alias}"

   Enter the SEPNETBCK Proxy 
   - SEPsesam UNIXe / Linux Server with User 'root':
    ucx add proxy sepnetbck /rem="root" /host={name}

   - SEPsesam Windows Server with User 'system':
    ucx add proxy sepnetbck /rem="system" /host={name}

   Warning: 
      The switch /permanent should never be selected or entered, since this prevents 
      the entry from being written to the active Database.

   Note: 
     The Proxy will be prompted during the installation procedure @sys$update:vmsinstal 
     and if not found it will be created.


2. Copy the ZIP File into the working directory: 

   For example: Create the directory SYS$SPECIFIC:[SEPNETBCK].


3. Unzip the file:

   For VMZ 7.1/7.2
   $ unzip "-V" sbc_vms_v2_0.zip                       
   or for VMZ 7.3/8.x
   $ unzip "-V" sbc_vms_v3_2.zip                       

   REQUIRED: The Symbol unzip must be defined   
             If applicable set with $ unzip="$ {Path}unzip" 

   The files VMS Kit sepsesam020.a and sepsesam020.b respectively sepsesam032.a and sepsesam032.b
   will be created.
   These files are VMS Backup Savesets and may not be used as files in 'Stream LF' Format but
   should be created rather with 'Fixed Length'.

   In the event the data was not unzipped correctly, the Kit files will not be accepted as valid 
   for @sys$update:vmsinstal. In this case check your unzip.exe version. 
   Important is the switch -"V" since otherwise the format ‘Stream LF’ is created.

               
4. Install the Kit with the command:

   $ @sys$update:vmsinstal            

   and make the specific entries

   1. With 'Y' answer the questions regarding Backup and active processes,
   2. Designate the working directory for the VMS Kit Files,
      E.g. 'SYS$SPECIFIC:[SEPNETBCK]'
   3. with '*' or 'SEPsesam' for Product,
   4. Select 'none' for the choice of specific options.
   5. Designate the SEPsesam Server and select the SEPNETBCK PROXY Users 'root' for UNIX or
      'system' for Windows SEPsesam Server.
   
   Now the SEP sesam kit will be installed. 

5. Check the client configuration.
 
   If there is a problem with UCX/TCPIP settings all entries including 
   Hosts und Proxies must be checked. It may be helpful to look at the Operator Log Files.
   (E.g. with reply/enable).

Example: (Use the Host Name identical to PROXY Host Names):

   SYS$SPECIFIC:[SEPNETBCK] $ ucx show host decunix

      LOCAL database

   Host address    Host name

   192.168.2.84    DECUNIX, decunix, DECUNIX.SEP.DE

   SYS$SPECIFIC:[SEPNETBCK] $ ucx show proxy sepnetbck

   VMS User_name     Type      User_ID    Group_ID   Host_name

   SEPNETBCK         CD        ROOT                  DECUNIX



Work to be performed on the SEPsesam Server
============================================   

Using the GUI the VMS Client is configured.

The source for the backup task will be entered in VMS Notation for a Directory or File.

E.g. DKA0:[000000...] for Full Back-up of the disk.
 
In the event of a Restore the Target Directory should be entered without ‘...’, E.g. DKA100:[SYS0].



Tests
=====

1. Check if access via rsh is possible

On SEPsesam Server: as user root (UNIX) or system (Windows)
*  rsh -l sepnetbck {vms_node} dir
*  rsh -l sepnetbck {vms_node} sbc
*  rsh -l sepnetbck {vms_node} 'sbc -h'
*   ...

Note: If the command arguments are included then the command must be enclosed with
      quotes ', with capital letters for switches and values enclosed in " 
      (E.g. -"S" or "SMS" )
                              
2. Perform a Testbackup on the console.

*  sm_backup -b {VMS_Bankup} -m {Mediapool}






User Information for OpenVMS System
=========================================

On VMS the necessary symbols are defined in sepnb$command:sepnblogin.com 
and can be modified for testing purposes
(sbc, sbc_gen, sbc_pre, sbc_post)

Call: $ @sepnb$command:sepnblogin.com

Attention:
     Unfortunately all command line arguments in VMS (DCL)
     Are changed to lower letters. This can be avoided by using quotation marks, E.g. "

In addition:
      All capitalized switches must be set using quotation marks (E.g.. -"S", "SMS" of "-R" )





Note
========

1. VMS Hard Links

VMS Hard links are not supported. Directories in the filesystem using Hard links 
on the same Directory tree are backed up individually. The amount of backup data 
created grows accordingly. 

In case of a restore into volumes with given directory structure containing Hard 
links files are multiple restored without increasing amount of data.
If restored without given Hard links all missing directories will be created and 
the data amount is increased accordingly.

In general directory Hard links are used on the System Volumes and not on volumes with 
User Data.



2. VMS Data Structure

To back up the VMS Files together with their file structure at first data and 
afterwards the structure is saved in a special CPIO archive. This two streams
allow to restore the file data and the structure (VMS file properties).
So for every file two streams will be saved.

In the restore protocol or log file the restored data stream and data structure 
are counted together. The output 'processed Items' together with 'not processed Items' 
returns a double amount of processed files and directories.




Release Notes 3.2
=================

The VMS Backup Module sbc.exe supports from Version 1.7.1
the OpenVMS ODS-5 Volumes.
I.e.  the file names are stored ODS-5 Notation.


Note
=======
In the event of a restore of ODS-5 data into a ODS-2 Volumes all file names will be automatically 
converted into ODS-2 conforming file names.