Shrinking data files causes fragmentation in your indexes, so I would strongly recommend you go and check for index fragmentation.

If a database has grown to a size it is usually because it needs to be that size. Granted one off imports and certain eronious instances where things just blow out of control happen and shrinking etc is the only way to reclaim the space, but 99% of the time you should never shrink a database unless you have a just and defined reason for doing so as the consequencies can be catestrophic if not immediatly resolved.

As you posted in the 2008 forum I am going out on a whim and saying your running SQL 2008, if so TRUNCATE_ONLY is not a valid backup option, it was removed in 2008 onwards due to the problems it causes.

As I have said in another article once today, go and check if your databases are in the right recovery model for your recoverability needs

http://msdn.microsoft.com/en-us/library/ms189275.aspx

Then put in place the proper transaction log management that is needed by refering to the two links I have already posted above.

If your in full, bulk-logged recovery but you dont do transaction log backups, you really need to start asking yourself do I really need to be in full, bulk-logged recovery.