Hi Lasse,
using the date for a file name is possible, but complicated. While the variable %date% contains the current system date, it will also contain certain characters, which are not allowed in file names (maybe depending from the local settings of your WHS), so that a simple %date%.log would often not work.
Workarounds for this:
Use always the same file name and have robocopy append the new logging information instead of overwriting the older logs.
By checking its modify date you already see, if the latest executions did work.
Set up another task to delete that file regulary, maybe one time per month.
Another workaround:
Make a separate task for each day of the week (or each week of the month, dependend from the frequency of your backups), pointing to a different log file.
The logfiles will be overwritten each time, that task runs again.
Best greetings from Germany
Olaf
I decided to go for the %date% alternative. Using the commandline like ...
> echo %date%
gave good result. (2008-10-09)
Also, using the command line I started Robocopy,,, and all performed well. The loggfile was created as expected,,, and my files where copied,,,
But ... using the exact syntax in the scheduled job task,,,, resulted in a log file called %date%
Whats the difference between starting a job (Sheduled task) and striting it from the commandline.... how do I avoid this???
//lasse
Lasse
