This points to the fact that the "connection" is bad.
Of course you can also verify that if you copy the files using another method.
If you achieve a similar result, it is obvious that there is something wrong with the network (configuration) - if the hardware itself is fine, it could well be that the traffic is routed in a strange way causing this limitation.
May I suggest you check the fundamental issues first before you rerun a test with NetWorker.
bingo.1
2.4K Posts
0
December 8th, 2015 06:00
Check whether the source data or the tape drive path is the troublemaker.
The easiest thing to do that is a "bigasm" backup or running a manual backup from the client for a huge file.
For details about "bigasm" please see "Performance Tuning Guide".
avmaint
1 Rookie
•
115 Posts
0
December 8th, 2015 20:00
the bigasm test also proved to be same from this backup client.
while backups were running on this test_grp one, I copied the backup client 4 savets into another group test_mj_grp and started a backup
now I see that 8 savestreams are sending data @1600KBps,
bingo.1
2.4K Posts
0
December 8th, 2015 22:00
This points to the fact that the "connection" is bad.
Of course you can also verify that if you copy the files using another method.
If you achieve a similar result, it is obvious that there is something wrong with the network (configuration) - if the hardware itself is fine, it could well be that the traffic is routed in a strange way causing this limitation.
May I suggest you check the fundamental issues first before you rerun a test with NetWorker.
avmaint
1 Rookie
•
115 Posts
0
December 11th, 2015 02:00
we escalated to DC team, who never told us what they did, but current transfer speed is 35000KBps. thanks for your concern.bingo
edino1
39 Posts
0
December 15th, 2015 06:00
You can try to speed up this backup with parallel save stream feature now...