Highlighted
Absent Member.
Absent Member.
1507 views

What is considered 'good' or 'bad' with TSATEST?

I'm trying to find an objective test to find if a backup bottleneck is with
the disk system, the tape hardware or somewhere else in the chain. TSATEST
is supposed to do that. However, I've been unable to find a baseline
performance that can be considered good or bad.

Ofcourse it all depends on the harddisks, RAID controllers and the system
itself, but it would be handy to have a guideline saying something like 'Use
TSATEST with blocksize <x>, with <y> threads and such-n-such other options
to get a realistics performance test for Arcserve'. Similar guidelines for
Syncsort, Legato, NetVault, you name it. Does Novell offer such a list??

Rob


Labels (1)
0 Likes
2 Replies
Highlighted
Absent Member.
Absent Member.

Re: What is considered 'good' or 'bad' with TSATEST?

Rob,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://support.novell.com/forums/


0 Likes
Highlighted
Absent Member.
Absent Member.

Re: What is considered 'good' or 'bad' with TSATEST?

Rob Turk wrote:
> I'm trying to find an objective test to find if a backup bottleneck is with
> the disk system, the tape hardware or somewhere else in the chain. TSATEST
> is supposed to do that. However, I've been unable to find a baseline
> performance that can be considered good or bad.
>
> Ofcourse it all depends on the harddisks, RAID controllers and the system
> itself, but it would be handy to have a guideline saying something like 'Use
> TSATEST with blocksize <x>, with <y> threads and such-n-such other options
> to get a realistics performance test for Arcserve'. Similar guidelines for
> Syncsort, Legato, NetVault, you name it. Does Novell offer such a list??
>
> Rob
>
>

There's no such list I've ever seen. It'd be a matter of calling your
vendor's tech support, and finding out how many threads they use, ect.
Block size is more determined by what you setup in nss I'm thinking.
After that, it's just a matter of figuring out what the slowest
data-transfer link is in your chain. i.e. how fast can the drives spit
it out, what kind of bus is the raid controller on, how much memory does
the server have to use for buffering, ect. Ideally, tsatest should spit
out a transfer rate that is the max of your slowest component.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.