Daily backups don't catch all files

[joe33067]

I have a job setup to backup all files created or changed for the current day (backup exec type 'Daily'). I have the job set to kick off at 11:59pm. The job will backup some of the files on the server, but not all. I have tried to identify - does 'Daily' look at files for the past 24 hours? If not, what is its parameter for identifying files created or changed today. I'm think about setting the start time to something like 7pm but incase that doesn't work, I'd like to have some other options. I'm using BE 8.6 3878.

 

[SQLBill]

According to Veritas' Backup Exec 8.6 Administrator's Guide:
Italics are from the document.

The Daily Backup Method backs up all files with today's date (created or changed today).

It doesn't say anything about the last 24 hours. It's just those files created or changed today (probably based on the system clock). So, if you ran it at 1 AM, you would be backing up very few files.

-SQLBill

 

[joe33067]

That makes sense, if the job were to enter a running state @ 1am. But since I have the job scheduled to kick off at 11:59pm, I would imagine that would be the controlling date (since 11:59 does come before midnight, when the system clock changes). It wouldn't make sense that if a job cross the midnight time frame, the date comparison routine fails. But you know, I've got an idea - I'm going to have 2 jobs run - one at 7pm, and one at 11:30pm - and compare there results...

 

[wtrdog]

If you are running this everyday, why not run an incremental backup. This should take care of getting all of the files that changed since the previous backup.

 

[joe33067]

In a nut shell, here's the strategy. We have a server that has approximately 400 gig of storage. It requires approximately 7-8 DLT IV tapes to back it up. We run a monthly FULL archive, and we run differentials during the month. Each day the tapes are sent offsite, so to facilitate user restore requests, I setup DAILY backups to an online disk folder, so we wouldn't need to wait for the tape to come back onsite. We can use incrementals, because that would screw up the differentials we run on a Su-Sa.

 

[joe33067]

I mean we CAN'T use differentials....

 

[SQLBill]

Check when the job ACTUALLY runs. Just because it's scheduled for 11:59PM doesn't mean it ran at that time. Remember, other things are going on. The drive needs to advance to the proper spot on the tape (and if you have an autoloader/library then first the tape needs to be loaded). Then BE needs to find the files, THEN it begins the backup. So your actual job may not start comparing the system time until AFTER 11:59PM.

So, in short, BE first has to load the tape, then prepare it, then find the files, THEN begin the backup.

-SQLBill

 

[joe33067]

SQLBill - I think you hit it. I checked the job job, and here is the extract (from the 11:30 job)


Media Name: "Media created 9/29/2003 11:30:13 PM"
Backup of "C: "
Backup set #1 on storage media #1
Backup set description: "DRFSFILP3_Daily"
Backup Type: DAILY - Files that Changed Today
Backup started on 9/30/2003 at 12:23:26 AM.

And here is the job I have set to run @ 7pm:

Media Name: "Media created 9/29/2003 07:00:06 PM"
Backup of "C: "
Backup set #1 on storage media #1
Backup set description: "DRFSFILP3_Daily"
Backup Type: DAILY - Files that Changed Today
Backup started on 9/29/2003 at 7:40:00 PM.

It appears that the prescan time was killing the comparison routing. I bet it I have the job scheduled to run @ 10pm, I'd probably be safe.

 

[SQLBill]

Yes, that's the way it looks to me. Give 10PM a try. I'm glad I got you pointed in the right direction.

-SQLBill