Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

A manager – system error occurred (174)

Status
Not open for further replies.

JenniferCheng

Programmer
Aug 10, 2005
34
CA
I met a problem when backup files. I set up policy test to backup /dev directory on backup server. When performing manual backup, got two jobs under Activity Moniter.
Following is information about two jobs:

Job 55, detailed status:
11/28/2005 14:48:13 – started process bpbrm (pid=3182)
11/28/2005 14:48:13 – connecting
11/28/2005 14:48:13 – started process bptm (pid=3185)
11/28/2005 14:48:14 – connected; connect time: 0:00:00
11/28/2005 14:48:14 – mounting 000003
11/28/2005 14:50:12 – mounted 000003; mount time: 0:01:58
11/28/2005 14:50:17 – positioning 000003 to file 3
11/28/2005 14:51:01 – positioned 000003; position time: 0:00:44
11/28/2005 14:51:01 – begin writing
11/28/2005 14:51:02 – end writing; write time: 0:00:01
the requested operation was successfully completed (0)

KB written: 960
Files written: 1527
Percent complete: 100%


Job 56, detailed status:
11/28/2005 14:51:21 – begin DB Backup
11/28/2005 14:51:21 – mounting 000003
11/28/2005 14:51:21 – started process bptm (pid = 3270)
11/28/2005 14:51:21 – Error bptm (pid=3270) media id 000003 is in media manager database, cannot be used for NB database backup or restore
11/28/2005 14:51:21 – Error bpbackupdb (pid=3268) load of media id 000003 failed, media manager – system error occurred
11/28/2005 14:51:21 – end DB Backup, elapsed time 0:00:00
11/28/2005 14:51:21 – Error bpbackupdb (pid=3268) NB database backup to media id 000003 FAILED
A manager – system error occurred (174)

Thanks

Jennifer
 
Job56 is a catalog backup. Catalog backups and regular media backups cannot reside on the same tape. You may wish to revisit how you use your volume pools. Catalog backup tapes must reside in the "NetBackup" pool.

If the tape was a dbbackup tape, you would get a like error from the regular media backup job stating the tape contained netbackup catalog data.
 
Yes, you are right. The tape was in NetBackup pool.
Now I deassigned the media and moved this media to DataStore pool. When backup /bin using policy Test_bin manually, get following error message:

11/29/2005 11:04:17 - started process bpbrm (pid=8503)
11/29/2005 11:04:17 - connecting
11/29/2005 11:04:17 - started process bptm (pid=8506)
11/29/2005 11:04:18 - Error bptm (pid=8506) Media Manager volume pool DataStore has no more unassinged media in tobotic device TL8(0)
11/29/2005 11:04:18 - connected; connect time: 0:00:00
11/29/2005 11:04:19 - Warning bpbrm (pid=8503) from client ermesc:WRN - /bin is only being backed up as a symbolic link
11/29/2005 11:04:19 - Error bpbrm (pid=8503) form client ermesx: ERR - bpbkar exiting because backup is aborting
11/29/2005 11:04:21 - end writting
11/29/2005 11:04:21 - Error bpsched (pid=8478) backup of client ermesx exited with status 96 (unable to allocate new media for backup, storage unit has none available)
11/29/2005 11:04:22 - Error bpsched (pid=8478) backup of client ermesx exited with status 96 (unable to allocate new media for backup, storage unit has none available)
unable to allocate new media for backup, storage unit has none available

It is strange that after build a policy and set a schedule. It will never do backup during the scheduled time. So I have to do it manually.

Thanks.

Jennifer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top