6.0 MP2 = NOTHING BUT PROBLEMS

Windows Server 2003 on 6.0MP2

The only reason I installed MP2 was because a support tech said that it
would "probably" fix a minor problem I was having, unfortunately it not only
didn't fix the problem but caused more serious problems. These are some of
the problems I am experiencing:

*Get errors that media is in use when trying to do restores (gave me a
workaround using nbrbutil)
*When trying to duplicate images it queues up but never starts (same
workaround, nbrbutil)
*Policies and clients are being skipped without giving any errors or
even attempting to try and backup (haven't heard back yet on a fix for
this)
*Catalog backups quit woking. Scheduled to start after each session of
scheduled or manual backups, will work the way its supposed to for
a few days and then stop, upon restarting the services (bpdown/bpup) it will
start woking again??? (also waiting to hear back on this)

Prior to installing MP2 I had non of these problems! Now I'm constantly
having to monitor all my backups (catalog included) for fear that they won't
kick-off. I'm hoping that MP3 will fix these problems and not cause others!
MF

I got the same issue : *Policies and clients are being skipped without giving
any errors or
even attempting to try and backup (haven't heard back yet on a fix
for
this)
that make me crasy ...how can you sleep...we never know if backup will run
or run..I still waiting an enginneer the call me back about this..

"MikeF" <mferlin@flyingj.com> wrote:[color=blue]
>Windows Server 2003 on 6.0MP2
>
>The only reason I installed MP2 was because a support tech said that it[/color]
[color=blue]
>would "probably" fix a minor problem I was having, unfortunately it not[/color]
only[color=blue]
>didn't fix the problem but caused more serious problems. These are some[/color]
of[color=blue]
>the problems I am experiencing:
>
> *Get errors that media is in use when trying to do restores (gave me[/color]
a[color=blue]
>workaround using nbrbutil)
> *When trying to duplicate images it queues up but never starts (same[/color]
[color=blue]
>workaround, nbrbutil)
> *Policies and clients are being skipped without giving any errors or[/color]
[color=blue]
>even attempting to try and backup (haven't heard back yet on a fix[/color]
for[color=blue]
>this)
> *Catalog backups quit woking. Scheduled to start after each session[/color]
of[color=blue]
>scheduled or manual backups, will work the way its supposed to[/color]
for[color=blue]
>a few days and then stop, upon restarting the services (bpdown/bpup) it[/color]
will[color=blue]
>start woking again??? (also waiting to hear back on this)
>
>Prior to installing MP2 I had non of these problems! Now I'm constantly[/color]
[color=blue]
>having to monitor all my backups (catalog included) for fear that they won't[/color]
[color=blue]
>kick-off. I'm hoping that MP3 will fix these problems and not cause others!
>MF
>
>[/color]

I had the same issues when upgrading from NBup 5.1 to 6.0MP2. Here is the
workaround Veritas gave me for policies that would not run during their scheduled
window.

Here are the steps for the workaround:

1) Stop the Netbackup services on the master server.

2) Remove the pempersist file in the \Netbackup\bin\bpsched.d directory.

3) Start the Netbackup services on the master server.


"MikeF" <mferlin@flyingj.com> wrote:[color=blue]
>Windows Server 2003 on 6.0MP2
>
>The only reason I installed MP2 was because a support tech said that it[/color]
[color=blue]
>would "probably" fix a minor problem I was having, unfortunately it not[/color]
only[color=blue]
>didn't fix the problem but caused more serious problems. These are some[/color]
of[color=blue]
>the problems I am experiencing:
>
> *Get errors that media is in use when trying to do restores (gave me[/color]
a[color=blue]
>workaround using nbrbutil)
> *When trying to duplicate images it queues up but never starts (same[/color]
[color=blue]
>workaround, nbrbutil)
> *Policies and clients are being skipped without giving any errors or[/color]
[color=blue]
>even attempting to try and backup (haven't heard back yet on a fix[/color]
for[color=blue]
>this)
> *Catalog backups quit woking. Scheduled to start after each session[/color]
of[color=blue]
>scheduled or manual backups, will work the way its supposed to[/color]
for[color=blue]
>a few days and then stop, upon restarting the services (bpdown/bpup) it[/color]
will[color=blue]
>start woking again??? (also waiting to hear back on this)
>
>Prior to installing MP2 I had non of these problems! Now I'm constantly[/color]
[color=blue]
>having to monitor all my backups (catalog included) for fear that they won't[/color]
[color=blue]
>kick-off. I'm hoping that MP3 will fix these problems and not cause others!
>MF[/color]

