Backing Up and Restoring Webtrends Data

Describes the Webtrends distributed architecture and introduces data recovery options. If you have a serious failure, or need to restore a large amount of historical data, you should contact Support for assistance.

How Webtrends Stores Data

Webtrends Analytics software stores your data both in user-defined file locations and in the Webtrends master database. To completely restore your Webtrends installation, you need to restore these files and the Webtrends master database. Webtrends recommends that you keep ongoing, coordinated backups of these components so that, in the event that you need to restore your data, you can restore it from closely aligned time periods.

Webtrends Visitor Data Mart software stores data in several different Microsoft SQL Server database locations as well as in the Webtrends master database; Webtrends Visitor Intelligence also stores data in an OLAP cube configuration. If you use Visitor Data Mart data, you should back up these locations regularly. For more information about required backups for Visitor Data Mart data, see Backing Up Webtrends Visitor Data Mart Data.

Webtrends 7.0 and higher provides the ability to scale individual components by adding more computers to accommodate the need for greater size and capacity.

Figure 1. Webtrends Distributed Architecture. Servers and databases in a typical Webtrends distributed architecture environment.

All data in this typical scenario is stored on the main application server. As you can see from the number of components with more than one server, this configuration provides some degree of fail-over and redundancy for many critical pieces of the operation.

The Webtrends Master Database is the central repository for all system-level configuration information. The Webtrends environment cannot run without the System Database intact, so a regular backup is critical to every operation. Microsoft SQL Server users should use their preferred tools and processes for backups.

Built-In Redundancies

As noted previously, many components of the Distributed Architecture environment can be easily built to expand for capacity or provide a higher level of availability by adding more systems. The following systems can be redundantly configured (and load balanced) or rebuilt relatively easily and quickly if no backup is available:

  • The SmartSource Data Collector
  • The User Interface server
  • The Webtrends Analysis Engine
  • The Event Database Loader
  • The GeoTrends database

These systems do not hold any data permanently, and are very quick to install and configure.

Webtrends Data Repositories

The non-database storage locations for your Webtrends data are specified during installation. However, you can change these storage locations. To determine where your data is stored, or to change your data storage locations, in the left pane, click Administration > Application Settings > System Management > Storage Locations .

Note: Storing your Backup Repository on a different computer from your Webtrends installation enables you to recover data in the event of a system failure.

Webtrends creates the following data (file-based) repositories:

Analysis Data Repository
Contains analyzed log data in compressed form.
Report Data Repository
Contains report-ready data that can be accessed by on-demand reporting.
Configuration Data Repository
Contains configuration settings for the Webtrends Web Analysis module.
Backup Repository
Contains any data created by Webtrends Analytics backup jobs.
Visitor History Export Repository
Contains data created by Visitor History exports.
Event Database Source Directory
Contains the log files before the Event Database Loader imports them into the Visitor Data Mart.

Backing Up Webtrends Analytics Analysis Data

When you create a profile backup job for a Webtrends Analytics profile, Webtrends backs up the analysis data for the profile. (After you restore, you can then regenerate your report data for the period after the backup by running an analysis based on the restored profile.) You can create backup jobs automatically for all new profiles or create them manually for individual profiles. Webtrends stores all data from backup jobs in the Backup Repository.

Note: When you first create a profile backup job, Webtrends also automatically backs up the configuration settings for the entire Web Analysis module. Configuration backups are used for reference by Support when recreating an older configuration. You cannot restore configuration data from a configuration backup. When you create a configuration backup, Webtrends does not display the backup in the Available Backups list.

To create profile backups for all future Webtrends Analytics profiles:

  1. In the left pane, click Administration > Application Settings > System Management > Backup/Restore > Backup Options .
  2. Select the New profiles will have backup jobs created check box. Webtrends creates a backup job for each subsequent profile you create. The backup event runs every 24 hours.

To create a backup job for a single profile:

  1. In the left pane, click Scheduler > Scheduled Jobs .
  2. Click New.
  3. In the Job Type dialog, click Backup Job.
  4. In the Profile dialog, select the profile you want to back up.
  5. Click Next.
  6. In the General dialog, type a description for the backup job. The description should identify the job as a backup job and link it to the correct profile.
  7. Click Next.
  8. In the Host Binding and Priority dialog, specify whether you want the backup job to run on any available host, or, if you have host groups configured in your distributed installation, select a host group. Host groups help you manage system resources in a distributed installation, and are defined in Administration > Application Settings > System Management > Host Groups .
  9. Select a job priority level. The job priority determines which jobs run first when multiple jobs are assigned to the same computer or host group. If all jobs are set to the same priority, jobs run in the order they enter the queue.
  10. Click Next.
  11. In the Schedule dialog, specify when and how often you want the backup job to run. By default, backup jobs run once per day.
  12. Click Next.
  13. Review the summary in the Summary dialog. Click Save to schedule the backup.

Viewing Available Backups

The Available Backups list shows all the backups that were created by a successful backup job, including the profile name and the date when they were created. To view the list of available backups in Webtrends Administration, select Administration > Application Settings > System Management > Backup/Restore > Restore Backup .

Backing Up a Microsoft SQL Server 2008 Express Edition System Database

You have two options for backing up a Microsoft SQL Server 2008 Express Edition database. You can download Microsoft SQL Server 2008 Management Studio Express from the Microsoft web site if you prefer to back up your database using a graphical interface. Alternately, you can use the sqlcmd utility included with Microsoft SQL Server 2008 Express Edition:

  1. Open a command prompt and navigate to the sqlcmd subdirectory in the Microsoft SQL Server 2008 Express Edition installation directory. By default, sqlcmd is located in the \Program Files\Microsoft SQL Server\90\Tools\Binn directory.
  2. Enter squelch.
  3. Enter BACKUP DATABASE database name where database name is the name of the SQL Server 2008 database.
  4. Enter TO DISK = 'pathname\database name.bak' where database name is the name of the SQL Server 2008 database and pathname is the fully qualified path to the directory where you will create the database backup.
  5. Enter WITH FORMAT;
  6. Enter GO

