Before developing your backup strategy, you need to develop a plan of action. Evaluate your company and ask, 'What is the maximum amount of downtime we can live with?' That is, perform a risk assessment.
Once this is established, you can decide on the appropriate course of action by matching your company's needs to the appropriate level of database backup.

A full backup is the easiest type of backup to implement in SQL Server. It takes a complete picture of your database that includes backing up users and permissions. In addition, this backup can occur while transactions are still occurring in your system. When the backup begins, the date is recorded, the data pages are backed up, and all transactions that occur while the backup runs are appended to the backup.

A full backup backs up your users but not your logins. If you want to back up your logins, remember to back up the Master database. Furthermore, if you ever restore your database to a different server, you must synchronise your logins by using the sp_change_users_login. For a more detailed explanation of this stored procedure, see SQL Books Online.

There are two backup procedures

• Enterprise Manager
• T-SQL

A transaction-log backup will back up all transactions that occur in the database and purge or clean up the log after the backup completes.
Using a transaction-log backup gives you point-in-time recovery for a database.

Keep in mind that you must be using Full or Bulk-Logged Recovery Models in order to perform transaction-log backups.

There are two transaction-log backup procedures

• Enterprise Manager
• T-SQL

A file-group backup lets you back up individual files or file groups. It basically allows you to back up a large database by spreading your backups out over time. This is a more granular type of backup that allows an admin to take a custom approach or to simply fill in the gaps of other backup methods.