Before upgrading, you should do the following:
- Perform test upgrades
- We strongly recommend running test upgrades against copies of current production databases.
- Create an upgrade schedule.
- Plan your
StarTeam Server upgrade when it will inconvenience the smallest number of users. A
StarTeam Server configuration cannot be running during some of the steps you take before and during the upgrade. You may want to plan the
StarTeam Server upgrade at the end of the workday or perhaps on a weekend. If you have a large repository or a slow system, the upgrade process
could be time consuming. Depending on the size of your database, you might need to schedule a couple of down-times for the
upgrade. For example, you might schedule one weekend for upgrading the
StarTeam Server and another for upgrading the database. Make backups before and after each of these steps to prevent loss of data.
- Advise your team ahead of time that you plan to make this transition during a specified period of time, and advise them when
they will need to have the latest version of a
StarTeam client installed. Unless specifically stated,
StarTeam clients for a given release work with that
StarTeam Server release, one release back, and one release forward. When an older client works with a newer
StarTeam Server, the client cannot access new features. For example, the older client cannot display any new menu commands.
- Backup the server configuration
- Make certain you have current, verified backups of the files and folders for the
StarTeam Server configuration (database files, archive files, and so on) prior to starting important steps in the upgrade process.