Imperva Cyber Community

I'm attempting to test the backup and restore of our version 14.7 MX server.

When triggering an export from the web console admin/maintenance page, the export/backup tgz file ends up in /var/tmp.
However, when I try to run the import-local command from an ssh session to the MX and tab to complete, only tgz files in /var/tmp/server-backups are displayed.
How does a backup get into that directory? When I do an export from the web console it does not go into that directory.
If I attempt to point import-local to a file in /var/tmp using the --dmpfile parameter I just get an error sayinh the choice in invalid.

I'm attempting to test the backup and restore of our version 14.7 MX server.

When triggering an export from the web console admin/maintenance page, the export/backup tgz file ends up in /var/tmp.
However, when I try to run the import-local command from an ssh session to the MX and tab to complete, only tgz files in /var/tmp/server-backups are displayed.
How does a backup get into that directory? When I do an export from the web console it does not go into that directory.
If I attempt to point import-local to a file in /var/tmp using the --dmpfile parameter I just get an error sayinh the choice in invalid.

Hello Rick,

Thank you for your post, by default the export file will be saved under /var/tmp during export, however you can choose your own path, where you want to save the file and the default extension is .tgz for the MX export, hope this answers your query, let us know if you face any challenges while importing the config.

I'm attempting to test the backup and restore of our version 14.7 MX server.

When triggering an export from the web console admin/maintenance page, the export/backup tgz file ends up in /var/tmp.
However, when I try to run the import-local command from an ssh session to the MX and tab to complete, only tgz files in /var/tmp/server-backups are displayed.
How does a backup get into that directory? When I do an export from the web console it does not go into that directory.
If I attempt to point import-local to a file in /var/tmp using the --dmpfile parameter I just get an error sayinh the choice in invalid.

Thanks for the reply Syed. I was facing problems with the import-remote command, which might turn out to be my ever changing environment and might not be solvable. So I pulled down a copy of the export/backup from s3 and attempted to do an import-local which also fails.
I raised a support case and we spent some time going through this. The import-local command should work but might have been broken by version 14.7.
In the end, unsealing the MX and using the full_expimp.sh script worked OK for me.  

Hello Rick,

Thank you for your post, by default the export file will be saved under /var/tmp during export, however you can choose your own path, where you want to save the file and the default extension is .tgz for the MX export, hope this answers your query, let us know if you face any challenges while importing the config.

I'm attempting to test the backup and restore of our version 14.7 MX server.

When triggering an export from the web console admin/maintenance page, the export/backup tgz file ends up in /var/tmp.
However, when I try to run the import-local command from an ssh session to the MX and tab to complete, only tgz files in /var/tmp/server-backups are displayed.
How does a backup get into that directory? When I do an export from the web console it does not go into that directory.
If I attempt to point import-local to a file in /var/tmp using the --dmpfile parameter I just get an error sayinh the choice in invalid.