Products
Webtrends Analytics 8.5
Webtrends Analytics 8.7
Webtrends Analytics 9.x
Cause
Last modified: 4/8/2013
Introduction:
A Webtrends Analytics 8.5x or later installation that has been removed from a server must be restored from the components backed up prior to removal.
Process:
How to install Webtrends Analytics using SQL Express (included):
1. Before beginning, ensure no Webtrends components, including SQL Server, are still installed on the server.
2. Run the installer and install Webtrends to the installation path used by the previous installation.
3. Stop the Webtrends services (some of the following may not be present):
“Webtrends – Scheduler Agent”
“Webtrends – User Interface”
“Webtrends – UI Web Services”
“Webtrends – Report Cache Server”
“Webtrends – Express Data Mover”
“Webtrends – Express Analysis Engine”
“Webtrends – GeoTrends”
“Webtrends – Email Notification Service”
“Webtrends – System Monitor”
“SQL Server(MSSQLSERVER)”
“SQL Server VSS Writer”
4. Rename the following folders and files:
\Webtrends\storage\
\Webtrends\common\database\SQLExpress\MSSQL.1\MSSQL\Data\wt_sched.mdf
\Webtrends\common\database\SQLExpress\MSSQL.1\MSSQL\Data\wt_sched_log.LDF
\Webtrends\common\database\SQLExpress\MSSQL.1\MSSQL\Data\wtMaster.mdf
\Webtrends\common\database\SQLExpress\MSSQL.1\MSSQL\Data\wtMaster_log.LDF
rename to:
\Webtrends\storage-clean
\Webtrends\common\database\SQLExpress\MSSQL.1\MSSQL\Data\wt_sched.mdf-clean
\Webtrends\common\database\SQLExpress\MSSQL.1\MSSQL\Data\wt_sched_log.LDF-clean
\Webtrends\common\database\SQLExpress\MSSQL.1\MSSQL\Data\wtMaster.mdf-clean
\Webtrends\common\database\SQLExpress\MSSQL.1\MSSQL\Data\wtMaster_log.LDF-clean
5. Copy the backed up \storage folders and files into the location above.
8. Start the Webtrends services in the opposite order in which they were stopped.
9. Log into the Webtrends user interface and verify the historical report data and configuration settings from the previous installation are now available.
How to restore Webtrends for installations using SQL Server Standard or Enterprise edition
1. Install SQL Server and select English as the default language.
2. Create two empty SQL Server databases. Name one of them “wtMaster” and the other “wt_Sched”.
3. Specify a port to which the Webtrends services will connect to the system database.
4. Create an SQL user account using Windows Authentication. This account will be the one used during installation of the product. The account must meet the following criteria for SQL Server:
The account must be a member of the securityadmin and dbcreator server roles.
The account must db_owner or db_ddladmin, db_datareader, and db_datawriter permissions for the Webtrends databases.
5. Open the SQL Server Configuration Manager and under the “Protocols” section ensure “TCP/IP” is enabled.
6. Make note of the host name of the SQL Server Standard or Enterprise Edition and the password for the SQL user account, as it will be required if Webtrends is installed on multiple servers in a distributed environment.
7. Install Webtrends to the installation path used by the previous installation.
8. Stop the Webtrends services (some of the following may not be present):
“Webtrends – Scheduler Agent”
“Webtrends – User Interface”
“Webtrends – UI Web Services”
“Webtrends – Report Cache Server”
“Webtrends – Express Data Mover”
“Webtrends – Express Analysis Engine”
“Webtrends – GeoTrends”
“Webtrends – Email Notification Service”
“Webtrends – System Monitor”
“SQL Server(MSSQLSERVER)”
“SQL Server VSS Writer”
9. Rename the following folder:
\Webtrends\storage\
rename to:
\Webtrends\storage-clean
10. Copy the backed up folder into the original location.
11. Open SQL Server Management Studio and restore the system database.
12. Start the Webtrends services in the opposite order in which they were stopped.
13. Log into the Webtrends user interface and verify the historical report data and configuration settings from the previous installation are now available.
Further information:
KB 062367 – How to manually back up and restore versions of Webtrends Analytics which use MySQL for the system database