Restore Dremio

This topic describes the Dremio CLI command, dremio-admin restore, and general information about restoring Dremio from a backup.

Dremio metadata and user uploaded files can be backed up and restored. Doing a restore does not restore the contents of the distributed cache such as acceleration cache, downloaded files and query results.


  • All cluster nodes are completely shut down. See Startup/Shutdown for more information.
  • This command is run on the master node.


A backup can only be restored using the same version of Dremio that the backup was created on.


<dremio_home>/bin/dremio-admin restore -d <BACKUP_PATH> [additional options]


To obtain a list of restore options on the command line:

./dremio-admin restore -h

Restore options:

  * -d, --backupdir
      backup directory path. for example, /mnt/dremio/backups or 
    -h, --help
      show usage
    -r, --restore
      restore dremio metadata
    -v, --verify
      verify backup contents


./dremio-admin restore -d /tmp/dremio_backup

Restoring Dremio Step-by-step

The following are step-by-step instructions for restoring Dremio from a backup.

  1. Make sure all cluster nodes are shutdown.

  2. On the master node, create a copy of <DREMIO_LOCAL_DATA_PATH>. (e.g. /data/dremio/ depending on your setup)

  3. On the master node, delete contents of <DREMIO_LOCAL_DATA_PATH> and then create an empty directory called db readable and writable by the user running restore tool and Dremio daemon under <DREMIO_LOCAL_DATA_PATH>.

  4. On the master node, run the following command located under <DREMIO_HOME>/bin/ to verify backup where -v option verifies backup contents.

     $ ./dremio-admin restore 
  5. If above step is successful, run the following command located under <DREMIO_HOME>/bin/ where -r option initiates a restore.

     $ ./dremio-admin restore 
  6. Look for the confirmation message. For example:

    Restored from backup at /tmp/dremio_backup_2017-02-23_18.25, dremio tables 14, uploaded files 1


Dremio on Edge Nodes

When Dremio is running on a edge node (Hadoop client installed) and a dremio-admin restore -v or -r is performed, by default, it looks at HDFS and comes back with file does not exist. The folder/file obviously does not exist is Hadoop.

Restore fails with the following stack:
Error Message: File /tmp/dremiobackup does not exist.
at org.apache.hadoop.hdfs.DistributedFileSystem.listStatusInternal(
at org.apache.hadoop.hdfs.DistributedFileSystem.access$600(
at org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(
at org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(
at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(
at org.apache.hadoop.hdfs.DistributedFileSystem.listStatus(
at org.apache.hadoop.fs.FileSystem.listStatus(
at org.apache.hadoop.fs.FileSystem.listStatus(
at com.dremio.dac.util.BackupRestoreUtil.scanInfoFiles(
at com.dremio.dac.util.BackupRestoreUtil.validateBackupDir(
at com.dremio.dac.cmd.Restore.main(
verify failed File /tmp/dremiobackup does not exist

Use file:/// to direct to local. For example, use the following command instead:

./dremio-admin restore -d file:///tmp/dremiobackup/dremio_backup_2019-04-22_20.30 -r

For More Information