chucks0 Absent Member.
Absent Member.

Backups and TSATEST

I have been living with poor backup performance with SMS based backups since we initially deployed OES2 in our environment. After a lot of testing, I have discovered that servers with 1 CPU (physical or virtual) perform terribly. Adding a 2nd CPU (physical or virtual) results in a performance increase of 400 percent or more. With 2 CPUs, the OES2 servers finally achieve throughput similar to our 1 CPU Windows servers.

Does anyone have any ideas why SMS performs so poorly with 1 CPU? I have already tried tuning tsafs by reducing readthreadsperjob and readaheads with no luck. TSATEST seems to reveal that file close time is the real culprit.
Labels (2)
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: Backups and TSATEST

Sorry that I have nothing to say to help you, but I am curious about what
your performance numbers actually are with the 1 and 2 cpu configurations.

I am testing backup software right now (Arkeia and possibly NetVault by
BacBone). The Arkeia backup is getting between 600MB/min and 3.2GB/min
from a NetWare vm, the average is 1.6GB/min. CPU utilization ranges from
50% to 80% and stays mostly around 70%+.

Eventually I'll be testing other clients - SLES, MacOSX, Windows - but I
am not planning on testing OES2/Linux since I am waiting for OES3 to hit
the streets (summer 2011...?).


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.