# PBM restore on the GMT+3

**URL:** <https://forums.percona.com/t/pbm-restore-on-the-gmt-3/17017>\
**Category:** Uncategorized\
**Created:** [August 13, 2022, 1:14pm UTC](https://forums.percona.com/t/pbm-restore-on-the-gmt-3/17017 "2022-08-13T13:14:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Magzhanova](https://avatars.discourse-cdn.com/v4/letter/m/c89c15/32.png) [@Magzhanova](https://forums.percona.com/u/Magzhanova)\
**Post date:** [August 13, 2022, 1:14pm UTC](https://forums.percona.com/t/pbm-restore-on-the-gmt-3/17017/1 "2022-08-13T13:14:49Z")

</div>

Servers, where mongod and pbm-agent are running are on the GMT+3.

When I brows backups using pbm status, I see UTC time.

Example:

Snapshots:  
2022-08-08T13:07:07Z 740.23KB [complete: 2022-08-08T13:07:13]

So, I understand, that backup completed at 16:07:13.

Is it correct to use current time minus 3 hours, when I use pbm restore?

If I use current time, I get …Error: verify oplog slices chain: no chunk with the target time, the last chunk ends on {1659964883 2}

---

<div class="post-metadata">

**Author:** ![Dmytro\_Zghoba](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/dmytro_zghoba/32/4721_2.png) [@Dmytro\_Zghoba](https://forums.percona.com/u/Dmytro_Zghoba)\
**Post date:** [August 14, 2022, 12:57pm UTC](https://forums.percona.com/t/pbm-restore-on-the-gmt-3/17017/2 "2022-08-14T12:57:23Z")

</div>

Hi @Magzhanova

PBM always uses UTC.

Your case: you have a backup called “2022-08-08T13:07:07Z”.  
If you run `pbm restore 2022-08-08T13:07:07Z`, database will be restored to a state at 2022-08-08 13:07:13 UTC (16:07:13 GMT+3).

If you do not configure PITR, you only can run the restore command with a concrete backup name to restore to **complete time**.  
However, PITR functionality allows you to restore to a desired time (specified in UTC only).
