# Key-value sizes at DR source and destination have a big difference

**URL:** https://forums.foundationdb.org/t/key-value-sizes-at-dr-source-and-destination-have-a-big-difference/3351
**Category:** Using FoundationDB
**Created:** [June 1, 2022, 7:03pm UTC](https://forums.foundationdb.org/t/key-value-sizes-at-dr-source-and-destination-have-a-big-difference/3351 "2022-06-01T19:03:44Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![lehu](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/lehu/32/995_2.png) [@lehu](https://forums.foundationdb.org/u/lehu)
#### Post date: [July 20, 2022, 8:52pm UTC](https://forums.foundationdb.org/t/key-value-sizes-at-dr-source-and-destination-have-a-big-difference/3351/6 "2022-07-20T20:52:12Z")

</div>

I found a related a posting, [Increased system keyspace size after backups finish - #6 by SteavedHams](https://forums.foundationdb.org/t/increased-system-keyspace-size-after-backups-finish/3321/6)

From reading the posting, it seems the system keyspace for backup (and DR, I believe) would contain the backup status data and backup snapshot file map.

We are just wondering if it would contain any transaction log entries (Some DBMSs do that). We are setting up DR for production, so the size increase is a concern for us.  
We are using FDB v6.2.27.

Thanks.

---

_[View the full topic](https://forums.foundationdb.org/t/key-value-sizes-at-dr-source-and-destination-have-a-big-difference/3351)._