ADSM-L

Re: [ADSM-L] A few questions about Node Replication

2015-09-16 07:53:14
Subject: Re: [ADSM-L] A few questions about Node Replication
From: Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 16 Sep 2015 13:51:41 +0200
If you are using a TSM server on Linux I suggest reading about the tc
utility for limiting bandwith.
It changes the speed of the NIC as presented for applications so there are
no dropped/resent packages.
I have been using it with TSM replication for a while now and it works
great.



On Wed, Sep 16, 2015 at 1:21 PM, Karel Bos <tsm.wad AT gmail DOT com> wrote:

> Hi,
>
> Replicate node is done over the connection you use within the "define
> server" command. So it is using the TSM server to server connection path.
>
> You can define a link on OS level to be dedicated used for server to server
> commands (and thus also replication) while still provide client access over
> another interface to each of the TSM servers.
>
> Bandwidth trotteling isn't something you can define in TSM and using
> limited number of sessions to reduce network load might not work when
> source and target are for instance on fast disks.
>
> In our setup the clients can connect to both backup servers using 1 VLAN
> and we have TSM server to TSM server communication (also used for node
> replications) over an another VLAN.
>
> Kind regards,
>
> Karel
>
> 2015-09-09 16:19 GMT+02:00 Meunier, Yann <yann.meunier AT caissedesdepots DOT 
> fr
> >:
>
> > Hi Spectrum Men ☺,
> >
> > We want to implement the nodes replication functions on our TSM servers.
> > The network team asks me a few questions which I am not able to answer.
> >
> > Can we isolate replication traffic on dedicated interfaces?
> > I think so, defining a TSM server with a dedicated access, but I do not
> > know what is the impact for the B/A Client :
> > Is he able to perform a restore through the alternate server, knowing
> that
> > it does not use and does not see the replication link ?
> >
> > Example of def :
> >
> > 16:09:53 FFT0010I CMD1 : q server
> >   Server       Comm.      High-level              Low-level     Days
> >  Server         Virtual        Allow
> >   Name         Method     Address                 Address       Since
> > Password       Volume         Replacement
> >                                                                 Last
> >  Set            Password
> >                                                                 Access
> >                 Set
> >   --------     ------     -------------           ---------     ------
> >  ----------     ----------     -----------
> >   TSMCFG       TCPIP      TSMCFG.serv.cdc.fr      4010              <1
> >  Yes            Yes            No
> >   TSMHP11      TCPIP      tsmhp11.serv.cdc.fr     4120              <1
> >  Yes            Yes            No
> >   REPLLINK     TCPIP      tsmhp11repl.serv.cdc.fr 4120              <1
> >  Yes            Yes            No
> >
> > If the replication is based on definition REPLLINK, and this link is only
> > accessible by TSM Servers (Primary & Alternate), the B/A Client could
> > perform a restore via the alternate server by the TSMHP11 definition?
> >
> > The second question:
> > Can we limit the bandwidth consumption through TSM.
> > For me the only way is to play with the maximum number sessions of
> > replication processus.
> >
> > Best regards,
> >
> > Yann MEUNIER (Spectreman ☺)
> > Ingénierie - Système Stockage
> > Informatique CDC - Etablissement DPI
> > Office : +33 1 58 50 53 01
> > Mobile : +33 6 62 47 88 56
> >
> > Ce message et toutes les pièces jointes (ci-après le « message ») sont
> > confidentiels et établis à l’intention exclusive de ses destinataires.
> > Toute utilisation de ce message non conforme à sa destination, toute
> > diffusion ou toute publication, totale ou partielle, est interdite, sauf
> > autorisation expresse. Si vous recevez ce message par erreur, merci de le
> > détruire sans en conserver de copie et d’en avertir immédiatement
> > l’expéditeur. Internet ne permettant pas de garantir l’intégrité de ce
> > message, la Caisse des Dépôts et Consignations décline toute
> responsabilité
> > au titre de ce message s’il a été modifié, altéré, déformé ou falsifié.
> Par
> > ailleurs et malgré toutes les précautions prises pour éviter la présence
> de
> > virus dans nos envois, nous vous recommandons de prendre, de votre côté,
> > les mesures permettant d'assurer la non-introduction de virus dans votre
> > système informatique.
> >
> > This email message and any attachments (“the email”) are confidential and
> > intended only for the recipient(s) indicated. If you are not an intented
> > recipient, please be advised that any use, dissemination, forwarding or
> > copying of this email whatsoever is prohibited without Caisse des Depots
> et
> > Consignations's prior written consent. If you have received this email in
> > error, please delete it without saving a copy and notify the sender
> > immediately. Internet emails are not necessarily secured, and declines
> > responsibility for any changes that may have been made to this email
> after
> > it was sent. While we take all reasonable precautions to ensure that
> > viruses are not transmitted via emails, we recommend that you take your
> own
> > measures to prevent viruses from entering your computer system.
> >
> >
>