IBM TS7650G User Manual page 216

Force a repository to leave a grid only if the repository has been destroyed and
should not be part of the grid or is inconsistent with the grid. This situation might
arise if the Replication Manager was permanently destroyed, or if the repository
was removed from the grid without coordination due to temporary network
disconnection.
For example, if the Replication Manager was installed on a Target repository which
was destroyed, the replication grid can be restored from a Source repository that
was a member of the now destroyed grid. After restore, the repository "thinks" it is
part of the grid, but the Replication Manager might not recognize the repository as
part of the grid. The repository will, therefore, be marked as inconsistent and must
be forcibly removed from the replication grid via the Grids Management view.
Procedure
From the Grids Management view, select Repository > Uncoordinated repository
removal to forcibly remove a repository from a grid.
Note:
If this procedure is being performed in a Disaster Recovery (DR) mode scenario,
the repository can be forcibly removed from the grid from the Systems
Management view. Select Replication > Uncoordinated repository removal from
grid.
What to do next
Once the repository has been removed from the replication grid, add the new
repository to the replication grid. Go to "Adding a repository to a replication grid"
on page 101.
196
®
IBM TS7650G Deduplication Gateway for ProtecTIER : User's Guide for FSI Systems