VDI Error

• 
  Hi,
  
  I would imagine any four-year-old information about VDI is just as well because the API hasn't changed all that much. However, you should probably check the Red Gate support center as well, because the information there is collated, researched, verified, and kept up-to-date.
  
  VDI 1000 caused by bad installation:
  http://www.red-gate.com/supportcenter/C ... 000241.htm
  VDI 1000 caused by permissions
  http://www.red-gate.com/supportcenter/C ... 000243.htm
  VDI 1000 caused by account lookup failure
  http://www.red-gate.com/supportcenter/C ... 000242.htm
  
  There could be many more causes. Basically VDI 1000 is a generic failure in creating the virtual backup device on the SQL Server end.

  Brian Donahue April 02, 2009 12:46

  - 0 +
• 
  Are those related to the GUI version as well?
  
  I can restore with GUI, but I'm considering moving to automatic restore via the console app.
  
  The error happened on the console app.
  
  I am using the parameters copied from the last step from the GUI.

  adriangodong April 02, 2009 12:50

  - 0 +
• 
  Are you running the backup command from a different computer? If your windows logon doesn't have the permissions, you may want to try SQL authentication. (-u and -p arguments).
  
  You could also use sqlcmd.exe to execute the stored procedure-formatted command and see if you get better results that way.

  Brian Donahue April 02, 2009 12:57

  - 0 +
• 
  We're using SQL auth.
  
  Anyway, I'll see if the Extended SQL does it better.
  
  Thanks.

  adriangodong April 02, 2009 13:05

  - 0 +
• 
  It may be that you had forgot to add the -I parameter if you are restoring a named instance.

  Brian Donahue April 02, 2009 13:11

  - 0 +
• 
  OK, problem resolved when using sqlcmd.
  
  Thanks!
  

  Brian Donahue wrote:

  You could also use sqlcmd.exe to execute the stored procedure-formatted command and see if you get better results that way.

  adriangodong April 03, 2009 07:31

  - 0 +

Add comment

Please sign in to leave a comment.