القائمة
Freeze the IRIS instance for an external (OS/SAN-level) snapshot backup and thaw it safely afterward — thaw ALWAYS runs, even if the snapshot step failed.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | run-external-backup |
| description | Freeze the IRIS instance for an external (OS/SAN-level) snapshot backup and thaw it safely afterward — thaw ALWAYS runs, even if the snapshot step failed. |
No server profile specified — omit server (or pass "") to use the default server on every tool call below.
Safety invariant: the instance must NEVER be left frozen. Step 4 (thaw) runs unconditionally, even if the external snapshot in step 3 failed or was cancelled.
iris_journal_info to confirm journaling is healthy (state, free space) before freezing.iris_backup_manage action 'freeze' to quiesce ALL database writes instance-wide (Backup.General.ExternalFreeze). This is DISRUPTIVE — no writes are accepted until thawed. Optionally supply 'logFile' and 'description'.iris_backup_manage action 'thaw' to resume database writes (Backup.General.ExternalThaw). If 'thaw' itself fails, retry immediately and escalate to the user — the instance must not be left frozen.iris_journal_info again and confirm journaling has resumed (state is normal, not frozen).iris_backup_manage action 'listHistory' to record/confirm the run in the backup history log.Report the overall outcome (frozen → snapshot result → thawed → journaling confirmed resumed) to the user.
Review and promote configuration/code drift from a source IRIS environment to a target using the review-before-write iris_env_diff -> iris_env_promote workflow (scoped diff, plan, an explicit user-selected step allowlist, confirmed execute, re-diff verify). Never acts on onlyInTarget warnings -- never deletes a target-only item, in any action.
Resend failed Interoperability messages for a config item using the dry-run-first iris_message_resend workflow — preview the match count before executing, then verify the new headers via iris_production_messages. States the duplication hazard and that resend/resendFiltered are governance-default-disabled writes.
Audit the IRIS instance's security posture: users (default passwords, %All holders), roles, service authentication settings, SSL/TLS configs, and instance auditing status.
Run a full IRIS instance health check (iris_health_check) and interpret every non-ok finding, naming the fixing tool for each one.
Deploy an ObjectScript class or package to IRIS (iris_doc_load, glob-path form), fix compile errors, then run its unit tests (iris_execute_tests) with a total-count check.
Diagnose a slow SQL query using iris_sql_analyze (explain, indexUsage, stats) and recommend a fix — never auto-applies one.