restore db,missing some records

__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.

1. backUp influxdbData in my window server ,use script "influxd backup -database lams_datacenter -start 2021-03-26T08:00:00Z -end 2021-04-08T08:00:00Z "D:\influxdb\backupData\lams_datacenter""
2. restore meta data in my local pc ,use script "influxd restore -metadir "D:\influxdb\meta" "D:\influxdb\backupData\meta""
3. restore db data in my local pc,use script "influxd restore -database lams_datacenter -datadir "D:\influxdb\data" "D:\InfluxDB\backupData\lams_datacenter""
Unfortunately, we can't add pictures here, so we can't describe the problem more accurately

__Expected behavior:__
data in "2021-03-26T08:00:00Z -end 2021-04-08T08:00:00Z " will be restore full

__Actual behavior:__
some records missed, Especially the data loss at the end of March and the beginning of April
__Environment info:__

* System info: server is windows server 2012R2, local pc is win10
* InfluxDB version: 1.8.1
* Other relevant environment details: Container runtime, disk info, etc

__Config:__
Copy any non-default config values here or attach the full config as a gist or file.

__Logs:__
Include snippet of errors in log.

__Performance:__
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.

```sh
# Commands should be run when the bug is actively happening.
# Note: This command will run for ~30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=30s"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz` and `iostat.txt` output files.
```

Start by reproducing the Windows backup and restore sequence with InfluxDB 1.8.1, using the commands and paths in the issue. Compare the restored records with the requested 2021-03-26 to 2021-04-08 range; done means identifying why records are missing and adding a verified fix or a reproducible diagnosis.

Written by the indexing model from the issue text.