You can issue backup SQL commands against your database.
It's pretty much standard syntax that you can execute against a connection object.
http://technet.microsoft.com/en-us/library/ms191304.aspx[
^]
However, this comes with some security issues that you would need to consider and naming considerations due to the multi-user environment
e.g
BACKUP DATABASE and BACKUP LOG permissions default to members of the sysadmin fixed server role and the db_owner and db_backupoperator fixed database roles.
So your client application that is issuing the backup command would need to have the appropriate permissions
Personally, I think this is a terrible approach to backups. If you want regular backups of a database, just schedule a job to perform them once per hour or whatever.
If you need to restore a db from backup, this is definitely something that should sit with a DBA in a multi-user environment. You wouldn't want your client application being able to do this, that way madness lies