kaba1

updated

18 years ago

K

kaba1

1 Rookie

•

95 Posts

0

593

February 24th, 2009 16:00

iSCSI LUN replication Schedule

I heave read 300-004-188.pdf from EMC support.
it talks how to setup bandwidth for replication within the specific dates and hours.

I would like to configure only one of my iSCSI LUNs to replicate only
this hours. 12:30 PM to 1:30 PM and 6 PM to 8 AM every day
How do I set this up?

thanks in advance
  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    328

    0

    Posted February 26th, 2009 07:00

    This isnt how Replicator with the builtin scheduler works

    The Replicator V2 idea is that its a continous replication - you only specify the RPO via max_out_of_sync param per session and the system automatically schedules the updates to happen so that they meet the RPO.

    A couple of options I can think of to try:

    - use Replication Manager to control the ISCSI replication - RM does the scheduling based on fixed times and schedules´and can acommodate that

    - try stopping the replication session for that LUN at 8am and restarting it at 12:30pm through nas_replicate commands via the crontab

    - try changing the max_out_of_sync value for that session to a high value via nas_replicate modify and crontab
  • gbarretoxx1

    2 Intern

    •

    366 Posts

    328

    0

    Posted February 26th, 2009 04:00

    Hi,

    the bandwidth throttling schedule is configured per "Data Mover Interconnect" basis, and you can have only one per DM pair.
    So, all replication sessions using this interconnect will have the same throttling scheduling.

    Regards,

    Gustavo Barreto.
  • kaba1

    1 Rookie

    •

    95 Posts

    328

    0

    Posted February 27th, 2009 09:00

    Time_out_sync option - how does it work?
    is it X period of time vs. bytes size watermark? which ever comes first?

    what is the size in MB or GB is it allowing to be out of think?
  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    328

    0

    Posted February 27th, 2009 09:00

    for RepV2 its always minutes

    only for Replicator V1 there were two watermarks for minutes and MB's - but that didnt support replicating ISCSI LUNs from the GUI or CLI

    the way it works is that it notices how much data there is to transfer and what the transfer rate was for the last updates
    so it starts the next update in time that it should be completed before the time_out_of_sync expires

    so its basically the max. time your replica is "behind" your production LUN
  • kaba1

    1 Rookie

    •

    95 Posts

    328

    0

    Posted February 27th, 2009 09:00

    what is the name of the log for replication? i thought it is repl.out but I do not see it...
  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    328

    0

    Posted February 27th, 2009 09:00

    there are some internal logs in /nas/logs but since RepV2 works mostly on the data mover you should be looking there using "server_log server_2"