[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Veritus BackupExec 9.1 -- backup 99% complete

I have Veritus BackupExec 9.1.

Whenever a backup completes successfully, the tape auto-ejects but the
job monitor continues displaying,  "99% complete"

I either have to cancel the backup or stop/start the BackupExecJobEngine service

Not a good prelude for when I want to schedule backup jobs

Any idea what’s happening?

0
Marketing_Insists
Asked:
Marketing_Insists
  • 4
  • 3
  • 2
1 Solution
 
rindiCommented:
Can you provide more info, like parts of the job log?
0
 
Marketing_InsistsAuthor Commented:

The Job History panel on the Job Monitor tab shows that the job has been canceled (where it shows how the last few backups ended: successful, failed, canceled), but the backup logs have no errors or hint of being canceled or of any trouble.
0
 
rindiCommented:
if you doubleclick that cancelled job in the job history you should get some more detail. Is that possible?
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.

 
Marketing_InsistsAuthor Commented:
this is the backup log: (kind of long)
In this most recent instance, I couldn't cancel the job and had to start/stop the BackupExec Service to get the console back.
It's satus is failed:

<--------------------- start ---------------------->

Job Operation - Backup

======================================================================
Job server: URSAMINOR
Job name: Backup 0001
Job started: Thursday, November 18, 2004 at 9:04:05 AM
Job type: Backup
Job Log: BEX00109.xml
======================================================================

Drive and media information from media mount:
Drive Name: COMPAQ 1
Media Label: DLT000003
Media GUID: {DAB1B7E0-BF1A-4D7A-8DFD-523495BBA213}
Overwrite Protected Until: 12/31/9999 12:00:00 AM
Appendable Until: 12/31/9999 12:00:00 AM
Targeted Media Set Name: Media Set 1
======================================================================
Media operation - append.
Hardware compression enabled.
======================================================================
\\URSAMINOROFO: Started for device: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
C: SYSAPP
Family Name: "Media created 9/20/2004 10:00:03 PM"
Backup of "C: SYSAPP"
Backup set #7 on storage media #1
Backup set description: "Backup 0001"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 11/18/2004 at 9:05:58 AM.
The .DR file required for Intelligent Disaster Recovery is created/updated.
Backup completed on 11/18/2004 at 9:11:37 AM.
Backed up 18652 files in 1550 directories.
Processed 2,754,052,985 bytes in  5 minutes and  39 seconds.
Throughput rate: 465 MB/min
----------------------------------------------------------------------
D: DATA
Family Name: "Media created 9/20/2004 10:00:03 PM"
Backup of "D: DATA"
Backup set #8 on storage media #1
Backup set description: "Backup 0001"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 11/18/2004 at 9:11:38 AM.
The .DR file required for Intelligent Disaster Recovery is created/updated.
Backup completed on 11/18/2004 at 9:23:34 AM.
Backed up 7695 files in 614 directories.
Processed 15,575,068,775 bytes in  11 minutes and  56 seconds.
Throughput rate: 1245 MB/min
----------------------------------------------------------------------
E: SWAP
Family Name: "Media created 9/20/2004 10:00:03 PM"
Backup of "E: SWAP"
Backup set #9 on storage media #1
Backup set description: "Backup 0001"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 11/18/2004 at 9:23:35 AM.
The .DR file required for Intelligent Disaster Recovery is created/updated.
Backup completed on 11/18/2004 at 9:23:45 AM.
Backed up 5 files in 5 directories.
Processed 26,450 bytes in  10 seconds.
Throughput rate: 0.151 MB/min
----------------------------------------------------------------------
URSAMINOR|D:
Family Name: "Media created 9/20/2004 10:00:03 PM"
Backup of "URSAMINOR|D: "
Backup set #10 on storage media #1
Backup set description: "Backup 0001"
Backup Type: FULL - Back up Database & Logs - Reset Archive Bit
Lotus Domino Agent: Started
Backup started on 11/18/2004 at 9:24:07 AM.
Backup completed on 11/18/2004 at 9:46:18 AM.
Backed up 470 files in 27 directories.
Processed 29,176,475,411 bytes in  22 minutes and  11 seconds.
Throughput rate: 1254 MB/min
----------------------------------------------------------------------
F: LOG
Family Name: "Media created 9/20/2004 10:00:03 PM"
Backup of "F: LOG"
Backup set #11 on storage media #1
Backup set description: "Backup 0001"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 11/18/2004 at 9:46:20 AM.
The .DR file required for Intelligent Disaster Recovery is created/updated.
Backup completed on 11/18/2004 at 9:48:30 AM.
Backed up 43 files in 6 directories.
Processed 2,483,151,586 bytes in  2 minutes and  10 seconds.
Throughput rate: 1093 MB/min
----------------------------------------------------------------------
Shadow?Copy?Components Shadow?Copy?Components
Family Name: "Media created 9/20/2004 10:00:03 PM"
Backup of "Shadow?Copy?Components Shadow?Copy?Components"
Backup set #12 on storage media #1
Backup set description: "Backup 0001"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 11/18/2004 at 9:48:31 AM.
The .DR file required for Intelligent Disaster Recovery is created/updated.
Backup completed on 11/18/2004 at 9:51:44 AM.
Backed up 5 Shadow Copy Writer(s)
Backed up 5 Shadow Copy Component(s)
Processed 1,108,259,698 bytes in  3 minutes and  13 seconds.
Throughput rate: 329 MB/min
----------------------------------------------------------------------
======================================================================
======================================================================
C: SYSAPP
Verify of "C: SYSAPP"
Backup set #7 on storage media #1
Backup set description: "Backup 0001"
Verify started on 11/18/2004 at 9:53:47 AM.
Verify completed on 11/18/2004 at 9:55:36 AM.
Verified 18652 files in 1550 directories.
0 files were different.
Processed 2,754,052,985 bytes in  1 minute and  49 seconds.
Throughput rate: 1446 MB/min
----------------------------------------------------------------------
D: DATA
Verify of "D: DATA"
Backup set #8 on storage media #1
Backup set description: "Backup 0001"
Verify started on 11/18/2004 at 9:55:37 AM.
Verify completed on 11/18/2004 at 10:06:05 AM.
Verified 7695 files in 614 directories.
0 files were different.
Processed 15,575,068,775 bytes in  10 minutes and  28 seconds.
Throughput rate: 1419 MB/min
----------------------------------------------------------------------
E: SWAP
Verify of "E: SWAP"
Backup set #9 on storage media #1
Backup set description: "Backup 0001"
Verify started on 11/18/2004 at 10:06:05 AM.
Verify completed on 11/18/2004 at 10:06:05 AM.
Verified 5 files in 5 directories.
0 files were different.
Processed 26,450 bytes in  1 second.
Throughput rate: 1.51 MB/min
----------------------------------------------------------------------
URSAMINOR|D:
Verify of "URSAMINOR|D: "
Backup set #10 on storage media #1
Backup set description: "Backup 0001"
Verify started on 11/18/2004 at 10:06:05 AM.
Verify completed on 11/18/2004 at 10:26:37 AM.
Verified 470 files in 27 directories.
0 files were different.
Processed 29,176,475,411 bytes in  20 minutes and  32 seconds.
Throughput rate: 1355 MB/min
----------------------------------------------------------------------
F: LOG
Verify of "F: LOG"
Backup set #11 on storage media #1
Backup set description: "Backup 0001"
Verify started on 11/18/2004 at 10:26:37 AM.
Verify completed on 11/18/2004 at 10:28:31 AM.
Verified 43 files in 6 directories.
0 files were different.
Processed 2,483,151,586 bytes in  1 minute and  54 seconds.
Throughput rate: 1246 MB/min
----------------------------------------------------------------------
Shadow?Copy?Components Shadow?Copy?Components
Verify of "Shadow?Copy?Components Shadow?Copy?Components"
Backup set #12 on storage media #1
Backup set description: "Backup 0001"
Verify started on 11/18/2004 at 10:28:31 AM.
Verify completed on 11/18/2004 at 10:29:09 AM.
Verified 5 Shadow Copy Writer(s)
Verified 5 Shadow Copy Component(s)
0 files were different.
Processed 1,108,259,698 bytes in  38 seconds.
Throughput rate: 1669 MB/min
----------------------------------------------------------------------
0
 
LucFCommented:
Hi Marketing_Insists,

I had this problem some time ago and it's a very common problem with veritas. You'll see that you have alerts to respond to. Only when you respond "OK" to the eject of the tape the backup will finish to 100%.

You can let BE automatically respond to alerts as explained at:

How to configure VERITAS Backup Exec (tm) to automatically respond to media alerts, including when a backup hangs at 99%, until the user responds to a tape eject prompt
http://seer.support.veritas.com/docs/192055.htm

Greetings,

LucF
0
 
rindiCommented:
Well, it looks like the backup itself worked well. Is there any post-backup Command running which might not work correctly? Where is Veritas info going to (log files, Catalog, Database etc)? Make sure there is enough empty space left available on that destination partition to accomodate for those files. If possible I'd move them to a data area (by default such data is stored in the Program Files\Veritas...... directory. Turn off verification, it just increases the time used and can give you more output with more error messages than needed (if your backing up data that gets changed during the backup, a verify will not spit out error messages which aren't error messages).