[color=blue]
> *Policies and clients are being skipped without giving any errors or[/color]
[color=blue]
>even attempting to try and backup (haven't heard back yet on a fix[/color]
for[color=blue]
>this)[/color]

This is a known bug in 6.0 MP2 and will be fixed in MP3, so I'm told. Happens
if you are using checkpointed backups. One workaround:

nbpem -terminate
sleep 30
nbpem

I don't see any problem with restarting this, doesn't kill any jobs in progress
or whatever.

I was given a command - I forget it offhand - that showed some jobs as "active"
even though they weren't, so the scheduler never even attempts to run them.
[color=blue]
> *Catalog backups quit woking. Scheduled to start after each session[/color]
of[color=blue]
>scheduled or manual backups, will work the way its supposed to[/color]
for[color=blue]
>a few days and then stop, upon restarting the services (bpdown/bpup) it[/color]
will[color=blue]
>start woking again??? (also waiting to hear back on this)[/color]

Although this isn't the issue, you should look into hot backups if you're
using v6.

Here what veritas send me..i will try that..

Symptoms: Backup jobs fail to start at scheduled times after having issues
with the master server "hanging". Backup jobs can be initiated manually.


Log Files: N/A

The condition is created when the job state in the pempersist file is not
correctly written.
Example: If a job state was written as active, and NetBackup Policy Execution
Manager (nbpem) was unexpectedly or accidentally stopped and restarted, the
job would be listed as active but will never get a job complete. This job
or jobs (if multiple jobs were active at the time of the shutdown) will never
schedule because nbpem thinks they are already active as indicated in the
pempersist file.
The above result can occur when NetBackup is incorrectly shut down with active
jobs.

To prevent this issue, always use the appropriate NetBackup shutdown method,
i.e. either stopping the individual services/daemons or using one of the
stop scripts.
This will prevent possible pempersist file problems with jobs written in
an active state.

Workaround:
If a graceful shutdown and restart did not correct the problem, deletion
of the pempersist file is required.
1. Stop all NetBackup services on the master server and delete the pempersist
file (found in /usr/openv/netbackup/bin/bpsched.d directory on a UNIX/Linux
master server, or in <install_path>\veritas\netbackup\bin\bpsched.d directory
on a Windows master server)

Note: Ensure all NetBackup activity, e.g. backup, restore, duplication, etc
is complete before stopping services.

After installing NetBackup 6.0 MP1, the pempersist file may be located in
the /usr/openv/netbackup/db/jobs directory on a UNIX/Linux master server,
or the <install_path>\veritas\netbackup\db\jobs directory on a Windows master
server.


CaseAuthKey=10B8BBEF

This e-mail message is for the sole use of the intended recipient(s) and
may contain certain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by e-mail and destroy all copies
of the original message. Symantec and the Symantec logo are U.S. registered
trademarks of Symantec Corporation. VERITAS is a trademark of Symantec Corporation.
Other brands and products are trademarks of their respective holders. Copyright
© 2006 Symantec Corporation. All rights reserved.


"Moe" <moe@email.com> wrote:[color=blue]
>
>I had the same issues when upgrading from NBup 5.1 to 6.0MP2. Here is the
>workaround Veritas gave me for policies that would not run during their[/color]
scheduled[color=blue]
>window.
>
>Here are the steps for the workaround:
>
>1) Stop the Netbackup services on the master server.
>
>2) Remove the pempersist file in the \Netbackup\bin\bpsched.d directory.
>
>3) Start the Netbackup services on the master server.
>
>
>"MikeF" <mferlin@flyingj.com> wrote:[color=green]
>>Windows Server 2003 on 6.0MP2
>>
>>The only reason I installed MP2 was because a support tech said that it[/color]
>[color=green]
>>would "probably" fix a minor problem I was having, unfortunately it not[/color]
>only[color=green]
>>didn't fix the problem but caused more serious problems. These are some[/color]
>of[color=green]
>>the problems I am experiencing:
>>
>> *Get errors that media is in use when trying to do restores (gave me[/color]
>a[color=green]
>>workaround using nbrbutil)
>> *When trying to duplicate images it queues up but never starts (same[/color]
>[color=green]
>>workaround, nbrbutil)
>> *Policies and clients are being skipped without giving any errors or[/color]
>[color=green]
>>even attempting to try and backup (haven't heard back yet on a fix[/color]
>for[color=green]
>>this)
>> *Catalog backups quit woking. Scheduled to start after each session[/color]
>of[color=green]
>>scheduled or manual backups, will work the way its supposed to[/color]
>for[color=green]
>>a few days and then stop, upon restarting the services (bpdown/bpup) it[/color]
>will[color=green]
>>start woking again??? (also waiting to hear back on this)
>>
>>Prior to installing MP2 I had non of these problems! Now I'm constantly[/color]
>[color=green]
>>having to monitor all my backups (catalog included) for fear that they[/color][/color]
won't[color=blue]
>[color=green]
>>kick-off. I'm hoping that MP3 will fix these problems and not cause others!
>>MF[/color][/color]

