Backup3G/EWC 3.1.1 Release Notes

This page was last modified 04:09, 25 February 2008.

From Documentation

< Backup3G(Difference between revisions)

Jump to: navigation, search

Current revision

[edit]

Overview and Features

[edit]

Enterprise Windows Client

The COSmanager Enterprise Windows Client for Windows 2000/XP/2003 V3.1.1 allows the integration of Windows hosts into the COSbackup policy based backup environment and COStask job scheduling environment. The management and delegation of the backup policy and job scheduling policy is UNIX or Linux centric. The backup and task environments can contain any number of UNIX, Linux or Windows 2000/XP/2003 hosts. These hosts and their resources (tape drives, filesystems, applications, etc) are then accessible by any other host in the environment.

EWC (Enterprise Windows Client) was previously known as EBC (Enterprise Backup Client).

[edit]

New features in EWC 3.1.1

The features of EWC V3.1.1 when used as a Backup Client are:

backup Windows data to Windows removable media drive
backup Windows data to UNIX/Linux removable media drive
backup UNIX/Linux data to Windows removable media drive
use media labelled or previously written on a UNIX/Linux host
use either RSH or COSserver communications protocol
operate with and control St Bernard’s Open File Manager (OFM) product
exclude files from backup by specifying a pattern
backup and restore the Registry
backup and restore user profiles
backup and restore the System State
backup and restore folder and file NTFS attributes and ACL’s including hidden files
backup and restore FAT filesystems
stop and start Windows services during a backup
ability for backups to span multiple media

The features of EWC V3.1.1 when used as a Task Client are:

extends the Unix/Linux centric Job Scheduling environment to include Windows hosts
run Windows batch (.BAT) files
run native Windows programs
run a subset of Unix commands on the Windows host
use either RSH or COSserver communications protocol

A detailed description of EBC and its features and benefits can be found in the COSmanager EBC User Guide V2.2.

[edit]

Environment

[edit]

Software prerequisites

To install and run EWC 3.1.1 on a Windows host, you must have:

a .exe distribution file containing the EWC software and installation script
a valid license key for this host with the correct application type [Backup (EBC) and/or Task (ETC)] and the correct SERVER or WORKSTATION options (see your COSmanager distributor if you don’t have a valid license key)
sufficient disk space (see Disk Space Required)
the ability to log in as an Administrator user

[edit]

Disk space required

Software	Approximately 10 MB in the "Program Files" directory.
Temporary Files	While EWC is running: less than 10 MB in /tmp.
Log Files	None. These are managed from the COSbackup or COStask Server

[edit]

Supported Windows Versions

Windows version supported by EBC V3.1.1 are:

Winodws 2000
Windows XP
Windows 2003

[edit]

Technical Notes: Using EWC 3.1.1

This section contains some technical notes and tips about EWC for Windows 2000/XP/2003 V3.1.

[edit]

Upgrading from Enterprise Windows Client V3.1

You are now not required to uninstall EWC V3.1 prior to installing EWC V3.1.1. Instead you just install EWC 3.1.1. The installation process will deal with stopping the communications services (COSserver and RSHD) and uninstalling the appropriate components of EWC 3.1 before it proceeds with installing EWC 3.1.1. By doing this you will retain license keys and allowed hosts configuration so you will not need to re-license and re-configure afterward.

[edit]

Upgrading from Enterprise Backup Client V2.1/V2.2/V2.2.1

You cannot have more than one version of the EBC [EWC] running at the same time. You must uninstall EBC V2.1/V2.2.1/V2.2.2 prior to installing EWC V3.1.

	Note
	Before uninstalling EBC V2.1/V2.2.1/V2.2.2, ensure the COSmanager Enterprise Backup Client (or RSH Daemon) service is first stopped, via Control Panel > Services .

After uninstalling EBC it is possible that some files are not completely removed. Ensure the following files, folders and entries have been removed before installing EWC V3.1.1. If you fail to remove these files errors may result when running backups or scheduled task jobs:

<EBC install folder>/EBC_2.1
<EBC install folder>/EBC_2.2
<WINNT>/system32/bin/cos.exe
<WINNT>/system32/bash.exe
<WINNT>/system32/rshd.exe
COSmanager Enterprise Backup Client services’ entry. The service may also be called RSH Daemon in older versions of EBC.

It is also recommended that you remove the following Registry keys before you install EWC 3.1.1:

