You can use scripts and windows scheduling service to automate ISA Server backup. With this script you can put backup file wherever you like in your network. I am using this script for some time now and it does a full server backup no problems so far.
<package> <job id="isasrvexport"> <form> </form> <script language="VBScript"> Dim WSHNetwork, objXML Dim strPath Dim strFileName Dim dtmThisMinute, dtmThisHour Dim dtmThisDay, dtmThisMonth, dtmThisYear Set WSHNetwork = CreateObject("WScript.Network") Set objXML = CreateObject("Msxml2.DOMDocument") strPath = "\\isa\BackupISA server" dtmThisMinute = PadDigits(Minute(Now), 2) dtmThisHour = PadDigits(Hour(Now), 2) dtmThisDay = PadDigits(Day(Now), 2) dtmThisMonth = PadDigits(Month(Now), 2) dtmThisYear = Year(Now) strFileName = WSHNetwork.ComputerName & "-" & dtmThisYear & "-" & dtmThisMonth & "-" & dtmThisDay & "-" & dtmThisHour & "-" & dtmThisMinute & ".xml" Dim objFPC Dim objArray Set objFPC = WScript.CreateObject("FPC.Root") Set objArray = objFPC.GetContainingArray objArray.Export objXML, 0 objXML.Save(strPath & "\" & strFileName) Function PadDigits(n, totalDigits) If totalDigits > len(n) then PadDigits = String(totalDigits-len(n),"0") & n Else PadDigits = n End If End Function </script> </job> </package>
at the beginning of the script i have put a name of the script "isasrvexport" you have to name the script the same. You can put whatever name there but you should keep in minde that the same name you have to put on the file as well. Also, the extention of the script should be .wsf. Therefore, the name of this script would be isasrvexport.wsf.
Use windows scheduler and as application use this script.