You are here: Plan > Use a Script Policy to Run Snap Creator

Use a Script Policy to Run Snap Creator

If you want to use ECX to back up a NetApp storage system or take application-aware snapshots, run NetApp Snap Creator using a Script policy in ECX.

This topic offers instructions for running Snap Creator remotely on a Windows 2008 R2 client machine by using a Script policy.

BEFORE YOU BEGIN:

  • Ensure Snap Creator server is installed and running on the Windows client machine.
  • Familiarize yourself with the syntax of the snapcreator command.
  • For scripts that require a password, enable secure password-less execution of scripts:
    • Ensure ssh is configured on the client machine. For Windows, use various sshd installations such as OpenSSHd or free sshd.
    • Ensure you can ssh to the client machine successfully from the ECX virtual appliance.
    • Ensure you have the password-less login to the client machine using ssh.
ClosedSnapcreator Command Syntax:

Syntax for the snapcreator command follows:

snapcreator.exe –profile <profile> -action <action> -config <config> –verbose

where:

  • <profile> is the name of the profile created within Snap Creator.
  • <action> is the action taken, such as snap, restore, delete, mount.
  • <config> is the Snap Creator configuration file located in the specified profile. It is required when multiple configuration files are present within the profile or when the profile name is different from the configuration file name.
  • – verbose displays all job log information to STDOUT.

To run Snap Creator remotely on a Windows 2008 R2 machine by using a Script policy:

  1. Write a batch script and save it under any location on your Windows client machine. For example, it could be saved as C:\snapcreator.bat. The following is an example of a valid batch script:
  2. @echo OFF
  3. set SCPRODIR="C:\Program Files\NetApp\Snap_Creator_Framework\scServer4.0.0"
  4. cd /D %SCPRODIR%
  5. snapcreator.exe -server 192.0.2.24 -port 8080 -user admin -passwd sysadmin -profile My_Profile -config VolumeSnapshot1 -action backup
  6. Start ECX.
  7. Navigate to Plan > All Policies > New > Miscellaneous > Script. The Script Policy Editor opens.
  8. Construct a Script policy that contains a single command:
  9. ssh <userId>@<Hostname/IP of client machine> powershell -command "<Path of script>"
  10. Click Finish to save the policy.
  11. Associate the Script policy with a schedule and run the job.

NEXT STEPS:

  • Track the progress of the job on the Monitor tab. See Monitor a Job Session.
  • If notification options are enabled, an email message with information about the status of each task is sent when the job completes.

RELATED TOPICS:

 

Catalogic ECX™ 2.4

© 2016 Catalogic Software, Inc. | All rights reserved. | 7/15/2016

MySupport | Knowledge Base | Trademarks | info@catalogicsoftware.com