HKLM/SOFTWARE/Functional Software
HKLM/SOFTWARE/Cygnus Solutions
HKCU/Software/Cygnus Solutions

[edit]

Licensing

EWC for Windows 2000/XP/2003 may be issued with a temporary license for use in trials or demonstrations. Temporary licenses have an in-built expiry date. You must obtain a permanent license or a new temporary license from your COSmanager distributor to keep using the product after the expiry date. Licensing EWC will fail if you attempt to license the product using a key that will expire within 5 days.

	Note
	In order for a valid permanent EBC/ETC license key to be supplied you must provide both the hostname and type of Windows installation, WORKSTATION or SERVER.

[edit]

UNIX to Windows connectivity

Connectivity, Unix to Windows, Windows to Unix, or Windows to Windows can either be via:

COSmanager Remote Server for EWC (COSserver), or
COSmanager Remote Shell Daemon (RSHD)

The COSmanager Remote Server for EWC Windows service runs as the SYSTEM user. In order for the Enterprise Windows Client to communicate with COSbackup on the UNIX host, the UNIX host must have a host entry in the COSmanager hostinfo table for the EWC host. This is achieved by entering the Windows host in the Host Information table, Config > COSmanager configuration > Host information .

The Remote Shell Daemon on Windows runs as the SYSTEM user. In order for the Enterprise Windows Client to communicate with COSbackup on the UNIX host, the UNIX host must have a SYSTEM entry in the cosmos <WINNT>/rhosts file for the EWC host. This is achieved by entering the Windows host in the Host Information table, Config > COSmanager configuration > Host information . If the OS version is set to a Windows OS, this entry will be automatically added when you run Remote > Allow access .

UNIX hostname must be able to be resolved to their associated IP address. If DNS is not used or is not properly configured for hostname resolution to occur, then you must appropriately populate the file <WINNT>/system32/drivers/etc/hosts.

[edit]

COSmanager Remote Server for EWC (COSserver)

Unlike RSHD, COSserver listens and communicates via a single port only, port 9002. This simplifies firewall setup. For further information on COSserver, see Technical Note 216 - COSserver Information.

Changes to the Windows hostinfo table are not read dynamically. The hostinfo table is only read during startup of the COSmanager Remote Server for EWC service. Restart the COSmanager Remote Server for EWC service to pick up any changes to the allowed hosts.

[edit]

COSmanager Remote Shell Daemon (RSHD)

Changes to the <WINNT>/rhosts file are not read dynamically. The rhosts file is only read during startup of the COSmanager Remote Shell Daemon service. Restart the COSmanager Remote Shell Daemon service to pick up any changes to the rhosts file.

The COSmanager Remote Shell Daemon service does not pick up the last line in the rhosts file if it is not followed by a carriage-return (CR). This may only become apparent if the file is edited manually. Ensure the last entry is followed by a carriage-return.

[edit]

Backup and Recovery

A backup item cannot define a directory with a single quote in it. The item can be created, but it will fail if it is run. Also you cannot specify a restore directory with a single quote in it. This will cause the recovery to fail.

Exclude file patterns (-x and -X options) and select file patterns (selected ntcpio backup methods) cannot contain spaces. The patterns will effectively be ignored. Instead substitute each space in your file pattern with question mark.

[edit]

Incremental backup of filesystems

The directory (or folder) being backed up must be writable. If the directory is not writable, a full backup of that directory will be performed.

The COSbackup term Incremental Backup actually refers to the generally accepted term Differential Backup.

[edit]

Generating an index

You cannot generate an index for UNIX/Linux specific backup methods on a Windows removable media drive. The index must be generated from a UNIX/Linux removable media drive. Re-generating an index for a Windows specific backup on a UNIX/Linux removable media drive will cause the backup data to sent across your network to the Windows host.

[edit]

System State backup

System State is a collection of system-specific data that can be backed up and restored. The System State data includes the registry, the COM Class Registration database, and the system boot files. For servers, the System State data also includes the Certificate Services database (if the server is operating as a certificate server). If the server is a domain controller, the System State data also includes the Active Directory directory services database and the SYSVOL directory.

If your COSbackup Master is running version 3.2.6 or earlier, you will need to add the following backup method before you can run a System State backup of a Windows host:

Select COSbackup configuration > Maintain other tables > Backup method .
Select Maintain > Add .

