Answer the question
In order to leave comments, you need to log in
What is the reason for the lack of backups?
Dear experts! Help solve the problem with backups. Essence in the following:
There is a domain network, at users . domain accounts. Through the GPO (in the task scheduler, the script that launches winrar), each account is configured to back up the "Desktop" and "My Documents" folders.
What we have as a result:
1) After the user receives the policy, the scheduler successfully executes the script, the backup is normally placed in the network folder.
2) If you do not restart the computer, the backup will also be updated every day in a network folder.
3) Those who do not turn off the computer, but only enter it into sleep mode, also back up normally
4) After rebooting, the backup in the network ball stops updating
5) At the same time, the scheduler log says that the task was successfully completed
6) If you delete the old user backup, a new one will appear and will be updated until the computer is restarted again.
Initial data:
The startup script is located in the network share and looks like this:
if exist "C:\Program Files (x86)\WinRAR\WinRAR.exe" ("C:\Program Files (x86)\WinRAR\WinRAR.exe" a -r -u -f -dh -rr8 -y -ibck "\\superhost\backups$\work\%username%.rar" @\\it\packages\scripts\backup.lst) else ( if exist "C:\Program Files\WinRAR\WinRAR.exe" ( "C:\Program Files\WinRAR\WinRAR.exe" a -r -u -f -dh -rr8 -y -ibck "\\superhost\backups$\work\%username%.rar" @\\it\packages\scripts\backup.lst ) )
exit
Answer the question
In order to leave comments, you need to log in
Did you check the process in memory? Maybe it hangs for some reason. Those. after restarting the machine, the script executes, starts winrar, and this winrar process remains hanging in memory.
Maybe I'm pointing my finger at the sky, but what a reboot does is flush all sorts of caches. Maybe you have some kind of clock desync issue (if winrar uses file modification times). Or some problem of reading a file from a network share, which does not appear until a reboot, because. the file (or even just its metadata) remains in the local cache.
Try redirecting the output of this script to a file, and then see what prevents it from being executed after reboot.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question