# Logging and preventing network hiccups

**URL:** <https://forums.percona.com/t/logging-and-preventing-network-hiccups/26790>\
**Category:** Percona XtraBackup\
**Tags:** closed-no-reply\
**Created:** [November 26, 2023, 6:52pm UTC](https://forums.percona.com/t/logging-and-preventing-network-hiccups/26790 "2023-11-26T18:52:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhare](https://avatars.discourse-cdn.com/v4/letter/b/a9a28c/32.png) [@bhare](https://forums.percona.com/u/bhare)\
**Post date:** [November 26, 2023, 6:52pm UTC](https://forums.percona.com/t/logging-and-preventing-network-hiccups/26790/1 "2023-11-26T18:52:45Z")

</div>

As far as I can tell when running `xtrabackup` with xbstream | `xbcloud` put it logs to the shell but does not log to any file. Is there a logfile by default? if not how do I save one?

I had an scenario where I lost SSH connection to an xtrabackup so I had to just wait until it the process was no longer in `ps` to know if it completed. When I went to restore it was missing part `.00000000000000001565` despite having all other 1566 parts. Would the log had said it was successful?

Is there a setting where it will keep retrying to upload a part indefinitely and never give up? this was painful to see it missed a single part when all the others were there.

Is there a way for it to add part 1565 back if it was ran with `--slave-info --safe-slave-backup` and the slave hasnt been restarted?