Backup3G/EWC/Man Pages
From Documentation
←Older revision | Newer revision→
Contents |
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:
- The local hostinfo table is consulted, to ensure that the request originates from a known COSmanager host;
- 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
-installInstall 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
-removeRemove 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
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.5 - Last modified 5th January 2008.
^ |
FSntcpio
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
FSregback
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
FSremote
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
FSsysstate
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
busplit
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
cos
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
db_date
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
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
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 4.1 - Last modified 24th January 2008.
^ |
devscan
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
ewc
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
file_excl
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
file_list
NAME
- file_list - generate list of files for backup
SYNOPSIS
file_list [-dr] [-n file] [-f file] [pattern...]
DESCRIPTION
- File_list writes a list of file names to standard output matching a given set of patterns, and other criteria. It is a little like find, but allows more flexible selection & exclusion based on file name patterns.
- File_list expands the given file patterns [see below], writing the list (optionally restricted by the -n option) to standard output. Patterns starting with the "!" character are excluded from the list.
- The following operands are supported:
pattern Include those files matching pattern. See below for the syntax. If omitted, all files below the current directory are included. File patterns must be relative the current directory.
OPTIONS
- File_list understands the following options:
-d Automatically include all ancestor directories of all files returned. This is useful when file_list is used to generate names for ntcpio to backup. -f file Read the list of file patterns from the given file. This list is in addition to any patterns specified on the command line. -n file Only return file names that have been modified since the specified file. -r Recursively descend all directories listed.
FILE PATTERNS
- File_list and file_excl both use a common form of file pattern, which is very similar to that used by the shell, but enhanced so that a single "*" character as a component of a pathname matches any depth of directory, including zero. Note that the forward slash must be used as the directory separator.
- For example:
*/core matches any "core" file in the current directory and any subdirectory. src/*/core matches any "core" file under ./src and its subdirectories. src/* matches all files under ./src. The normal shell file expansion characters are also observed. i.e.: ? matches any single character. * matches 0 or more characters, with the exception of the above. [..] matches any one of the enclosed characters. If the first character of the list is "!", then any character not enclosed is matched.
- A backslash before any of the above characters removes its special meaning.
- Patterns can also be specified in a pattern-file. In this case each pattern must be on a separate line. Blank lines and lines starting with "#" are ignored.
- File_list allows patterns to specify files to be either included or excluded. If the pattern begins with "!", the files are to be excluded.
- The file EWC_5.1\db\exclude contains patterns that file_list always excludes.
EXAMPLES
file_list "src/*" "!*/core" "!*/*.[oa]"
- Generates a list of all files under ./src except core files, object (.o) files, and archive libraries (.a).
DIAGNOSTICS
- Warning: No match found for <pattern>.
- No file matching the given pattern could be found. This is purely a warning.
WARNINGS
- File patterns on the command line should be quoted to avoid the shell expanding the names itself.
SEE ALSO
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
mt
NAME
- mt - magnetic tape control
SYNOPSIS
mt [-f tapename] command [count]
mt -h
DESCRIPTION
- Used to control magnetic tape devices. By default mt performs the requested operation once. Multiple operations can be performed by specifying count. If tapename is not specified, the default device tape0 is used.
- The following commands are supported:
bsf Space backward count file marks. blocksize Set the blocksize to count bytes (0 = variable). compression Turn compression on (count = 1) or off (count = 0). fsf Space forward count file marks. help Output help message. offline Take the tape offline. rewind Rewind the tape. status Output drive and media status.
OPTIONS
- The following options are supported:
-f tapename Specify the name of the device to control. tapename can be specified using either \\.\tape# or tape# notation. -h Display short help message
EXAMPLES
mt rewind
- Rewind the media in tape device tape0 to the beginning.
mt -f tape1 compression 0
- Turn compression off for tape device tape1.
DIAGNOSTICS
- The following exit values are returned:
2 command failure whilst performing the operation 1 invalid usage, invalid device or no media loaded 0 successful
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
ntcpio
NAME
- ntcpio - Backup/restore utility for Microsoft Windows
SYNOPSIS
ntcpio -i [-tv] [pattern]
ntcpio -o [-AtTv] [-I file]
DESCRIPTION
- The ntcpio command is used to backup files into (-o flag) and restore files from (-i flag) an ntcpio archive. Based on the UNIX cpio command, ntcpio follows the same structure, but has been adapted to support Windows features such as Access Control Lists. The ntcpio format is not compatable with the cpio format.
- When restoring files from an archive, only those files matching pattern are selected. If pattern is not specified, all files are restored.
- An archive is created by reading a list of files and/or directories from standard input and writing the data from those files along with their associated information to standard output.
- The following operands are supported:
pattern Only restore those files matching pattern. The notation used is similar to file patterns in the Unix shell.
OPTIONS
- The following options are supported:
-i Recover files from an archive on standard input. -o Backup files listed on standard intput to an archive on standard output. -A Only include files whose Archive bit is set. -I file Write a human-readable index of the archive to the specified file. -t Print table of contents (list the file names) of the archive to standard output. When used with -i, no files are restored. -v Verbose output. When used in conjunction with -t flag, extra file information is output. -T Similar to -t, but print a full index of the archive.
EXAMPLES
file_list | ntcpio -ov > backup.dat
- Generate an ntcpio archive of all files in the current directory to the backup.dat file.
ntcpio -ivt < backup.dat
- Print out an index of all files contained in the backup.dat ntcpio format archive.
DIAGNOSTICS
- The following exit values are returned:
1 invalid usage, program or system error 0 successful
SEE ALSO
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
regback
NAME
- regback - registry backup and restore
SYNOPSIS
regback -b | -p | -r [-Rv] [-d directory]
DESCRIPTION
- Used to backup the registry to file and restore the registry from file.
- To perform a registry backup, you must have the Backup privilege. When backing up the registry, a file named EBC.DAT is created. This file contains details about the registry keys that were backed up. Only the keys in HKEY_LOCAL_MACHINE and the DEFAULT user in HKEY_USERS are backed up. A separate file is created for each sub-key under HKEY_LOCAL_MACHINE and one for the DEFAULT user in HKEY_USERS.
- To perform a registry restore, you must have the Restore privilege. The file EBC.DAT is opened and each of the keys listed in that file are set to be restored. These keys are restored the next time the host is rebooted. Temporary files ending in 999 are created for the restore process. These files can be manually removed once the host has been rebooted.
- A profile listing can be generated by using the -p flag. This is the profile location for each user account on the system. This function can be used in conjuction with an archive utility to perform a backup of these directories.
OPTIONS
- The following options are supported:
-b Dump registry keys to file. A list of the files created is written to standard output. The files can then be backed up to tape using ntcpio. -p Dump user profiles to file. A list of the files created is written to standard output. The files can then be backed up to tape using ntcpio. -r Recover registry keys from file. -d directory Change to directory prior to backup or restore. -R Reboot the system after performing any other specified actions. -v Verbose output.
EXAMPLES
regback -b -d D:/tmp
- Dump keys in HKEY_LOCAL_MACHINE and DEFAULT user in HKEY_USERS to file in the D:/tmp directory.
regback -rR
- Recover the registry from file and then reboot the machine. The EBC.DAT file and files for each of the registry keys to be restored must exist in the current directory.
DIAGNOSTICS
- The following exit values are returned:
1 invalid usage or program error
0 successful
SEE ALSO
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
rsh
NAME
- rsh - remote shell client
SYNOPSIS
rsh [-bd] [-l username] hostname command
rsh -h
rsh -v
DESCRIPTION
- Connects to the specified host and executes the specified command using the rsh protocol. The rsh standard input is passed to the remote command and the remote command's standard output and standard error become that of rsh's.
OPTIONS
- The following options are supported:
-b Turn off binary output mode. -d Display debugging messages. Useful for diagnosing problems. -h Display help screen. -l username Specify the username under which the remote command is to be executed. -v Display version information.
EXAMPLES
rsh decoy "ls -l"
- Run ls -l on host decoy.
rsh -l cosmos aunty pwd
- Run pwd on host aunty. An entry for the local username is required in the cosmos .rhosts file.
DIAGNOSTICS
The following exit values are returned:
2 invalid usage
1 program error
0 successful
SEE ALSO
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
rshd
NAME
- rshd - remote shell daemon
'SYNOPSIS
rshd -install
rshd -remove
rshd [-d] [-n | -s shell]
rshd -h
rshd -v
DESCRIPTION
- The Remote Shell Daemon provides remote execution facilities. It is used to execute commands requested by remote shell clients.
- Clients connect to the daemon and request the execution of a command on behalf of a user. If the user has the necesary authority, the remote shell daemon 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.
OPTIONS
- The following options are supported:
-install Install rshd as a service. Once installed, it can be controlled using the net command, or using the Services window invoked from the Control Panel. -remove Remove the rshd service. -d Turn on debugging. Useful if there is a problem connecting. -h Display help screen. -n Use the default Windows shell (usually cmd.exe) to execute commands. The default is to use bash.exe. -s shell Use shell to execute commands. The shell extension must be specified eg. sh.exe. The default is to use bash.exe. -v Display version information. There are a couple of other flags mentioned in the help screen which are only useful for testing purposes.
EXAMPLES
rshd -install
- Install the remote shell daemon as a service.
rshd -remove
- Remove the remote shell daemon service.
rshd -d -s sh.exe
- Start the remote shell daemon using sh.exe instead of bash.exe to execute commands, and turn on debug information.
FILES
- $WINDIR/rhosts
- This file contains the list of users and hosts that are allowed to execute commands on the local host. Each line in the file contains the hostname, a space or tab and then the username. This specifies that username can execute commands from hostname.
DIAGNOSTICS
- The following exit values are returned:
1 program or system error 0 successful
SEE ALSO
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 1.15 - Last modified 5th January 2008.
^ |
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 5th 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
COPYRIGHT
- Copyright © 1990-2024 Functional Software. All rights reserved.
- Based on version 2.3.1.9 - Last modified 24th January 2008.
^ |