Skip to main content
Druva Documentation

Re-register a Phoenix Backup Store

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

Re-register a Phoenix Backup Store to replace it with a new or if it gets disconnected. The Phoenix Backup Store can get disconnected from the Phoenix Cloud if:

  • A hardware refresh has been performed on the Phoenix Backup Store
  • A Phoenix Backup Store is replaced with a different server
  • A Phoenix Backup Store virtual machine is deleted from the vCenter host

Re-registration ensures that all the settings on the existing Phoenix Backup Store such as backup mounts, retention settings, maximum bandwidth, and the IP whitelist are applied to the new Phoenix Backup Store. Phoenix does not break the snapshot chain of the Oracle RMAN backups uploaded to the Phoenix Cloud from the Phoenix Backup Store.

Prerequisites

Perform the following steps on the Phoenix Backup Store that you want to replace:

  1. Run the following command to stop the Phoenix Backup Store service:
    sudo service PhoenixBackupStore stop        
    
  2. Run the following command to remove the existing ZFS pool on the Phoenix Backup Store:
    zpool destroy -f Phoenix
    
  3. Run the following command to remove the existing the database state:
    rm -rf /var/Phoenix/ExportService/database.db
    
  4. Remove the existing entries from /etc/exports.

Ensure that the PhoenixBackupStore service on the old Phoenix Backup Store is stopped.

In addition, ensure that the network settings of the Ubuntu server or the virtual machine that you are re-registering with Phoenix matches the network settings of the Phoenix Backup Store it replaces.   

Download the package and generate activation token

The Phoenix Backup Store package is available on the Druva downloads page. In addition, you can download the package when you generate the activation token. If you want to:

  • Set up the Phoenix Backup Store on a physical appliance, download the Debian package 
  • Set up the Phoenix Backup Store as a virtual machine, download the Open Virtual Appliance (OVA) package

To generate the activation token: 

  1. Log in to the Phoenix Management Console.
  2. From the top menu, select the Organization where you want to configure the Phoenix Backup Store.
    The Organization page appears. 
  3. On the Organization page, click Protect > Oracle from the top-menu. 
    The Oracle page appears. 
  4. On the Oracle page, under the Phoenix Backup Stores tab, click the name of the Phoenix Backup Store that is disconnected. 
  5. On the Phoenix Backup Store page, click Re-Register Store. The Re-Register Phoenix Backup Store wizard appears. 
  6. In the first step of the wizard, read the information and click Proceed.
  7. In the Install Package section of the wizard, use the Click here link to launch the downloads page and download the package. If you have already downloaded the package, click Next.
  8. In the Generate Activation Token section of the wizard, provide:
    Field Description
    Token Description A string that can help you identify the token.
    This token can activate <the number of> stores The number of Phoenix Backup Stores that can be activated using this token.
    The token expires in The number of days after which the token cannot be used for activating a Phoenix Backup Store.
    After you provide the details above, click Next
  9. In the Store Activation section, Druva provides the token that you use to activate the Phoenix Backup Store. Copy the token, save it on a text file, and click Finish. You can also navigate to Manage > Tokens from the top menu bar to get the token again. 

Deploy the Debian package on an Ubuntu server and register the Phoenix Backup Store

The Debian package that you download is deployed on an Ubuntu server to create the Phoenix Backup Store. The mount created on the Phoenix Backup Store serves as the location to store Oracle RMAN backups. 

Prerequisite

Ensure that the package is accessible on the Ubuntu server.

