We are an I.T. provider to companies in our region. We use a very popular online backup service. We also use a monitoring system from another provider. We need to have a bat or vbs script created which will parse the log file for the online backup program and then, based on the codes logged in the online backup log file, your script will need to create & set a variable that states whether the backup is successful or failed. We consider the backup successful only if: 1. It occurred within the past day (24 hours). AND 2. It is the most recent backup attempt logged. The log file timestamps the beginning of every log line with a timestamp in the following format: 17Jun2011 21:47:59 So although this is probably not too difficult to parse, it is also probably not the simplest timestamp format. Your script would of course have to compare the current timestamp against the timestamp for the most recent backup process run. If more than 24 hours have lapsed in between the logged timestamp of the last backup AND the current (Now()) timestamp, a failure must be specified in the variable used to indicate the status. Other requirements: ============== Your script must run successfully on all versions of: Windows XP (Home & Pro) Windows Vista (Home Premium, Business, Ultimate, Enterprise) Windows 7 (Home Premium, Pro, Ultimate, Enterprise) The script must not have any software dependencies for successful execution, aside from the common component preinstalled on the above mentioned operating systems (hence the preference for .bat or .vbs). The script must first parse a registry variable which stores the value corresponding to the log file location within the local file system The script must exit with a return code of 0 if the backup is deemed successful (based on the above mentioned criteria), and a code of 1 if the backup is deemed unsuccessful. The online backup product we are using actually has 2 types of backups: 1. Online 2. Local (to attached USB storage). The logfile line which shows the status of the most recent backup job specifies whether the current log line is pertaining to the Online backup job, or the Local backup job. Parsing & distinguishing between these is as simple as checking for the string "Online" or "Local" (or very similar) in the corresponding log line. We will actually require two versions of the script to be created. One which will check the status of the online backup. The other will check the status of the local backup. Other than parsing for the string "online" or "local" in the relevant log line, the two scripts will be nearly identical. So this should only add 5 minutes to the overall time required to build the scripts. Other pertinent details: To save you time, we have already attempted to build this script ourselves both as a .bat script, and as a .vbs. We have made significant progress in each, but ultimately decided that the script would be completed quicker by outsourcing its completion to you. Upon initiating the job, we will provide you with an example copy of the log file, as well as a .bat & .vbs version of the script, which we have already partially completed. You may use either of these scripts as references, or build on them and simply add the needed code to see them completed. However, there is no question that they will be a valuable part of you completing this job in less time. Both scripts already contain the location of the reg key that needs loaded, as well as the code to do so. One or both of them also already include code to parse the timestamps formatting. We do not have code to properly traverse the logs. You must write that. We do not have a preference between .bat or .vbs. Only one version is required to be completed & fully functional, in order for the project to be considered complete. We believe that a skilled, seasoned .bat or .vbs scripting expert should be able to produce the required script in 2-5 hours of your time. Desired Skills: Scripts & Utilities, bat, vbs Keywords: Software Application, Script, bat, vb, Utility