Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-16 Thread Ryder, Michael S
.folke...@gmail.com] > Sent: Thursday, September 15, 2016 3:17 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] protect pool plus replicate node equals poor > replication efficiencies > > There is a relatively new command called "protect stgpool" that does the >

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Nixon, Charles D. (David)
DSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] protect pool plus replicate node equals poor replication efficiencies There is a relatively new command called "protect stgpool" that does the "replication" of the data part that replication node used to do. You only do a replicate nod

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Stefan Folkerts
> > From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU ] on > behalf of Stefan Folkerts [stefan.folke...@gmail.com ] > Sent: Thursday, September 15, 2016 12:02 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] protect pool plus replicate node

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Nixon, Charles D. (David)
ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] protect pool plus replicate node equals poor replication efficiencies Do you have a fast Spectrum Protect database / active log? We run 2.4TB of metadata per hour with replication (note, this is not actual data, this is metadata representing 2.4TB of data).

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Stefan Folkerts
the 846GB over 4.5 hours. > > > > > > > > > > > > > > 09/15/16 10:58:08 ANR0327I Replication of node NODENAME > > > > > completed. > > > > > > > Files > > > > > > > current

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Ryder, Michael S
s replicated: 752 > of > > > > 752. > > > > > > Files > > > > > > updated: 602 of 602. Files deleted: 692 > > of > > > > 692. > > > > > > Amount > > > > > >

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Stefan Folkerts
updated: 602 of 602. Files deleted: 692 > of > > > 692. > > > > > Amount > > > > > replicated: 12,487 GB of 12,487 GB. > Amount > > > > > transferred: > > > > >

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Ryder, Michael S
(SESSION: 414242, PROCESS: 539) > > > > --- > > > > David Nixon > > > > Storage Engineer II > > > > Technology Services Group > > > > Carilion Clinic > > > >

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Stefan Folkerts
rvices Group > > > Carilion Clinic > > > 451 Kimball Ave. > > > Roanoke, VA 24015 > > > Phone: 540-224-3903 > > > cdni...@carilionclinic.org > > > > > > Our mission: Improve the health of the communities we serve. > > > > >

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Ryder, Michael S
cdni...@carilionclinic.org > > > > Our mission: Improve the health of the communities we serve. > > > > > > > > ____ > > From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] on behalf of Stefan > > Folkerts [stefan.fo

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Stefan Folkerts
mission: Improve the health of the communities we serve. > > > > > From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] on behalf of Stefan > Folkerts [stefan.folke...@gmail.com] > Sent: Thursday, September 15, 2016 10:45 AM > To: ADSM-L@VM.

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Nixon, Charles D. (David)
the communities we serve. From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] on behalf of Stefan Folkerts [stefan.folke...@gmail.com] Sent: Thursday, September 15, 2016 10:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] protect pool plus replicate node equals poor

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Stefan Folkerts
>Support confirmed that the amount of data replicated in a replnode command is the same, regardless of the protect pool command status. I think that this is only in the statistics, not in the actual transfer on the wire. the replnode should not transmit actual data if the data was send by the prot

Re: protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Karel Bos
Doc states only meta data should be replicated in that phase. Do you really see the 1tb go over the line or is it just being reported? Op 15 sep. 2016 16:33 schreef "Nixon, Charles D. (David)" < cdni...@carilionclinic.org>: > We opened a ticket related to long replication times in a container poo

protect pool plus replicate node equals poor replication efficiencies

2016-09-15 Thread Nixon, Charles D. (David)
We opened a ticket related to long replication times in a container pool after replication takes place, and got an answer that 'we can recreate your problem but it is likely working as designed' even though it's contrary to documentation. Any ideas would be appreciated. -Two TSM servers at 7.1