Back up is not backing up until I tell it to...

[ToniL]

Veritas BackUp Exec is supposed to backup my exchange server, which is about 17 GB of info. It's on a schedule, but then when I check the backups the following day, it has only backed up about 2-3 MB of info, but it says 100% finished. When I go check the backup log, it says that it cannot open the *.bkf file. I then went to check if it's a valid file, and it is. Then I right click the exchange entry and tell it to run now... it does in it's entirety. Why won't it backup fully when it's scheduled to, but backup fully when it's told to?

 

[packdragon]

Does the account it uses when running as a service have the same privileges as the account you use when you tell it to run the backup?

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[justin2000]

Maybe the bkf is open when you are trying to back it up during the scheduled job?

 

[ToniL]

Everything is OK, the >bkf file is not open, I checked to see if the spelling is right, and that it's trying to get the right file from the right box... That isn't the problem, though... It's doing the backup, but only a teeny tiny bit of it, then it stops, and when I physically click it and tell it to backup, it does--completely. The problem is why won't it backup on schedule, but when I tell it to, it does? I verified the schedule and checked everything out, but it still does the same thing. >:-<

 

[ToniL]

I forgot to mention that I am using BEX 8.60... I know it's old, but it was here when I got here, and I don't think my boss has any plans to change it. Are there any known problems with this version? This seems like a strange problem. It's just weird that the scheduled backup pukes and the others don't; but when I TELL it to do the backup, it goes off without a hitch.

 

[SQLBill]

Have you checked:

1. The Backup Exec Alert messages?
2. The Backup Exec Job History?
3. The Windows Event Viewer Logs (application and system)

There might be messages in one or more of those that can 'shed light' on your issue.

Have you tried to change the time the job runs at? That will show you if it's time-specific. Then it might be a network/system job running that interferes.

-SQLBill

 

[ToniL]

I have looked at the job log even though it says it's 100% complete, 2 or 3 MB it not even close to what that backup is supposed to look like. When I do look at the job log, it tells me that it couldn't open the *.bkf file, so it skips it. But it has no problem opening it when I run the backup manually. There are no errors in the event viewer, either. I'm gonna take your advice, though, and change the time that the backup runs, but why would it have a problem opening the file when it's on it's own, but when I'm there forcing it to backup, it does? Does this thing need to be baby-sat?

 

[SQLBill]

What is the .bkf file?
Is it being used at the time that BE tries to back it up?
Are you using the AOFO/OFO?

To me, this appears to be an issue of timing. When the job is scheduled, something is happening with the .bkf file (being used). When you manually run the job, it's at a time when the .bkf file is closed (not being used).

The only way to confirm this, is to change the time the job runs at. If you resked it for the time that you manually run it and it works...then it's an issue with the time the job is running. Then you can track down what is being done with that file at that time.

-SQLBill

 

[ToniL]

The .bkf file is the backup file. BEX is supposed to get the file from the Exchange server, and back it up to tape. And I scheduled the backup for 7:00 pm because the office is closed and there's no one here to use the file. When I run the backup manually, there is an office full of people here that can possibly be using the file. That's why I don't understand this. Besides that, the file backs up 2-3 MB of info... WHAT exactly is it backing up, and WHY is it not backing up everything else? I will change the time of the backup, and see if that changes things... I will keep you posted, in the meantime, I welcome any more suggestions fro you all.

 

[SQLBill]

Since it's a downtime for the office, does anyone else have a scheduled maintenance job running at that time? Are you the only one who does backups? Could someone else be backing up the OS?

Just some questions to consider.

-SQLBill

 

[justin2000]

the bkf file is open when you are trying to back it up - by the job telling you it cannot open the file and it has skipped it, this is what it means.
I would say the exchange backup is still running creating the bkf, which is why BE can't back it up properly.

AOFO will not do anything for you here, as you will need the backup of exchange to complete totally before taking the backup of the bkf.

 

[ToniL]

So, Justin, I should schedule the backup for an even later time than 7:00, to insure that Exchange is done making the file??? I will try that, too, but the problem is that by itself, it won't perform the backup in its entirety, but when I tell it to, it does. Yesterday, I scheduled an Exch. backup for 5:30; 30 minutes before I left the office... I went back 20 minutes later to check the backup, and it was 100% successful, in 3 minutes with 2 1/2MB backed up. That is NOT right. So then I manually ran the backup, and presto!!! This morning I come in to a 17 gig backup just like it's supposed to be... AAAAAARRRGGGGGGGGHHHHHHHHHHH!!!!! I am tearing my hair out here...

 

[SQLBill]

What time did you manually run the job? Schedule the job to run at that time and see what happens. If it fails, then it's not a time issue. If it suceeds then it is a time issue.

Or try to run it manually at 5:30. See what happens. If it runs then you know it's something with the scheduling/job and not with the time the job happens.

-SQLBill

 

[ToniL]

I manually ran the job about 5:50; 10 minutes before I left the office... I will set it to run at 5:50 tonight and see if it runs right, if it doesn't, then what??? I've tried everything I can think of short of taking it out to dinner to get this thing to work. I don't know what the next step is, but I'm kinda leaning toward a sledge hammer...

 

[SQLBill]

First lets see if it worked when you changed the time of the job.

-SQLBill

 

[ToniL]

WOO HOO... IT WORKED!!! Thank you all for your help... It was a time issue, I thought that if 2 things were scheduled at once, the other would just go in the que until the first one finished... The backup ran at 11:30 am in its entirety all weekend, but the true test is giving it its present home at 7:30 pm and see if it runs then...