I’ve got a script that runs every AM to check on windows backup and Acronis log files to look for failures. It relies on the Automise FileSet function, reverse sorted by date to identify the file which it then passes to a small program that goes through and looks for problems.
Recently I noticed on a customer who had a massive amount of log files, that the fileset was being built in the report, but it didn’t pass anything to the environment variable when I wanted to take the top item off. I found that this reliably occurred somewhere above the 260 file count. (I didn’t feel like spending all day figuring it out.)
Is this something happening in Automise, or is there another explanation?
I’ve added a copy of the logfile with the relevant portions for your review.
Thanks!backupcheck.txt (137.615 KB)
Hi Keith,
This is actually a Windows limit in that the total size of the Environment block for a process is 32,767 Unicode characters (65,534 bytes), which means the NTLogs environment variable can’t hold that much information. We’ve put in a check in Automise to actually error out if this is the case instead of just not setting the variable, this will be in future builds.
Regards,
Paul.