Migrate export failed on R80.10

[Ankur_Datta]

Hi Moderators,

I am facing issue with migrate export on R80.10. At the moment, I exported the database from R80.10 and imported it into different management server running R80.10 Code. The exported database file is around 3Gb. I deleted the old database revisions but the difference is off 150-200 mb. The new management server has 2 TB of HD. Below is the screenshot of current management server and new management server disk partition.

current management server:

New Management server:

The existing management server has build 421 and i am importing the database on R80.10 buid 462. Can this be issue?

I attached the log file generated during import. Kindly please help me in this case.

Further, please let me know what closed logs means in migrate import/export?

[G_W_Albrecht]

What closed logs means in migrate export: Open log files (currently in use) are not exported. A migrate export can be execcuted while log server is working - to have the best of both wolds, issue a logswitch before running migrate export.

Concerning the migrate import error i would suggest to involve TAC supplying the log file.

[Ankur_Datta]

Thanks for the Reply Gunther. So when we do migrate export the old logs files are also exported?

[G_W_Albrecht]

I think you named the question wrongly - this is no migrate export error, but an error on migrate import ! And yes, migrate export -l will include closed log files in export.

[Ankur_Datta]

Sorry Gunther, just noticed it now. 

if i don't use -l parameter, will it copy old logs and not the current one in database?

Thanks

[G_W_Albrecht]

If you do not use -l parameter no logs will be included in the migrate export (remember, you can always export logs after disabling the old log server, see Firewall Log Archive and Import in R80.10/ R77.30).