Migrate to Different Facen Model¶
Do not hesitate to contact our experts on migration by firstname.lastname@example.org.
Before the migration, sure to backup the database.
Sometimes you have to migrate your face biometric data (facens) to another facen model. This usually happens when you decide to update to the latest version of the product.
To migrate to a different facen model, use the
findface-sf-api-migrate utility. To pass migration settings, launch it with the
-config option and provide a configuration file shown in the example below.
findface-sf-api-migrate -config <migration.ini>
Example of the configuration file:
extraction-api: timeouts: connect: 5s response_header: 30s overall: 35s idle_connection: 0s extraction-api: http://127.0.0.1:18666 storage-api-from: # current location of the gallery timeouts: connect: 5s response_header: 30s overall: 35s idle_connection: 10s max-idle-conns-per-host: 20 shards: - master: http://127.0.0.1:8001/v2/ slave: "" storage-api-to: timeouts: connect: 5s response_header: 30s overall: 35s idle_connection: 10s max-idle-conns-per-host: 20 shards: - master: http://127.0.0.1:8002/v2/ slave: "" workers_num: 3 faces_limit: 100 extraction_batch_size: 8 normalized_storage: type: webdav enabled: True webdav: upload-url: http://127.0.0.1:3333/uploads/ s3: endpoint: 172.20.77.75:9000 bucket-name: sf-api-normalized access-key: W0G6EQT6MC3BZC8136DW secret-access-key: XnottrdxRFp70wfEGdkvKgkzKZ3mEa2Y9bYmob4I secure: False region: "" operation-timeout: 10 public-url: 123
||Previous facen storage|
||Storage for re-generated facens|
||Storage of normalized face images.|