I sent a nasty e-mail to our Symantec rep today. I installed CPS on 2 new servers, setup a CPS Backup job, then proceeded to wait almost 4 hours for the system to backup 5Gb. I then installed Backup Exec, setup a Backup Exec job to back the remote server up, and the 5Gb backup completed in about 15 minutes.
Here is a list of other issues I've run across with CPS:
-If CPS runs across a file it can't backup, it fails the job completely. I.E. it doesn't backup the rest of the files on the server, it just stops running. At least Backup Exec would mark the job "Completed with Exceptions"...not so with CPS.
-Starting a job manually requires at least 30 minutes of "Gathering Information" to take place on a server with as little as 5Gb of data. Hate to see a 100Gb backup with CPS, it would take all week (and no, I'm not doing any pre-scanning).
-Backing up a server with NT compressed drives or files seems to require you to have your backup destination compressed as well. Otherwise the job fails because it can't backup the compressed files on the source server.
-Where are the alerting or reporting features that Backup Exec has? You would think a backup system would have some sort of alerting system to inform you of the failed jobs your going to experience.
I'm very disappointed in CPS...it clearly is not ready for a large environment with numerous servers, SOX reporting requirements, high performance requirements, etc. I could backup my servers to USB quicker and more reliably than with CPS.