Server is rebooting after taking backup and it is not giving the Bak file also

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Backups » Server is rebooting after taking backup and...

Server is rebooting after taking backup and it is not giving the Bak file also

Rate Topic

Display Mode

Topic Options

Author

Message

naga.rohitkumar

Posted Thursday, March 14, 2013 12:07 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Yesterday @ 2:45 AM
Points: 525, Visits: 1,005

HI to all,

Server is getting restarted whenever we are running the SQL Backup [scheduled backup maintenance plan job and also tried manually ]. This issue has started after the storage migration activity.

1. on the daily monitoring basis i check the scheduled backup job at 10 am which is not executing nor giving any errors and in job activity monitor also job is not showing failed status and at the same time 10am daily server is rebooting no errors are identified in windows or in sqlserver logs.

2. I tried to execute the backup from job activity monitor -- start job at a step

3. from data base right click --- tasks --- backup

4. management---- maintenance plan ---- execute

all the possible ways i tried to take backup but after some time backup running and server is rebooting

what should we do in this scenario to solve this

Thanks & Regards
NAGA.ROHITKUMAR

Post #1430769

SQLRNNR

Posted Thursday, March 14, 2013 12:18 AM

SSCoach

Group: General Forum Members
Last Login: Yesterday @ 10:25 AM
Points: 18,754, Visits: 12,337

Is it throwing any errors into the error logs? Please post the errors.

Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008

SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp

Post #1430773

naga.rohitkumar

Posted Thursday, March 14, 2013 1:17 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Yesterday @ 2:45 AM
Points: 525, Visits: 1,005

its not posting any errors in event viewer or in sql server error logs both dba and wintel team is working from 2days on this to stop server rebooting at backup time from my end i disabled all the maintenance plan backup jobs...what is the actual reason unable to find we suspect after the activity storage migration its happening mainly

Thanks & Regards
NAGA.ROHITKUMAR

Post #1430791

SQLRNNR

Posted Thursday, March 14, 2013 10:14 AM

SSCoach

Group: General Forum Members
Last Login: Yesterday @ 10:25 AM
Points: 18,754, Visits: 12,337

No errors posted in any log?

Not in the storage logs?

Not in the OS logs?

Not in the SQL logs?

If not in any of those places, then maybe somebody has created a nasty alert that fires off a server shutdown any time a backup is created.

Maybe there is a scheduled reboot task in the windows scheduler.

Post #1431095

naga.rohitkumar

Posted Thursday, March 14, 2013 11:06 PM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Yesterday @ 2:45 AM
Points: 525, Visits: 1,005

nobody has created any of the schedules coz its occuring a the time of running backup manually or by scheduled backup jobs

it is in cluster also and it is giving failure audit of another node AP server failure log in DB server event viewer

we tried to take backup in both node [DB and AP servers ] at both it is rebooting and givng blue dump in windows. there also unable to find the errors

my exp is very less and so iam unable to find the root cause but iam trying my level best this is the site which made me to know more when ever a issue comes

Thanks & Regards
NAGA.ROHITKUMAR

Post #1431355

Bill (fluffydeadangel)

Posted Friday, March 15, 2013 8:42 AM

Valued Member

Group: General Forum Members
Last Login: Yesterday @ 9:59 PM
Points: 70, Visits: 223

Do you show any errors on the SAN side? is it dropping the luns due to too much data change or a journal getting full? If it happens after some time, i doubt it would be something like a shutdown trigger... if the SAN was recently changed, I'd look at what they're doing. Do you have the option at least to add a physical drive to the server to get a good backup going? maybe see if backing up to a physical drops you or not (if one is easy to obtain)

Post #1431567

SQLRNNR

Posted Friday, March 15, 2013 10:11 AM

SSCoach

Group: General Forum Members
Last Login: Yesterday @ 10:25 AM
Points: 18,754, Visits: 12,337

naga.rohitkumar (3/14/2013)

What commands are you using to run a manual backup?

The blue screen and windows dump is an issue. This would generate logs and dmp files. When a blue screen occurs, I'd be more focused on the hardware, drivers, or windows installation.

Post the actual backup command you are using. It is possible that due to a driver misconfiguration or failing hardware that the IO load from a backup will provoke a blue screen. But for that there would be some information in the windows logs, dump files or possibly in the SAN logs.

Post #1431616

naga.rohitkumar

Posted Wednesday, March 20, 2013 1:11 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Yesterday @ 2:45 AM
Points: 525, Visits: 1,005

Hi SQLRNNR & Bill

Thanks for your replies issues is partially solved here i'am giving description and also can you please suggest why it is solved ?

1. we didn't find any root cause and errors from any side but after deep monitoring in the server from wintel steam had updated firmware later from DB end i tried to take backup manually to check whether the server is rebooting now also.. but the one of the database backup is executed and in the properties of the job we find the owner has changed and by comparing the job which has success we changed and tried to take backup then it also executed [these two databases are user databases ]

2. in system database[master.model,msdb] maintenance plan backup jobs are continuesly failing even after checking all the permissions correct

1. then i disabled the current one and created a duplicate backup
maintenance plan and tried to execute it went success and the .BAk files is available for current time similarly created for every one and scheduled also whether its working or not ... it is succeeded

2. deleted all jobs and freshly created and checked its working and
now it is under monitoring for few days

3. can any one say why it got succeeded and what is the actual cause because i want to know the root cause.
"some times right things get wrong and wrong one clicks "

Thanks & Regards
NAGA.ROHITKUMAR

Post #1433022

« Prev Topic | Next Topic »

Permissions