Deploy the package
  1. Connect to the Ubuntu server using PuTTy or launch the terminal on the Ubuntu server. 
  2. Install the ZFS package on the Ubuntu server. The command to install the ZFS package is:
    sudo apt install zfsutils-linux=0.7.5-1*
    
  3. Install the NFS kernel package on the server. The command to install the NFS kernel package is:
    sudo apt install nfs-kernel-server=1:1.3.4-2.1*
  4.  On the terminal, run the dpkg command with the path to the Debian package to install it.
    sudo dpkg -i <path-to-the-Phoenix-Backup-Store-debian-package>
    For example:
    sudo dpkg -i /home/test-usr/Downloads/druva-phoenix-backupstore-4.7.6-110.amd64.deb

    Ensure that you provide the correct path to the location of the Debian package and its name.
    These steps install the ZFS package,  the NFS kernel, and the Druva binaries that Phoenix needs to create the Phoenix Backup Store. 

  5. [Optional] If the Ubuntu server on which you are deploying a the Phoenix Backup Store Debian package is a VMware virtual machine, perform the following steps to set disk.EnableUUID = True on the virtual machine:

    1. On the vSphere client that is connected to the vCenter/ESXi host, select the virtual machine that you are configuring as a Phoenix Backup Store and then turn it off.

    2. Select the virtual machine on the vSphere client, and then click Edit Settings

    3. In the Virtual Machine Properties dialog, select the Options tab.

    4. In the Options tab, select General under Advanced on the left pane.  

    5. On the right pane, click Configuration Parameters... in the Configuration Parameters section. The Configuration Parameters dialog appears.

    6. In the Configuration Parameters dialog that appears, update the value of the parameter with the name disk.EnableUUID to true and then click OK
      If disk.EnableUUID parameter is not listed under the Name column, click the Add Row button to add it and then set its value to true.

    7. Turn the virtual machine on.

  6. After the package is installed, perform the following steps to create a ZFS pool using the disks on the Ubuntu server:
    1. To get the disk IDs, run the following command on the command line terminal:
      ls -l /dev/disk/by-id/ 
      
      The output of the command looks like:
      drwxr-xr-x 2 root root 460 Jan  2 07:21 ./
      drwxr-xr-x 7 root root 140 Jan  2 07:21 ../
      lrwxrwxrwx 1 root root   9 Jan  2 07:17 ata-VMware_Virtual_SATA_CDRW_Drive_00000000000000000001 -> ../../sr0
      lrwxrwxrwx 1 root root   9 Jan  2 07:21 scsi-36000c291a9ac60a4f33cfce60c7b3860 -> ../../sdc
      lrwxrwxrwx 1 root root   9 Jan  2 07:21 scsi-36000c29484ebb93eaece5ac0dc845d08 -> ../../sdb
      lrwxrwxrwx 1 root root   9 Jan  2 07:17 scsi-36000c29b9dce7313dfdb13871518563a -> ../../sdd
      lrwxrwxrwx 1 root root   9 Jan  2 07:17 scsi-36000c29f3116f1d4f65e63c182d3ecf0 -> ../../sda
      lrwxrwxrwx 1 root root  10 Jan  2 07:17 scsi-36000c29f3116f1d4f65e63c182d3ecf0-part1 -> ../../sda1
      lrwxrwxrwx 1 root root  10 Jan  2 07:17 scsi-36000c29f3116f1d4f65e63c182d3ecf0-part2 -> ../../sda2
      lrwxrwxrwx 1 root root   9 Jan  2 07:21 wwn-0x6000c291a9ac60a4f33cfce60c7b3860 -> ../../sdc
      lrwxrwxrwx 1 root root   9 Jan  2 07:21 wwn-0x6000c29484ebb93eaece5ac0dc845d08 -> ../../sdb
      lrwxrwxrwx 1 root root   9 Jan  2 07:17 wwn-0x6000c29b9dce7313dfdb13871518563a -> ../../sdd
      lrwxrwxrwx 1 root root   9 Jan  2 07:17 wwn-0x6000c29f3116f1d4f65e63c182d3ecf0 -> ../../sda
      lrwxrwxrwx 1 root root  10 Jan  2 07:17 wwn-0x6000c29f3116f1d4f65e63c182d3ecf0-part1 -> ../../sda1
      lrwxrwxrwx 1 root root  10 Jan  2 07:17 wwn-0x6000c29f3116f1d4f65e63c182d3ecf0-part2 -> ../../sda2
      
    2. To create a ZFS pool, run the following command:
      ./zpool_config_no_raid.sh <disk-id-of-disk1> <disk-id-of-disk2> ... 
      
      For this example, the command to use the disks sdb and sdc is:
      ./zpool_config_no_raid.sh scsi-36000c29484ebb93eaece5ac0dc845d08 scsi-36000c291a9ac60a4f33cfce60c7b3860
      
    3. The above disk IDs are examples. Ensure that you provide the correct disk IDs when you create a ZFS pool.  To create a ZFS pool with RAIDZ configuration:

      • Use zpool_config_raidz1.sh in place of zpool_config_no_raid.sh

      • RAIDZ configuration requires at least three disks.

      • The scripts are stored under the /opt/Druva/Phoenix/PhoenixBackupStore/bin folder on the Phoenix Backup Store.

  7. Run the following command to restart the Phoenix Backup Store service:

    sudo service PhoenixBackupStore restart
  8.  After installing the package and configuring the ZFS pool, run the activation command with the token you generated above to activate the Phoenix Backup Store:

    PhoenixBackupStoreControl activate <govcloud> <activation_token>
    

    Example activation command for public cloud

    PhoenixBackupStoreControl activate ExampleToken1234
    

    Example activation command for Gov cloud

    PhoenixBackupStoreControl activate govcloud ExampleToken1234
    

    Ensure that you replace example values with real values. In the above syntax, replace ExampleToken1234 with the token that you generate. 