Backup method	system state
Description	Backup Windows system state
Format	ntcpio
Backup command	FSsysstate $Options
Multipart support?	no
Uses STDOUT?	yes
Index support?	no
Remote support?	yes
Run on host	file_host

Press Accept to save this backup method.

[edit]

Controlling Open File Manager

If your COSbackup Master is running version 3.2.6 or earlier, you will need to add the following backup methods before you can control OFM running on a Windows host from your backup job:

Select COSbackup configuration > Maintain other tables > Backup method .
Select Maintain > Add .

Backup method	sync OFM
Description	Syncronize OFM from St Bernard running on Windows
Format
Backup command	ofm sync $Options
Multipart support?	no
Uses STDOUT?	no
Index support?	no
Remote support?	yes
Run on host	file_host

Press Accept to save this backup method.

3. Select Maintain > Add .

Backup method	unsync OFM
Description	Unsyncronize OFM from St Bernard running on Windows
Format
Backup command	ofm unsync $Options
Multipart support?	no
Uses STDOUT?	no
Index support?	no
Remote support?	yes
Run on host	file_host

Press Accept to save this backup method.

[edit]

Restoring with Open File Manager

When you restore files and directories to a Windows host that has OFM running, you must pause or stop OFM first. This is because the restore uses ntcpio and will cause OFM to syncronize before any files are restored. If you do not pause or stop OFM first, it is common to see messages in the recovery log like:

ntcpio: Cannot create directory ./abc

	Caution!
	Before restoring files to a Windows host that is running OFM, ensure OFM is first paused or stopped, via Control Panel > Services, or via OFM > System > Stop.

[edit]

Excluding files from backup

You can set up a standard set of files to be excluded from your Windows backups. By default “*/pagefile.sys” is excluded. You can add extra exclude file patterns, one pattern per line, by editing the file <install folder>/db/exclude.

[edit]

Installing COSmanager Enterprise Windows Client

To install the COSmanager Enterprise Windows Client, you must be logged in as an Administrator, that is, either Administrator or a member of the Administrators group. Before installing the EWC, check the System Requirements to ensure your system has the required resources.

You need :

a Windows 2000, XP or 2003 host that is connected to the network
be logged in as an Administrator user, that is, a user who is a member of the Administrators group

The procedure is:

Select Settings > Control Panel from the Start button. The Control Panel program group should now be displayed.
Open Add/Remove Programs. The Add/Remove Programs Properties dialog should be displayed.
Press Install (or Add New Programs).
Browse your Functional Software CD or hard disk and select the EWC V3.1.1 distribution.
For example, on CD the distribution file will be D:\distribs\windows\EWC311.exe.
Press Finish to continue.
A dialog should be displayed saying “Welcome to the Enterprise Windows Client Setup Wizard”.
Press Next to continue.
The License Agreement screen is displayed. If at any time you wish to exit from the installation, press Cancel.
Select I accept the agreement and press Next to continue.
The Information screen is displayed. The README document is displayed.
Press Next to continue.
The installation program will now ask you for the destination directory for the Enterprise Windows Client software. To change the destination, press the Browse button and select the new location.
Press Next to continue.
You will be asked for the Start Menu Folder for the Enterprise Windows Client.
Press Next to continue.
The Settings you have chosen for the installation of the Enterprise Windows Client software will be displayed. If you wish change any of the settings, press Back.
Press Next to continue.
The installation will now unpack the necessary files and place them in the destination specified. A status indicator displays the progress of the installation. Other installation procedures are also carried out at this point.
You may be asked to specify the Master COSbackup host. This is the UNIX/Linux COSbackup Server host that the backup configuration is performed on. Entering a hostname and pressing Accept will add an entry to the <WINNT>/rhosts file and to the <install folder>/db/hostinfo file. This entry will allow the COSbackup Server host to access this host.
All installed files installed will be set to Full Control by Administrator group and Read Access by SYSTEM.
A dialog indicating the installation is complete should be displayed. The option License and configure EWC will be checked.
Press Finish to end the installation of the Enterprise Windows Client and launch Enterprise Windows Client.
You can now license your installation on this host and add other hosts that are allowed COSbackup access to resources on this host.

[edit]

Further Information

Further technical documentation can be found via Start > Programs > COSmanager > Enterprise Windows Client 3.1 > Help . Technical documentation includes:

Readme General information
Installation Notes How to install and deinstall EWC
License Agreements License agreements, copyight and trademarks
Release Notes Version 3.1.1 release notes
Error Listing Listing of error messages and possible solutions
Manual Pages Reference pages for command usage