"Mike" <mrobinson@arrayasolutions.com> wrote:[color=blue]
>
>[color=green]
>> *Policies and clients are being skipped without giving any errors or[/color]
>[color=green]
>>even attempting to try and backup (haven't heard back yet on a fix[/color]
>for[color=green]
>>this)[/color]
>
>This is a known bug in 6.0 MP2 and will be fixed in MP3, so I'm told. Happens
>if you are using checkpointed backups. One workaround:
>
>nbpem -terminate
>sleep 30
>nbpem
>
>I don't see any problem with restarting this, doesn't kill any jobs in progress
>or whatever.
>
>I was given a command - I forget it offhand - that showed some jobs as "active"
>even though they weren't, so the scheduler never even attempts to run them.
>[color=green]
>> *Catalog backups quit woking. Scheduled to start after each session[/color]
>of[color=green]
>>scheduled or manual backups, will work the way its supposed to[/color]
>for[color=green]
>>a few days and then stop, upon restarting the services (bpdown/bpup) it[/color]
>will[color=green]
>>start woking again??? (also waiting to hear back on this)[/color]
>
>Although this isn't the issue, you should look into hot backups if you're
>using v6.[/color]

I too am having lots of problems. I am now in the habit of if a job fails
stop and restart netbackup. What a pain. I am experiencing lots of problems
with Vaulting. Anyone else getting tape errors only with vaulting?

You mentioned having problems with vault. What problems are you having?
I too had problems with vault after upgrading to 6.0 MP2.

"Irene Reed" <reed.irene@jobcorps.org> wrote:[color=blue]
>
>
>
>"Mike" <mrobinson@arrayasolutions.com> wrote:[color=green]
>>
>>[color=darkred]
>>> *Policies and clients are being skipped without giving any errors[/color][/color][/color]
or[color=blue][color=green]
>>[color=darkred]
>>>even attempting to try and backup (haven't heard back yet on a fix[/color]
>>for[color=darkred]
>>>this)[/color]
>>
>>This is a known bug in 6.0 MP2 and will be fixed in MP3, so I'm told.[/color][/color]
Happens[color=blue][color=green]
>>if you are using checkpointed backups. One workaround:
>>
>>nbpem -terminate
>>sleep 30
>>nbpem
>>
>>I don't see any problem with restarting this, doesn't kill any jobs in[/color][/color]
progress[color=blue][color=green]
>>or whatever.
>>
>>I was given a command - I forget it offhand - that showed some jobs as[/color][/color]
"active"[color=blue][color=green]
>>even though they weren't, so the scheduler never even attempts to run them.
>>[color=darkred]
>>> *Catalog backups quit woking. Scheduled to start after each session[/color]
>>of[color=darkred]
>>>scheduled or manual backups, will work the way its supposed[/color][/color][/color]
to[color=blue][color=green]
>>for[color=darkred]
>>>a few days and then stop, upon restarting the services (bpdown/bpup) it[/color]
>>will[color=darkred]
>>>start woking again??? (also waiting to hear back on this)[/color]
>>
>>Although this isn't the issue, you should look into hot backups if you're
>>using v6.[/color]
>
>I too am having lots of problems. I am now in the habit of if a job fails
>stop and restart netbackup. What a pain. I am experiencing lots of problems
>with Vaulting. Anyone else getting tape errors only with vaulting?[/color]

You may be interested in this article which resolves issues with jobs not
starting with no errors:

[url]http://seer.support.veritas.com/docs/281780.htm[/url]

Basically you have to stop all services on the master, delete the pempersist
file and restart all services...we now make this a nightly task! MP3 is
meant to solve this but I have no test results as yet....