Apply all windowsupdates that haven't been applied yet. Also download the newest backupexec patches and updates and install them.

If there is anything strange in your Window eventvwr can you please give us a reading of that?

Thx.
0
 
Marketing_InsistsAuthor Commented:
LucF,
I have alerts turned off, so no sneaky pop-ups hiding behind the console.
Also, "Eject Media After Job Completes" is unchecked, but it still ejects anyway (stupid Hewlet Packard SDLT 320 issue)
 -Often, when media like this ejects, pushing the tape back in will allow the job to finish.  But not this time.  It's not even 25% full so it dosn't need a extra tape.

rindi
no post-backup commands.
It uses SQL database client to store info, I'll mung around for it.
As far as app logs, nothing other than me manually canceling or terminating a backup related service.
I'll turn of verification and see what happenz, and look into the patches,

One weird thing that happens is that if I cancel a backup job or stop/start the backup service, then resume the backup, the Domino e-mail service on the same server will crash!  On closer inspection, this appears to occur before the actual backup begins, rather it happens after the data to be backed up has been cataloged ( within about 40 min of starting the job )

I have another thread on that @ http://www.experts-exchange.com/Applications/Email/Lotus_Notes_Domino/Q_21209096.html

g'night for now
0
 
rindiCommented:
Did you backup domino in the job as well (I didn't see any refernce to domino in the backup log)? Otherwise I can't imagine Domino having anything directly to do with it. I think best option would be to get those veritas patches.

Do you have an Idea of the system load when the above things happen? Is this domino Server mainly used to for mail transfer or does it also host the users mailbox? Does it host many domino files? How many users? How much Ram is present in the server? What OS does it run? do you reboot the server regularly?
0
 
LucFCommented:
>>I have alerts turned off, so no sneaky pop-ups hiding behind the console.<<
Those are not the kind of alerts meant by this :)

Please try it:

To configure the automated response, follow the steps given below:
1. Browse to \Program files\Veritas\Backup Exec\NT
2. Run BEUtility.exe
3. Add the media server from File | New | New Media Server
4. In BEUtility, select the media server, and from the left pane, click Edit configuration and set the response for the alerts
5. Open the Backup Exec interface. Click Alerts  | Configure alert categories
6. Within the Alert Categories dialog window, select the alert category, and then within the Automatically clear alert after option, specify the time interval

Good luck,

LucF
0

Featured Post

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.

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now