New territory - Page 2

desireemm · #16 (**permalink**) 01-09-09, 14:21

I am just manually doing a full backup of all our databases until I get this all sorted out.

MCrowley · #17 (**permalink**) 01-09-09, 14:22

Well, just to let you sleep at night (or keep you awake for a week straight), run this on a server you hope is being backed up:

Code:

select max(backup_start_date) as "Last Full Backup On", Database_name
from msdb..backupset
where type = 'D'
group by Database_name

desireemm · #18 (**permalink**) 01-09-09, 14:25

thank you MCrowley here is what I got

2009-01-09 08:50:52.000 ReportServer
2009-01-09 11:13:57.000 CommissionEmployee_Exclusionsdb
2009-01-09 10:50:07.000 SlotMachineDatabase
2009-01-09 11:15:18.000 DK09ADatabase
2009-01-09 08:50:55.000 PatronsDisputeDB
2009-01-09 09:09:39.000 New Exclusions Database
2009-01-09 09:34:36.000 SlotMachineDBSQL
2009-01-09 08:50:50.000 ReportServerTempDB
2009-01-09 08:50:57.000 LicensingActions
2009-01-09 11:00:55.000 SoftWareTesterdb
2009-01-09 11:17:51.000 Exclusions Database
2009-01-09 08:50:48.000 SKDatabase
2009-01-09 11:12:50.000 86
2009-01-09 11:14:50.000 DepartmentStats
2008-03-18 20:26:23.000 OBXKites
2009-01-09 11:18:48.000 GamingCommissiondb
2009-01-09 08:51:09.000 Distributor
2009-01-09 11:15:52.000 DKADatabase
2009-01-09 08:50:59.000 IncidentReportsdb
2009-01-09 11:13:21.000 Auditorsdb
2009-01-09 11:14:25.000 CorovanWareHouse
2009-01-09 08:50:44.000 VendorLicense
2008-03-18 20:25:25.000 SurveillanceStatsdb

PMASchmed · #19 (**permalink**) 01-09-09, 14:32

Quote:

Originally Posted by pootle flump

That sounds fair. Some people on here (me included) aren't fans of maintenance plans but they are probably best right now.
I would check the backup exec backups - maybe try a test restore on a test box. Unless he used the special SQL Server backup version of backup exec they are probably worth squat and are unrestorable.

Prefer to use agent jobs myself that run scripts, no likee maint plans.

PMASchmed · #20 (**permalink**) 01-09-09, 14:33

Quote:

Originally Posted by desireemm

Hi guys, we lost one of our IT guys and all of SQL SERver will be falling on me. He use to handle the backing up with BackUp Exec but now I will be handling it. I will not use Backup Exec I will use SQL Server itself. I was thinking of creating a Maintenance plan for all the user databases, Full Backup twice a week and Differential backup three times a week, setting the Database at Simple Recovery since we are nto the interested in Point in Time recovery. No one is entering data on a daily basis all throught out the day. Data is entered every other day I would say.

Does this sound like the correct approach guys??

Curious, was he/she a victim of this stellar economy, or was it a voluntary resignation, being you have to "take over" the duties, I imagine it was not the latter. I could see the same thing happening where I am currently. Infra guy can take over server level stuff, and developers can take ETL stuff. It really sucks now, I hope things pick up soon.

MCrowley · #21 (**permalink**) 01-09-09, 14:35

Well, I do hope that the OBXKites and SurveillanceStatsdb databases were dropped some time ago. They have not been backed up in some time.

Everything else has had a full backup today, at least.

desireemm · #22 (**permalink**) 01-09-09, 14:38

Thats cause I just backed them Up, this is the part where I go shoot myself

MCrowley · #23 (**permalink**) 01-09-09, 15:11

Actually, no. tThis is when you play around with that query, until you can assure yourself every day that the backups worked.

desireemm · #24 (**permalink**) 01-09-09, 15:13

you mean the query yoiu just gave me??
Yes you are right this is no time to go into depression and stress out

Thrasymachus · #25 (**permalink**) 01-09-09, 15:35

i wish my biggest problem was making sure the trains ran on time. those days seem so much simpler now.

economy shmonomy. my team is still hiring. need a sql developer in DC.

desireemm · #26 (**permalink**) 01-09-09, 16:18

guys I just want to make sure this is correct cause I think what he did was copy the MDF AND THE LDF OVER TO THE Backup file.
When I go into SQL Server and right click on a Database and look at the FILES here is the path
D:\Database\MSSQL\MSSQL.1\Data thats the path for the MDF AND THE LDF, but when I look in the BACKUP file hes got the same exact thing in there and its 71.6 GB I dont see actual backups

MCrowley · #27 (**permalink**) 01-09-09, 16:28

If that is the case, there had better be some sort of regular job to shut down the SQL Service, or he has no good backups. See if you can attach one of his "backups" to a dev server.

desireemm · #28 (**permalink**) 01-09-09, 16:48

Yes I detached and then Attached

Pat Phelan · #29 (**permalink**) 01-09-09, 18:01

Hmmm... I would have expected the server to scream bloody murder about that. Based on the file dates you cited above, I'd guess that those were old images from 2008-03-06 (which could be, those would attach without complaint and put the data back the way it was when those files were copied).

-PatP

desireemm · #30 (**permalink**) 01-09-09, 18:35

I dont know, this is frustrating. he has the same exact thing in the backups folder MDF AND LDF's. now when I did a backup my are .BAK extension. The same exact thing thats in the DATA file is the Same thing in the Backup file. Those arent Backups it looks like he just did a copy paste of the database and put them in the Backup file. Does that make sense??

Internet Services

Web Development

Digital Marketing

Consumer Tech