Basically as stated above above, but maybe a starting point is to actually evaluate or determine your requirements for a backup package based on the following catagories:<br><br>A backup package -<br>MUST HAVE/BE ABLE TO do:<br>xxxx<br>xxx<br><br>WHERE WILL MY SYSTEMS BE NEXT YEAR, WILL THE PACKAGE GO WITH ME?<br><br>WOULD BE EXTREMELY USEFUL IF IT COULD/DOES do xxx<br><br>WOULD BE NICE/HANDY IF IT COULD/DOES DO xxxx<br><br>What Servers/Clients DOES IT NEED TO SUPPORT?<br><br>What Support does the vendor give?<br><br>Then go look at the glossies, call in those that say they can fulfil your MUST DO list and do or are going to fulfil your USEFUL/HANDY/NICE list, get eval copies and prove that it all does as advertised (make sure you do stress the packages not just play with them) and voila your fixed<br><grin> well hopefully its a good starting point...