topic Re: trying to get Snap Creator (Cache) to freeze the file system AFTER it the CACHE DB is stopped and BEFORE a snapshot is taken? in Data Protection

trying to get Snap Creator (Cache) to freeze the file system AFTER it the CACHE DB is stopped and BEFORE a snapshot is taken?

jerryh — Thu, 05 Jun 2025 05:44:56 GMT

We’re trying to get Snap Creator (Cache) to freeze the file system AFTER it the CACHE DB is stopped and BEFORE a Netapp snapshot is taken,

but don’t see a place in the GUI to do this. Any resources whom can help?

Here’s a log example:

########## PRE APPLICATION QUIESCE COMMANDS ##########

[2014-01-22 10:52:24,453] INFO: Pre application quiesce commands are not defined

########## PRE APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY ##########

[2014-01-22 10:52:24,469] INFO: Application auto discovery is not enabled skipping .

[2014-01-22 10:52:24,469] INFO: Validate volume is not enabled skipping validate volume task.

########## Application Quiesce ##########

[2014-01-22 10:52:26,044] DEBUG: [10.255.4.80:9090 (4.0.0.1)] CACHE::setENV finished successfully

[2014-01-22 10:52:26,044] INFO: [10.255.4.80:9090 (4.0.0.1)] Quiescing instance REL

[2014-01-22 10:52:26,044] DEBUG: [10.255.4.80:9090 (4.0.0.1)] Executing command: su root "-c /usr/bin/csession REL -U%SYS '##Class(Backup.General).ExternalFreeze(\"\",\"NetApp SnapCreator attempting to freeze instance...\",1,\"\",\"\",1,\"\",\"\",\"\")'"

[2014-01-22 10:52:26,044] INFO: [10.255.4.80:9090 (4.0.0.1)] Quiescing command output:

Journal file switched to:

/epic/reljrnalt/REL20140122.002

Journal marker set at

offset 196624 of /epic/reljrnalt/REL20140122.002

[2014-01-22 10:52:26,044] INFO: [10.255.4.80:9090 (4.0.0.1)] Quiescing instance finished successfully

########## Application Quiesce finished successfully ##########

########## POST APPLICATION QUIESCE COMMANDS ##########

[2014-01-22 10:52:26,232] INFO: Post application quiesce commands are not defined

########## POST APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY ##########

########## PRE NTAP COMMANDS ##########

[2014-01-22 10:52:26,434] INFO: Pre ntap commands are not defined “Need filesystem freeze command to happen here”

########## PRE NTAP COMMANDS FINISHED SUCCESSFULLY ##########

########## Generating Info ASUP on prinetaappc2 ##########

[2014-01-22 10:52:26,934] INFO: STORAGE-01001: Creating autosupport message with event id [0], category [Backup Started], description [INFO: Snap Creator Framework 4.0p1 Backup for Rel_ss ACTION: backup POLICY: daily Plugin: CACHE Not supported Volumes: fc_lun_epic_aix_poc_Relvg, Started], level [INFO], hostname [NTAPWFAPP01 [10.255.4.80:9090]].

[2014-01-22 10:52:26,934] DEBUG: <ems-autosupport-log>

<computer-name>NTAPWFAPP01 [10.255.4.80:9090]</computer-name>

<event-id>0</event-id>

<event-source>SNAPCREATOR</event-source>

<app-version>Snap Creator Framework 4.0p1</app-version>

<category>Backup Started</category>

<event-description>INFO: Snap Creator Framework 4.0p1 Backup for Rel_ss ACTION: backup POLICY: daily Plugin: CACHE Not supported Volumes: fc_lun_epic_aix_poc_Relvg, Started</event-description>

<log-level>6</log-level>

<auto-support>false</auto-support>

</ems-autosupport-log>

