The only wrong behavior that I see here is b) from comment #2, i.e. that innobackupex hangs on error.
Everything else is expected:
Conflicts with existing files in the temporary directory are always possible. XtraBackup uses --tmpdir to create a PID file, and (for streaming backups) temporary copies of xtrabackup_logfile, xtrabackup_checkpoints, backup-my.cnf, xtrabackup_binlog_info, xtrabackup_slave_info, etc, or (for --rsync) xtrabackup_rsync_pass1, xtrabackup_rsync_pass2. If naming conflicts are possible with any of those files, one has to ensure that --tmpdir points to a unique temporary directory.
The fact that --tmpdir specifies the location for temporary files is also documented.
I'm changing the title to reflect the actual problem.
The only wrong behavior that I see here is b) from comment #2, i.e. that innobackupex hangs on error.
Everything else is expected:
Conflicts with existing files in the temporary directory are always possible. XtraBackup uses --tmpdir to create a PID file, and (for streaming backups) temporary copies of xtrabackup_logfile, xtrabackup_ checkpoints, backup-my.cnf, xtrabackup_ binlog_ info, xtrabackup_ slave_info, etc, or (for --rsync) xtrabackup_ rsync_pass1, xtrabackup_ rsync_pass2. If naming conflicts are possible with any of those files, one has to ensure that --tmpdir points to a unique temporary directory.
The fact that --tmpdir specifies the location for temporary files is also documented.
I'm changing the title to reflect the actual problem.