weaviate_backup_restore_ms
The number of samples used to calculate the duration of backup restoresDimensions:None
Available on:
Datadog (1)
Interface Metrics (1)
Dimensions:None
Technical Annotations (59)
Configuration Parameters (3)
imagerecommended: semitechnologies/weaviate:<specific-version>wait_for_completionrecommended: TrueCLUSTER_HOSTNAMErecommended: original node hostname from backup sourceError Signatures (16)
entrypoint was deleted in the object store, it has been flagged for cleanup and should be fixed in the next cleanup cyclelog patternexplorer: get class: vector search: object vector search at indexlog patternweaviate.exceptions.UnexpectedStatusCodeExceptionexception422http statusunable to restore backup as it was produced by a higher versionlog patternmmap file: invalid argumenterror codefailed to load shard: Unable to load shardlog patterninit disk segments: init segmentlog patternError: Restore process failed due to missing files.log patternError: Incomplete restore operation detected.log patternresolve node name "0d83d09dea6c" to host'log patterncoordinator: stat: stat /var/lib/weaviate/.../lsm/property_.../secondary: no such file or directorylog patternstat: stat /var/lib/weaviate/.../lsm/property_.../secondary: no such file or directorylog patternflush: unlinkat /var/lib/weaviate/test/{index_name}/w8G6ci6OWwEL/lsm/property__id/segment-*.scratch.d: directory not emptylog patternwrite index: unlinkat /var/lib/weaviate/test/{index_name}/w8G6ci6OWwEL/lsm/property_*/segment-*.dbcompaction.scratch.d: directory not emptylog patterndevice or resource busylog patternCLI Commands (8)
curl http://localhost:8090/v1/backups/filesystem/my-very-first-backup/restoremonitoringmd5sum /path/to/backup/filediagnosticweaviate-cli restore --backup /path/to/backup --target /path/to/targetremediationcurl -X POST -H "Content-Type:application/json" <WEAVIATE_URL>/v1/backups/filesystem -d "{\"id\": \"20240712-page_v3\", \"include\": [\"Page_v3\"]}"diagnosticcurl <WEAVIATE_URL>/v1/backups/filesystem/20240712-page_v3diagnosticfind . -name 'secondary'diagnosticPOST /v1/backups/{provider}/{backupId}/restorediagnosticGET /v1/backups/{provider}/{backupId}monitoringTechnical References (32)
entrypointcomponentshardcomponentobject storecomponentstatus:STARTEDconceptbackup format versionconcepts3componentsemitechnologies/weaviatecomponentclassconceptLSMconceptNFSprotocolAzure file sharecomponent/var/lib/weaviatefile path/var/log/weaviate/file pathCLUSTER_HOSTNAMEcomponentsecondarycomponent.dbcompaction.scratch.dcomponentshard replica nodescomponentreplicated classescomponentclass schemaconceptmulti-tenancyconceptdisaster recoveryconceptRaftprotocolgossip protocolprotocolembedded DBcomponentdata_bind_portcomponentintra-cluster servercomponentLSM (Log-Structured Merge-tree)componenttombstonesconceptmemtable flushcomponentcompactioncomponentscratch spacecomponentfilesystemcomponentRelated Insights (17)
Vector search entrypoint deleted after backup restore cyclecritical
▸
Backup restore processes fail when actually needed in productioncritical
▸
Asynchronous backup operations require status pollinginfo
▸
Weaviate remains operational during backup and restore operationsinfo
▸
Backup version mismatch prevents restorationcritical
▸
Backup restore completes with success status but transfers only schema when versions mismatchcritical
▸
Backup restoration fails with mmap error due to LSM segment corruption on NFS storagecritical
▸
Weaviate restore process fails to completecritical
▸
Long-running backup operations require status monitoringinfo
▸
Backup restore fails with hostname resolution error on different nodecritical
▸
Backup fails when LSM compaction scratch directory exists with missing secondary filecritical
▸
Backup procedure failed to create shard backups across all replicascritical
▸
Incomplete backup of class schemas on nodes without local datacritical
▸
Untested backup restore fails during disaster recoverycritical
▸
Embedded server backup failure due to Raft port conflictcritical
▸
Backup failure after bulk object deletion due to LSM compaction conflictscritical
▸
Cross-version backup restore causes tenant data inaccessibilitycritical
▸