The Phoenix Backup Store is deployed and registered with Druva. 

Deploy the OVA package on a VMware setup and register the Phoenix Backup Store virtual machine

In addition to the Debian package, Druva provides an open virtual appliance (OVA) package that you can use to create a Phoenix Backup Store on a VMware setup. The OVA package that you download is deployed on a VMware setup to create the Phoenix Backup Store virtual machine. The mount created on the Phoenix Backup Store serves as the location to store Oracle RMAN backups. 

Before you begin

Ensure that the OVA package is downloaded.

Deploy the package

To deploy the Phoenix Backup Store OVA on a VMware setup, see Deploy an OVF or OVA template [External link to VMware documentation].

Note: When the vSphere client prompts you to review the deployment details in the fourth step of the deployment process, ensure that you click Next. The vSphere client shows this warning due to the advanced configuration options that Druva adds in the OVA package to ensure that the virtual disks get a static disk-ID which is required for creating a ZFS pool.
ova_deploy_warning1.png

The OVA package can be deployed for vCenter/ESXi version 6.0 or later. After you deploy the Phoenix Backup Store OVA, start the virtual machine and connect to the virtual machine using PuTTy or any other remote utility. To log in to the Phoenix Backup Store enter:

  • root as the username
  • PBS@123 as the password

After logging in, perform the following steps on the terminal:

  1. Create a ZFS pool using the virtual disks. The following procedure describes how to create a ZFS pool.
    1. To get the disk IDs, run the following command on the command line terminal:
      ls -l /dev/disk/by-id/ 
      
      The output of the command looks like:
      drwxr-xr-x 2 root root 460 Jan  2 07:21 ./
      drwxr-xr-x 7 root root 140 Jan  2 07:21 ../
      lrwxrwxrwx 1 root root   9 Jan  2 07:17 ata-VMware_Virtual_SATA_CDRW_Drive_00000000000000000001 -> ../../sr0
      lrwxrwxrwx 1 root root   9 Jan  2 07:21 scsi-36000c291a9ac60a4f33cfce60c7b3860 -> ../../sdc
      lrwxrwxrwx 1 root root   9 Jan  2 07:21 scsi-36000c29484ebb93eaece5ac0dc845d08 -> ../../sdb
      lrwxrwxrwx 1 root root   9 Jan  2 07:17 scsi-36000c29b9dce7313dfdb13871518563a -> ../../sdd
      lrwxrwxrwx 1 root root   9 Jan  2 07:17 scsi-36000c29f3116f1d4f65e63c182d3ecf0 -> ../../sda
      lrwxrwxrwx 1 root root  10 Jan  2 07:17 scsi-36000c29f3116f1d4f65e63c182d3ecf0-part1 -> ../../sda1
      lrwxrwxrwx 1 root root  10 Jan  2 07:17 scsi-36000c29f3116f1d4f65e63c182d3ecf0-part2 -> ../../sda2
      lrwxrwxrwx 1 root root   9 Jan  2 07:21 wwn-0x6000c291a9ac60a4f33cfce60c7b3860 -> ../../sdc
      lrwxrwxrwx 1 root root   9 Jan  2 07:21 wwn-0x6000c29484ebb93eaece5ac0dc845d08 -> ../../sdb
      lrwxrwxrwx 1 root root   9 Jan  2 07:17 wwn-0x6000c29b9dce7313dfdb13871518563a -> ../../sdd
      lrwxrwxrwx 1 root root   9 Jan  2 07:17 wwn-0x6000c29f3116f1d4f65e63c182d3ecf0 -> ../../sda
      lrwxrwxrwx 1 root root  10 Jan  2 07:17 wwn-0x6000c29f3116f1d4f65e63c182d3ecf0-part1 -> ../../sda1
      lrwxrwxrwx 1 root root  10 Jan  2 07:17 wwn-0x6000c29f3116f1d4f65e63c182d3ecf0-part2 -> ../../sda2
      
    2. To create a ZFS pool, run the following command:
      ./zpool_config_no_raid.sh <disk-id-of-disk1> <disk-id-of-disk2> ... 
      
      For this example, the command to use the disks sdb and sdc is:
      ./zpool_config_no_raid.sh scsi-36000c29484ebb93eaece5ac0dc845d08 scsi-36000c291a9ac60a4f33cfce60c7b3860
      
    3. The above disk IDs are examples. Ensure that you provide the correct disk IDs when you create a ZFS pool. The OVA that Druva provides comes with three disks. However, the first two disks with the storage capacity of 100 GB each are for backup and the third disk with the storage capacity of 200 GB is for restore. Ensure that you do not use the third disk with 200 GB storage capacity for creating the ZFS pool. 

    4. To create a ZFS pool with RAIDZ configuration:

      • Use zpool_config_raidz1.sh in place of zpool_config_no_raid.sh

      • RAIDZ configuration requires at-least three disks. Since the OVA ships with two disks for backup and one disk for restore, add a fourth virtual disk with the storage capacity of 100 GB and use the fourth disk along with the first and second disk. The Phoenix Backup Store uses the third disk with the storage capacity of 200 GB for restore. Ensure that you do not use the third disk with 200 GB storage capacity for creating the ZFS pool.

      • The scripts are stored under the /opt/Druva/Phoenix/PhoenixBackupStore/bin folder on the Phoenix Backup Store.

  2. Run the following command to restart the Phoenix Backup Store service. 
    sudo service PhoenixBackupStore restart 
  3. Run the activation command with the token you generated above to activate the Phoenix Backup Store:
    PhoenixBackupStoreControl activate <govcloud> <activation_token>
    

    Example activation command for Public cloud:

    PhoenixBackupStoreControl activate ExampleToken1234
    

    Example activation command for Gov cloud:

    PhoenixBackupStoreControl activate govcloud ExampleToken1234

    Ensure that you replace example values with real values. In the above syntax, replace ExampleToken1234 with the token that you generate. 

The Phoenix Backup Store is deployed and registered with Druva. 

Ensure that you use this activation token for the correct Phoenix Backup Store. If you use this token on a different store, backup jobs will fail on this store as well on the Phoenix Backup Store you originally wanted to re-register. In addition, on the Phoenix Backup Stores tab of the Oracle page, details of the other Phoenix Backup Store  become identical to the Phoenix Backup Store you originally wanted to re-register. 

Reuse a Phoenix Backup Store

You can reuse an older Phoenix Backup Store. However, before you reuse the Phoenix Backup Store, ensure that certain Phoenix files are removed from it. Perform the following steps to clean up a Phoenix Backup Store for reuse:

  1. Run the following command to remove the existing ZFS pool on the Phoenix Backup Store:
    zpool destroy -f Phoenix
    
  2. Run the following command to remove the existing the database state:
    rm -rf /var/Phoenix/ExportService/database.db
    
  3. Remove the existing entries from /etc/exports.

After performing the steps above, follow the steps in the deploy and register a Phoenix Backup Store article and register it as a new Phoenix Backup Store.