# No base snapshot

**URL:** <https://forums.percona.com/t/no-base-snapshot/16270>\
**Category:** Percona Backup for MongoDB\
**Created:** [June 23, 2022, 5:15am UTC](https://forums.percona.com/t/no-base-snapshot/16270 "2022-06-23T05:15:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Seventh\_Son](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/seventh_son/32/6333_2.png) [@Seventh\_Son](https://forums.percona.com/u/Seventh_Son)\
**Post date:** [June 23, 2022, 5:15am UTC](https://forums.percona.com/t/no-base-snapshot/16270/1 "2022-06-23T05:15:15Z")

</div>

First of all thanks Percona for such an amazing tool- **pbm**.

pbm status show some chunks and this:

```auto
2022-05-31T19:34:27Z - 2022-06-23T04:10:07Z (no base snapshot)

```

nevertheless snapshots exist for long time, scheduled by cron to run twice a day and I even ran pbm backup manually.  
So PITR does not use regular snapshots as base and run its own?  
How to fix (no base snapshot) PITR issue?

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [June 24, 2022, 11:13am UTC](https://forums.percona.com/t/no-base-snapshot/16270/2 "2022-06-24T11:13:45Z")

</div>

Hello, seems somehow the metadata got out of sync with the actual files. Did you try  
`pbm config --force-resync` ?

---

<div class="post-metadata">

**Author:** ![Seventh\_Son](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/seventh_son/32/6333_2.png) [@Seventh\_Son](https://forums.percona.com/u/Seventh_Son)\
**Post date:** [June 29, 2022, 12:51pm UTC](https://forums.percona.com/t/no-base-snapshot/16270/3 "2022-06-29T12:51:46Z")

</div>

Hi Ivan.

yes, I tried, no luck. It seems for me it started after some S3 changes applied, like Management-\>LifeCycle, AWS moved some files to Glacier and it broke the chain.  
Will try to revert S3 policy and resync again.

Ivan, could you please clarify what full backup PITR use as base?  
Does PITR use any last full backup as a base for next oplog slices or just first one, initially created?