Backup3G/EWC/Man Pages

From Documentation

Revision as of 13:24, 19 February 2008

COSserver

NAME

COSserver - remote COSmanager command execution

SYNOPSIS

COSserver -i | -install

COSserver -r | -remove

COSserver [-d]

DESCRIPTION

COSserver is a TCP service listening on port 9002 and provides remote execution facilities. It is used to execute commands requested by remote COSserver clients.

Clients connect to the server and request the execution of a command on behalf of a user. If the client has the necessary authority, theserver will execute the command and return the standard output and standard error of the command to the client. Any standard input sent from the client is passed to the command. It will also return the exit status of the command executed.

COSserver does a series of authentication steps to ensure that the request is genuine. These are:

1. The local hostinfo table is consulted, to ensure that the request originates from a known COSmanager host;
2. COSserver generates a random number, which is passed back to the host making the request. This random number is then hashed with the contents of the request, and the encrypted hash code is passed back to COSserver. COSserver then verifies that the hash code is correct.

OPTIONS

-i -install	Install COSserver as a service. Once installed, it can be controlled using the net command, or using the Services window invoked from the Control Panel.
-r -remove	Remove the COSserver service.
-d	Turn on debugging. Useful if there is a problem connecting.

There are a couple of other flags mentioned in the help screen which are only useful for testing purposes.

EXAMPLES

COSserver -install

Install the COSserver as a service.

COSserver -remove

Remove the COSserver service.

COSserver -d

Run COSserver interactively, and turn on debug information. Note that the COSserver service must be turned off for this to work.

FILES

$EWC_HOME/db/hostinfo

This file contains the list of hosts that are allowed to execute commands on the local host. Each host is followed by a comunications method that is used from the local host to execute commands on that host.

ENVIRONMENT

APPL_HOME

The base directory of the Enterprise Windows Client. This value is retrieved from the registry via the HomeDir value under the Enterprise Windows Client section of HKEY_LOCAL_MACHINE\SOFTWARE

For example: /cygdrive/C/Program Files/Functional Software/EWC_5.1

APPL_NAME

For the cos command to be run in the correct environment, the variable APPL_NAME must be set. APPL_NAME can be set to either backup or task.

EWC_HOME

The base directory of the Enterprise Windows Client in DOS syntax.

For example: C:\Program Files\Functional Software\EWC_5.1

FULLNAME

The fullname of the user connecting to the Enterprise Windows Client.

For example: COSmanager

LOGNAME

The username of the user connecting to the Enterprise Windows Client.

For example: cosmos

PATH

The location, relative to EWC_HOME of the Enterprise Windows Client executables is prepended to the PATH variable.

For example: /bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows

USERNAME

The username of the user connecting to the Enterprise Windows Client.

For example: cosmos

DIAGNOSTICS

The following exit values are returned:

1	program or system error
0	successful

SEE ALSO

FSremote(1)

COPYRIGHT

Copyright © 1990-2024 Functional Software. All rights reserved.

Based on version 1.5 - Last modified 5^th January 2008.

FSntcpio

FSregback

FSremote

FSsysstate

busplit

cos

db_date

devio

NAME

devio - handle I/O to devices such as tape drives

SYNOPSIS

devio -i|o [-bcdLmnprs1] [command]

DESCRIPTION

Devio reads data from or writes data to either a disk file or a device such as a tape drive. Devio can be called several times in succession to write to a set of tapes or other media, and handle volume changes as necessary.

Normally devio reads from the device, passing data to standard output (-i option) or writes to the device, obtaining data from standard input (-o option). However, if a command is given as a parameter (which must be quoted to ensure that it is passed as a single parameter), then it is executed, and data is piped to or from that process. Devio will then terminate with the same exit status as this process. This is useful if devio is called from a shell script which needs to know whether the data transfer was successful.

OPTIONS

-i	Devio will read data from the device, passing it to STDOUT or to the standard input of the optional command.
-o	Devio will write data to the device, reading it from STDIN or from the standard output of the optional command.
-d device	I/O will be done to the specified device or file. Typically this would be a Windows tape device name, such as tape0. If this option is omitted, the environment variable TAPE should specify the device.
-n name	This specifies a name by which the user knows the device, as specified by the -d option. If this option is specified, then any user messages referring to the device will use the specified name, rather than the Windows device name.
-b blocksize	The blocksize in KB that should be used for I/O to the device. The default is 64KB.
-c capacity	The capacity in KB of each volume. This figure should be the amount of data that can safely be written. Devio will request a change of volume after this amount has been read or written. The default is unlimited capacity, implying that media changes will occur at physical end of volume or on an I/O error.
-m command	A command to run to change the volume in the device. This command should exit with a status of 0 when the drive is ready and loaded with the new volume. It can also optionally write the name of the next device to use on its STDOUT (if it has changed). A non-zero exit status will cause devio to exit with that status. This command can also do things like checking for or writing a label on the new tape.
-s startpos	The amount of data in KB to to skip or that has already been written on the first volume. This tells devio how much data can still fit (if writing) or remains (if reading) on the first volume. On subsequent volumes it is assumed that the full capacity (given by -c) is available. The default is 0, i.e.: starting at the beginning of the volume.
-r amount	The amount of data in KB that devio should read. This is only applicable with the -i option, and is only necessary on devices, such as floppy disks, which have no mechanism for delimiting files or datasets on the one volume. By default devio will read to end of file.
-P volsizes	The amounts of data in KB that devio should read on each volume. If more than one size is given, devio will read the first amount, request a volume change, and continue to read the second amount etc. This is only applicable with the -i option. By default devio will stop at end of file.
-L	Indicates that the data being read or written is a single block tape label. Unless -b is specified, this will be a 512 byte block.
-p	Indicates that all blocks are to be written at the specified blocksize. Normally devio will write a short last block if there is insufficient data to fill the block. This flag will cause such a block to be NULL padded.
-1	Indicates that at least one block should be written to the device, even if there is no input data. This is useful for jobs which write multiple files to one tape, and want to ensure that the relative positions of each file is constant, even if one file is empty. Many tape devices have no means of writing an empty file.
-u	Causes devio to write details of the amounts of data written, the elapsed time & rate to the given file.

