renameCollection: backup fails but no messages in pbm-agent or pbm-coordinator logs

I don't think there is automatic check with the rename collection, but the drop collection and drop index make the same problem - please take a look at and probably there were no changes regarding this between old version and new one.

OK, I looked up the docs on what will happen.

A renameCollection operation does block a lot of things. From the renameCollection documentation:

Also:

So the dump phase can't continue dumping a collection if there is a renameCollection command on it simultaneously. Hence PBM also can not support backups that encounter a renameCollection - unless it was to have an auto-retry behaviour.

But I don't think PBM should be modified to have an auto-retry behaviour when it hits a renameCollection-caused error.

• A) It would have to be from the start, and

• B) statistically it is likely to be an application doing the renames repeatedly, so there's a good chance it will just happen again and again putting the backup in a long- or even infinitely-running loop.