Installing the Clients

Starting ADSM

The Windows NT client can only be run by a user who is a member of the administrator's group or the domain admin group.

You can start the ADSM Backup-Archive client by selecting the ADSM backup client menu item from the ADSM program group on the start menu (Windows 95 and Windows NT 4.0), by double-clicking on the ADSM backup client icon in the ADSM program group (Windows NT 3.5.1), or by entering dsm on the command line.

You can start the ADSM Administrator client by selecting the ADSM administrative client menu item from the ADSM program group on the start menu (Windows 95 and Windows NT 4.0), by double-clicking on the ADSM administrative client icon in the ADSM program group (Windows NT 3.5.1), or by entering dsmadm.exe on the command line.

You must start ADSM from the ADSM directory or include the directory in the start command unless you update your environment. You can update your environment using the SET command or the Control Panel.

Your ADSM administrator has the option to force you to use a password to connect to the ADSM server. ADSM prompts you for the password if one is required. Contact your administrator if you do not know your password.

Starting the Client Scheduler

To start the client scheduler on Windows NT or Windows 95, select the ADSM scheduler icon from the ADSM program group, or enter the SCHEDULE command as follows: 

   dsmc schedule

When you start the client scheduler, it runs continuously until you close the window, shut down your system, or log out of your system.

The communication software must be running before you start ADSM.

For Windows NT the recommended scheduled backup method is to install and use the Scheduler Service Configuration Utility which allows ADSM Scheduler Services installation and configuration on local and remote Windows NT machines. The Scheduler Service Configuration Utility runs on Windows NT only and must be run from an account that belongs to the Administrator/Domain Administrator group. The syntax of the utility is: 

  dsmcutil command {option ...}

The following files must exist in the directory where the utility resides:

Note:The minimum abbreviation for the commands and options documented are in upper case.

The valid commands are the following:

INSTall
Install and configure an ADSM Scheduler Service.

Required options:

REMove
Remove an installed Scheduler Service

Required options: The name of the service to be removed.

UPDate
Update Scheduler Service registry values.

Required options:

The following options are valid:

The UPDATEPW command should be used to update the registry password.

Query
Query Scheduler Service registry values.

Required options:

The following options are valid:

The SHOWPW command should be used to display the registry password.

List
List installed Scheduler Services

Required options: none

SHOWPW
Display ADSM registry password in clear text.

Required options: The node name to display the password for.

The password is validated with the ADSM server if the /VALIDATE:YES option is specified.

UPDATEPW
Generate encrypted ADSM registry password.

Required options:

The password is validated with the ADSM server if the /VALIDATE:YES option is specified.

The password will be updated on the ADSM server if the /UPDATEONSERVER:YES options is specified. If this option is specified the current ADSM password must be specified with the /OLDPASSWORD option.

The valid options are the following

/NAME:servicename
The name of the scheduler service. The name should be quote delimited if it contains embedded spaces.

/CLIENTDIR:clientdir
The fully qualified directory path where the Scheduler Service files reside.This directory should be relative to the target machine where the service is installed. UNC names are not allowed. The default is the current directory.

/OPTFILE:optionsfile
The fully qualified ADSM options file. This is the options file the specified Scheduler Service will used to connect to ADSM. The utility will also use the file to connect to ADSM to validate and update passwords. Note that although this option will override the default option file in the current directory (dsm.opt), the ADSM API requires that a default option file exists in the current directory. The default is dsm.opt in the /CLIENTDIR directory.

/EVENTLOGGING:[YES|NO]
Turns detailed event logging on/off for the specified scheduler service. The default is YES.

/NODE:nodename
The ADSM node name the Scheduler Service will use to connect to the ADSM server. Also used when displaying or updating the ADSM registry password. The default is the NT machine name.

/PASSWORD:password
The ADSM password which is generated encrypted into the registry.

/MACHINE:machinename
A remote NT machine name to connect to.

/VALIDATE:[Yes|No]
Perform validation when display/updating the encrypted registry password. The default is Yes.

/AUTOSTART:[Yes|No]
Indicates is the Scheduler Service will start automatically at system boot time. The default is No.

/OLDPASSWORD:oldpw
Current ADSM server password. Used in conjunction with the /UPDATEONSERVER option when updating a password on the ADSM server.

/UPDATEONSERVER:[Yes|No]
Indicates that a specified password should be updated on the ADSM server. Requires use of the /OLDPASSWORD option.

Starting ADSM: Advanced Considerations

You can include ADSM options on the DSM command, or by modifying the settings for the ADSM icon. For example, you can modify the format used to display dates, times, and numbers, or you can include your password so that ADSM does not prompt for it. (However, if you include the PASSWORD option, your password can be seen by someone who sees you enter the command or who looks in your icon settings).

For example, you might have two machines that back up files to an ADSM server under separate node names. If you want to recover a file from one machine (JONES1) while at the other machine (JONES2), you can start ADSM using the NODENAME option specifying JONES1: 

   start dsm -nodename=jones1

Be careful if you use ADSM in this way. Do not attempt to do an incremental backup from the JONES2 machine while connected to ADSM as JONES1. If the drive labels are the same on the JONES1 and JONES2 machines, the incremental backup will expire any files that are not on the JONES2 machine, even if they still exist on JONES1. You could lose some valuable backup generations.

For information about getting started with the ADSM Windows graphical user interface, see Using the Windows Backup-Archive Clients, SH26-4078.

Starting the WebShell Client Interface

You can use the WebShell client interface to manage backup and restore operations from any machine, on any platform, on any network. Using the WebShell, you can back up and restore your own data, or an ADSM administrator can centralize the backup/restore operations of many ADSM clients, regardless of platform. To use it, simply point your Web browser at any ADSM client machine that is running the WebShell client interface. It provides you with the following client operations:

To use the WebShell,

  1. Enter the following command to inform WebShell of your password. This step is not required when the ADSM password generate option is used. 
    adsmpswd p <your password> <directory>

    This password file, adsmpswd.ws, resides in the wsstuff directory created during installation.

  2. Enter the following command to inform WebShell of the userids on the system, their type (regular user or administrator), and the passwords to use for Web authentication: 
       mkwspswd p <username> <password> <flag> <directory>

    This password file, adsmweb.ws, resides in the wsstuff directory created during installation.

  3. To start WebShell, enter the following, where xxx is the optional port number and yyy is the optional location of the Web authentication file: 
       webshell <xxx><yyy>
  4. To access WebShell, enter this URL: 
       http://YourMachineName:PortNumber/webshell
    Note:The default port number is 2121.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]