Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsHow To - Enterprise Workloads
How to change the agent metadata location on the Linux server to avoid backup failures
How to change the agent metadata location on the Linux server to avoid backup failures

How to change the agent metadata location on the Linux server to avoid backup failures

Updated over a week ago

Problem description

  • When you install Druva agents on your servers, the Druva agent creates a directory:
    For 6.x Version: under /var/Phoenix/FS.
    For 7.x Version: Under /var/Druva/EnterpriseWorkloads

  • The size of the metadata depends on the size of the data that is backed up or restored.

  • With each backup or restore, the metadata grows.

  • If the metadata consumes nearly all the free space on your volume, backups from the servers might fail. To avoid this issue, consider changing the default location of the agent metadata.

Solution

Change the agent metadata location

  1. For Agent Version 6.x:

    1. Stop the Phoenix service.
      service Phoenix stop

    2. Copy the folder to the desired location.
      cp -R /var/Phoenix /abc/xyz/Phoenix

    3. Keep a backup until the backup starts writing to the changed location.
      mv /var/Phoenix /var/Phoenix_Moved

    4. Create a link.
      ln -s /abc/xyz/Phoenix /var/Phoenix

    5. Stop the Phoenix service.
      service Phoenix start

    6. Start the backup and you will see that the timestamp of the new location changes, this means metadata is written to the new location.

  2. For Agent Version 7.x:

    1. Stop the Druva-EnterpriseWorkloads service.
      service Druva-EnterpriseWorkloads stop

    2. Copy the folder to the desired location.
      cp -R /var/Druva /abc/xyz/Druva

    3. Keep a backup until the backup starts writing to the changed location.
      mv /var/Druva /var/Druva_Moved

    4. Create a link.
      ln -s /abc/xyz/Druva /var/Druva

    5. Stop the Phoenix service.
      service Druva-EnterpriseWorkloads start

    6. Start the backup and you will see that the timestamp of the new location changes, this means metadata is written to the new location.

Did this answer your question?