9 Replies Latest reply: Apr 23, 2013 9:23 AM by DHARENKAMP RSS

LREP with VSM vs. QSM options

Currently Being Moderated

First let me thank anyone in advance for their feedback this solution has be a bit perplexed. I have been pulled into something that was sold but clearly not architected prior...

 

We have FAS2050A's one in MI, one in MA and only a 4.5MB pipe between the two locations. We have two data sets that are supposed to be mirrored for DR purposes, both of these are 1.5TB in size. These are both LUN's dedicated to IBM's TSM servers. Neither of the devices can be shipped as they are being used for other production data. There is no Tape devices at either location so SM2T isn't an option. The data sets have both been built for VSM. Reading around I have seen LREP is an option for QSM but not VSM so here's my question...

 

Does anyone have either a crazy idea, or a way to migrate the Volume into a Qtree so I can setup QSM and LREP the data sets to USB?

 

Or could I license SV with LREP and utilize it to create the baseline SM relationship?

  • Re: LREP with VSM vs. QSM options
    adamfox
    Currently Being Moderated

    I'll need to know the volume layout before proposing any solution.  So what does the volume look like with respect to qtrees currently?  Where are the LUNs in the volume currently?

     

    -- Adam Fox

    • Re: LREP with VSM vs. QSM options
      Currently Being Moderated

      Simple Volume defined with 1 lun per volume, the TSM server is a windows 2008 server connecting via iSCSI. No qtrees used or defined (yet)

       

      example

      Aggr1

           Vol1

                Lun1

           Vol2

                Lun1

      • Re: LREP with VSM vs. QSM options
        adamfox
        Currently Being Moderated

        Ok then it's possible to have a QSM relationship and thus use lrep.  You can mirror the default qtree to an non-default qtree via QSM.  The name of the default qtree is -.  So you mirror /vol//qtree.  Note the dest. cannot be - since - always exists and destination qtrees cannot pre-exist. Note that the snapmirror relationship will have to be QSM going forward if using lrep.

         

         

        Hope this helps.

        -- Adam Fox

  • Re: LREP with VSM vs. QSM options
    STORAGESPECTOR
    Currently Being Moderated

    In the primary Site vol/qtree that is backed up to a USB extrnal drive. Use this command to back it up based on reading documentation;

     

    lrep_reader.exe -f SAN01 -q /vol/TCS_TCL -o F:\sv_init@0 ILCHIFSV03:D:\

     

    (secondary filer is SAN01) it backed up the volume and qtree, ex. files named sv_init at 1 gig chunks on my USB drive.

     

    Now transfer the USB drive to your secondary location (SAN01). Use lrep_writer to move the data over to this filer.

     

    I execute this command on a workstation with lrep_writer;

     

    lrep_writer.exe -p snapvault_start -O D:\sv_init


    lrep_writer: Will read 258 files from prefix d:\sv_init

     

    Error in socket (inet6) : 10047

     

                               **********************Waiting for connection (inet)**********************

     

    Use snapvault start command on secondary to create a relationship

     

    now go to the secondary filer and try to create the relationship by:

     

    snapvault start -S laptop:D:\sv_init /vol/TCS_TCL/TCS_TCL retail for example

     

    Please advise if you need more clarity

  • Re: LREP with VSM vs. QSM options
    lebedevanton
    Currently Being Moderated

    Lrep is a OSSV tool only to be used with Snapvault, you cannot use with volume snapmirror.

    so you cannot really use this solution to transfer your 1.5TB lun easily.

    Is there currently a snapmirror between the 2 filers?

     

    What may be a possibility is moving the lun into a qtree, and then using lrep to dump the qtree onto a 2TB USB Drive and ship it to your secondary dr filer where you maybe able to restore it.

     

    I had a similar situation.

    I have a filer in chicago and a dr filer in nj.

    1 TB qtree which i transfered to a usb drive and shipped to my dr location.

    transfered it over to my dr location (with a lot of trouble mind you, long story)

    changed the relationship between secondary filer/usb drive and primary filer... and im still stuck on an error now that the primary filer tells the secondary the snap is not there.

     

    I have a case open with Netapp, and let me tell you know the LREP support is so limited that many of the folks i spoke with dont know anything about it.

    Im having my case escalated to somebody thats really saavy in snapvault and knows the ins and out of it.

     

    I will post my findings as soon as I get it working

  • Re: LREP with VSM vs. QSM options
    fledoux.ovesys
    Currently Being Moderated

    LREP as a snapmirror_init mode to do snapmirror baselines. I used it a  couple of week ago and it works well. I used it to mirror qtrees, I  didn't test it with volumes.

     

    There is a good article on now that you can find with the following keywords: lrep snapmirror

     

    The lrep_reader command I used to copy my qtree to usb disk looks like this:

     

    lrep_reader.exe   -p snapmirror_init -f dest_filer -q /vol/dest_vol/dest_qtree -O -o   E:\path\data@0 src_filer:/vol/src_vol/src_qtree

     

    With  VSM you have another possibility called SnapMirror to tape (snapmiror  store, snapmirror retrieve commands)  but you need a drive a fc or sas  tape drive depending on which ports are available on your storage  system.

More Like This

  • Retrieving data ...