Restoring Webtrends Analytics Data from a Profile Backup

  1. Determine the date of the last good backup, or the date from which you want to begin reanalysis.
  2. Set your Webtrends Administration configuration settings to the state you want to use for reanalysis and future analyses. You can determine whether and when configuration changes were made using the Change History feature in Webtrends Administration. Use Webtrends Administration to make any required configuration changes.
  3. In the left pane, click Administration > Application Settings > System Management > Backup/Restore > Restore Backup .
  4. Mouse over the backup for the profile and date you want to restore and click Restore Backup on the Action menu.
  5. In the Restore Backup dialog, click Restore Backup to continue.
  6. Click OK.
  7. After you finish restoring, re-run analysis for the profile. Webtrends Analytics detects the dates of analyzed data that was restored and then reanalyzes any newer data from the log files available in this profile’s data source.

Backing Up Webtrends Visitor Data Mart Data

Webtrends Visitor Data Mart data resides in a Microsoft SQL Server 2008 database. To determine where your Visitor Data Mart data is stored, edit the profile in Webtrends Administration and click Analysis > Visitor Data Mart . This dialog shows the location of the Microsoft SQL database and the names of each component database. You can access these locations using Microsoft SQL Server 2008 Management Studio or another third-party tool.

Visitor Data Mart profile data includes the following components:

  • Event Database (EDB)
  • Module Database (MDB)
  • Extended Attributes Database (XDB)
  • Analysis Services Database (containing profile-specific cube information)

You should maintain regular backups of these databases using the SQL management tools of your choice. You should also back up your Analysis Services Database each time you make changes to your cube configuration. Back up the Analysis Services Database both before and after you change the cube configuration.

As a best practice, you should also back up the following Visitor Data Mart components:

  • The XMDB_System_Master database contains global information about Extended Attributes databases and can reside on the same Microsoft SQL database or in a remote location.
  • wtWHReporting resides on the same Microsoft SQL server location as XMDB_System_Master.

Finally, even if you do not use Webtrends Analytics profiles, you should always back up your Webtrends System Database.

Restoring Webtrends Visitor Data Mart Data

The following procedure is designed to restore data for a profile, not for your entire Visitor Data Mart installation. It includes instructions for restoring Visitor Intelligence cube data. For information about disaster recovery, you should contact Webtrends Support.

To restore data for a Visitor Data Mart profile:

  1. In the left pane, click Administration > Web Analysis > Reports & Profiles .
  2. Edit your Visitor Data Mart profile and select Analysis > Event Analysis .
  3. Click Analysis Paused. Pausing analysis allows Visitor Data Mart to continue collecting data while event data loading and other analysis processing is suspended.
  4. Using the third-party SQL tools of your choice, restore the Event Database, Module Database, and Extended Attributes Database for the profile.
  5. To restore from the .xmla file created when you backed up the Analysis Services Database, open a query in Microsoft SQL Server Management Studio or execute wtascmd.exe.
  6. Perform a complete cube reprocess:
    1. Open a command prompt and navigate to the wtCube directory.
    2. Execute this command:

      wtcube profileguid -processfull

      where profileguid is the ID for the profile you are restoring. You can find this ID by editing the profile in Webtrends Administration and clicking Summary.

  7. In the left pane, click Administration > Web Analysis > Reports & Profiles .
  8. Edit your Visitor Data Mart profile and select Analysis > Event Analysis .

Recovering from Data Center Failure

Planning for a data center failure can be complex, as it involves a large Webtrends topology as depicted in the System Requirements for Analytics and Visitor Data Mart. Here are a few things to keep in mind before beginning:

  • If the disaster recovery planning is limited to a situation where a data center is only temporarily unavailable, disaster recovery planning could focus specifically on providing access to reporting data, and not analysis.
  • The Webtrends environment uses Web log data in the analysis process, but makes no provisions to back up or restore Web log data. You must ensure that the original log data remains available.
  • The complete storage requirements for a Webtrends installation can be quite large. As a result, copying the data between data centers for fail-over can be time-consuming. Before proceeding with this scenario, ensure that the bandwidth capacity between data centers is sufficient to meet the needs of the environment.
Option 1: Data Collection and Reporting Redundancy

If your data loss is temporary, you can use a secondary environment to provide reporting. If you use this solution, no new data analysis can occur until the primary data center is recovered. Users will be able to log in to the Webtrends environment located at the secondary data center and view historical reports, but current data will not be analyzed. If you use the Webtrends SmartSource Data Collector, we recommend enabling a redundant SDC installation at the secondary data center so you can continue collecting SDC data while the primary data center is unavailable.

Figure 2. Storage Redundancy. Systems required for data collection and reporting redundancy

As an alternative, to reduce costs in the secondary data center, you could install the UI server directly on the main application server. Report performance and capacity will decrease slightly as a result, but this trade-off is often acceptable for a temporary situation.

Option 2: Full Redundancy of the Webtrends Environment

To plan for recovery after a total failure, you can duplicate the complete Webtrends system at the secondary data center to provide full capacity and full fail-over in the event of a catastrophic failure of the primary data center. In this scenario, you deploy an exact copy of each system at the secondary data center. Because Webtrends does not provide an automated method of fail-over, you would have to accomplish this with the help of your local IT resources.

Figure 3. Full Redundancy. Completely redundant deployment with secondary data center

Was this topic helpful? Send feedback.