# Are there any reasons to NOT use pt-archiver on a master-master environment?

**URL:** <https://forums.percona.com/t/are-there-any-reasons-to-not-use-pt-archiver-on-a-master-master-environment/3245>\
**Category:** Percona Toolkit\
**Created:** [February 1, 2014, 4:13pm UTC](https://forums.percona.com/t/are-there-any-reasons-to-not-use-pt-archiver-on-a-master-master-environment/3245 "2014-02-01T16:13:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tomdesp](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/tomdesp/32/977_2.png) [@tomdesp](https://forums.percona.com/u/tomdesp)\
**Post date:** [February 1, 2014, 4:13pm UTC](https://forums.percona.com/t/are-there-any-reasons-to-not-use-pt-archiver-on-a-master-master-environment/3245/1 "2014-02-01T16:13:21Z")

</div>

I also have another — probably connected — question: why is the whole slave-lag checking thing so important in archiving?  
I’m probably missing something important but I don’t see the risks of a sometimes lagging replication, as far as archiving is concerned.

Thanks a lot!
