Ola’s Maintenance Solution Plan script newer version

You need to change the appropriate upstream precedence constraint(s) in the flow to On Completion instead of On Success.

This is done one of two ways:

1. Right-clicking the constraint on the design surface (shown below) and selecting the appropriate type from the popup menu.
2. In the Precedence Constraint Editor dialog (which you had open), select the appropriate type from the Value dropdown list.

In earlier versions than 2012, the constraint arrow will turn blue; in 2012, the arrow gets a more explicit "Completion" caption.

Now having said that, if you want to keep all of this in one flow, I would actually recommend using SQL Server Data Tools to create the package, because what you really need is a Sequence Container to put all the maintenance stuff in (keeping the existing On Success constraint types), and then connect the container to the backups task with an On Completion precedence constraint.

Alternatively -- and this is what I would usually do -- separate the backup portion of the process into a different subplan, and schedule it after the maintenance portion is expected to complete.

Agree with Jon.

Instead of going through the pain of setting up Maintenance Plans, I highly recommend to use

Ola Hallengren's SQL Server Maintenance Solution

This solution is flexible (can be adjusted as per your needs) and is supported on SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 as well as it is widely used in SQL Server community.

We have a much more complex environment and we use backup as well as maintenance solutions from Ola's site.