Executing restic on windows server - redirect output to log

Getting Help
1

Hi everyone,
I am using restic (version 0.17.3) on a Windows Server.
I need to backup a relatively large file (about 3 Gb) on an Amazon AWS repository, but I have a relatively slow Internet connection.
Everything works well, but I would like to run “restic backup blah blah” redirecting the output in a file.
I have tried to execute the command with “–verbose --verbose” option and redirecting the output to a file.

The “problem” is that in the log file I have very little clue on what is going on and on the time that the operations have last.

Here are the sample of the log file

open repository
using parent snapshot 3f89a32f
load index files
start backup on [D:\foo\bar\file.ext]

Is there any native mean (without using tee) that I could use to get more detail on log file ?

Thanks in advance

Paolo

2

Please note that I have just tried to use a native implementation of tee for Windows (GitHub - dEajL3kA/tee-win32: Tee for Windows) with no success : the content of the log file has not changed, and I have still no progress after the “start backup on […]” line.

Paolo

3

I’ve never heard of “Tee”, I just did a search and it’s something to do with redirecting standard output. I don’t know why you’d need that. Restic can back up files any size to anywhere, it breaks the files into blocks.

Suggest you edit your question to say what the problem is, rather than how you’ve tried to solve it. Share the command(s) you use and any error messages. Ask a clear question about what you need help with. For example you said “I need to backup a relatively large file (about 3 Gb) on an Amazon AWS repository” - do you mean you have a large file on your PC that you need to back up to AWS S3? Or do you have a large file on an “AWS repository” like CodeCommit. People can help you more easily if you’re clear and precise about your current state and your issue.

I run a backup from my Windows machine to AWS S3 that backs up files from tiny to multi-GB, no problems. Logs are stored on the file system, though I virtually never look at the logs.

4

tee on unix writes data from stdin to the specified file while also sending it to stdout. For example echo "test" | tee some-file.txt.

For log files restic by default only logs completed files. But you can set the environment variable RESTIC_PROGRESS_FPS (see Manual — restic 0.18.0 documentation for details) to for example 0.166` to get one status update every minute.