# Access backup report / log files

**URL:** <https://kopia.discourse.group/t/access-backup-report-log-files/1293>\
**Category:** Support\
**Created:** [July 22, 2022, 7:09pm UTC](https://kopia.discourse.group/t/access-backup-report-log-files/1293 "2022-07-22T19:09:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luis\_Ito](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/luis_ito/32/424_2.png) [@Luis\_Ito](https://kopia.discourse.group/u/Luis_Ito)\
**Post date:** [July 22, 2022, 7:09pm UTC](https://kopia.discourse.group/t/access-backup-report-log-files/1293/1 "2022-07-22T19:09:54Z")

</div>

Hello, im running Kopia and want to be updated of success/errors and some briefing. Using folder actions I was hoping to call my script to grep the log files for the job id, however im unable to find where kopia stores its task log. I checked inside cache dir and while there are current log files none of them has information related to every job. What am i missing? The loggin settings in the policies are at their default values.

Cheers

---

<div class="post-metadata">

**Author:** ![basldfalksjdf](https://avatars.discourse-cdn.com/v4/letter/b/ce73a5/32.png) [@basldfalksjdf](https://kopia.discourse.group/u/basldfalksjdf)\
**Post date:** [July 22, 2022, 7:32pm UTC](https://kopia.discourse.group/t/access-backup-report-log-files/1293/2 "2022-07-22T19:32:17Z")

</div>

It sounds like you are using KopiaUI. Is that correct? If so, you won’t find logs for the tasks. Currently, KopiaUI saves logs in memory rather than on disk. There is a feature request open for someone to change this:

> <https://github.com/kopia/kopia/issues/2073>
>
> (1) Currently the logs for each task when using KopiaUI are not persistent -- th…ey are stored in memory only and not on disk. This means it is impossible to read the log for each task, since the \`Logs\` screen in KopiaUI truncates the logs and there is no underlying file we can look at. This is particularly troublesome if there is any error, such as when doing a restore, because one cannot read the log to identify the error. I talked with @jkowalski and he mentions it would be great to make the logs persistent so that they are saved to disk instead of just stored in memory. This would allow users to easily identify errors for any task. Note that logs when using Kopia CLI are already persistent; just not for KopiaUI.
> 
> (2) I think it would also be great if a link can be added in KopiaUI for each task that links to the log file for each task, a link that one can click to open the full log file in a text editor for easier viewing. The link can be added at the bottom of where the logs are already displayed in KopiaUI under \`Tasks\`. Note that some tasks will have multiple log files, since Kopia splits really large logs into multiple files. In such a situation, KopiaUI should link to all the log files for the particular task.
> 
> Thank you!

---

<div class="post-metadata">

**Author:** ![Luis\_Ito](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/luis_ito/32/424_2.png) [@Luis\_Ito](https://kopia.discourse.group/u/Luis_Ito)\
**Post date:** [July 22, 2022, 7:39pm UTC](https://kopia.discourse.group/t/access-backup-report-log-files/1293/3 "2022-07-22T19:39:32Z")

</div>

thanks, i’ve subscribed to that issue. I’m using Kopia in server mode, I guess it also means it’s using the UI, right?