Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Issues backing up our Backing Store (iw-store)
Wardo
We are having some issues backing up our backing store (iw-store). There doesn’t seem to be much information on backing up the TeamSite backing store (only 3 pages in admin guide) other than using iwfreeze and a discussion on backup of workareas through the file system mount (Y: Drive).
We are attempting to backup the backing store (located on d: drive on the TeamSite Server) using Veritas Netbackup Datacenter v3.4.1 SP_3. We are experiencing disconnects due to slow throughput (avg. 112kb/s). Has anyone else experience this?
We understand that the TeamSite Backing Store must reside on a single volume. Currently, the backing store resides on its own drive. Is this what most administrators are doing? Is anyone using NAS or SAN storage? If so, are you having good results?
Thanks for the feedback!
Find more posts tagged with
Comments
Migrateduser
I know that some folks have improved backup performance and reduced freeze time by doing a 2-stage backup: first, after freezing, copy the entire backing store to a new directory in the same volume, and then unfreeze. Then run the backup tool on the copy, deleting it when done.
As for other storage types, I'm ignorant. I can tell you that as per the backing store, you'll ge the best performance by using a RAID 0+1 hardware device. Alternatively, RAID 5 gives you hot-swap at slightly reduced drive access speeds.
bw
Bob Walden [bob.walden@interwoven.com]
Interwoven Education Group
IM: Yahoo, MSN bob_walden
Bryan_K
One of the things we have been doing to give us an extra level of protection is to run a nightly script that does an NT backup on our backing store. We shut down TeamSite completely to do this, but I believe you could probably just freeze the store and it would still work. Our backing store resides on a SAN for 1 server and a local drive array for the other. Each one seems to work fine using this method. In addition we use ADSM (Tivoli) and drop that to a tape.
Sundodger
What we do here (running 4.5.2) is to have a great big stripe mirrored three ways. That allows the ability to do a really quick iwfreeze and then break off a plex of the mirror. The mirror can then either stay out as a backup for the day and/or be backed up to tape. With 5.0, you can break up the backing store into partitions so it doesn't have to be on one volume.