Migrating resource logs from local storage to object storage on Linux

This topic describes how to migrate resource logs from your local system storage to object storage.

After successfully migrating the resource logs, disable the migration job.

Before you begin

Run the following command to back up your $MODEL9_HOME/backups directory: 

To set up the migration job

1. Update the following parameters in the model9-local.yml file, which resides in the $MODEL9_HOME/conf/ directory:

   1. Disable saving resource logs to your local system by deleting the following parameter: 

      model9.backup.log.saveToFile: true

   2. Schedule the migration job to run by specifying the cron expression in accordance with your needs. The following example schedules the migration job to run at midnight on October 1, 2025:

      model9.backup.log.migration.cron: "0 0 0 1 10 * 2025"

2. Restart the server by using the following command: 

   docker restart model9-v4.3.0

3. After the scheduled migration job completes, check the server logs and verify that the migration was successful. 

   Information

   Example

   yyyy-mm-dd 13:46:00,718 [quartzScheduler_Worker-1] INFO  z.BackupLogMigrationJob - Time taken to migrate backup log data for total 1026993 records in seconds is 6408.981
   yyyy-mm-dd 13:46:00,718 [quartzScheduler_Worker-1] INFO  z.BackupLogMigrationJob - Successfully updated backup log data for rows: 1026993.

   Error

   Warning

   If any part of your migration job fails, contact BMC Support.

To disable the migration job

1. Delete the model9.backup.log.migration.cron parameter in the model9-local.yml file.

2. Restart the server by using the following command: 

   docker restart model9-v4.3.0