07-29-2013 11:38 AM
Hello all,
I do have a window 2003 R2 server with service pack 2. earlier we were taking its backup through WAN and were getting superb throughput. but when we install a local appliance to the server and tried to take its backup it started with 30 KBPS. can someone help me on that
Solved! Go to Solution.
01-29-2014 01:11 PM
sorry guys, i forgot to put the solution of this query.
there was bandwidth throttling enabled for the client and entry was made in master server and that was provoking client to get the throughput.
We removed the entry and backup starts with good throughput.
Thanks all for your valuable suggestions.
07-30-2013 01:23 AM
07-31-2013 01:24 PM
Hi,
Thanks for your reply...
here are the details:-
Earlier the backup was taken via WAN. It was Client side Dedup Backup
Its a 5220, 4 x 1 GB 802.3ad bonding
1000/Full on client side
on WAn we were getting throughput of 50-60 MBPS
entries of PD.conf from the local appliance which is also media server are:-
08-02-2013 01:41 AM
ok. Thats strange!
is the less throughput observed each backup for the client? I ask you this - as I want to eliminate first time seeding issues.
And do you see similar issue with other client's side dedupe too ?
Are you able to capture the spoold log from the client. and media 5220 and check for gaps in the time delays if any ?
Interesting thing here for me is - Are the initial speeds better than 30KBps ? or is just over time the speed graph starts to detoriate ?
08-02-2013 06:49 AM
We have two clients at that location and earlier both were running over WAN going to master appliance in another state. Now we implemented local appliance, one client is giving marvellous throughput while other is giving only 30 KBPS.
how to collect spoold logs?
over WAN this client was giving good throughput and even now till the time issue got resolved we are running it over WAN. but on local appliance from very first day its throughput is 20-30 KBPS.
08-02-2013 07:50 AM
@nick17,
Spoold logs can be obtained here - <dedupe_partition>/log/spoold/spoold.log & <dedupe_partition>/log/spoold/storaged.log
What I also think here is the problem could be more at client side network settings!
Because - Appliance won't act strange with specific client incase of client side dedupe. Because Appliance is on the receiving end.
Now, the other client which is giving good throughput - could you ask Network guys to compare the configurations on these two clients to the switch? And the connection between switch and appliance.
Look at the hops and ask the network team for a data flow path between the slow throughput client and your local appliance.
Also as the backup is active - on the local appliance,
Main.menu> Network> Statistics , to see appliance NIC activity
08-05-2013 08:33 AM
Hi,
here are the findings from network team...
please find mentioned below answers to your queries regarding file server and appliance network connectivity.
Network guys to compare the configurations on these two clients to the switch?
Both the file servers are connected to same switch same module and have same port configuration.
And the connection between switch and appliance.
Connection between switch and appliance is intact and working fine with 4 gig ports bundled in Po2.
Look at the hops and ask the network team for a data flow path between the slow throughput client and your local appliance.
There is no L3 hop as appliance and file servers are in same vlan but two L2 hops between appliance and file servers. The two L2 hops are connecting appliance and connecting file servers and both of these switches are directly connected with each other. The path is same for both the file servers communication with appliance.
08-21-2013 07:06 AM
As only one client is affect it is the client you need to look at mainly, though it could be a DNS issue on the appliance too
I would start by adding hosts file entries on the client and appliance so that they do not need to use DNS when talking to each other
Next check out the pd.conf on the client - it may even be worth deleting the new appliance server entry from its ost-plugins directory and allow it to be re-creatred in case it has anything not quite right about it.
Hope this helps
01-29-2014 01:11 PM
sorry guys, i forgot to put the solution of this query.
there was bandwidth throttling enabled for the client and entry was made in master server and that was provoking client to get the throughput.
We removed the entry and backup starts with good throughput.
Thanks all for your valuable suggestions.