Forum Moderators: DixonJones
How does everyone do it? I've already split the backup into multiple threads, reduced it down to only backup the core files, and eliminated anything not needed in the event of a failure. The backup still takes 24+ hours to complete.
The problem is the way WebTrends is laid out on the file level, with the thousands (millions maybe?) of small files that make up the structure of the program the tape drive needs to write a header and footer for every single file increasing the backup time by a huge factor.
Does anyone have any tips as to how to speed this thing up? It's one of the longest backups the company has, and it's not a small company. Being that support has always said that the program and it's services need to be down in order to back it up it means over a day of downtime for our customers. There must be some other way.
We are running 7.5b (going to 8.0a next month) on a single system. WebTrends is 100s of profiles big and takes up a few 100 gigs.
Thanks.
Also, we have WebTrends do backups of the databases and configurations through its admin console, putting the backups on a network drive. We've decided that weekly backups are enough though we did dailies for awhile. WebTrends' Scheduler agent seems to do it pretty efficiently.
You are right, WebTrends has zillions of files per profile, and this makes conventional tape backup really slooow.
[edited by: cgrantski at 9:09 am (utc) on July 10, 2006]
