Re: SMS SQL DB backup
From: Cathy Moya [MS] (camoya_at_online.microsoft.com)
Date: 10/08/04
- Next message: Dave Halperin: "Re: Advanced Client Installation"
- Previous message: Eric Holtz [MSFT]: "Re: Help with Site Settings from WMI script"
- In reply to: Rune Norberg: "Re: SMS SQL DB backup"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 8 Oct 2004 12:09:51 -0700
We have a whole guide on backup, recovery, and site maintenance:
Scenarios and Procedures for SMS 2003: Maintenance, Backup, and Recovery
http://www.microsoft.com/smserver/techinfo/productdoc/default.asp
-- Cathy Moya, MCSE: Security, MCT Technical Writer, Enterprise Management Content Group Check out the SMS Technical FAQ: http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx This posting is provided AS IS with no warranties and confers no rights. "Rune Norberg" <runeno@online.no_NOSPAM> wrote in message news:4166ae60$1@news.wineasy.se... > Yes - you are understanding this correctly. > > Also - the SMS Site Recovery Wizard will try to recover changes done > between the backup time and the failure by looking at a reference site. But > of course that will only apply to replicated objects like packages, > advertisements and collections; for reports and queries that does not > replicate I would consider keeping an "offline" copy by using the export > feature of SMS 2003 for those classes. > > Rgds, > Rune > > "Frank" <figlesias@namb.net> wrote in message > news:21816012.0410080704.5d0f1639@posting.google.com... > > Thanks for the info. That is very helpful as I was not aware of sync > > issues. So I guess what I am wondering then as if the SQL server > > blows up say two days after the SMS backup runs and lots of stuff > > whether it be reports, advertisements or whatever was added, the best > > way to get that back would be either back up SMS very often so as to > > not lose data knowing that depending on the time of failure, some > > stuff could be lost. Am I understanding this correctly? > > > > Thanks again for the info! > > > > Frank > > > > "Rune Norberg" <runeno@online.no_NOSPAM> wrote in message > > news:<416633e8$1@news.wineasy.se>... > >> When you restore SMS you need the SQL DB, the file struture and registry > >> from the point in time. The reason for this is some "counters" that needs > >> to > >> be in sync. > >> > >> Running SQL DB in Full Recovery mode would allow you restore the DBto a > >> certain point in time, but that DB would be out of sync with the file > >> structure and registry. So the best pratice is to use simple recovery > >> mode > >> for SQL and use SMS's builtin backup task. > >> > >> Rgds, > >> Rune > >> > >> "Frank" <figlesias@namb.net> wrote in message > >> news:21816012.0410071954.8a76796@posting.google.com... > >> >I have an SMS2003 installation that is replcaing or SMS 2.0 site (no > >> > upgrade) and am wondering about SQL backups. I realize that SMS has > >> > its own backup routine and we do utilize that of course. However, in > >> > SQL 2000, I noticed that the SMS DB was set up in a Simple Recovery > >> > Mode as opposed to full under the db options. Is there any reason for > >> > this? We would like to switch it to Full to get SQL full and > >> > transaction log backups independent of SMS but are uncertain if there > >> > are any issues that may arise from this. I have actually had to > >> > restore an SMS 2.0 SQL 7 db method this way once so it was real > >> > helpful to have this in place. If we could switch to Full recovery > >> > mode, that would be great. Any ideas? > >> > > >> > Frank > >
- Next message: Dave Halperin: "Re: Advanced Client Installation"
- Previous message: Eric Holtz [MSFT]: "Re: Help with Site Settings from WMI script"
- In reply to: Rune Norberg: "Re: SMS SQL DB backup"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|