Skip to main content
NetApp Knowledge Base

SCSQL Backup Failure: “Host is not registered with SnapCenter”

  1. Last updated
  2. Save as PDF
Views:
7
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter Plug-in for Microsoft SQL Server (SCSQL)
  • SnapCenter Server 5.X (SC)
  • Microsoft SQL Server on Windows 2016 and above

Issue

SnapCenter SQL backup jobs fail with errors referring to unregistered or unreachable hosts. 

Log Output Examples:

ERROR SnapManagerWeb_243633 PID=[8076] TID=[102] Exception when creating request for host: Host <scsql_hostname> is not registered with SnapCenter.

ERROR SnapManagerWeb_243633 PID=[8076] TID=[102]ErrorCode(-1), ErrorMessage(Host <scsql_hostname> is not registered with SnapCenter.)

...

DEBUG SnapManagerWeb_243865 PID=[10064] TID=[19] Scheduledjob is not triggered on host(s) 'scsql_hostname' either because of the host(s) being not reachable or schedules not active. Marking them as failure.

Customer Context:

  • The affected SCSQL Plug-in host no longer exists or has been removed from SnapCenter.
  • Backup schedules in SnapCenter still reference the removed host.
  • Backup jobs for other hosts in the same resource group may also be marked as failed or show warnings, even if their backups complete successfully.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.