Highlighted

Client - Media - PureDisk Linux network traffic

Hello everyone.

 

We have a backup solution and I am trying to find a bottleneck.

Configuration is as follows:

Veritas SFHA clustered Master server running NBU 7.5.0.6 on RHEL6.1. 

Number of Media servers.

And 3 pairs of PureDisk 6.5.5 pools as a storage servers.

 

My concern is:

How does network traffic flow during backup assuming clientside deduplication is enabled?

I tried tcpdump and appears that it is client - media - puredisk and vica-versa. But there are nbstproxy processes.

 

Appreciate on any assistance. 

Thank you.

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Re: Client - Media - PureDisk Linux network traffic

I found it in 7.5 deduplication guide on a page 222.

Figure 10-5 shows the backup process of a client that deduplicates its own data. The destination is a PureDisk storage pool. A description follows.

View solution in original post

2 Replies
Highlighted
Accepted Solution!

Re: Client - Media - PureDisk Linux network traffic

I found it in 7.5 deduplication guide on a page 222.

Figure 10-5 shows the backup process of a client that deduplicates its own data. The destination is a PureDisk storage pool. A description follows.

View solution in original post

Highlighted

Re: Client - Media - PureDisk Linux network traffic

Please note that PureDisk has reached EOSL in 2014. 
See: https://sort.veritas.com/eosl/show_matrix 

Please discuss options to replace PD and mgrate from it with your local Veritas reseller.