backup job question

• Burt Jacobs

  SSC Journeyman

  Points: 79

  More actions

  April 30, 2004 at 11:29 am

  #85497

  Hi,

  Here is the Command I have in a Job step:

  exec sp_addumpdevice 'disk','aisys_bu','e:\ai_prod_backups\[DATE]_aisys.bak'

  backup database aiindex_system to aisys_bu

  Here is what happens:

  The .bak ends up in e:

  When I change the Command to just put the file on e:, the file ends up in e:, but the Job monitor reports failure, even when the .bak is actually there (in e.

  Can anyone shed some light as to what is going on?

  Thank you very much,

  Burt

• SQLBill

  SSC Guru

  Points: 51440

  More actions

  April 30, 2004 at 1:23 pm

  #504883

  What is the actual command you are using?

  Are you telling it to put it on e: or e:\  ?

  -SQLBill

• Burt Jacobs

  SSC Journeyman

  Points: 79

  More actions

  April 30, 2004 at 1:46 pm

  #504885

  Hi,

  I think I figured out what is happening.

  The problem arises when I try to run the above script/job for the second time.

  There seems to be the need to sp_dropdevice in the above script, or the sp_addumpdevice (I believe) has a problem when the backup device is already there and I start the job again - something like that, I think.

  I have 0 experience with mssql - and didn't/don't fully understand this backup device thing.

  So I just happened to see all the "backup devices" that I was supposedly creating when I drilled down to Backups in entman. I saw them there, blew them away, and then the script worked when I ran it again - the little light went on.

  The file not ending up where I thought/wanted is, I believe, an artifact of my ignorance concerning mssql.

  Here is what it looks like now - it seems to work more than once - i'll schedule it again and see what happens.

  exec sp_addumpdevice 'disk','aisys_bu','e:\burttest\[DATE]_aisys.bak'

  backup database aiindex_system to aisys_bu

  exec sp_dropdevice 'aisys_bu'

  Thank you for your help.

  Burt