How to transfer Databases from one server to another using the copy/paste method in MongoDB?

Question

MongoDB

After simply copying the data folder from one machine to another, replacing that folder, the Mongo service does not start on the second machine. Gives an error message. dump is not offered. It is necessary to solve it with the copy/paste method.
I changed the rights to the folder - it started up, but there was another problem both on the source and on the receiver. when opening the same project on a node - express writes an error -MongoError: Topology was destroyed

2018-10-24T09:44:06.095+0300 I CONTROL  [main] ***** SERVER RESTARTED *****
2018-10-24T09:44:06.520+0300 I CONTROL  [main] Trying to start Windows service 'MongoDB'
2018-10-24T09:44:06.521+0300 I CONTROL  [initandlisten] MongoDB starting : pid=3404 port=27017 dbpath=E:\MongoDB\Server\4.0\data 64-bit host=epsilon
2018-10-24T09:44:06.521+0300 I CONTROL  [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
2018-10-24T09:44:06.521+0300 I CONTROL  [initandlisten] db version v4.0.3
2018-10-24T09:44:06.521+0300 I CONTROL  [initandlisten] git version: 7ea530946fa7880364d88c8d8b6026bbc9ffa48c
2018-10-24T09:44:06.521+0300 I CONTROL  [initandlisten] allocator: tcmalloc
2018-10-24T09:44:06.521+0300 I CONTROL  [initandlisten] modules: none
2018-10-24T09:44:06.521+0300 I CONTROL  [initandlisten] build environment:
2018-10-24T09:44:06.521+0300 I CONTROL  [initandlisten]     distmod: 2008plus-ssl
2018-10-24T09:44:06.521+0300 I CONTROL  [initandlisten]     distarch: x86_64
2018-10-24T09:44:06.521+0300 I CONTROL  [initandlisten]     target_arch: x86_64
2018-10-24T09:44:06.522+0300 I CONTROL  [initandlisten] options: { config: "C:\Program Files\MongoDB\Server\4.0\bin\mongod.cfg", net: { bindIp: "127.0.0.1", port: 27017 }, service: true, storage: { dbPath: "E:\MongoDB\Server\4.0\data", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "C:\Program Files\MongoDB\Server\4.0\log\mongod.log" } }
2018-10-24T09:44:06.522+0300 I STORAGE  [initandlisten] Detected data files in E:\MongoDB\Server\4.0\data created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-10-24T09:44:06.522+0300 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=7679M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2018-10-24T09:44:06.705+0300 I STORAGE  [initandlisten] WiredTiger message [1540363446:704794][3404:140717136089216], txn-recover: Main recovery loop: starting at 9/37376
2018-10-24T09:44:06.844+0300 I STORAGE  [initandlisten] WiredTiger message [1540363446:843797][3404:140717136089216], txn-recover: Recovering log 9 through 10
2018-10-24T09:44:06.920+0300 I STORAGE  [initandlisten] WiredTiger message [1540363446:919811][3404:140717136089216], txn-recover: Recovering log 10 through 10
2018-10-24T09:44:06.988+0300 I STORAGE  [initandlisten] WiredTiger message [1540363446:987807][3404:140717136089216], txn-recover: Set global recovery timestamp: 0
2018-10-24T09:44:07.005+0300 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
2018-10-24T09:44:07.033+0300 I CONTROL  [initandlisten] 
2018-10-24T09:44:07.033+0300 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2018-10-24T09:44:07.033+0300 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2018-10-24T09:44:07.033+0300 I CONTROL  [initandlisten] 
2018-10-24T09:44:07.185+0300 W FTDC     [initandlisten] Failed to initialize Performance Counters for FTDC: WindowsPdhError: PdhExpandCounterPathW failed with 'Указанные объекты не найдены на этом компьютере.' for counter '\Memory\Available Bytes'
2018-10-24T09:44:07.185+0300 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory 'E:/MongoDB/Server/4.0/data/diagnostic.data'
2018-10-24T09:44:07.186+0300 I NETWORK  [initandlisten] waiting for connections on port 27017
2018-10-24T09:44:07.186+0300 I STORAGE  [initandlisten] Service running
2018-10-24T09:44:37.331+0300 I NETWORK  [listener] connection accepted from 127.0.0.1:52019 #1 (1 connection now open)
2018-10-24T09:44:37.332+0300 I NETWORK  [conn1] received client metadata from 127.0.0.1:52019 conn1: { driver: { name: "nodejs", version: "2.2.36" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "6.3.9600" }, platform: "Node.js v10.12.0, LE, mongodb-core: 2.1.20" }
2018-10-24T09:44:37.345+0300 I NETWORK  [conn1] end connection 127.0.0.1:52019 (0 connections now open)
2018-10-24T09:44:37.346+0300 I NETWORK  [listener] connection accepted from 127.0.0.1:52020 #2 (1 connection now open)
2018-10-24T09:44:37.346+0300 I NETWORK  [conn2] received client metadata from 127.0.0.1:52020 conn2: { driver: { name: "nodejs", version: "2.2.36" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "6.3.9600" }, platform: "Node.js v10.12.0, LE, mongodb-core: 2.1.20" }
2018-10-24T09:44:37.364+0300 I NETWORK  [conn2] end connection 127.0.0.1:52020 (0 connections now open)

Answer 1

1. MongoDb versions must match
2. Configurations must be
the same 3. File and folder permissions must be correct
What's in the logs?
Why Copy/Paste? Maybe then replication or snapshots are better?