[2014-01-22 10:52:26,934] INFO: STORAGE-01002: Creating autosupport message with event id [0], category [Backup Started], description [INFO: Snap Creator Framework 4.0p1 Backup for Rel_ss ACTION: backup POLICY: daily Plugin: CACHE Not supported Volumes: fc_lun_epic_aix_poc_Relvg, Started], level [INFO], hostname [NTAPWFAPP01 [10.255.4.80:9090]] finished successfully.

[2014-01-22 10:52:26,934] INFO: ASUP finished successfully on prinetaappc2

########## Running Snapshot copy Rename on Primary devices ##########

Re: trying to get Snap Creator (Cache) to freeze the file system AFTER it the CACHE DB is stopped and BEFORE a snapshot is taken?

spinks — Wed, 22 Jan 2014 17:02:29 GMT

Jerry,

You've highlighted the PRE_NTAP area of the config file, so the work is partially done as you know when you want the command to run.

You will need to perform two steps:

1) Add command to the config file - This command can't be added through the GUI - You'll need to open the config file through a text editor - You can either open the file directly on the Snap Creator Server by logging into the server and changing directories to: path/to/scServer/engine/configs/<profile> and editing the .conf file -or- you can right click on the config file in the GUI and download it. Change the file then right click on the profile to upload it (you will be prompted to overwrite).

Specifically you are looking for the PRE_NTAP_CMD - use the search function of your editor - it will likely be the second entry as the first is the description.

Add your command to: PRE_NTAP_CMD01=

Save your file (Upload the file if you downloaded it)

Reload the configuration file in the GUI so that you have the latest copy (click the reload button)

2) once you have the command defined in the config file, you need to allow the command to be run on the Snap Creator Agent.

You didn't mention what version of Snap Creator you were using - I am guessing 4.0 or older. The instructions are slightly different for 4.1.

For 4.0 and older the Agent contains a file called agent.conf - this is located in the Agent installation directory:

/path/to/scAgent/config/agent.conf

Open agent.conf using a text editor

Add the command to the file - for example, if using chfs, then update the agent.conf to read:

command: chfs

*please note the space between the ":" and the command*

Save the file.

For 4.1 and up the process is slightly different - instead of agent.conf there is a file called allowed_commands.config. This is located in the Agent install directory at:

/path/to/scAgent/etc/allowed_commands.conf

Open allowed_commands.conf using a text editor

Add the command to the file - for example, if using chfs, then update the agent.conf to read:

command: chfs

*please note the space between the ":" and the command*

*If using a script or a command that isn't in the PATH statement then the command must be fully qualified - with agent.conf sdcli.exe was ok, but with allowed_commands.confg the full path must be listed*

Save the file.

Restart the Snap Creator Agent for the command to be accepted

These two changes should allow the command to work.

I can't advise you on the proper commands to use.

You may want to consider using SnapDrive to take the Snapshot copies instead of using the native method of taking Snapshots - this is especially true in a Windows environment.

The steps would be very similar, except that instead of adding PRE_NTAP you would want to add a NTAP_SNAPSHOT_CREATE_CMD.

This can be done using the GUI by adding a "Snapshot Copy Create Command" in the command tab of the GUI.

You will still need to allow the Snapshot copy Create Command to run on the agent side as described above.

Hope this helps!

John

Re: trying to get Snap Creator (Cache) to freeze the file system AFTER it the CACHE DB is stopped and BEFORE a snapshot is taken?

sivar — Wed, 22 Jan 2014 17:03:51 GMT

Hello Jerry,

Snap Creator Framework snapshots are crash-consistent snapshots.

In your case, since you have CACHE application on top of FCP LUNs in AIX Operating System, you may want to make use of chfs like commands.

A quick video is discussed here. http://poweritpro.com/aix/how-freeze-and-thaw-file-system-aix

You may be able to prove that Data ONTAP's crash consistent snapshots are good enough for your application.

If you want to be more sure by quiescing your Operating System's filesystem, then those commands go in the PRE_NTAP commands. (which is what the message is about).

Note: In my experience, your application may be okay with crash-consistent snapshots. Most modern journal filesystems can recover from a crash consistent snapshot.

Thanks,
Siva Ramanathan