Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2659
  • Last Modified:

Backup Exec 10d: How to configure the append / overwrite periods

We are using the Open File option to run backups on our database.  The day starts off by doing a complete backup at 6am.  then from 7am until midnight, we run an incremental backup every 30 minyutes.  So, there are two backup jobs ran per day.

A days worth of backups takes up about 1.5GB.   I want to set the backups to remain on disk for 48 hours.  Thus, Wednesday's backup will be overwriting Monday's, Thursday will overwrite Tuesday, and so on.

I've read the manual, but still somewhat confused.  Advice is appreciated.
0
fuze44
Asked:
fuze44
  • 6
  • 5
  • 2
  • +1
1 Solution
 
shankshankCommented:
For overwriting backup media, you would create a media set, and then you can set the overwrite and append media protection. This way, anything that is associated with that particular media set, will have those policies in place. You would ahve to update your job to use that media then also.
0
 
fuze44Author Commented:
There are overwrite/append options under both the media set properties and the job properties. Do you know how one overrides the other?
0
 
shankshankCommented:
Under the job if you specify it there, I believe it will attemp to do so, but the media set has the underlying decision whether if it is overwritable/appendable or not
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
fuze44Author Commented:
So, from what i've described, would you agree that I need to set by Append period to infinite and the overwrite period to 47  hours?
0
 
shankshankCommented:
You can do that, but you would want to make sure in the job you specifiy to overwrite, so that on tues it will try and fail and then append, but then wed it will overwrite
0
 
shankshankCommented:
I have a similiar setup, but you would want to this it completely since from experience I had to make a few minor tweaks.

I had a rotation that did every on week, mon -t hur, overwritable 13 days and appendable I believe was set at either 8 hours or infinite
0
 
fuze44Author Commented:
There are two options in the job for overwriting:  "Overwrite media" or "Append to media, overwrite if no appendable media is available."   Which one are you referring to?

Thanks
0
 
shankshankCommented:
That depends.

Apend to media, terminate job if no appendable media is available.
If you do this, then let's say that you forget to switch the tape, then the job won't even run.

Append to media, overwrite if no appendable media is available.
This is how my current jobs are setup. If I have my Mon tape in and don't take it out, then Tues job will prompt me to insert the correct media. I also did EJECT MEDIA after job complete, so that no accidents happen.

I think if you do the overwrite, it won't override what you actually set in the media set properties.

0
 
rindiCommented:
Just a warning, you say you are backing up a database with the open file agent. For databases that often isn't the optimal backup method, and for most server databases you can get an agent specificaly for it. What database are you backing up?
0
 
fuze44Author Commented:
We use a Visual Foxpro DB.    Since there's no agent for it, we went with the open file option.   Please let me know if you have a better option!

Thanks
0
 
rindiCommented:
Stop the database for the backup duration, use tools in foxpro which allows you to export the data to text files and back those up, or use a server database engine like sql to which as far as I know foxpro should be compatible to.
0
 
David_FongCommented:
I think you should be using Continuous Data Protection that came with 10d rather than all those incrementals.

Apart from that If you do want to to stick to using backup I would set the daily backup to have a 6 hour append period and a 40 hour overwrite protect and the incremental with a 20 hour append period and 26 hour overwrite protect. Note both add up to 46 hours rather than 48 from the file/tape being initially written but that allows a couple of hours for the actual backup to complete. You could tweak it a bit closer to exactly 48 hours but you would have to do very exact timings to get closer to optimum.
0
 
fuze44Author Commented:
Rindi, unfortunately, neither of those options are practical.  We have multiple users working in the DB throughout the day and can't shut down the DB every 30 minutes to back it up.  While we may convert to a SQL backend in the future, that would be a major ordeal at this time.   I've tested Visual Fox Pro with the Open File option and it seems to work fine.

David, from what I've read about Continuous Data Protection, it either works as an alternative or in conjunction with Windows Server 2003's Shadow Copy feature.  That's primarily for end users to recover data without bothering IT to do it.  That's not really what we're after here.  We just want a way to lose as little data as possible in case of a server crash.  If the server were to go down during the day, the most that should be lost is the work that was done in the past 30 minutes.

Please correct me if I misunderstand.

Much appreciated.
0
 
David_FongCommented:
It is able to provide the users with snapshots of previous versions but if you don't use that feature then it just keeps track of any changes on your open files so you can do a point-in-time restore manually if I understand right. But of course it is not clever enough to understand what the application stores in RAM any more than a traditional backup with an open file agent can.
0
 
fuze44Author Commented:
Thanks, all.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 6
  • 5
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now