3 Replies Latest reply: Apr 9, 2013 5:12 AM by spinks RSS

snapcreator plugin with domino

RAKESHMOLE2
Currently Being Moderated

hi

I am using the snapcreator plugin for domino for the firstime.I was reading through the document and it says the single file/database *.nsf file restore is not supported unless it is a nfs filesystem.

is this true , since i use iscsi, is there any workaround for this , i mean like to mount the snapshot on another server.

Please let me know.

  • Re: snapcreator plugin with domino
    spinks
    Currently Being Moderated

    Rakesh,

     

    Single File Restore is only available through the GUI at this time with NFS environments.

    This is becuase Snap Creator by itself cannot make the block to file conversion.

    If you attempt to perform a single file restore all you can see is the underlying LUN - you cannot see the individual files.

    Since all we can see if the LUN, that is all Snap Creator can restore.

     

    If you are using Snap Creator 3.6 you CAN restore single files in a SAN (FC or iSCSI) environment - you just have to do it through the CLI instead of the GUI.

    I've added some details below including the necessary command structure.

     

    There is also a video on this that walks though the process:  https://communities.netapp.com/videos/2771

     

    Please let me know if you have additional questions.

     

    Thanks,

    John

     

    Single Database Restore OUTSIDE of Snap Creator

    A new feature in SC 3.6 is the ability to restore a file from outside of Snap Creator then use SC to apply change info and logging. Essentially this will require that Snap Creator be called after a file is restored through Snap Drive using a new action called --action custom. This would typically be used in a FC/iSCSI environment for single database restore.

    Here is an example of how this would be used:

    1. Mount a snapshot as a drive letter using SDW. (I copied the snapshot name to a text file to be sure that I had the right one before mounting)
    2. Copy a database from the temporary mount point to a location inside the Domino data directory (F:\Domino\data\restore\mail\<dbname>)
    3. Run the SC command:

    snapcreator.exe --action custom --profile domino --config fuji15 --params snapname=fuji15-daily_20120419130836 datapath=F:\Domino\data\restore\mail\dadams.nsf restoretype=u2m disablereplication=Y

    Here are the settings that you can use for this feature:

    snapname=

    • This is the name of the snapshot that you will be recovering data from. This snapshot must exist in the changeinfo folder as well for the changeinfo to be applied.

    datapath=

    • This is the path to the restored Domino database, including the database name

    restoretype=<u2m|su2m>

    • leave this parameter out to perform a point-in-time restore
    • u2m = up-to-the-minute
    • su2m = selectable up-to-the-minute. If this is used you will also need to use the restoretime= parameter

    restoretime=

    • provide this in '<date> <time>' format. An example is: '09/15/2011 17:13:00'

    disablereplication=<Y|N>

    • This parameter is used to disable Domino replication. This value defaults to 'N' if not included.
    • Re: snapcreator plugin with domino
      CHRISTIANMINIBEK
      Currently Being Moderated

      Hello,

       

      I tried this for a couple of times. When I am not using the restoretype, then the point-in-time is the snapshot-time - works fine. When I use u2m, the rollback of the logs is don up to now - workls also fine. But when I am using su2m with the restoretime parameter, it will be ignored. Allways a u2m is done, it does not matter which format I am using for the restoretime, seems to be ignored.

       

      Snapcreator 3.6.0

      SnapDrive 6.5
      Domino 8.5.3FP3 64bit on Windows 2008R2 64bit

      Running on a VM (ESX) with NFS Datastores

       

      Here is my log:

      [Tue Apr  9 10:20:00 2013] INFO: Logfile timestamp: 20130409102000

      [Tue Apr  9 10:20:00 2013] DEBUG: GMT - Tue Apr  9 08:20:00 2013

      [Tue Apr  9 10:20:00 2013] DEBUG: Version: NetApp Snap Creator Framework 3.6.0

      [Tue Apr  9 10:20:00 2013] DEBUG: Profile: Domino

      [Tue Apr  9 10:20:00 2013] DEBUG: Config Type: STANDARD

      [Tue Apr  9 10:20:00 2013] DEBUG: Action: custom

      [Tue Apr  9 10:20:00 2013] DEBUG: Application Plugin: domino

      [Tue Apr  9 10:20:00 2013] DEBUG: File System Plugin: null

      [Tue Apr  9 10:20:00 2013] DEBUG: Policy: null

      [Tue Apr  9 10:20:00 2013] DEBUG: Snapshot Name: null

      [Tue Apr  9 10:20:00 2013] INFO: Plugin validation for domino completed successfully

      [Tue Apr  9 10:20:00 2013] INFO: Removing log TLATSMSVLD01.out.20130404144244.log

      [Tue Apr  9 10:20:00 2013] INFO: Removing log TLATSMSVLD01.debug.20130404144244.log

      [Tue Apr  9 10:20:00 2013] INFO: Removing log TLATSMSVLD01.stderr.20130404144244.log

       

       

      ########## Parsing Environment Parameters ##########

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing VOLUMES - controller: atsm-mc-v01 volume: vm_sas_v01_dominodaos

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing VOLUMES - controller: atsm-mc-v01 volume: vm_sas_v01_dominodata

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing VOLUMES - controller: atsm-mc-v21 volume: vm_sas_v21_dominotranslog

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing NTAP_USERS - controller: atwo-bup-v01 user: root

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing NTAP_USERS - controller: atsm-mc-v01 user: root

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing NTAP_USERS - controller: atsm-mc-v21 user: root

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing NTAP_SNAPSHOT_RETENTIONS - policy: daily retention: 14

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing NTAP_SNAPVAULT_RETENTIONS - sv policy: daily retention: 21

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing SNAPVAULT_VOLUMES - controller: atsm-mc-v01 sv volume: vm_sas_v01_dominodaos

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing SNAPVAULT_VOLUMES - controller: atsm-mc-v01 sv volume: vm_sas_v01_dominodata

      [Tue Apr  9 10:20:00 2013] DEBUG: Parsing SNAPVAULT_VOLUMES - controller: atsm-mc-v21 sv volume: vm_sas_v21_dominotranslog

       

       

      ########## Custom plug-in action ##########

      [Tue Apr  9 10:20:00 2013] [tlatsmsvld01.itc.global.mahle:9090(3.6.0.1)] DEBUG: Restoring to current time.

      [Tue Apr  9 10:20:00 2013] [tlatsmsvld01.itc.global.mahle:9090(3.6.0.1)] DEBUG: Calling dominocore::postRestoreToTime with arguments(C:\Program Files\IBM\Lotus\Domino\notes.ini,D:\IBM\Lotus\Domino\data\restore,N:\ChangeInfo\TLATSMSVLD01-daily_20130408082121,-1,D:\IBM\Lotus\Domino\data\restore\test\Test.nsf,UP-TO-THE-MINUTE,N:\ChangeInfo\logs\)

      [Tue Apr  9 10:20:02 2013] [tlatsmsvld01.itc.global.mahle:9090(3.6.0.1)] TRACE: Notes API initialized

      Applying Change info for:D:\IBM\Lotus\Domino\data\restore\test\Test.nsf

      NSFRecoverDatabases returned successfully.

      ERROR_CODE:0

      [Tue Apr  9 10:20:02 2013] [tlatsmsvld01.itc.global.mahle:9090(3.6.0.1)] INFO: Restoring databases finished successfully

       

       

      ########## Custom plug-in action completed successfully ##########

      [Tue Apr  9 10:20:02 2013] DEBUG: Exiting with error code - 0

      • Re: snapcreator plugin with domino
        spinks
        Currently Being Moderated

        Christian,

         

        This is a known bug in Snap Creator 3.6. 

         

        As you noted point-in-time and up-to-the-minute actions work fine.

        Selectable up-to-the-minute always performs an up to the minute.

         

        It was discovered a few months ago and is fixed in Snap Creator 4.0.

        Currently there are no plans to fix this in Snap Creator 3.6 as the release of 4.0 is imminent. (Currently expected by the end of April).

         

        Sorry for the inconvenience!

         

        John

More Like This

  • Retrieving data ...