Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Maintenance Plans - Backups and Removing Old Files Expand / Collapse
Author
Message
Posted Monday, June 3, 2002 12:00 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Monday, November 17, 2014 2:20 PM
Points: 6,800, Visits: 1,914
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/awarren/maintenanceplansbackupsandremovingoldfiles.asp>http://www.sqlservercentral.com/columnists/awarren/maintenanceplansbackupsandremovingoldfiles.asp

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #4595
Posted Monday, June 10, 2002 4:11 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, February 28, 2007 8:14 AM
Points: 14, Visits: 1
You say:
"Now you'd think...really...that it would make sense to delete the files first, then do the backup?"

I would say that that would absolutely make no sense at all, and I thank MS on my bare knees (as a manner of speaking :) that they agree with me. It would be very bad to delete the previous backup unless you were 100% sure that the new backup was OK (that is: written to disk and preferably verified too). Otherwise if the backup failed it would be possible to end up without a valid backup since the older one was already deleted.

I think that if you choose to keep 2 old backups, you should know that you are guaranteed to have those, even if the last backup failed for some reason. In your scenario, if a backup failed, the older one would already have been deleted. Backups are just to important to take such gambles with!



Post #34935
Posted Monday, June 10, 2002 4:34 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Monday, November 17, 2014 2:20 PM
Points: 6,800, Visits: 1,914
I sorta see your point, but ultimately what you dont have is a current backup, which to me is a far greater problem!

Andy
http://www.sqlservercentral.com/columnists/awarren/




Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #34936
Posted Monday, June 10, 2002 6:44 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 3:07 PM
Points: 2,049, Visits: 3,592
Have to agree with Andy on this one. Rather loose two days ago backup and try to get a good current one.

Anyway, thanks for finding this out Andy! Good to know.



David


David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #34937
Posted Tuesday, September 7, 2004 8:14 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, February 23, 2006 12:48 PM
Points: 4, Visits: 1

Hi Andy,

 

I have been having a problem with the maintenance plan where it does not remove transaction logs older than the specified number of days set in the properties.  In one plan, i have 5 databases manually selected and i have enabled the transaction log backup once a week and the plan is supposed to remove the .trn files older than a week.  However, only 2 databases are showing .trn files and those .trn files are never deleted, and just keep adding up week by week.  Other plans are working fine.  Do you have any idea what could be causing this?  Do i need to limit one plan per db when backing up the transaction log?

 

thanks,

Guy




Post #135638
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse