SIMS Backup - has dbattach changed its behaviour?

[psydii]

Just had a massive scare. Out nightly dbattach /backiup job was not doing what it was supposed to.

 

The job puts the backup file into the MSSQL\BACKUP folder and then copies that to a safe location.

 

Fine, except at some point dbattach seems to have started to return immediately, while the  sqlserver plods on through with the backup. The script doesn't appear to be expecting this and is written so that the copy (and the other bits of house keeping) happen as soon as dbattach returns.  This causes the copy to fail as sqlserver has the backup file locked (because it hasn't finished the backup!), and things get unglued from there.

 

Anyone else seen this behaviour? or have I missed something?