Large Backing Store

we need to either expand our backingstore from 200GB to 400GB or split it into two
(which is not going to be easy). It literally took days to do a iwfsck on this (200gb) to try and
track down a problem with a branch. Does anyone else have large (300GB+) backingstores?
Do you have any metrics on how long things like iwfsck take to run against it?

Does it seem like a generally bad idea?

Thanks,
MArtin

Find more posts tagged with

Comments

iwovGraduate

What version of TS ? Patch/SP level ?
OS ?

Mfitch

we are currently running TS 5.5.2 on Solaris 8 current patches -
we hope to migrate to TS 6.5.1 when it's available.

how does this imact the size of a backing store?

iwovGraduate

how does this imact the size of a backing store?

TS version does make a difference on the size of your backing store since the backing store format has changed over the years with significant performance improvements. If you don't specify the details (atleast your TS version) its had for anybody to comment on your question(s).

Adam Stoller

You might want to look into MultiStore ... It costs $$'s for licensing but it allows you to subdivide your backing store fairly easily --- the one big caveat (besides the $$'s) is that virtually no commands operate between/across backing stores -- so only subdivide your backing store on clean lines where the content in one store has absolutely zero dependencies on the content in the other backing store(s) - otherwise you're probably going to run into some brick walls.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

bturns

Yeah, we've got a large BS over here. It also took us days to run iwfsck. I think ours is about 200GB.

Smiley Wink