"Moe" <moe@email.com> wrote:[color=blue]
>
>You mentioned having problems with vault. What problems are you having?[/color]
[color=blue]
>I too had problems with vault after upgrading to 6.0 MP2.
>
>"Irene Reed" <reed.irene@jobcorps.org> wrote:[color=green]
>>
>>
>>
>>"Mike" <mrobinson@arrayasolutions.com> wrote:[color=darkred]
>>>
>>>
>>>> *Policies and clients are being skipped without giving any errors[/color][/color]
>or[color=green][color=darkred]
>>>
>>>>even attempting to try and backup (haven't heard back yet on a[/color][/color][/color]
fix[color=blue][color=green][color=darkred]
>>>for
>>>>this)
>>>
>>>This is a known bug in 6.0 MP2 and will be fixed in MP3, so I'm told.[/color][/color][/color]
[color=blue]
>Happens[color=green][color=darkred]
>>>if you are using checkpointed backups. One workaround:
>>>
>>>nbpem -terminate
>>>sleep 30
>>>nbpem
>>>
>>>I don't see any problem with restarting this, doesn't kill any jobs in[/color][/color]
>progress[color=green][color=darkred]
>>>or whatever.
>>>
>>>I was given a command - I forget it offhand - that showed some jobs as[/color][/color]
>"active"[color=green][color=darkred]
>>>even though they weren't, so the scheduler never even attempts to run[/color][/color][/color]
them.[color=blue][color=green][color=darkred]
>>>
>>>> *Catalog backups quit woking. Scheduled to start after each session
>>>of
>>>>scheduled or manual backups, will work the way its supposed[/color][/color]
>to[color=green][color=darkred]
>>>for
>>>>a few days and then stop, upon restarting the services (bpdown/bpup)[/color][/color][/color]
it[color=blue][color=green][color=darkred]
>>>will
>>>>start woking again??? (also waiting to hear back on this)
>>>
>>>Although this isn't the issue, you should look into hot backups if you're
>>>using v6.[/color]
>>
>>I too am having lots of problems. I am now in the habit of if a job fails
>>stop and restart netbackup. What a pain. I am experiencing lots of problems
>>with Vaulting. Anyone else getting tape errors only with vaulting?[/color]
>[/color]

The problems I have with vault is the it holds on to tape definitions. I
have to use nbrbutil -dump followed by nbrbutil -releaseMDS MDS#. Sometimes
vaulting won't duplicate a job, but when I retry it it will. Strange stuff
like that.
"Moe" <moe@email.com> wrote:[color=blue]
>
>You mentioned having problems with vault. What problems are you having?[/color]
[color=blue]
>I too had problems with vault after upgrading to 6.0 MP2.
>
>"Irene Reed" <reed.irene@jobcorps.org> wrote:[color=green]
>>
>>
>>
>>"Mike" <mrobinson@arrayasolutions.com> wrote:[color=darkred]
>>>
>>>
>>>> *Policies and clients are being skipped without giving any errors[/color][/color]
>or[color=green][color=darkred]
>>>
>>>>even attempting to try and backup (haven't heard back yet on a[/color][/color][/color]
fix[color=blue][color=green][color=darkred]
>>>for
>>>>this)
>>>
>>>This is a known bug in 6.0 MP2 and will be fixed in MP3, so I'm told.[/color][/color][/color]
[color=blue]
>Happens[color=green][color=darkred]
>>>if you are using checkpointed backups. One workaround:
>>>
>>>nbpem -terminate
>>>sleep 30
>>>nbpem
>>>
>>>I don't see any problem with restarting this, doesn't kill any jobs in[/color][/color]
>progress[color=green][color=darkred]
>>>or whatever.
>>>
>>>I was given a command - I forget it offhand - that showed some jobs as[/color][/color]
>"active"[color=green][color=darkred]
>>>even though they weren't, so the scheduler never even attempts to run[/color][/color][/color]
them.[color=blue][color=green][color=darkred]
>>>
>>>> *Catalog backups quit woking. Scheduled to start after each session
>>>of
>>>>scheduled or manual backups, will work the way its supposed[/color][/color]
>to[color=green][color=darkred]
>>>for
>>>>a few days and then stop, upon restarting the services (bpdown/bpup)[/color][/color][/color]
it[color=blue][color=green][color=darkred]
>>>will
>>>>start woking again??? (also waiting to hear back on this)
>>>
>>>Although this isn't the issue, you should look into hot backups if you're
>>>using v6.[/color]
>>
>>I too am having lots of problems. I am now in the habit of if a job fails
>>stop and restart netbackup. What a pain. I am experiencing lots of problems
>>with Vaulting. Anyone else getting tape errors only with vaulting?[/color]
>[/color]