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?
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.
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.
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