[edit]

Known Problems in this Release

None known.

October 2002

Retrieved from "https://documentation.fs.com.au/index.php/Backup3G/EWC_3.1.1_Release_Notes"

 The COSmanager Remote Server for EWC Windows service runs as the SYSTEM user. In order for the Enterprise Windows Client to communicate with COSbackup on the UNIX host, the UNIX host must have a host entry in the COSmanager hostinfo table for the EWC host. This is achieved by entering the Windows host in the Host Information table, {{cnav | Config > COSmanager configuration > Host information}}.
-The Remote Shell Daemon on Windows runs as the SYSTEM user. In order for the Enterprise Windows Client to communicate with COSbackup on the UNIX host, the UNIX host must have a SYSTEM entry in the cosmos <WINNT>/rhosts file for the EWC host. This is achieved by entering the Windows host in the Host Information table, {{cnav | Config > COSmanager configuration > Host information}}. If the OS version is set to a Windows OS, this entry will be automatically added when you run {{cnav | Remote > Allow access}}.
+The Remote Shell Daemon on Windows runs as the SYSTEM user. In order for the Enterprise Windows Client to communicate with COSbackup on the UNIX host, the UNIX host must have a SYSTEM entry in the cosmos <code><WINNT>/rhosts</code> file for the EWC host. This is achieved by entering the Windows host in the Host Information table, {{cnav | Config > COSmanager configuration > Host information}}. If the OS version is set to a Windows OS, this entry will be automatically added when you run {{cnav | Remote > Allow access}}.
-UNIX hostname must be able to be resolved to their associated IP address. If DNS is not used or is not properly configured for hostname resolution to occur, then you must appropriately populate the file <tt><WINNT>/system32/drivers/etc/hosts</tt>.
+UNIX hostname must be able to be resolved to their associated IP address. If DNS is not used or is not properly configured for hostname resolution to occur, then you must appropriately populate the file <code><WINNT>/system32/drivers/etc/hosts</code>.
 <br>
 ==== COSmanager Remote Server for EWC (COSserver) ====
 ==== COSmanager Remote Shell Daemon (RSHD) ====
-Changes to the <tt><WINNT>/rhosts</tt> file are not read dynamically. The rhosts file is only read during startup of the COSmanager Remote Shell Daemon service. Restart the COSmanager Remote Shell Daemon service to pick up any changes to the rhosts file.
+Changes to the <code><WINNT>/rhosts</code> file are not read dynamically. The ''rhosts'' file is only read during startup of the COSmanager Remote Shell Daemon service. Restart the COSmanager Remote Shell Daemon service to pick up any changes to the ''rhosts'' file.
-The COSmanager Remote Shell Daemon service does not pick up the last line in the rhosts file if it is not followed by a carriage-return (CR). This may only become apparent if the file is edited manually. Ensure the last entry is followed by a carriage-return.
+The COSmanager Remote Shell Daemon service does not pick up the last line in the ''rhosts'' file if it is not followed by a carriage-return (CR). This may only become apparent if the file is edited manually. Ensure the last entry is followed by a carriage-return.
 <br>
 ==== Backup and Recovery ====
 A backup item cannot define a directory with a single quote in it. The item can be created, but it will fail if it is run. Also you cannot specify a restore directory with a single quote in it. This will cause the recovery to fail.
-Exclude file patterns (-x and -X options) and select file patterns (selected ntcpio backup methods) cannot contain spaces. The patterns will effectively be ignored. Instead substitute each space in your file pattern with question mark.
+Exclude file patterns ('''-x''' and '''-X''' options) and select file patterns (selected ntcpio backup methods) cannot contain spaces. The patterns will effectively be ignored. Instead substitute each space in your file pattern with question mark.
 <br>
 ==== Incremental backup of filesystems ====
 ==== System State backup ====
-System State is a collection of system-specific data that can be backed up and restored. The System State data includes the registry, the COM Class Registration database, and the system boot files. For servers, the System State data also includes the Certificate Services database (if the server is operating as a certificate server). If the server is a domain controller, the System State data also includes the Active Directory directory services database and the SYSVOL directory.
+''System State'' is a collection of system-specific data that can be backed up and restored. The ''System State'' data includes the registry, the COM Class Registration database, and the system boot files. For servers, the ''System State'' data also includes the ''Certificate Services'' database (if the server is operating as a certificate server). If the server is a domain controller, the ''System State'' data also includes the ''Active Directory'' directory services database and the SYSVOL directory.
 If your COSbackup Master is running version 3.2.6 or earlier, you will need to add the following backup method before you can run a System State backup of a Windows host:
