How to push the backup job to the Primary IBDR Appliance from the Secondary IBDR Appliance

How to push the backup job to the Primary IBDR Appliance from the Secondary IBDR Appliance

Introduction

There are some recovery scenarios that require the backup job to exist on the Primary IBDR Appliance, for example: 
  • Full System Image restore using DR Image backup job.
  • Full System VM Image restore using VMware or Hyper-V job.
  • File and folder restore with a significant amount of data using any type of job.

In case there is a need for recovery, but the desired job does not exist on the Primary IBDR Appliance (but exists on the Secondary), it is possible to push the backup job from the Secondary IBDR Appliance to the Primary.

While the job is being pushed from the Secondary Appliance to the Primary Appliance, replication will be unable to push any other jobs to the secondary appliance.

Prerequisites

  • You are logged in to the Secondary IBDR Appliance Management Console

If you need assistance on how to log in please refer to the following articles:
How To Access a Cloud Appliance via the Infrascale Dashboard
How To Access IBDR Appliance Management Console via LAN

Instructions

1) Navigate to the "Jobs", "History" tab and find the job you would like to push.


2) Select the job you would like to push and click on "Push Back to Primary".

Note that the only one backup job can be pushed from the secondary appliance to the primary at a time.



Once you click on "Push Back to Primary", you will get a popup with a confirmation that the job was added to the queue.


Replication will start pushing the backup job from the Secondary Appliance to the primary. It will take some time which depends on the amount of data and throughput between appliances. Once it is completed, the backup job will appear on the primary IBDR Appliance in the "History", "Jobs" tab.

The backup job pushed back to the primary appliance will be pinned. This means it will not be removed automatically by the retention policy. If you wish to delete that job manually, it will need to be unpinned first on the Primary Appliance.