Video Screencast Help

How to backup newly created files in specific folder

Created: 19 Dec 2012 • Updated: 19 Dec 2012 | 12 comments
b1gg1e's picture

Dear ALL!

A have such problem. I backup our DB in /opt/backup folder every 3 hours. The names on backup files are, for example, backup_%CURRENT_DATE_TIME%.bck.

So in my backup job I want to backup only new backups. In Include/Exclude options I can select Only modified files, Files dated etc, but no New files option.

I want to notice that we have to use only Full backup method.

Thanks in advance.

Comments 12 CommentsJump to latest comment

Kiran Bandi's picture

What if you select modified files? I think it should backup the new file. I presume that the other files in the directory will never be modifed after creation.

b1gg1e's picture

I tryed.

A thought that it will be my solution. But it doesn't backup new files..

Kiran Bandi's picture

Then i do not see any other way to backup only newly created files with backup method as FULL. You would need to change the selections manually everytime to point new file (OR) change the script to overwrite the old file, so that only one file will be available in the directory. Might not be the preferred way. 

Runnning one full followed by all incrementals is a simple solution, but not in your case with only full limitation.

b1gg1e's picture

It's really bad.

In case of incrementals I will need to keep my FULL backup for several years and the time of restore will increase in geometric progression...

Or recreate the job manually at least once a year. 

Kiran Bandi's picture

You are taking backup of BACKUP files. So, in case of a restore, i believe you would need to restore only the recent backup file (which will be part of your recent incremental), but not the complete folder. Am i correct?

If so, you no need to bother about retaining full backup and restoring first full then all incrementals in order, in this case. You would be needing full backup as backup software will not let you take incrementals without a full backup.

b1gg1e's picture

Kiran, thank's for your reply.

So, is it good practice to keep a full backup for a several month and years?

Finally, I will not able to delete previous incrementals..

pkh's picture

Where is this /opt/backup directory?  Does that location have either a RAWS or RALUS installed?

In BE 2012, if you are using disk storage, you would cannot delete backup sets that have dependencies, so you cannot delete prior incremental backups and keep the latest incremental backup.

b1gg1e's picture

It's a Linux RH 6.3 server's with RALUS installed.

I understand that I can't delete prior incrementals.. But I don't see any other way to perform my backup strategy, and what about you?

pkh's picture

RHEL 6.3 is not supported, meaning that it has not been tested.  See the SCL below

BE 2012 SCL

This could be why your incrementals do not work.

b1gg1e's picture

I saw it. Only what not work's for me is Advanced Open File Option (symsnap driver didn't installed during installation of RALUS). But I do not need this option at all. I need to backup files that don't use by other applications during my backup job's.

Incrementals works good - already tested.

Donald Eady's picture

I'm a little confused as to what you're trying to accomplish. But from what i understand you should be able to incorporate full/incremental backups in your solution. Would running a Full backup 1 day a week and incremental every other day work for you. this would back up only the changes and you would only have to restore the latest full and subsequent incrementals

I hope this posting was helpful


b1gg1e's picture

Donald, I want you to understand that the size and number of backup files (what we make with native DB backup operation) will increase. The size of disk in my Linux is 20 Tb. And I have 20Tb on disk and 30 Tb of tapes for backup.

With native DB backup operation I make full backup of DB every week, every one day - cumulative, every 3 hours - incremental. All to /opt/backup folder.

And all of that I have to duplicate with Backup Exec. (keep for 2 week's on disk storage and 2 year's - on tapes).

So if in future I will have for example 4 TB size of my production database, how can I keep all of that?

So, for example, I have in my Linux PC in backup folder files of full backup like this:

Full_01-10-2012.bkp - 1 Gb

Full_08-10-2012.bkp - 2 Gb

Full_15-10-2012.bkp - 3 Gb

Full_22-10-2012.bkp - 4 Gb

Full_29-10-2012.bkp - 5 Gb

...... and so on

Full_10-12-2012.bkp - 10 Gb

Full_17-12-2012.bkp - 12 Gb

On my first full backup job I will backup all this files with file mask - "Full_*.bkp".

Next week I will no need to backup this files, I will need to backup only Full_24-12-2012.bkp. With backup exec I can do it only manually or using incremental backup.. But in future I will need to delete some intermediate backups because of storage size issue.

So in my case, I don't worry about disk storage because the depth of backup is 2 weeks on it. I want to have such backup result on my tapes (data keeps for 2 years):

 Previous week This week Next Week
...... and so on    

But not:

 Previous week This week Next Week
Full_01-10-2012.bkp Full_01-10-2012.bkp Full_01-10-2012.bkp
Full_08-10-2012.bkp Full_08-10-2012.bkp Full_08-10-2012.bkp
Full_15-10-2012.bkp Full_15-10-2012.bkp Full_15-10-2012.bkp
Full_22-10-2012.bkp Full_22-10-2012.bkp Full_22-10-2012.bkp
Full_29-10-2012.bkp Full_29-10-2012.bkp Full_29-10-2012.bkp
...... and so on ...... and so on ...... and so on
Full_10-12-2012.bkp Full_10-12-2012.bkp Full_10-12-2012.bkp
Full_17-12-2012.bkp Full_17-12-2012.bkp Full_17-12-2012.bkp
  Full_24-12-2012.bkp Full_24-12-2012.bkp