Symposium Web Client Server 4.02 User database 1

[hwntel]

I am in the process of replacing an outdated SWCS with a new machine the customer does not want to upgrade to 4.5.
How can I copy the user information (access and partition management, user passwords and reports) from the working server to the new one. The change will be done after hours because the customer wants NO user ipmact.

 

[johnpoole]

what rls is the old box? without an upgrade zero user impact is going to be a major problem.. happy testing

john poole
bellsouth business
columbia,sc

 

[hwntel]

My mistake 4.02.016.04

 

[sandyml]

Since the customer doesn't want to upgrade to 4.5, I will assume that you are using Windows 2000 vs. 2003. This will involve, in part, backing up and restoring the Active Directory. Here is the section from the NTPs:

Backing up and restoring user data:

Symposium Web Client makes use of Active Directory and other data files to store user data. Therefore, ensure you back up both Active Directory and the data files listed below. In addition, during the backup, you must ensure that no data is changed between backing up Active Directory and the data files. It is recommended, therefore, that you perform backups during periods of low activity.

Backing up Active Directory

In the Windows 2000 environment, Microsoft provides a backup utility that performs the Active Directory backup as part of the system state data backup.
System state data includes interdependent items such as the registry, system startup files, class registration database, certificate services database, file
replication service, cluster service, domain name service, and Active Directory.
When backing up data using this utility, choose Only back up the System State data and save the backup file in a safe location in your network.
For more information, refer to the procedures on Active Directory backup and restore in the Microsoft Windows 2000 Server documentation.
You may also want to consult the Microsoft documentation for other backup strategies. One important point to consider when choosing a backup utility is that it must allow you to back up Active Directory data (or system state data).
Choose the strategy that is most appropriate for your organization.

Backing up Symposium Web Client data files

In addition to storing user data in Active Directory, Symposium Web Client also stores other user information in various data files. Make sure you back up the
files listed below in their respective default paths.
In the following default path, c:\Program Files\Nortel Networks\WClient\Apps\Reporting\Historical\data
back up these files:
! LimitChecker.mdb
! Netcallbycall.mdb
! nicrpt.mdb
! nicrpt_dms.mdb
! schedule.mdb
In the following default path,
c:\Program Files\Nortel Networks\WClient\Apps\Common\Icedb
back up these files:
! Schedule.mdb
! icelog.mdb
In the following default path,
c:\Program Files\Nortel Networks\WClient\Apps\AccessMgmt\AccessXML
back up this file:
! counter.xml
In addition to the files listed above, you should also back up any files that you
have saved on the application server for Web Client operations, such as .rpt files
that you have created with Crystal Reports for the user-created historical reports.

Restoring data

Ensure that Active Directory and the data files that you are restoring were backed up at the same time; that is, you must ensure that the user data did not change between backing up Active Directory and the user data files. It is
recommended, therefore, that you perform backups during periods of low activity.

Restoring Active Directory

The Microsoft Backup utility also allows you to perform data restore. However, before you proceed, make sure that you have a copy of your system state data backup. Refer to the Microsoft Windows 2000 Server documentation on Active
Directory backup and restore procedures for details. As of date of publication, you can view this information at

http://www.microsoft.com/technet/tr...ows2000serv/reskit/distsys/part1/dsgch09.asp.

You may also wish to consult the Microsoft documentation for other suggested restore strategies. Choose the strategy that is most appropriate for your organization.
Note: You cannot restore a backup image that is older than the tombstone lifetime setting because your backup image may contain objects that have already been deleted and cannot be recovered. The tombstone lifetime is the
number of days that a deleted object is maintained before the garbage collection process permanently removes it from Active Directory. The default value is 60 days. For more information, see the article ?Backup of the Active Directory Has
60-Day Useful Life (Q216993)? on the Microsoft web site.
When you restore Active Directory, you can choose to restore it onto the same application server where the backup was created or onto a different application
server. When restoring onto a different application server, because you restore the system state data (which includes registry information) from the ?source? server,
your ?target? server inherits attributes, such as the computer name and IP address. Therefore, these two servers cannot both be active on the same network at the same time. Also, the location of the system root in your target application server should be the same as that in your source application server.

Restoring backed up data onto a server with a different hardware platforma:

To restore Active Directory onto a target application server that has a different
hardware platform, note the following:

! The target server must have the same type of hard disk controllers as the source server; in other words, it must have either Small Computer System Interface (SCSI) or Integrated Drive Electronics (IDE).
! The size of the target server hard disk must be at least as large as that of the source server.
! If your target server has a different video adapter or multiple network adapters, then you must uninstall them before you restart the server. The normal Plug-and-Play functionality makes the appropriate updates once
you restart the server.
! To simplify the restore procedure, Nortel Networks recommends that the source and the target application server support the same number of processors.

Restoring Symposium Web Client data files

When restoring data, ensure you restore all files to their original paths, as listed in the previous section on backing up data.

Backing up data from one application server and restoring it onto another:

The following section outlines the steps you need to perform to back up Symposium Web Client data from one application server and restore the same data to a brand new application server. You can use this procedure to recover
from a system failure should your Symposium Web Client application server fail completely (for example, due to hardware problems).

Note: Make sure you have read the previous sections on backing up and restoring data to understand the requirements of your new application server.
1. Create a system state data backup image of your existing Symposium Web
Client application server using the Microsoft Backup utility.
2. Make backup copies of Symposium Web Client data files.
Note: Nortel Networks recommends that you perform these two steps as often as necessary to always have copies of the latest data.
3. Follow the installation instructions listed in the checklists in Chapter 1 to install and configure the Windows 2000 Server operating system, thirdparty
software (such as Microsoft Active Directory and Sybase Open
Client), and Symposium Web Client on your new application server.

Note: Nortel Networks recommends that you install all software to the same directories as those used on your original application server.
4. Restore the system state data from the image created in step 1 using the Microsoft Backup utility.
5. Restore Symposium Web Client data files to their original paths.

After completing this final step, you should now be able to start using Symposium Web Client on your new application server. Since this new server has the same computer name and IP address as the original server, ensure that
the two servers are not active on the same network at the same time.

Note: You may have third-party software applications other than those mentioned in step 3 installed on your original application server; however, you do not have to install the same applications on your new application server. For a
complete list of software requirements on the application server, see ?Application server software requirements? on page 24.

Using ghost images

Instead of creating backup images of your application server as outlined above, you can back up and restore data on your application server by using a ghost
image. A ghost image is a snapshot of all the information installed on the PC, including the operating system and software applications. There are many thirdparty
applications that you can use to create ghost images of your PC. Use the application recommended by your company.