Better Backup and Restore in WebTrends 7.x or worse?

WebTrends Backup Restore improvements in 7.0

[eforums]

Let's suppose today on 2/22/2005, I created a new profile and run logs from Jan 1st, 2004 to Feb 29th, 2004.

In WebTrends6.x, we can configure to keep 4 backups in archive so we will have snapshots of report data of
2/29, 2/22, 2/15, 2/8.

In 7.x, we can only have one data backup event today, so let set it to do backup after we ran logs from Jan 1st to 31st, 2004. Which means we have only one snapshot on Jan 31st, 2004 -- all the report data on this date and earlier.

Now here's the problem. If tomorrow 2/23/2005, we find a data problem in 2/28 report, in WT6.x, we can restore to 2/22, and fix the logs and rerun logs from 2/23 to 2/29.

However in 7.1, we can only restore to 1/31 and have to rerun the whole month of Feb, 2004 after we fix the logs on 2/28/2004.

Did I miss anything? Or we just miss the safty protection of having 4 or more backups within one day's data running in WT7.0?

Thanks for your opinions.

[cgrantski]

I think it's worse in the sense that you describe, but I don't fully understand the Data Retention settings and there could be something there to counteract what you describe. Before, you could keep backups in time period chunks. Now, it seems your backups are more like normal system backups, and are stored by the date of the analysis, not of the analyzed data. Maybe they figure that if you can analyze months of data in a day or less, it won't be too terrible to re-analyze. Dunno.