Background: the fix for bug #711166 released in 2.0.5 had broken, among other things, partial streaming backups with multiple InnoDB tablespaces. XtraBackup erroneously printed the "Skipping <tablespace>" message to stdout rather than stderr. I noticed and fixed that while working on the fix for #1130627, though I did not report a separate bug for it.
I cannot reproduce this bug with the fix for #1130627, but I can reproduce it with that fix reverted.
So this bug is not reproducible with XB 2.0.6, though technically it's not a duplicate of bug #1130627, it's just been fixed with the same patch.
And the reason why the mentioned regression went unnoticed is that the XB test suite does not have any tests for this combination, i.e. partial streaming backups with multiple InnoDB tablespaces.
This bug is fixed in 2.0.6.
Background: the fix for bug #711166 released in 2.0.5 had broken, among other things, partial streaming backups with multiple InnoDB tablespaces. XtraBackup erroneously printed the "Skipping <tablespace>" message to stdout rather than stderr. I noticed and fixed that while working on the fix for #1130627, though I did not report a separate bug for it.
I cannot reproduce this bug with the fix for #1130627, but I can reproduce it with that fix reverted.
So this bug is not reproducible with XB 2.0.6, though technically it's not a duplicate of bug #1130627, it's just been fixed with the same patch.
And the reason why the mentioned regression went unnoticed is that the XB test suite does not have any tests for this combination, i.e. partial streaming backups with multiple InnoDB tablespaces.
Let's keep this report to add such a test case.