-. Select COSbackup configuration > Maintain other tables > Backup method.
+#Select {{cnav |COSbackup configuration > Maintain other tables > Backup method}}.
-. Select Maintain > Add.
+#Select {{cnav |Maintain > Add}}.
-Backup method system state
+::{|border="0" cellpadding="2" cellspacing="0"
-Description Backup Windows NT system state
+! align="left" width="150" | Backup method
-Format ntcpio
+| system state
-Backup command FSsysstate $Options
+|-
-Multipart support? no
+! align="left" width="150" | Description
-Uses STDOUT? yes
+| Backup Windows system state
-Index support? no
+|-
-Remote support? yes
+! align="left" width="150" | Format
-Run on host file_host
+| ntcpio
-Press Accept to save this backup method.
+|-
+! align="left" width="150" | Backup command
+| FSsysstate $Options
+|-
+! align="left" width="150" | Multipart support?
+| no
+|-
+! align="left" width="150" | Uses STDOUT?
+| yes
+|-
+! align="left" width="150" | Index support?
+| no
+|-
+! align="left" width="150" | Remote support?
+| yes
+|-
+! align="left" width="150" | Run on host
+| file_host
+|}
+::Press Accept to save this backup method.
 <br>
 ==== Controlling Open File Manager ====
 If your COSbackup Master is running version 3.2.6 or earlier, you will need to add the following backup methods before you can control OFM running on a Windows host from your backup job:
-. Select {{cnav |COSbackup configuration > Maintain other tables > Backup method}}.
+#Select {{cnav |COSbackup configuration > Maintain other tables > Backup method}}.
-. Select {{cnav |Maintain > Add}}.
+#Select {{cnav |Maintain > Add}}.
-Backup method sync OFM
+::{|border="0" cellpadding="2" cellspacing="0"
-Description Syncronize OFM from St Bernard running on Windows
+! align="left" width="150" | Backup method
-Format
+|sync OFM
-Backup command ofm sync$Options
+|-
-Multipart support? no
+! align="left" width="150" | Description
-Uses STDOUT? no
+|Syncronize OFM from St Bernard running on Windows
-Index support? no
+|-
-Remote support? yes
+! align="left" width="150" | Format
-Run on host file_host
+|
-. Select {{cnav |Maintain > Add}}.
+|-
-Backup method unsync OFM
+! align="left" width="150" | Backup command
-Description Unyncronize OFM from St Bernard running on Windows
+|ofm sync $Options
-Format
+|-
-Backup command ofm unsync$Options
+! align="left" width="150" | Multipart support?
-Multipart support? no
+|no
-Uses STDOUT? no
+|-
-Index support? no
+! align="left" width="150" | Uses STDOUT?
-Remote support? yes
+|no
-Run on host file_host
+|-
+! align="left" width="150" | Index support?
+|no
+|-
+! align="left" width="150" | Remote support?
+|yes
+|-
+! align="left" width="150" | Run on host
+|file_host
+|}
+::Press Accept to save this backup method.
+:3. Select {{cnav |Maintain > Add}}.
+::{|border="0" cellpadding="2" cellspacing="0"
+! align="left" width="150" | Backup method
+|unsync OFM
+|-
+! align="left" width="150" | Description
+|Unsyncronize OFM from St Bernard running on Windows
+|-
+! align="left" width="150" | Format
+|
+|-
+! align="left" width="150" | Backup command
+|ofm unsync $Options
+|-
+! align="left" width="150" | Multipart support?
+|no
+|-
+! align="left" width="150" | Uses STDOUT?
+|no
+|-
+! align="left" width="150" | Index support?
+|no
+|-
+! align="left" width="150" | Remote support?
+|yes
+|-
+! align="left" width="150" | Run on host
+|file_host
+|}
+::Press Accept to save this backup method.
 <br>
 ==== Restoring with Open File Manager ====
 The procedure is:
-#Select Settings > Control Panel from the Start button. The Control Panel program group should now be displayed.
+#Select {{cnav | Settings > Control Panel}} from the Start button. The Control Panel program group should now be displayed.
 #Open Add/Remove Programs. The Add/Remove Programs Properties dialog should be displayed.
 #Press Install (or Add New Programs).
