3 Replies Latest reply: Mar 22, 2013 1:44 AM by tom.taelman@fitit.be RSS

Protect SMO Backup (version 3.2) without Protection Manager

michaeldparker
Currently Being Moderated

Hi All,

 

According to the SMO 3.2 documentation, I should be able to use Post scripts in SMO to tell SMO to proctect the DB to a secondary array without the use of Protection manager (see pg 186 of SMO Unix guide)  I'm attempting to follow the directions, but keep getting this error:

 

Snapmirror update failed:Can't connect to host (err=111). errno:111

 

This is when the script is executing this line:  $SM_SNAPDRIVE_HOME/bin/smsv snapmirror update $SECONDARY_STORAGE_NAME:$SECONDARY_VOLUME_NAME

 

I have added the array to snapdrive via the "snapdrive config set" command and I'm certain that the password is correct.  Does anyone have any idea how to troubleshoot this problem?  I assume by host it is referring to the storage array?

 

Thanks

 

Michael

  • Re: Protect SMO Backup (version 3.2) without Protection Manager
    3GISSMORACLE
    Currently Being Moderated

    Hi Michaeld ,

     

    Acctually I haven't used post scripts in SMO yet because I suppose that it's not easy to use. This is my own way , hope that it's helping you.

     

    -Create volumes in the secondary system.

    -Create snapmirror relationship between primary and secondary system in the secondary system.

    - Initialize snapmirror.

     

    Regards

    Tien

  • Re: Protect SMO Backup (version 3.2) without Protection Manager
    tom.taelman@fitit.be
    Currently Being Moderated

    I have the same issue but with SMSAP and SnapVault update.

    Sometimes it works and sometimes not.

     

    I could not find any log indicating what is the real problem

     

    When I execute the command (smsv snapvault update) manually, I could not create the problem.

     

    This is what I have in the SMSAP log file:

     

    2013-03-22 08:36:08,876 [RMI TCP Connection(2)-10.161.1.217] [DEBUG]: setting plugin global environment [SM_SNAPDRIVE_HOME] to [/opt/Ontap/snapdrive]

    2013-03-22 08:36:08,876 [RMI TCP Connection(2)-10.161.1.217] [DEBUG]: The Global Environment for plugin has been setted successfully

    2013-03-22 08:36:08,876 [RMI TCP Connection(2)-10.161.1.217] [DEBUG]: setting plugin specific environment [SECONDARY_STORAGE_NAME] to [netapp1]

    2013-03-22 08:36:08,876 [RMI TCP Connection(2)-10.161.1.217] [DEBUG]: setting plugin specific environment [SECONDARY_QTREE_NAMES] to [/vol/VAULT_DEV/SV_DEV_MIRRLOGA,/vol/VAULT_DEV/SV_DEV_MIRRLOGB,/vol/VAULT_DEV/SV_DEV_ORACLE,/vol/VAULT_DEV/SV_DEV_ORIGLOGA,/vol/VAULT_DEV/SV_DEV_ORIGLOGB,/vol/VAULT_DEV/SV_DEV_SAPDATA,/vol/VAULT_DEV/SV_DEV_USRSAP,/vol/VAULT_DEV_ARCHLOG/SV_DEV_ARCHLOG]

    2013-03-22 08:36:08,876 [RMI TCP Connection(2)-10.161.1.217] [DEBUG]: Plugin specific environment has been setted successfully

    2013-03-22 08:36:08,876 [RMI TCP Connection(2)-10.161.1.217] [DEBUG]: executing, timeout [0]: [/opt/Ontap/smsap/plugins/backup/create/post/Vault_the_backup.sh], argument [-execute]

    2013-03-22 08:36:08,876 [RMI TCP Connection(2)-10.161.1.217] [DEBUG]: EXE-00000: Executing shell command:

    2013-03-22 08:36:53,560 [Execution Monitor Thread [/opt/Ontap/smsap/plugins/backup/create/post/Vault_the_backup.sh -execute]] [DEBUG]: EXE-00001: Shell result [0:00:44.684] (Exit Value: 4):

    2013-03-22 08:36:53,561 [RMI TCP Connection(2)-10.161.1.217] [DEBUG]: [/opt/Ontap/smsap/plugins/backup/create/post/Vault_the_backup.sh] :[execute started, SECONDARY_STORAGE_NAME : netapp1, SECONDARY_QTREE_NAME : /vol/VAULT_DEV/SV_DEV_MIRRLOGA, , Snapvault update Success., SECONDARY_QTREE_NAME : /vol/VAULT_DEV/SV_DEV_MIRRLOGB, Snapvault update failed:Can't connect to host (err=110). errno:110, Command complete.]

    2013-03-22 08:36:53,561 [RMI TCP Connection(2)-10.161.1.217] [DEBUG]: stdout has entry [Command complete.]

    2013-03-22 08:36:53,561 [RMI TCP Connection(2)-10.161.1.217] [DEBUG]: plugin [Vault the backup] / [/opt/Ontap/smsap/plugins/backup/create/post/Vault_the_backup.sh] returned with [4]

    2013-03-22 08:36:53,561 [RMI TCP Connection(2)-10.161.1.217] [ERROR]: SMSAP-11176: Plugin "Vault the backup" completed with fatal errors and returned [[execute started, SECONDARY_STORAGE_NAME : netapp1, SECONDARY_QTREE_NAME : /vol/VAULT_DEV/SV_DEV_MIRRLOGA, , Snapvault update Success., SECONDARY_QTREE_NAME : /vol/VAULT_DEV/SV_DEV_MIRRLOGB, Snapvault update failed:Can't connect to host (err=110). errno:110, Command complete.]]. Plugin processing has been stopped.

  • Re: Protect SMO Backup (version 3.2) without Protection Manager
    tom.taelman@fitit.be
    Currently Being Moderated

    See KB ID: 2017185

    For error 111

     

     

    Symptoms

     

    SnapMananger for Oracle/ SnapManager for SAP (SMO/ SMSAP) are shipped with a post-task script to update an existing SnapMirror or SnapVault relationship. A failure occurs when trying to use this script:

     

    Plugin "Protect Backup" completed with fatal errors and returned [[execute started, SECONDARY_STORAGE_NAME : FILER, SECONDARY_VOLUME_NAME : /vol/smo_data/qtree, Snapmirror update failed:Can't connect to host (err=111). errno:111, Command complete.]]. Plugin processing has been stopped.

     

     

    Cause

     

    The post-task script calls the smsv executable that ships with SnapDrive for UNIX (SDU). This executable sends ZAPI calls to the secondary storage controller and is unable to contact the storage controller.

    Solution

     

    Perform the following steps as a workaround:

     

        Establish network connectivity from the database host to the secondary storage controller

        Set up SnapDrive to connect to the secondary storage controller

        snapdrive config set <storage user name> <storage name or ip>

        Set up the secondary storage controller to recieve ZAPI calls

        options httpd.admin.enable on

        -OR-

        options httpd.admin.ssl.enable on

     

     

    I'm having error 110

More Like This

  • Retrieving data ...