Lars Bo Heuser

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-02-02
08:33
210 views
Hi, I have a job which completes with errors.
I'm still a novice with this product and can't find any useful error information in the GUI's log. How can I find out which folders/files fails?
I can see an "administrators command prompt" feature within "Programs - HP Data Protector" that I thought maybe could be useful, but when I fill in administrators password it just closes down. I didn't originally install Data Protector and use the domain admin pw to log in - is that correct?
Secondly, is it possible to make the job ignore these errors or do I have to uncheck folders/files from the job template?
I'm still a novice with this product and can't find any useful error information in the GUI's log. How can I find out which folders/files fails?
I can see an "administrators command prompt" feature within "Programs - HP Data Protector" that I thought maybe could be useful, but when I fill in administrators password it just closes down. I didn't originally install Data Protector and use the domain admin pw to log in - is that correct?
Secondly, is it possible to make the job ignore these errors or do I have to uncheck folders/files from the job template?
1 Solution
Accepted Solutions
dbw

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-02-02
14:41
Hi,
to find out what is wrong - You have to see backup report details. There are at least two ways to get backup report:
1. from GUI (connect to Cell Manager and go to "Internal database tab, and next point to "Sessions", find session with problems, right click on "properties. In "General" tab check "Reporting level" (if there is "Critical, you only see critical mesaages - so better choose "Normal"). Next go to "Message Tab" and find what was wrong during backup.
2. from commnad line:
#omnistat -previous
(write down backup session number, this with "failures")
#omnidb -ses -rep
to find out what is wrong - You have to see backup report details. There are at least two ways to get backup report:
1. from GUI (connect to Cell Manager and go to "Internal database tab, and next point to "Sessions", find session with problems, right click on "properties. In "General" tab check "Reporting level" (if there is "Critical, you only see critical mesaages - so better choose "Normal"). Next go to "Message Tab" and find what was wrong during backup.
2. from commnad line:
#omnistat -previous
(write down backup session number, this with "failures")
#omnidb -ses
3 Replies
dbw

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-02-02
14:41
Hi,
to find out what is wrong - You have to see backup report details. There are at least two ways to get backup report:
1. from GUI (connect to Cell Manager and go to "Internal database tab, and next point to "Sessions", find session with problems, right click on "properties. In "General" tab check "Reporting level" (if there is "Critical, you only see critical mesaages - so better choose "Normal"). Next go to "Message Tab" and find what was wrong during backup.
2. from commnad line:
#omnistat -previous
(write down backup session number, this with "failures")
#omnidb -ses -rep
to find out what is wrong - You have to see backup report details. There are at least two ways to get backup report:
1. from GUI (connect to Cell Manager and go to "Internal database tab, and next point to "Sessions", find session with problems, right click on "properties. In "General" tab check "Reporting level" (if there is "Critical, you only see critical mesaages - so better choose "Normal"). Next go to "Message Tab" and find what was wrong during backup.
2. from commnad line:
#omnistat -previous
(write down backup session number, this with "failures")
#omnidb -ses
Lars Bo Heuser

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-02-03
08:50
Hi,
Thank you very much for your quick reply.
I managed to find out, that the problem was minor and related to "not enough diskspace" on my server. I extended the volume and expect the problem to be solved.
Thx and enjoy your well-deserved points! 🙂
Thank you very much for your quick reply.
I managed to find out, that the problem was minor and related to "not enough diskspace" on my server. I extended the volume and expect the problem to be solved.
Thx and enjoy your well-deserved points! 🙂
Lars Bo Heuser

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-02-03
09:34
The solution can be found in the thread