The Snap Creator Framework error messages can help you troubleshoot any issues that occur.
Error code | Error message | Description/resolution |
---|---|---|
scf-00001 | Could not get the serial number %s | Make sure that the serial number is set or blank. The serial number when set can only be numeric. This means that the Snap Creator setup was not run. Run the snapcreator --profile setup command. |
scf-00002 | Backup handling of plug-in [%s] failed with error [%s] and exit code [%s], Exiting! | Application backup failed due to an application error. Check the logs and application settings. |
scf-00003 | Backup cleanup handling of plug-in [%s] failed with error [%s] and exit code [%s], Exiting! | Application backup cleanup failed due to an application error. Check the logs and application settings. |
scf-00004 | Clone handling of plug-in [%s] failed with error [%s] and exit code [%s], Exiting! | Application clone failed due to an application error. Check the logs and application settings. |
scf-00005 | Clone cleanup handling of plugin [%s] failed with error [%s] and exit code [%s], Exiting! | Application clone cleanup failed due to an application error. Check the logs and application settings. |
scf-00006 | Pre-clone handling of [%s] failed with error [%s] and exit code [%s], Exiting! | Application pre-clone operation failed due to an application error. Check the logs and application settings. |
scf-00007 | Post-clone handling of plug-in [%s] failed with error [%s] and exit code [%s], Exiting! | Application post-clone operation failed due to an application error. Check the logs and application settings. |
scf-00008 | Cloned LUN igroup map of [%s] to igroup [%s] on [%s] failed, Exiting! | The igroup mapping for the LUN clone failed. Check the error. There might be a NetApp Manageability error that might reveal the cause of the problem. |
scf-00009 | NetApp Management Console backup list end for dataset [%s] failed with exit code [%s], Exiting! | Snap Creator started the backup delete operation in NetApp Management Console, but failed to list Snapshot copies. Make sure that Snap Creator is registering backup and check the configuration parameters NTAP_PM_UPDATE and NTAP_DFM_DATA_SET. |
scf-00010 | NetApp Management Console backup list is undefined, no backups for dataset [%s] exist, Exiting! | Snap Creator started the backup delete operation in NetApp Management Console, but the Snapshot copies exist. Make sure that Snap Creator is registering backup and check the configuration parameters NTAP_PM_UPDATE and NTAP_DFM_DATA_SET. |
scf-00011 | NetApp Management Console backup version ID [%s] Timestamp [%s] Delete for dataset [%s] failed with exit code [%s], Exiting! | Make sure that Snap Creator is registering backup and check the configuration parameters NTAP_PM_UPDATE and NTAP_DFM_DATA_SET. |
scf-00012 | Retrieving NetApp Management Console dataset status for dataset [%s] failed with exit code [%s], Exiting! | Make sure that the dataset exists and status is conformant. Also make sure that the dataset was created by Snap Creator. Datasets that are not created by Snap Creator are not application datasets and do not work. |
scf-00013 | Failed to register the Snapshot copies with dataset [%s] exit code [%s] | Check the configuration parameters NTAP_PM_UPDATE and NTAP_DFM_DATA_SET. |
scf-00014 | NetApp Management Console backup start for [%s] ([%s]) failed, Exiting! | Check the configuration parameters NTAP_PM_UPDATE and NTAP_DFM_DATA_SET. |
scf-00015 | NetApp Management Console backup for job-id [%s] completed with errors - [%s]|[%s]|[%s]|[%s] | Snap Creator started the NetApp Management Console backup and getting the progress of the same failed. Check the configuration parameters NTAP_PM_UPDATE and NTAP_DFM_DATA_SET. |
scf-00016 | SnapMirror status for [%s] failed, Exiting! | Snap Creator was unable to find any SnapMirror relationships for the given controller. Log in to the storage controller and run a snapmirror status command and make sure that the relationship exists. |
scf-00017 | SnapMirror relationship for [%s]:[%s] does not exist, Exiting! | Snap Creator was unable to find SnapMirror relationships for the given controller:volumes. Log in to the storage controller and run a snapmirror status command and ensure that the relationships for the given controller name exist. If a different name is used, then you must configure the SECONDARY_INTERFACES parameter to tell Snap Creator what maps to the storage controller. |
scf-00018 | SnapVault Status list for [%s] failed, Exiting! | Snap Creator was unable to find any SnapVault relationships for the given controller. Log in to the storage controller and run the snapvault status command and make sure that the relationship exists. |
scf-00019 | SnapVault relationship for [%s]:[%s] does not exist, Exiting! | Snap Creator was unable to find the SnapVault relationship. Log in to the storage controller and run the snapvault status command and ensure that the SnapVault relationship for the given controller name exists. If a different name is used, then you must configure the SECONDARY_INTERFACES parameter to tell Snap Creator what maps to the storage controller. |
scf-00020 | Running SnapVault update on destination [%s] using source [%s] failed! | Snap Creator was unable to start SnapVault update. Log in to the storage controller and run the snapvault status command and ensure that the SnapVault relationship for the given controller name exists. If a different name is used, then you must configure the SECONDARY_INTERFACES parameter to tell Snap Creator what maps to the storage controller. |
scf-00021 | SnapMirror transfer error detected - [%s], Exiting! | Check the error and storage controller settings for SnapMirror. |
scf-00022 | SnapMirror update on source [%s] failed to complete in [%s] minutes, Exiting! | The SnapMirror update took longer than the configured wait time. You can adjust the wait time by increasing the value for NTAP_SNAPMIRROR_WAIT in the configuration file. |
scf-00023 | SnapVault update on source [%s] failed to complete in [%s] minutes, Exiting! | The SnapVault update took longer than the configured wait time. You can adjust the wait time by increasing the value for NTAP_SNAPVAULT_WAIT in the configuration file. |
scf-00024 | SnapVault transfer Error detected - [%s], Exiting! | Check the error and storage controller settings for SnapVault. |
scf-00025 | Post restore handling of plug-in [%s] failed with error [%s] and exit code [%s] | Application post restore operation failed due to an application error. Check the logs and application settings. |
scf-00026 | Restore cleanup handling of plug-in [%s] failed with error [%s] and exit code [%s] | Application restore cleanup operation failed due to an application error. Check the logs and application settings. |
scf-00027 | Pre restore handling of plug-in [%s] failed with error [%s] and exit code [%s] | Application pre restore operation failed due to an application error. Check the logs and application settings. |
scf-00028 | Auto Discovery for plug-in [%s] failed with error [%s] and exit code [%s], Exiting! | Application discovery failed due to an application error. Check the logs and application settings. In addition, automatic discovery can be disabled by setting APP_AUTO_DISCOVERY=N and commenting out VALIDATE_VOLUMES. |
scf-00029 | Auto Discovery for plug-in [%s] failed because environment is empty, Exiting! | The application plug-in is not supported to use automatic discovery. Disable automatic discovery by setting APP_AUTO_DISCOVERY=N. |
scf-00030 | File system quiesce for plug-in [%s] failed with error [%s] and exit code [%s], Exiting! | File system quiesce failed due to file system error. Check the logs and file system settings. To ignore errors and proceed with the backup, you can set APP_IGNORE_ERROR=Y. |
scf-00031 | File system quiesce for plug-in [%s] encountered errors, exit code [%s], proceeding with backup! | File system quiesce failed due to file system error. However, APP_IGNORE_ERROR=Y; Snap Creator will proceed with the backup. Check the logs and file system settings. |
scf-00032 | Application unquiesce failed due to application error. To ignore application errors and to proceed with backup, you can set APP_IGNORE_ERROR=Y | Check the logs and application settings. |
scf-00033 | Application unquiesce for plug-in [%s] failed with exit code [%s], proceeding with backup! | Application unquiesce failed due to application error. However, APP_IGNORE_ERROR=Y; Snap Creator will proceed with the backup. Check logs and application settings. |
scf-00034 | LUN clone create of [%s] from [%s] on [%s]:[%s] failed, Exiting! | The LUN clone creation failed. Check the error; there might be a NetApp Manageability error that might reveal the cause of the problem. |
scf-00035 | Inventory of LUNs on [%s] failed, Exiting! | The LUN list create failed. Check the error; there might be a NetApp Manageability error that might reveal the cause of the problem. |
scf-00036 | Application quiesce for plug-in [%s] failed, no exit code returned from plug-in, Exiting! | Application quiesce finished with no exit code. Check the logs and application settings. |
scf-00037 | Application quiesce for plug-in [%s] failed with error [%s] and exit code [%s], Exiting! | Application quiesce failed due to application error. Check the logs and application settings. To ignore application errors and proceed with backup, you can set APP_IGNORE_ERROR=Y. |
scf-00038 | Application quiesce for plug-in [%s] failed with exit code [%s], continuing with backup. | Application quiesce failed due to application error. However, APP_IGNORE_ERROR=Y; Snap Creator will proceed with the backup. Check the logs and application settings. |
scf-00039 | The controller [%s] specified did not match any controllers specified in the configuration. Check the NTAP_USERS parameter in the configuration file. | Check NTAP_USERS and make sure that the storage controller is defined in the configuration file. |
scf-00040 | The volume [%s] specified did not match any storage system or volume specified in the configuration. Check the VOLUMES parameter in the configuration file. | Check the VOLUMES setting in the configuration file and ensure that the correct controller volumes are configured. |
scf-00041 | Clustered Data ONTAP detected but CMODE_CLUSTER_NAME is not configured correctly. Check the configuration parameter, Exiting! | The parameter CMODE_CLUSTER_NAME is required and used for AutoSupport and SnapMirror. Define this correctly in the configuration file. |
scf-00042 | Clustered Data ONTAP detected, but CMODE_CLUSTER_USERS is not configured correctly. Check the configuration parameter, Exiting! | The parameters CMODE_CLUSTER_NAME and CMODE_CLUSTER_USERS are required and used for AutoSupport and SnapMirror. Define these correctly in configuration file. |
scf-00043 | SnapVault is not supported in clustered Data ONTAP, set NTAP_SNAPVAULT_UPDATE to N in configuration. | Check configuration and change parameter. Clustered Data ONTAP does not support SnapVault. |
scf-00044 | The META_DATA_VOLUME parameter is defined, but storage system:volume specified does not match what is configured in VOLUMES parameter. Check the configuration. | This happens if the META_DATA_VOLUME parameter is not specified in VOLUMES. Add the metadata volume to VOLUMES. |
scf-00045 | The META_DATA_VOLUME parameter is defined but it cannot be the only volume specified in VOLUMES parameter. The metadata volume must be a separate volume. | This happens if the volume specified in META_DATA_VOLUME is the only volume present in VOLUMES. There should be other volumes also. Do not use META_DATA_VOLUME for normal Snapshot operation. |
scf-00046 | NetApp Management Console supports only timestamp Snapshot copies. | Update the configuration file and set the SNAP_TIMESTAMP_ONLY option to Y. |
scf-00047 | Incompatible settings have been selected. The NTAP_SNAPVAULT_UPDATE and NTAP_SNAPVAULT_SNAPSHOT options both cannot be enabled | Edit the configuration file and disable one of the two options. |
scf-00048 | Mount handling of plug-in [%s] failed with error [%s] and exit code [%s], Exiting! | Application mount failed due to an application error. Check the logs and application settings. |
scf-00049 | Umount handling of plug-in [%s] failed with error [%s] and exit code [%s], Exiting! | Application umount failed due to an application error. Check the logs and application settings. |
scf-00050 | Custom action is supported only for application plug-ins | The APP_NAME parameter was not set in the configuration file. This determines which plug-in to use. The custom action is only supported with an application plug-in. |
scf-00051 | NetApp Management Console dataset creation failed for [%s] with exit code [%s], Exiting! | Check the debug error message. There could be a problem communicating with the OnCommand Unified Manager server. |
scf-00052 | Restore handling of plug-in [%s] failed with error [%s] exit code [%s], Exiting! | Restore failed due to an application error. Check the logs and application settings. |
scf-00053 | File system unquiesce for plug-in [%s] failed with error [%s] and exit code [%s], Exiting! | File system unquiesce failed due to file system error. However, APP_IGNORE_ERROR=Y; Snap Creator will proceed with the backup. Check logs and file system settings. |
scf-00054 | File system unquiesce for plug-in [%s] encountered errors, exit code [%s], proceeding with backup! | File system unquiesce failed due to file system error. However, APP_IGNORE_ERROR=Y; Snap Creator will proceed with the backup. Check logs and file system settings. |
scf-00055 | NetApp Management Console driven backup [%s] of dataset [%s] with policy [%s] on storage controller [%s] | |
scf-00056 | Creating NetApp Management Console driven backup [%s] of dataset [%s] with policy [%s] on storage controller [%s] finished successfully | |
scf-00057 | Creating NetApp Management Console driven backup [%s] of dataset [%s] with policy [%s] on storage controller [%s] failed with error [%s] | Check the configuration parameters NTAP_PM_UPDATE and NTAP_DFM_DATA_SET. |
scf-00058 | Update configuration with application discovered value failed for [%s], Exiting! | Could not update the file. This is usually a permissions problem or failure to parse the values returned from the application. Check the permissions of the user running Snap Creator and ensure that the permissions are correct. |
scf-00059 | [%s] dump for plug-in [%s] failed with exit code [%s], Exiting! | The scdump action failed due to an application error. Check the logs and application settings. |
scf-00060 | Invalid DTO: [%s] | A required field in the DTO is not set or is invalid. This caused a validation error when processing the DTO. Correct the issue and resend the DTO. |
scf-00061 | Archive log deletion failed with error [%s], Exiting! | Snap Creator could not delete the archive logs for a given application. Check the permissions for the Snap Creator user; this could be the Snap Creator Server or Snap Creator Agent, depending on the configuration. |
scf-00062 | Authentication Failed! | Authentication failed, user does not have permission to perform the operation. |
scf-00063 | Discovery for [%s] failed with return code [%s] and message [%s] | Application discovery using VALIDATE_VOLUMES=DATA failed due to an application error. Check the logs and application settings. |
scf-00064 | Discovery discovered no storage objects | Application discovery using VALIDATE_VOLUMES=DATA failed. Snap Creator was unable to discover any data volumes residing on the storage system. To disable automatic discovery, comment out VALIDATE_VOLUMES. |
scf-00065 | Volume [%s] on [%s] is not included in the configuration file | Application discovery detected that some volumes are missing. Check for the missing volumes and add them to VOLUMES parameter so they can be included in the backup. |
scf-00066 | Agent validation failed for [%s] with error [%s] | Configured agent is not reachable. This might be because the agent is down or there is a local firewall issue. Check the configuration parameter SC_AGENT. |
scf-00067 | Failed to list external Snapshot copy for [%s] with name pattern [%s] | Snap Creator could not find external Snapshot copy based on regx pattern NTAP_EXTERNAL_SNAPSHOT_REGEX. Log in to the controller and match the snap list output with regx pattern. |
scf-00068 | File system pre_restore for plug-in [%s] failed with exit code [%s], Exiting! | File system pre-restore failed due to file system error. Check the logs and file system settings. |
scf-00069 | File system pre_restore for plug-in [%s] encountered errors exit code [%s], proceeding with backup! | File system pre-restore failed due to file system error. However, APP_IGNORE_ERROR=Y; Snap Creator will proceed with other operations. Check logs and file system settings. |
scf-00070 | File system post_restore for plug-in [%s] failed with exit code [%s], Exiting! | File system post restore failed due to file system error. Check the logs and file system settings. |
scf-00071 | File system post_restore for plug-in [%s] encountered errors, exit code [%s], proceeding with backup! | File system post restore failed due to file system error. However, APP_IGNORE_ERROR=Y; Snap Creator will proceed with other operations. Check the logs and file system settings. |
scf-00072 | Policy [%s] is not a defined Snapshot copy retention policy in the configuration, Exiting! | The policy you are using is not valid. Check the configuration file and configure NTAP_SNAPSHOT_RETENTIONS properly. |