> Source: [sk173832](https://support.checkpoint.com/results/sk/sk173832)

# sk173832 - Installation fails on Secondary Security Management Server after restoring a backup on Full High Availability cluster members

| Property | Value |
|----------|-------|
| Solution ID | sk173832 |
| Date Created | 2021-06-04 |
| Last Modified | 2021-06-08 |
| Technical Level | Advanced |
| Products | Security Gateway, Security Management Server |
| Versions | R81 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- "`Installation failed. Reason: Peer sent SIC name different from name configured in server Security Management Server. Reset SIC from peer, and establish trust again.`" error in SmartConsole after restoring a backup on Full High Availability cluster members

## Cause

After restoring a backup on a new cluster member, it installs a restrictive Security Policy named "InitialPolicy" to protect itself. This policy blocks the sync connection

Example:

```
[Expert@HostName:0]# fw stat
HOST      POLICY           DATE
localhost InitialPolicy   28May2021 17:58:46 : [>eth0] [<eth0] [>eth1] [>eth2]
[Expert@HostName:0]#
```

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
