Job Status "Unknown"

[Casey_King]

Specs:

Windows 2003 Server, Standard Edition
NB: 5.1MP3


I think that will work for this problem. In the Admin Console, I have a job with a status unknown. I tried to cancel the 'job' but I cannot cancel it. I opened the job to see if there would be information telling what the job was before it became 'unknown' but there is no information. How do I go about stopping/canceling this job?

Thanks

Casey

[DavidParker]

Casey,
I've had similar occurrences.

Try this when you have a quiet period on your backups:

Shutdown all NetBackup services.
Go to: \VERITAS\netbackup\db\jobs
Look for a file called bpjobd.act
Rename it to bpjobd.act.old
Restart your services.

Also, as a side note, you're still on MP3? You should really upgrade to MP5, especially if you have Windows 2003 clients. There is a known issue with pre-MP5 where NetBackup will not backup the entire System State/Registry of Windows 2003 clients correctly! See this tech note:

http://support.veritas.com/docs/280511
The %windir%\registration folder on Windows 2003 clients is being omitted from backups performed by the Veritas NetBackup (tm) Server / Enterprise Server 5.1 and 6.0 releases, and therefore, will not be available for restore.

[Casey_King]

David,

Thanks for pointing out issues with MP3, I did not know there was a problem of this nature. We are now discussing when we can find the opportunity to upgrade to the current version of NetBackup.

I would probably mark your response as 'correct,' but I have to find the ever elusive 'quiet' time for backups. I think I have about 5 minutes around 8:50 that I could possibly do this without interfering with backups

[DavidParker]

LOL
Wow, a whole 5 minute window?!
:)

Oh, I forgot to mention this about the MP5 thing; you'll need to update all of your Windows 2003 clients with MP5 too. Unfortunately this one wasn't one that could be fixed by just patching the master server. :(

On the bright side, updating the MP on Windows machines is a cinch (remote install for multiple clients!).

[Casey_King]

Okay, updating the clients remotely wouldn't be too bad. Here is my question. I have only been dealing with Netbackup (heck, backups for that matter) for about 4 months now. I am finally feeling confidently wrecklace in what I do to resolve issues that occur.

okay, now to my question:

I believe, if I am going to upgrade, I might as well go to v6.0. Is it possible to upgrade the Master Server only and leave my 7 other media servers at current levels or must they all be upgraded to v6.0 and then pushed to the clients. We are running Enterprise Vault as well, off the top of your head, would an upgrade of this nature involve necessary modifications in that area?

[Stumpr2]

STOP !

stay with 5.x and enjoy your time off :)

[DavidParker]

Sure, you could upgrade to 6.0 ...
But I'm going to agree with Bob here, why put yourself through the major hassle that is required to upgrade to 6.0? There have been numerous 'issues' reported doing that.

Might as well stick with 5.1 for as long as you can; especially if everything is working well!
If it ain't broke, why fix it?

And, later, when it's required to go to 6.0, I hear that the best method is to set it up as a new, clean install and then migrate over clients (as opposed to upgrading your current setup).

$0.00.5

[Dennis_Strom]

Just one more to say stay with 5.1

[Casey_King]

Hmmm...so it seems that 6.0 is not the way to go right at the moment. Might just stay at 5.1, I am not sure what kind of issues are presented in 6.0, but we are getting ready to bring down three of the media servers and deploy new servers, that is one of the reasons I thought, why not go to 6.0 if I am going to take down old servers and deploy new servers.

[dslam24]

Casey, This is completely unrelated but I had to ask. Where are you from? I went to FHSU with a Casey King.

[Casey_King]

Yes, I went to FHSU...how are you doing Mauro :)

[Dennis_Strom]

upgrading to 6.0
http://forums.symantec.com/discussions/thread.jspa?threadID=68537&tstart=0
run NCVU utility before upgrade
run a catalog consistency check (bpdbm ?consistency)
is your catalog data in binary or ACSII? It is
highly suggested to convert any NetBackup ACSII catalog
information to binary mode using the cat_convert utility
install pbx
upgrade to latest version of 5.1 (and stay there :)
nbpushdata command after installing 6 and latest mp.

http://support.veritas.com/docs/283712
GENERAL ERROR: The nbpushdata command can fail if the
REQUIRED_INTERFACE entry exists in the vm.conf file
on a clustered NetBackup server

http://support.veritas.com/docs/283176
GENERAL ERROR: Running "nbpushdata" on Veritas NetBackup
(tm) 6.0 Maintenance Pack 2 (MP2) fails to push the globDB.

would really like to avoide downgrading
before upgrading once again described in
http://seer.support.veritas.com/docs/282327.htm

http://support.veritas.com/docs/285223
Welcome to the Veritas NetBackup (tm) 6.0 Upgrade Portal!

http://support.veritas.com/docs/285590
Symantec's Veritas NetBackup (tm) 6.0 Upgrade Guide, Version "B"
I still would not upgrade to 6!

Upgrading to Veritas NetBackup? 6.0
http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/285590.pdf

If you upgrade to 6.0 convert from cold catalog backups to hot catalog backups
http://support.veritas.com/docs/277787
How to configure Hot Catalog Backups with Veritas NetBackup (tm) 6.0

http://support.veritas.com/docs/278610
DOCUMENTATION: VERITAS NetBackup (tm) 6.0 "Hot Catalog Backup" will not include the jobs databas
e. The jobs database will restart with a JobID of 1 after a Hot Catalog Backup recovery.Message was edited by:
Dennis Strom

[Casey_King]

Thanks a lot Dennis, I am going to read through the links you sent, but I can see where it would probably be a good idea to stay in the 5.1 MPx for now until 6.0 is truly ready for use.

[Casey_King]

I am going to do this process in the morning. I checked the directory to see what you explained would be there. I am confident what you say is gong to work....and if not...well then....don't go to sleep :)

[dslam24]

hey shoot me an e-mail
mgonzalez@nex-techMessage was edited by:
Mauro Gonzalez