导入数据到MongoDB
~/.asdf/plugins$ which docker
/usr/bin/docker
linlin@linlin-i5:~/.asdf/plugins$ sudo docker pull mongo:5.0.6
[sudo] password for linlin:
5.0.6: Pulling from library/mongo
Digest: sha256:fed6248ae0bb0d54c0448eb786c87120737eedc522172ee1536ad47789782348
Status: Image is up to date for mongo:5.0.6
docker.io/library/mongo:5.0.6
linlin@linlin-i5:~/.asdf/plugins$ sudo docker start ^C
linlin@linlin-i5:~/.asdf/plugins$ cd /workspace/
linlin@linlin-i5:/workspace$ mkdir docker_folder
mkdir: cannot create directory ‘docker_folder’: File exists
linlin@linlin-i5:/workspace$ cd docker_folder
linlin@linlin-i5:/workspace/docker_folder$ ls
collection-0--7642342716083924179.wt collection-7--7642342716083924179.wt index-16--7642342716083924179.wt index-8--7642342716083924179.wt storage.bson
collection-11--7642342716083924179.wt collection-9--7642342716083924179.wt index-1--7642342716083924179.wt journal WiredTiger
collection-13--7642342716083924179.wt diagnostic.data index-18--7642342716083924179.wt _mdb_catalog.wt WiredTigerHS.wt
collection-15--7642342716083924179.wt docker_folder2 index-19--7642342716083924179.wt mongo5.0.6 WiredTiger.lock
collection-17--7642342716083924179.wt index-10--7642342716083924179.wt index-3--7642342716083924179.wt mongo5.0.7 WiredTiger.turtle
collection-2--7642342716083924179.wt index-12--7642342716083924179.wt index-5--7642342716083924179.wt mongod.lock WiredTiger.wt
collection-4--7642342716083924179.wt index-14--7642342716083924179.wt index-6--7642342716083924179.wt sizeStorer.wt
linlin@linlin-i5:/workspace/docker_folder$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
linlin@linlin-i5:/workspace/docker_folder$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3b2d46e0543a f4a2a7264d08 "/bin/bash -c 'volta…" 2 weeks ago Exited (127) 2 weeks ago compassionate_gould
a2f73981864a f4a2a7264d08 "/bin/bash -c 'volta…" 2 weeks ago Exited (127) 2 weeks ago kind_davinci
sudo docker start 5d5b
5d5b
linlin@linlin-i5:/workspace/docker_folder$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5d5b156fb1b0 mongo:5.0.6 "docker-entrypoint.s…" 8 weeks ago Up 3 seconds 0.0.0.0:27017->27017/tcp, :::27017->27017/tcp mongo5.0.6
linlin@linlin-i5:/workspace/docker_folder$ sudo docker exec -it 5d5b bash
root@5d5b156fb1b0:/# mongo
MongoDB shell version v5.0.6
connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
Error: couldn't connect to server 127.0.0.1:27017, connection attempt failed: SocketException: Error connecting to 127.0.0.1:27017 :: caused by :: Connection refused :
connect@src/mongo/shell/mongo.js:372:17
@(connect):2:6
exception: connect failed
exiting with code 1
root@5d5b156fb1b0:/# exit
linlin@linlin-i5:/workspace/docker_folder$ mongo
Command 'mongo' not found, did you mean:
command 'mono' from deb mono-runtime (6.8.0.105+dfsg-3)
Try: sudo apt install <deb name>
linlin@linlin-i5:/workspace/docker_folder$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5d5b156fb1b0 mongo:5.0.6 "docker-entrypoint.s…" 8 weeks ago Up About a minute 0.0.0.0:27017->27017/tcp, :::27017->27017/tcp mongo5.0.6
linlin@linlin-i5:/workspace/docker_folder$ sudo docker run -it -p 127.0.0.1:27017:27017 -v /workspace/docker_folder/mongo5.0.6:/data/db -d mongo:5.0.6
786e35bab6c87c0deca3d950f533f4c4b3d4f3f491ae81a518b57d83f096f8a2
docker: Error response from daemon: driver failed programming external connectivity on endpoint quizzical_clarke (593b4bb8dc19e384da3be1d256ff80dbe1c92cd29363038d723e921bbde1868d): Error starting userland proxy: listen tcp4 127.0.0.1:27017: bind: address already in use.
linlin@linlin-i5:/workspace/docker_folder$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5d5b156fb1b0 mongo:5.0.6 "docker-entrypoint.s…" 8 weeks ago Up 3 minutes 0.0.0.0:27017->27017/tcp, :::27017->27017/tcp mongo5.0.6
linlin@linlin-i5:/workspace/docker_folder$ sudo docker stop 5d5b
5d5b
sudo docker run -it -p 127.0.0.1:27017:27017 -v /workspace/docker_folder/mongo5.0.6:/data/db -d mongo:5.0.6
74378c6e312082860d162442edaf6c434da6e6dee1a7ab052365fc8fccec34b3
linlin@linlin-i5:/workspace/docker_folder$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
74378c6e3120 mongo:5.0.6 "docker-entrypoint.s…" 5 seconds ago Up 4 seconds 127.0.0.1:27017->27017/tcp modest_thompson
linlin@linlin-i5:/workspace/docker_folder$ sudo docker exec -it 7437 bash
root@74378c6e3120:/# top
top - 10:52:06 up 5 days, 6:54, 0 users, load average: 1.17, 1.15, 1.01
Tasks: 3 total, 1 running, 2 sleeping, 0 stopped, 0 zombie
%Cpu(s): 7.9 us, 1.4 sy, 0.0 ni, 90.5 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
MiB Mem : 15699.0 total, 270.0 free, 12958.7 used, 2470.3 buff/cache
MiB Swap: 2048.0 total, 0.0 free, 2048.0 used. 1121.2 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1 mongodb 20 0 1543264 112636 49288 S 0.3 0.7 0:01.14 mongod
59 root 20 0 4248 3444 2872 S 0.0 0.0 0:00.01 bash
67 root 20 0 6156 3228 2692 R 0.0 0.0 0:00.00 top
root@74378c6e3120:/# mongo
MongoDB shell version v5.0.6
connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("b6d60aa1-903f-4ab6-ac1c-92dfa9da1daf") }
MongoDB server version: 5.0.6
================
Warning: the "mongo" shell has been superseded by "mongosh",
which delivers improved usability and compatibility.The "mongo" shell has been deprecated and will be removed in
an upcoming release.
For installation instructions, see
https://docs.mongodb.com/mongodb-shell/install/
================
Welcome to the MongoDB shell.
For interactive help, type "help".
For more comprehensive documentation, see
https://docs.mongodb.com/
Questions? Try the MongoDB Developer Community Forums
https://community.mongodb.com
---
The server generated these startup warnings when booting:
2022-06-24T10:51:20.365+00:00: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
2022-06-24T10:51:21.222+00:00: Access control is not enabled for the database. Read and write access to data and configuration is unrestricted
---
---
Enable MongoDB's free cloud-based monitoring service, which will then receive and display
metrics about your deployment (disk utilization, CPU, operation statistics, etc).
The monitoring data will be available on a MongoDB website with a unique URL accessible to you
and anyone you share the URL with. MongoDB may use this information to make product
improvements and to suggest MongoDB products and deployment options to you.
To enable free monitoring, run the following command: db.enableFreeMonitoring()
To permanently disable this reminder, run the following command: db.disableFreeMonitoring()
---
> show dbs
admin 0.000GB
config 0.000GB
local 0.000GB
lueluelue 0.001GB
>
bye
root@74378c6e3120:/# ls
bin boot data dev docker-entrypoint-initdb.d etc home js-yaml.js lib lib32 lib64 libx32 media mnt opt proc root run sbin srv sys tmp usr var
root@74378c6e3120:/# cd /root/
root@74378c6e3120:~# ls
20220624-065751.archive
root@74378c6e3120:~# mongo
MongoDB shell version v5.0.6
connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("bfeb1ae3-06f3-4b89-aa4c-175193269433") }
MongoDB server version: 5.0.6
================
Warning: the "mongo" shell has been superseded by "mongosh",
which delivers improved usability and compatibility.The "mongo" shell has been deprecated and will be removed in
an upcoming release.
For installation instructions, see
https://docs.mongodb.com/mongodb-shell/install/
================
---
The server generated these startup warnings when booting:
2022-06-24T10:51:20.365+00:00: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
2022-06-24T10:51:21.222+00:00: Access control is not enabled for the database. Read and write access to data and configuration is unrestricted
---
---
Enable MongoDB's free cloud-based monitoring service, which will then receive and display
metrics about your deployment (disk utilization, CPU, operation statistics, etc).
The monitoring data will be available on a MongoDB website with a unique URL accessible to you
and anyone you share the URL with. MongoDB may use this information to make product
improvements and to suggest MongoDB products and deployment options to you.
To enable free monitoring, run the following command: db.enableFreeMonitoring()
To permanently disable this reminder, run the following command: db.disableFreeMonitoring()
---
> show dbs
admin 0.000GB
config 0.000GB
local 0.000GB
lueluelue 0.001GB
> use lueluelue
switched to db lueluelue
>
bye
root@74378c6e3120:~# mongo
mongo mongod mongodump mongoexport mongofiles mongoimport mongorestore mongos mongosh mongostat mongotop
root@74378c6e3120:~# mongo
mongo mongod mongodump mongoexport mongofiles mongoimport mongorestore mongos mongosh mongostat mongotop
root@74378c6e3120:~# mongorestore --help
Usage:
mongorestore <options> <connection-string> <directory or file to restore>
Restore backups generated with mongodump to a running server.
Specify a database with -d to restore a single database from the target directory,
or use -d and -c to restore a single collection from a single .bson file.
Connection strings must begin with mongodb:// or mongodb+srv://.
See http://docs.mongodb.com/database-tools/mongorestore/ for more information.
general options:
--help print usage
--version print the tool version and exit
--config= path to a configuration file
verbosity options:
-v, --verbose=<level> more detailed log output (include multiple times for more verbosity, e.g. -vvvvv, or specify a numeric value,
e.g. --verbose=N)
--quiet hide all log output
connection options:
-h, --host=<hostname> mongodb host to connect to (setname/host1,host2 for replica sets)
--port=<port> server port (can also use --host hostname:port)
ssl options:
--ssl connect to a mongod or mongos that has ssl enabled
--sslCAFile=<filename> the .pem file containing the root certificate chain from the certificate authority
--sslPEMKeyFile=<filename> the .pem file containing the certificate and key
--sslPEMKeyPassword=<password> the password to decrypt the sslPEMKeyFile, if necessary
--sslCRLFile=<filename> the .pem file containing the certificate revocation list
--sslFIPSMode use FIPS mode of the installed openssl library
--tlsInsecure bypass the validation for server's certificate chain and host name
authentication options:
-u, --username=<username> username for authentication
-p, --password=<password> password for authentication
--authenticationDatabase=<database-name> database that holds the user's credentials
--authenticationMechanism=<mechanism> authentication mechanism to use
--awsSessionToken=<aws-session-token> session token to authenticate via AWS IAM
kerberos options:
--gssapiServiceName=<service-name> service name to use when authenticating using GSSAPI/Kerberos (default: mongodb)
--gssapiHostName=<host-name> hostname to use when authenticating using GSSAPI/Kerberos (default: <remote server's address>)
namespace options:
-d, --db=<database-name> database to use
-c, --collection=<collection-name> collection to use
uri options:
--uri=mongodb-uri mongodb uri connection string
namespace options:
--excludeCollection=<collection-name> DEPRECATED; collection to skip over during restore (may be specified multiple times to exclude additional
collections)
--excludeCollectionsWithPrefix=<collection-prefix> DEPRECATED; collections to skip over during restore that have the given prefix (may be specified multiple times
to exclude additional prefixes)
--nsExclude=<namespace-pattern> exclude matching namespaces
--nsInclude=<namespace-pattern> include matching namespaces
--nsFrom=<namespace-pattern> rename matching namespaces, must have matching nsTo
--nsTo=<namespace-pattern> rename matched namespaces, must have matching nsFrom
input options:
--objcheck validate all objects before inserting
--oplogReplay replay oplog for point-in-time restore
--oplogLimit=<seconds>[:ordinal] only include oplog entries before the provided Timestamp
--oplogFile=<filename> oplog file to use for replay of oplog
--archive=<filename> restore dump from the specified archive file. If flag is specified without a value, archive is read from stdin
--restoreDbUsersAndRoles restore user and role definitions for the given database
--dir=<directory-name> input directory, use '-' for stdin
--gzip decompress gzipped input
restore options:
--drop drop each collection before import
--dryRun view summary without importing anything. recommended with verbosity
--writeConcern=<write-concern> write concern options e.g. --writeConcern majority, --writeConcern '{w: 3, wtimeout: 500, fsync: true, j: true}'
--noIndexRestore don't restore indexes
--convertLegacyIndexes Removes invalid index options and rewrites legacy option values (e.g. true becomes 1).
--noOptionsRestore don't restore collection options
--keepIndexVersion don't update index version
--maintainInsertionOrder restore the documents in the order of their appearance in the input source. By default the insertions will be
performed in an arbitrary order. Setting this flag also enables the behavior of --stopOnError and restricts
NumInsertionWorkersPerCollection to 1.
-j, --numParallelCollections= number of collections to restore in parallel
--numInsertionWorkersPerCollection= number of insert operations to run concurrently per collection
--stopOnError halt after encountering any error during insertion. By default, mongorestore will attempt to continue through
document validation and DuplicateKey errors, but with this option enabled, the tool will stop instead. A small
number of documents may be inserted after encountering an error even with this option enabled; use
--maintainInsertionOrder to halt immediately after an error
--bypassDocumentValidation bypass document validation
--preserveUUID preserve original collection UUIDs (off by default, requires drop)
--fixDottedHashIndex when enabled, all the hashed indexes on dotted fields will be created as single field ascending indexes on the
destination
root@74378c6e3120:~# mongorestore --archive=
.bashrc .dbshell .profile 20220624-065751.archive
.config/ .mongorc.js .wget-hsts
root@74378c6e3120:~# mongorestore --archive=20220624-065751.archive
2022-06-24T10:54:22.765+0000 preparing collections to restore from
2022-06-24T10:54:22.775+0000 reading metadata for lueluelue.claims from archive '20220624-065751.archive'
2022-06-24T10:54:22.775+0000 reading metadata for lueluelue.redeem_codes from archive '20220624-065751.archive'
2022-06-24T10:54:22.775+0000 reading metadata for lueluelue.invalid_domains from archive '20220624-065751.archive'
2022-06-24T10:54:22.775+0000 reading metadata for lueluelue.simple_redeem_codes from archive '20220624-065751.archive'
2022-06-24T10:54:22.776+0000 reading metadata for lueluelue.domain_registers from archive '20220624-065751.archive'
2022-06-24T10:54:22.776+0000 reading metadata for lueluelue.domains from archive '20220624-065751.archive'
2022-06-24T10:54:22.776+0000 restoring to existing collection lueluelue.claims without dropping
2022-06-24T10:54:22.776+0000 restoring lueluelue.claims from archive '20220624-065751.archive'
2022-06-24T10:54:22.872+0000 continuing through error: E11000 duplicate key error collection: lueluelue.claims index: _id_ dup key: { _id: ObjectId('61a71b291828d7531dae46ab') }
2022-06-24T10:54:22.872+0000 continuing through error: E11000 duplicate key error collection: lueluelue.claims index: _id_ dup key: { _id: ObjectId('61a70c55f48225bbe6932360') }
2022-06-24T10:54:23.238+0000 continuing through error: E11000 duplicate key error collection: lueluelue.domain_registers index: _id_ dup key: { _id: ObjectId('626a168e4cf72c5084e166a0') }
2022-06-24T10:54:23.256+0000 finished restoring lueluelue.domain_registers (3020 documents, 2153 failures)
2022-06-24T10:54:23.256+0000 restoring indexes for collection lueluelue.domains from metadata
2022-06-24T10:54:23.256+0000 index: &idx.IndexDocument{Options:primitive.M{"name":"name_1", "unique":true, "v":2}, Key:primitive.D{primitive.E{Key:"name", Value:1}}, PartialFilterExpression:primitive.D(nil)}
2022-06-24T10:54:23.256+0000 no indexes to restore for collection lueluelue.claims
2022-06-24T10:54:23.257+0000 no indexes to restore for collection lueluelue.simple_redeem_codes
2022-06-24T10:54:23.257+0000 no indexes to restore for collection lueluelue.domain_registers
2022-06-24T10:54:23.257+0000 no indexes to restore for collection lueluelue.redeem_codes
2022-06-24T10:54:23.257+0000 no indexes to restore for collection lueluelue.invalid_domains
2022-06-24T10:54:23.264+0000 3122 document(s) restored successfully. 7339 document(s) failed to restore.
root@74378c6e3120:~# remove-shell ^C
root@74378c6e3120:~# mongo
MongoDB shell version v5.0.6
connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("669e3406-dedf-4b4c-bf38-1129bc966e22") }
MongoDB server version: 5.0.6
================
Warning: the "mongo" shell has been superseded by "mongosh",
which delivers improved usability and compatibility.The "mongo" shell has been deprecated and will be removed in
an upcoming release.
For installation instructions, see
https://docs.mongodb.com/mongodb-shell/install/
================
---
The server generated these startup warnings when booting:
2022-06-24T10:51:20.365+00:00: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
2022-06-24T10:51:21.222+00:00: Access control is not enabled for the database. Read and write access to data and configuration is unrestricted
---
---
Enable MongoDB's free cloud-based monitoring service, which will then receive and display
metrics about your deployment (disk utilization, CPU, operation statistics, etc).
The monitoring data will be available on a MongoDB website with a unique URL accessible to you
and anyone you share the URL with. MongoDB may use this information to make product
improvements and to suggest MongoDB products and deployment options to you.
To enable free monitoring, run the following command: db.enableFreeMonitoring()
To permanently disable this reminder, run the following command: db.disableFreeMonitoring()
---
> help
db.help() help on db methods
db.mycoll.help() help on collection methods
sh.help() sharding helpers
rs.help() replica set helpers
help admin administrative help
help connect connecting to a db help
help keys key shortcuts
help misc misc things to know
help mr mapreduce
show dbs show database names
show collections show collections in current database
show users show users in current database
show profile show most recent system.profile entries with time >= 1ms
show logs show the accessible logger names
show log [name] prints out the last segment of log in memory, 'global' is default
use <db_name> set current database
db.mycoll.find() list objects in collection mycoll
db.mycoll.find( { a : 1 } ) list objects in mycoll where a == 1
it result of the last line evaluated; use to further iterate
DBQuery.shellBatchSize = x set default number of items to display on shell
exit quit the mongo shell
> use p^C
bye
root@74378c6e3120:~# mongo
MongoDB shell version v5.0.6
connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("80f50328-35c3-450d-91e4-a3e618358789") }
MongoDB server version: 5.0.6
================
Warning: the "mongo" shell has been superseded by "mongosh",
which delivers improved usability and compatibility.The "mongo" shell has been deprecated and will be removed in
an upcoming release.
For installation instructions, see
https://docs.mongodb.com/mongodb-shell/install/
================
---
The server generated these startup warnings when booting:
2022-06-24T10:51:20.365+00:00: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
2022-06-24T10:51:21.222+00:00: Access control is not enabled for the database. Read and write access to data and configuration is unrestricted
---
---
Enable MongoDB's free cloud-based monitoring service, which will then receive and display
metrics about your deployment (disk utilization, CPU, operation statistics, etc).
The monitoring data will be available on a MongoDB website with a unique URL accessible to you
and anyone you share the URL with. MongoDB may use this information to make product
improvements and to suggest MongoDB products and deployment options to you.
To enable free monitoring, run the following command: db.enableFreeMonitoring()
To permanently disable this reminder, run the following command: db.disableFreeMonitoring()
---
> show dbs
admin 0.000GB
config 0.000GB
local 0.000GB
lueluelue 0.002GB
> use lueluelue
switched to db lueluelue
> db.dropDatabase()
{ "ok" : 1 }
> show dbs
admin 0.000GB
config 0.000GB
local 0.000GB
>
bye
root@74378c6e3120:~# mongorestore --archive=20220624-065751.archive
2022-06-24T10:55:45.812+0000 preparing collections to restore from
2022-06-24T10:55:45.853+0000 reading metadata for lueluelue.domains from archive '20220624-065751.archive'
2022-06-24T10:55:45.853+0000 reading metadata for lueluelue.claims from archive '20220624-065751.archive'
2022-06-24T10:55:45.853+0000 reading metadata for lueluelue.redeem_codes from archive '20220624-065751.archive'
2022-06-24T10:55:45.853+0000 reading metadata for lueluelue.invalid_domains from archive '20220624-065751.archive'
2022-06-24T10:55:45.853+0000 reading metadata for lueluelue.simple_redeem_codes from archive '20220624-065751.archive'
2022-06-24T10:55:45.853+0000 reading metadata for lueluelue.domain_registers from archive '20220624-065751.archive'
2022-06-24T10:55:45.893+0000 restoring lueluelue.claims from archive '20220624-065751.archive'
2022-06-24T10:55:45.914+0000 finished restoring lueluelue.claims (1126 documents, 0 failures)
2022-06-24T10:55:45.919+0000 restoring lueluelue.redeem_codes from archive '20220624-065751.archive'
2022-06-24T10:55:45.930+0000 finished restoring lueluelue.redeem_codes (300 documents, 0 failures)
2022-06-24T10:55:45.935+0000 restoring lueluelue.domains from archive '20220624-065751.archive'
2022-06-24T10:55:45.962+0000 finished restoring lueluelue.domains (3702 documents, 0 failures)
2022-06-24T10:55:45.968+0000 restoring lueluelue.invalid_domains from archive '20220624-065751.archive'
2022-06-24T10:55:45.979+0000 finished restoring lueluelue.invalid_domains (59 documents, 0 failures)
2022-06-24T10:55:45.985+0000 restoring lueluelue.simple_redeem_codes from archive '20220624-065751.archive'
2022-06-24T10:55:45.996+0000 finished restoring lueluelue.simple_redeem_codes (101 documents, 0 failures)
2022-06-24T10:55:46.002+0000 restoring lueluelue.domain_registers from archive '20220624-065751.archive'
2022-06-24T10:55:46.079+0000 finished restoring lueluelue.domain_registers (5173 documents, 0 failures)
2022-06-24T10:55:46.079+0000 restoring indexes for collection lueluelue.domains from metadata
2022-06-24T10:55:46.079+0000 index: &idx.IndexDocument{Options:primitive.M{"name":"name_1", "unique":true, "v":2}, Key:primitive.D{primitive.E{Key:"name", Value:1}}, PartialFilterExpression:primitive.D(nil)}
2022-06-24T10:55:46.080+0000 no indexes to restore for collection lueluelue.claims
2022-06-24T10:55:46.080+0000 no indexes to restore for collection lueluelue.simple_redeem_codes
2022-06-24T10:55:46.080+0000 no indexes to restore for collection lueluelue.domain_registers
2022-06-24T10:55:46.080+0000 no indexes to restore for collection lueluelue.redeem_codes
2022-06-24T10:55:46.080+0000 no indexes to restore for collection lueluelue.invalid_domains
2022-06-24T10:55:46.129+0000 10461 document(s) restored successfully. 0 document(s) failed to restore.
root@74378c6e3120:~#