Presuming your SysAdmin guys are using Data Protection Manager (full name from MS: System Center Data Protection Manager 20XX) to back up the server, there's a few "gotchas."
First, DPM doesn't give you quite the "fine-grained" control of a point-in-time recovery. You can ONLY recover a DB to the point DPM backed it up. So if DPM is doing hourly backups, and the DB gets hosed at 59 minutes after the hour, that's 59 minutes of data gone.
Second, DPM (at least in my situation) when backing up SQL DBs directly, broke my backup log chain (See this thread
) Not fun.
Third, DPM won't keep your transaction logs under control, so you'll still need to perform SQL backups, or put the DBs into Simple recovery mode.
My suggestion would be to work with the Sysadmins, perhaps by setting up regular backups in SQL to a folder either on the SQL server, or on the network, then have them back that up. They could also still run complete backups of the server, as I believe DPM can do "bare metal restores" of protected servers. So if the server caught fire, the Sysadmins could restore everything, then you go in and restore your SQL backups (making sure to drop the "pre-attached" SQL DBs that DPM would still have backed up)
And, of course, before doing any of this against production, test, test, test, test.