| The format for storing privacy information changed in Sametime 7.5. If your users have stored privacy information ("who can see me") on an earlier release of Sametime, this information appears to be lost after upgrading to Sametime 7.5 or 7.5.1 from a release prior to Sametime 7.5.
This document provides information about running a utility after upgrading your server to Sametime 7.5 to migrate the privacy information to the correct format for Sametime 7.5.
There is no need to run this utility unless you have upgraded from an earlier release and your users have stored privacy data from the earlier release.
NOTE for Sametime 7.5.1 and later Releases: This document and the attached .tar file only apply to upgrades to Sametime 7.5. If you are upgrading to a later release, such as 7.5.1, the command to migrate privacy data is included in the product and has also been changed and enhanced. You can now select a subset of users rather than migrating privacy data for ALL users. To migrate privacy data after upgrading to Sametime 7.5.1, see the installation and upgrade information for your server platform.
Notes:
- If you have multiple Sametime servers within a single Sametime Community (but have not configured them as a Community Services cluster), each of the servers maintains a separate version of vpuserinfo.nsf. It is highly recommended that you run the upgrade utility on each of the Sametime servers in the community immediately after upgrading each one to Sametime 7.5.
If you delay running the utility, users may create additional privacy data on the Sametime 7.5 server. In this situation, the new data is stored in addition to the existing data and it is not predictable which privacy record will be used. Running the upgrade utility will not solve the problem. If necessary, the administrator can manually delete one of the privacy records from vpuserinfo.nsf.
- If you have multiple Sametime servers operating as a Sametime Community Services server cluster to support server failover and load balancing, it is best to upgrade all of the servers to Sametime 7.5 at the same time if possible. Then you should immediately run the upgrade utility on just one of the Sametime servers in the cluster and allow the vpuserinfo.nsf updates to replicate to the other servers.
If it is not possible to upgrade all of the servers in the cluster at the same time, consider advising your users to avoid creating additional privacy data until all of the servers have been upgraded. If users who are connected to a server running a release prior to 7.5 create new privacy data, it will be stored in the older format. This may conflict with privacy data that has already been migrated to the newer format. More than one privacy record for a user and conflicts between the records can cause unexpected results. Running the upgrade utility again will not solve the problem. If necessary, the administrator can manually delete one of the privacy records from vpuserinfo.nsf.
- The time required to run the utility depends on the size of vpuserinfo.nsf . For example, running the utility for a 2G vpuserinfo.nsf file may take 30 minutes.
- When the utility runs, two files are created in the \lotus\domino\data directory:
-- vpuserinfo.nsf<time_stamp>: backup copy of vpuserinfo.nsf before it was modified by the utility
-- vpuserinfo.nsf<time_stamp>.log: log of activity which occurred when utility ran For Windows Sametime servers:
This example assumes the default Domino installation directory (c:\Program Files\Lotus\Domino).
1. Stop the Sametime server.
2. Open a Windows command prompt.
3. Run the following command:
<c:\program files\lotus\Domino> jvm\bin\java.exe -cp upgradeBLUtil.jar com.ibm.sametime.upgradeUtil.UpgradeUtil <server_data_directory>
(where "c:\program files\lotus\Domino" is the directory where the Domino server is installed).
If you do not specify the server data directory (the last parameter shown above), the SametimeDirectory entry in the sametime.ini file is used.
4. Check the vpuserinfo.nsf<time_stamp>.log file which has the latest time stamp to verify that the utility ran successfully.
For i5/OS Sametime servers:
1. Stop the Sametime server.
2. From any i5/OS command line, start the qsh shell interpreter:
3. Run the following shell commands:
cd <sametime_server_data_directory> upgrade_privacy
4. Check the vpuserinfo.nsf<time_stamp>.log file which has the latest time stamp to verify that the utility ran successfully.
You can exit qsh and browse to the file or run the following shell command to display the contents:
cat vpuserinfo*.log For AIX and Solaris Sametime servers: 1. Download the attached file (upgrade_util_unix.tar) and unzip it to any convenient directory on the server.
2. Make the script executable by running the following command:
- chmod u+x upgrade_util.sh
3. Stop the Sametime server.
4. Run the upgrade utility as the user defined for your Domino and Sametime deployment, typically "notes":
upgrade_util.sh <domino_program_directory> <sametime_server_data_directory>
5. Check the vpuserinfo.nsf<time_stamp>.log file which has the latest time stamp to verify that the utility ran successfully. |