Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsTroubleshooting - Enterprise Workloads
Oracle PBS Restore failed with Error while exporting restore path (Error Code : PHOENIX127)
Oracle PBS Restore failed with Error while exporting restore path (Error Code : PHOENIX127)

Restore failed with Error while exporting restore path (Error Code : PHOENIX127)

Updated over 3 weeks ago

Problem Description

Restore fails with the error PHOENIX127, which indicates that the restore mount cannot be located. This is caused by stale or incorrect restore mount entries in the /etc/exports file or the Phoenix.cfg configuration file.

Traceback

Phoenix Job Logs:

[2024-12-26 16:46:42,889] [INFO] <_MainThread(MainThread)> Export restore folder REST API executed successfully. Response [{'error_code': -1, 'error_msg': 'Error while exporting restore path', 'result': {'jobid': 162, 'mount_name': 'DB1', 'restore_path': ''}}]

[2024-12-26 16:46:42,890] [ERROR] <_MainThread(MainThread)> Error details : {'error_code': 4294967423, 'error_msg': 'Error while exporting restore path' (#10000007f) (Error Code : PHOENIX127)\n'}

Export Service Logs:

File "/code/src/oracleconfig_py3/client/exportservice/PhoenixES.py", line 518, in export_restore_folder

File "/code/src/oracleconfig_py3/client/exportservice/export_service_bl.py", line 616, in export_restore_path

File "/code/src/oracleconfig_py3/client/exportservice/nfs_utils.py", line 30, in reexport_all

AttributeError: 'CalledProcessError' object has no attribute 'message'

[2024-12-26 16:46:42,886] [ERROR] [backup_mount:DB1] Error while exporting restore path

Cause:

  1. The default restore path /mnt/restores is replaced in the Phoenix.cfg file.

  2. The new path does not exist or has stale entries from previous restore attempts.

  3. This conflict prevents successful export of the restore path.

Solution

Follow these steps to resolve the issue:

Step 1: Verify Stale Entries in /etc/exports

Run the following command to check for stale mount entries:
​exportfs -r

If stale entries are present, you'll see output like:
​exportfs: Failed to stat /Phoenix/PBSTEST/DB1/161/data: No such file or directory

Step 2: Clean Up Stale Restore Mount Entries

  1. Open the /etc/exports file:
    ​vi /etc/exports

  2. Locate the stale entries related to the failed restores, such as:
    ​/Phoenix/PBSTEST/DB1/161/data

  3. Delete or comment out the entries using #:

    • To comment out:
      ​# /Phoenix/PBSTEST/DB1/161/data

  4. Save and exit:

    • Press ESC, type :wq, and hit Enter.

Step 3: Correct the Phoenix.cfg File

  1. Open the Phoenix.cfg file:
    ​vi /etc/Phoenix/ORACLE/Phoenix.cfg

  2. Locate the following variable:
    ​ORACLE_RESTORES_BASE_PATH

  3. Set it to the default mount point /mnt/restores or an available, valid mount point:
    ​ORACLE_RESTORES_BASE_PATH = '/mnt/restores'

  4. Save and exit:

    • Press ESC, type :wq, and hit Enter.

Step 4: Restart Phoenix Backup Store Service

  1. Restart the service:
    ​systemctl restart PhoenixBackupStore

  2. Confirm the service is running:
    ​systemctl status PhoenixBackupStore

    The service should show as "active" and "connected" in the Druva console.

Step 5: Retry the Restore

  1. Log into the Druva console.

  2. Initiate the restore operation again.

Key Verification

  • Ensure the updated mount points are valid and accessible.

  • Use the exportfs command to confirm there are no stale entries:
    ​exportfs -v

Following these steps will resolve the PHOENIX127 error and allow the restore process to proceed successfully.

Related Articles
Oracle errors
Oracle PBS| How to change default restore location
User Guide - Preparing your environment for successful Druva Oracle PBS Restore
Linux NAS backup fails with error Phoenix 370
NAS Backup failed after changing the credentials for NAS device
Did this answer your question?