EXAMPLES

devio -o -b32 -d tape0 'FSntcpio -f C:/local'

Write a backup of C:/local to tape device tape0 using 32K blocksize.

devio -i -b32 -d tape0 'FSntcpio -r C:/tmp'

Recover the contents of tape device tape0 to C:/tmp. Data is read from tape0 in 32K blocks and passed to FSntcpio.

SEE ALSO

devscan(1), ntcpio(1), FSntcpio(1)

COPYRIGHT

Copyright © 1990-2024 Functional Software. All rights reserved.

Based on version 4.1 - Last modified 24^th January 2008.

devscan

ewc

file_excl

file_list

mt

ntcpio

regback

rsh

rshd

service

NAME

service - control services

SYNOPSIS

service info

service start [-vy] [-w secs] service

service start [-vy] [-w secs] -f file

service stop [-vy] [-w secs] service

service stop [-vy] [-w secs] -f file

DESCRIPTION

Used to control services. Includes displaying information on currently running services, starting services and stopping services.

The services to be controlled can be either listed in a file or a single service can be supplied on the command line.

The following commands are supported:

info	Output a list of currently running services.
start	Start the specified service.
stop	Stop the specified service.

OPTIONS

-f file	Perform the specified action on all services listed in the file. The services are listed one per line, and you may include comment lines starting with #. The file should be saved in the db directory under the EWC directory (eg: in C:\Program Files\Functional Software\EWC_5.1\db).
-w secs	Wait the specified number of seconds after starting or stopping the service(s). This option may be used to delay subsequent processing if a service takes some time to start or stop.
-v	Verbose output.
-y	Respond with yes to service control queries. The default is to respond no.

EXAMPLES

service start rshd

Start the rshd service.

service stop -w 90 -f services

Stop all services listed in the services file. Then wait 90 seconds to allow the listed services time to completely shutdown.

ENVIRONMENT

WINDIR

The location of the Windows directory. Used to locate the net command (that is, $WINDIR/system32/net).

eg. C:\Windows

DIAGNOSTICS

The following exit values are returned:

2	command failure whilst performing the operation
1	invalid usage
0	successful

COPYRIGHT

Copyright © 1990-2024 Functional Software. All rights reserved.

Based on version 1.9 - Last modified 5^th January 2008.

tapelabel

NAME

tapelabel - read and write electronic tape labels

SYNOPSIS

tapelabel -r device

tapelabel -w device [device] number

DESCRIPTION

Used to read and write electronic tape labels.

When writing a tape label, the tape is first rewound using mt. Then a heading, the date and the tape number is written to the tape using devio. The tape is left positioned after the tape label.

To read a tape label, the tape is first rewound using mt. Then devio is used to read the first block of the tape. If the data is read correctly and the tape label is valid, the tape number will be written to standard output. The tape is then rewound.

Tape labels are written as a single 512 byte block.

OPTIONS

-r	Read the tape label. The tape number from the label is written to standard output.
-w	Write a new label to the start of the tape with the specified tape number.

OPERANDS

device	The name of the tape device. eg. tape0.
number	The number to label the tape with (-w only).

EXAMPLES

tapelabel -r tape0

Write out the label of the tape loaded in drive tape0.

tapelabel -w tape1 tape1 100

Label the tape in drive tape1 as number 100.

DIAGNOSTICS

The following exit values are returned:

1	invalid usage. I/O, program or system error.
0	successful

NOTES

The optional second device operand is used only for compatibility with the UNIX version of tapelabel. It is not required on Windows.

Some older versions of tapelabel wrote a 1 KB label instead of 512 bytes. This version will read the old label, but always writes new 512 byte labels.

SEE ALSO

devio(1), mt(1)

COPYRIGHT

Copyright © 1990-2024 Functional Software. All rights reserved.

Based on version 2.3.1.9 - Last modified 24^th January 2008.