Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
richard102
Starting Member
25 Posts |
 Posted - 2011-10-09 : 16:58:15
|
| I'm a little obsessed with keeping backups simple/robust (for ease of restoration) and am scratching-my-head with this new customer.They want to start backing-up to a NAS where the "date modified" setting says 2002!! Assuming I cannot get the 3rd party to correct the date on the NAS, I need to find a way to implement a classic weekly-full, daily-diff, hourly-tran backup strategy.Using the GUI off-course ALL backups are 'cleaned up' being out-of-date.Experimentation shows that if I backup locally then copy across to the NAS the date's stay correct (2011). But that's just too complicated for me (and btw local backups frequently ran out of space I hear).Driven by the urgent need to have 'some backups' occurring, I quickly bashed-out appropriate sql-jobs.Now ... :) ... I just need some second-job-steps to remove old trn's and bak's?btw a complete set of full backups is about 120GB, and the NAS is 1TB I hear.thanksrichard102 |
|
|
chris_cs
Posting Yak Master
223 Posts |
Posted - 2011-10-10 : 05:49:56
|
| There is a maintenance plan that removes old files which could be used.Alternatively, you could create a batch file or VBScript and execute this as a step to remove files older than a certain date.Junior DBA learning the ropes |
 |
|
|
lappin
Posting Yak Master
182 Posts |
Posted - 2011-10-10 : 10:28:39
|
| File System Object in VBScript as chris suggests can move files depending on date. Do a Google for: fso sql server copy backups |
|
|
|
|
|
|
backups to NAS with wrong dates