Not sure of course...But, I would blame NFS
Did you check the negotiated speed of your NFS eth 10G ifaces?
And that network?
Regards,
--
Sasa Drnjevic
www.srce.unizg.hr
On 24.7.2017. 15:49, Zoltan Forray wrote:
> 8-cores/16-threads. It wasn't bad when it was replicating from 4-SP/TSM
> server
Hi Zoltan!
You are right! I just checked and this is new in 7.1 and higher. So I stand
corrected.
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan
Forray
Sent: maandag 24 juli
8-cores/16-threads. It wasn't bad when it was replicating from 4-SP/TSM
servers. We had to stop all replication due to running out of space and
until I finish this cleanup, I have been holding off replication. So, the
deletion has been running standalone.
I forgot to mention that DB backups are
On 24.7.2017. 15:25, Zoltan Forray wrote:
> Due to lack of resources, we have had to stop replication on one of our SP
> servers. The replication target server is 7.1.6.3 RHEL 7, Dell T710 with
> 192GB RAM. NFS/ISILON storage.
>
> After removing replication from the nodes on source server, I have
Due to lack of resources, we have had to stop replication on one of our SP
servers. The replication target server is 7.1.6.3 RHEL 7, Dell T710 with
192GB RAM. NFS/ISILON storage.
After removing replication from the nodes on source server, I have been
cleaning up the replication server by deleting
Actually there are the APPLICATION fields/columns.
APPLICATION_VERSION,APPLICATION_RELEASE,APPLICATION_LEVEL,APPLICATION_SUBLEVEL
For example, on a node that uses the Oracle TDP, I get
APPLICATION_VERSION = 7
APPLICATION_RELEASE = 1
APPLICATION_LEVEL = 3
APPLICATION_SUBLEVEL = 0
or 7.1.3.0 for