-#Browse your Functional Software CD or harddisk and select the EWC V3.1.1 distribution.
+#Browse your Functional Software CD or hard disk and select the EWC V3.1.1 distribution.<br>For example, on CD the distribution file will be <code>D:\distribs\windows\EWC311.exe</code>.<br>Press Finish to continue.
-For example, on CD the distribution file will be D:\distribs\windows\EWC311.exe.
+#A dialog should be displayed saying “Welcome to the Enterprise Windows Client Setup Wizard”.<br>Press Next to continue.
-Press Finish to continue.
+#The ''License Agreement'' screen is displayed. If at any time you wish to exit from the installation, press Cancel.<br>Select '''''I accept the agreement''''' and press Next to continue.
-#A dialog should be displayed saying “Welcome to the Enterprise Windows Client Setup Wizard”.
+#The ''Information'' screen is displayed. The ''README'' document is displayed.<br>Press Next to continue.
-Press Next to continue.
+#The installation program will now ask you for the destination directory for the Enterprise Windows Client software. To change the destination, press the Browse button and select the new location.<br>Press Next to continue.
-#The “License Agreement” screen is displayed. If at any time you wish to exit from the installation, press Cancel.
+#You will be asked for the Start Menu Folder for the Enterprise Windows Client.<br>Press Next to continue.
-Select “I accept the agreement” and press Next to continue.
+#The ''Settings'' you have chosen for the installation of the Enterprise Windows Client software will be displayed. If you wish change any of the settings, press Back.<br>Press Next to continue.
-#The “Information” screen is displayed. The README document is displayed.
-Press Next to continue.
-#The installation program will now ask you for the destination directory for the Enterprise Windows Client software. To change the destination, press the Browse button and select the new location.
-Press Next to continue.
-#You will be asked for the Start Menu Folder for the Enterprise Windows Client.
-Press Next to continue.
-#The “ Settings” you have chosen for the installation of the Enterprise Windows Client software will be displayed. If you wish change any of the settings, press Back.
-Press Next to continue.
 #The installation will now unpack the necessary files and place them in the destination specified. A status indicator displays the progress of the installation. Other installation procedures are also carried out at this point.
-#You may be asked to specify the Master COSbackup host. This is the UNIX/Linux COSbackup Server host that the backup configuration is performed on. Entering a hostname and pressing Accept will add an entry to the <WINNT>/rhosts file and tothe <install folder>/db/hostinfo file. This entry will allow the COSbackup Server host to access this host.
+#You may be asked to specify the Master COSbackup host. This is the UNIX/Linux COSbackup Server host that the backup configuration is performed on. Entering a hostname and pressing Accept will add an entry to the <code><WINNT>/rhosts</code> file and to the <code><install folder>/db/hostinfo</code> file. This entry will allow the COSbackup Server host to access this host.
 #All installed files installed will be set to Full Control by Administrator group and Read Access by SYSTEM.
-#A dialog indicating the installation is complete should be displayed. The option “License and configure EWC” will be checked.
+#A dialog indicating the installation is complete should be displayed. The option '''''License and configure EWC''''' will be checked.<br>Press Finish to end the installation of the Enterprise Windows Client and launch Enterprise Windows Client.
-Press Finish to end the installation of the Enterprise Windows Client and launch Enterprise Windows Client.
 #You can now license your installation on this host and add other hosts that are allowed COSbackup access to resources on this host.
 | <br>[[#top|^]]
 |}
 == Further Information ==

Search

Backup3G/EWC 3.1.1 Release Notes

From Documentation

Current revision

Contents

Overview and Features

Enterprise Windows Client

New features in EWC 3.1.1

Environment

Software prerequisites

Disk space required

Supported Windows Versions

Technical Notes: Using EWC 3.1.1

Upgrading from Enterprise Windows Client V3.1

Upgrading from Enterprise Backup Client V2.1/V2.2/V2.2.1

Licensing

UNIX to Windows connectivity

COSmanager Remote Server for EWC (COSserver)

COSmanager Remote Shell Daemon (RSHD)

Backup and Recovery

Incremental backup of filesystems

Generating an index

System State backup

Controlling Open File Manager

Restoring with Open File Manager

Excluding files from backup

Installing COSmanager Enterprise Windows Client

Further Information

Known Problems in this Release