Extract "migrate export" and "clish config" from backup

[bernhard_m]

Does anyone know of a tool / script or an easy procedure to extract useful parts from a backup file?

I'm thinking of a "migrate export" format by repackaging the relevant files of a backup file and a conversion tool for converting the /config/inital file to clish configuration commands

Any help is appreciated,

Bernhard

[G_W_Albrecht]

I do know no tool, so the procedure would be to restore on a fresh install before performing migrate export and save configuration.

[bernhard_m]

That's what i am aware of and wanted to avoid. Especialy because i think this is a task where the main parts of the code should be available already (at Check Point at least).

A really cool solution would be a BackupParserUtility (like the new DiagnosticView but fed with a backup-file instead of a cpinfo) and different export Features.

... just dreaming... could also add this request to the "Idea of the year section"

[G_W_Albrecht]

Such a tool surely is possible - in R77.30, you could perform that manually (by copying fwauth.ndb, lcrulebases_5_0.fws, rulebases_5_0.fws, fgrulebases_5_0.fws, slprulebases_5_0.fws and Objects_5_0.C from SMS /conf), but now, all data is in an SQL database. But honestly, where and for what purpose should such a tool be needed ? If i have a backup, i can get a working configuration in a very short time. And if - on SMS - i never do a migrate export i have only myself to blame 😉

[bernhard_m]

Because it's easy to schedule and upload a backup to an external storage via clish. If i want the same with migrate export I have to write and schedule it myself (for scp, ftp, or whatever destination if want). Why doing it twice if the information is available in the backup file? And most of the time i need a migrate export instead of a full backup...

[G_W_Albrecht]

If you need a migrate export most of the time (i would suppose that for SMS, this is the ideal kind of backup), why not do it that way ? Easy to script and schedule in GAiA ! Is anyone else interested in such a tool ?

[Danny · Accepted solution]

In your case I would simply edit the configuration scheme for management backups

/var/CPbackup/schemes/mgmts.cpbak‍‍‍

and have it including a migrate export directly into the backup archive. This way you can simply extract it whenever you need it.

Alternatively you could also create a second cron job that performs an migrate export one hour before your backup schedule. Just include the path and filename of the created archive within the INCLUDE_FILES section:

<INCLUDE_FILES>
BERNHARDS_MIGRATE_EXPORT.tgz
</INCLUDE_FILES>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

[bernhard_m]

Thanks Danny. That's great alternatives to repackage a migrate export format from the backup.

[bernhard_m]

Any ideas regaring the conversion of the /config/initial to clish configuration commands?

[G_W_Albrecht]

I can only find /config/db/initial and /config/db/initial_db

[bernhard_m]

You are right. The correct path is /config/db/initial.