Re: [wiredtiger-users] can we use wired tiger for commercial backup solutions?

[Will Korteland]

Hi Rejith,

Thanks for your interest in WiredTiger! It sounds like you're using MongoDB, rather than WiredTiger directly. If this is the case, I would strongly encourage you to use MongoDB for backups. You'll need to find a Mongo-specific help resource for this functionality, as this mailing list applies specifically to WiredTiger.

For the first error, WiredTiger does not support two processes modifying the same database, so if you want to work on it you'll have to stop mongod (as you have done).

The second error has occurred because your copy of the WT binary was build from a source tree without snappy enabled - you could try re-running cmake with the "-DENABLE_SNAPPY=1" option. It may also be the case that the snappy library is not installed on the machine that you're running the WT tool on. We have further documentation on this option here: https://source.wiredtiger.com/develop/build-posix.html#posix_configure

Regards,

 - Will

On Tue, 20 Feb 2024 at 21:51, Rrrr <rrr27...@gmail.com> wrote:

Hi,

We are trying mongodb backups using wiredtiger.

Can we use wired tiger to build commercial backup solution?

Also can you help me with below error?

below is error when database is in open state :

[root@blrv009c192 mongo]# ./wt -h /var/lib/mongo backup /home/binary
[1708412873:851287][3036868:0x7f9ce6ac24c0], wt, wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: __posix_file_lock, 398: ./WiredTiger.lock: handle-lock: fcntl: Resource temporarily unavailable
[1708412873:851333][3036868:0x7f9ce6ac24c0], wt, wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: __conn_single, 1921: WiredTiger database is already being managed by another process: Device or resource busy
wt: Device or resource busy
Note: this issue typically arises from running wt util in an incorrect directory or not specifying one. Ensure you execute wt within a WiredTiger directory, or use the -h flag to direct it to one.

when I stop mongod instance

[1708412665:139021][3036001:0x7feaba4c64c0], wt, file:WiredTigerHS.wt, hs_access: [WT_VERB_DEFAULT][ERROR]: __compressor_confchk, 202: unknown compressor 'snappy': Invalid argument
[1708412665:139093][3036001:0x7feaba4c64c0], wt, txn-recover: [WT_VERB_DEFAULT][ERROR]: __wt_txn_recover, 1229: Recovery failed: Invalid argument
[1708412665:139293][3036001:0x7feaba4c64c0], wt, connection: [WT_VERB_DEFAULT][ERROR]: __wt_cache_destroy, 378: cache server: exiting with 6 pages in memory and 0 pages evicted
[1708412665:139306][3036001:0x7feaba4c64c0], wt, connection: [WT_VERB_DEFAULT][ERROR]: __wt_cache_destroy, 381: cache server: exiting with 139248 image bytes in memory
[1708412665:139309][3036001:0x7feaba4c64c0], wt, connection: [WT_VERB_DEFAULT][ERROR]: __wt_cache_destroy, 384: cache server: exiting with 143176 bytes in memory
wt: WT_PANIC: WiredTiger library panic
Note: this issue typically arises from running wt util in an incorrect directory or not specifying one. Ensure you execute wt within a WiredTiger directory, or use the -h flag to direct it to one.

Regards,

Rejith Mohan

--
You received this message because you are subscribed to the Google Groups "wiredtiger-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wiredtiger-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wiredtiger-users/d0542524-e33c-4fd1-af1d-84aa149e0bf3n%40googlegroups.com.