Backup issue

All replies

• 

  

  1

  Sign in to vote

  I guess you have multiple backups scheduled did you checked SQL server jobs completely and made sure no other jobs are configured ?

  Its not possible that backup information is printed in Log file without backup being initiated so I can only say you did not checked the server completely

  Also can you post the complete error message does its says anything about VIRTUAL DEVICE if this is the case there is some TP backup scheduled as well

  ---

  Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
  
  My Technet Wiki Article
  MVP

  • Proposed as answer by Ed Price - MSFTMicrosoft employee Thursday, December 15, 2016 2:54 AM
  • Marked as answer by Ed Price - MSFTMicrosoft employee Tuesday, January 3, 2017 11:57 PM

  Tuesday, June 9, 2015 3:46 PM
• 

  

  1

  Sign in to vote

  Hi, is the backup performed using SqlAgent? Can you post here error log?
  

  Verify free disk space on backup device

  ---

  Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

  Tuesday, June 9, 2015 3:46 PM
• 

  

  0

  Sign in to vote

  Hi Shanky Sir,

  I am very sure that no other jobs are configured for backups.

  for Second point-- job history and the backup history shows that the job succeeded and last backup was on is correct as per the schedule, checked event viewer, the only error says "BACKUP failed to complete the command BACKUP DATABASE ABCDE. Check the backup application log for detailed messages"

  For third point-- did not find anything about VIRTUAL DEVICE.

  please note sir that this is netbackup.

  Thanks,

  Tuesday, June 9, 2015 4:19 PM
• 

  

  1

  Sign in to vote

  Run below query to see backup device name for database. Make sure to change database name.

  USE [databasename]
  go
  SELECT TOP 100 
      s.database_name, 
      m.physical_device_name,
      CAST(DATEDIFF(second, s.backup_start_date,
      s.backup_finish_date) AS VARCHAR(100)) + ' ' + 'Seconds' TimeTaken,
      s.backup_start_date,
      CASE s.[type]
      WHEN 'D' THEN 'Full'
      WHEN 'I' THEN 'Differential'
      WHEN 'L' THEN 'Transaction Log'
      END AS BackupType,
      s.server_name,
      s.recovery_model
      FROM msdb.dbo.backupset s
      INNER JOIN msdb.dbo.backupmediafamily m ON s.media_set_id = m.media_set_id 
      WHERE s.database_name = DB_NAME()
      ORDER BY backup_start_date DESC, backup_finish_date

  
  

  ---

  Regards,
  Vishal Patel
  Blog: http://vspatel.co.uk
  Site: http://lehrity.com

  • Proposed as answer by Ed Price - MSFTMicrosoft employee Thursday, December 15, 2016 2:54 AM
  • Marked as answer by Ed Price - MSFTMicrosoft employee Tuesday, January 3, 2017 11:57 PM

  Tuesday, June 9, 2015 4:57 PM
• 

  

  1

  Sign in to vote

  So how do you take backup via TSQL backup command or via Third party tool Netbackup ?
  

  ---

  Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
  
  My Technet Wiki Article
  MVP

  Tuesday, June 9, 2015 5:40 PM
• 

  

  0

  Sign in to vote

  We take net backup  via batch file, like "D:\Program Files\VERITAS\ ........

  Thanks.

  Tuesday, June 9, 2015 5:58 PM
• 

  

  1

  Sign in to vote

  I suggest you talk to Veritas.

  ---

  Tibor Karaszi, SQL Server MVP | web | blog

  • Proposed as answer by Ed Price - MSFTMicrosoft employee Thursday, December 15, 2016 2:54 AM
  • Marked as answer by Ed Price - MSFTMicrosoft employee Tuesday, January 3, 2017 11:57 PM

  Tuesday, June 9, 2015 6:11 PM
• 

  

  1

  Sign in to vote

  We take net backup  via batch file, like "D:\Program Files\VERITAS\ ........

  Thanks.

  
  So this means you are talking backup using third part tool correct and what about job scheduled with SQL server agent is that using TSQL ? You are not giving complete answer at point you are saying you use TP tool and then you are saying you are not can you clearly mention what all tools you are using and how SQL Server agent is taking backup
  

  ---

  Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
  
  My Technet Wiki Article
  MVP

  • Proposed as answer by Ed Price - MSFTMicrosoft employee Thursday, December 15, 2016 2:54 AM
  • Marked as answer by Ed Price - MSFTMicrosoft employee Tuesday, January 3, 2017 11:57 PM

  Tuesday, June 9, 2015 6:11 PM
• 

  

  1

  Sign in to vote

  Hi Shanky Sir,

  Yes, the job is scheduled via SQL server agent using CmdExec which uses batch file from a location D:\Program Files\VERITAS\.... so on.

  The only tool we us here is net backup/veritas to backup the databases. 

  Thanks.

  Tuesday, June 9, 2015 6:37 PM
• 

  

  2

  Sign in to vote

  Hi Shanky Sir,

  Yes, the job is scheduled via SQL server agent using CmdExec which uses batch file from a location D:\Program Files\VERITAS\.... so on.

  The only tool we us here is net backup/veritas to backup the databases. 

  Thanks.

  
  Its very hard to tell from here where the message is coming from you yourself have to find if you dont use any other backup contact the vendor
  

  ---

  Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
  
  My Technet Wiki Article
  MVP

  • Proposed as answer by Ed Price - MSFTMicrosoft employee Thursday, December 15, 2016 2:55 AM
  • Marked as answer by Ed Price - MSFTMicrosoft employee Tuesday, January 3, 2017 11:57 PM

  Wednesday, June 10, 2015 4:09 AM
• 

  

  1

  Sign in to vote

  Good day venkatesh1985,

  Why wont we start from the start :-)
  Do you need to use the current backup procedure?
  Can you ignore the current backup procedure, and third party application, and just start manually to create FULL backup of the database.

  *** This mean that if you have backup chain you will lose it! DON'T DO IT if you have any backup CHAIN that you need to continue, or if you do not 100% clear of what is backup chain. Moreover! since I am not familiar if and what third party application you are using, I can not recommend this action.

  IF you decide to continue: Can you manually execute this backup command (after you change the data to fit your database and file path)?

  BACKUP DATABASE [QQ] -- replace the database name
  TO  DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL13.SQL2016\MSSQL\Backup\QQ.bak' -- replace the path and make sure that you have permissions
  WITH 
  	NOFORMAT, NOINIT,  
  	NAME = N'QQ-Full Database Backup', -- replace the name (you can any)
  	SKIP, NOREWIND, NOUNLOAD,  STATS = 10
  GO

  If simple backup work OK for you, then next I will probably try to create new JOB using simple backup. If this OK as well then you can start create your own backup procedure (ful+log backup as needed).

  The big issue is that we do not have information regarding the current backup procedure, and the big question is DO YOU HAVE :-) if no one in your company have any information on the current procedure then maybe it is time to start from scratch?

  this can help you to chose and start Backup Best Practices:
  http://www.brentozar.com/sql/backup-best-practices/

  *** If you are using third party application then you should ask them for support :-)
  ** If someone else in the company in-charge on backups or create the current procedure then you should ask him.

  ---

  Ronen Ariely  [Personal Site]    [Blog]    [Facebook]

  • Proposed as answer by Ed Price - MSFTMicrosoft employee Thursday, December 15, 2016 2:55 AM
  • Marked as answer by Ed Price - MSFTMicrosoft employee Tuesday, January 3, 2017 11:57 PM

  Friday, July 17, 2015 2:27 PM