issue with 6.5.3 and 2 of my 2008 servers

[J_H_Is_gone]

 I have done my MP3 upgrade (yeah I know they call it different now but old habits are hard to break).

In my DR site upgrade went fine.

In my prod site it went kind of ok.

I have 2 servers that do not like MP3. If I put them back to 6.5.2a they run fine.

If they are on 6.5.3 they fail with 49’s


Environment

6.5.3 Unix master/media

6.5.3 Unix media

6.5.3 – 2 San Media

6.5.2a – 1 San media



Clients are Unix(aix), windows 2000, windows 2003 and windows 2008, exchange 2003 and exchange 2007



But ONLY 2 servers fail with 49’s

I have un-installed netbackup on the server and reinstalled to MP3 and they still fail

Took them back down to 6.5.2a and it works just fine



Has anybody had issues with 2008 x64 servers not liking 6.5.3?( I have other 2008 servers on 6.5.3 doing just fine)





Details of job

2/4/2009 9:21:48 AM - requesting resource Master/media_Media

2/4/2009 9:21:48 AM - requesting resource master/media.NBU_CLIENT.MAXJOBS.client

2/4/2009 9:21:48 AM - requesting resource master/media.NBU_POLICY.MAXJOBS.client_E

2/4/2009 9:21:49 AM - granted resource master/media.NBU_CLIENT.MAXJOBS.client

2/4/2009 9:21:49 AM - granted resource master/media.NBU_POLICY.MAXJOBS.client_E

2/4/2009 9:21:49 AM - granted resource T00001

2/4/2009 9:21:49 AM - granted resource IBM.ULT3580-TD4.003

2/4/2009 9:21:49 AM - granted resource master/media-hcart-robot-tld-0

2/4/2009 9:21:50 AM - estimated 5802205 kbytes needed

2/4/2009 9:21:50 AM - begin Parent Job

2/4/2009 9:21:50 AM - begin Snapshot , Start Notify Script

2/4/2009 9:21:51 AM - started process RUNCMD (237952)

Status 0

2/4/2009 9:21:51 AM - end Snapshot , Start Notify Script; elapsed time: 00:00:01

2/4/2009 9:21:51 AM - begin Snapshot , Step By Condition

Status 0

2/4/2009 9:21:51 AM - end Snapshot , Step By Condition; elapsed time: 00:00:00

2/4/2009 9:21:51 AM - begin Snapshot , Stream Discovery

Status 0

2/4/2009 9:21:51 AM - end Snapshot , Stream Discovery; elapsed time: 00:00:00

2/4/2009 9:21:51 AM - begin Snapshot , Read File List

Status 0

2/4/2009 9:21:51 AM - end Snapshot , Read File List; elapsed time: 00:00:00

2/4/2009 9:21:51 AM - begin Snapshot , Create Snapshot

2/4/2009 9:21:52 AM - started process bpbrm (356600)

2/4/2009 9:21:56 AM - begin Create Snapshot

2/4/2009 9:21:57 AM - Error bpbrm(pid=356600) client client didn't start

2/4/2009 9:21:57 AM - end Create Snapshot; elapsed time: 00:00:01

2/4/2009 9:21:57 AM - end writing

Status 49

2/4/2009 9:21:57 AM - end Snapshot , Create Snapshot; elapsed time: 00:00:06

2/4/2009 9:21:57 AM - begin Snapshot , Stop On Error

Status 0

2/4/2009 9:21:57 AM - end Snapshot , Stop On Error; elapsed time: 00:00:00

2/4/2009 9:21:57 AM - begin Snapshot , Delete Snapshot On Exit

Status 0

2/4/2009 9:21:57 AM - end Snapshot , Delete Snapshot On Exit; elapsed time: 00:00:00

2/4/2009 9:21:57 AM - begin Snapshot , End Notify Script

2/4/2009 9:21:58 AM - started process RUNCMD (340384)

Status 0

2/4/2009 9:21:58 AM - end Snapshot , End Notify Script; elapsed time: 00:00:01

Status 49

2/4/2009 9:21:58 AM - end Parent Job; elapsed time: 00:00:08

client did not start(49)

[sdo]

The only thing I can initially think of... is there being one or more DLLs that are not properly registered.

$ bperror -S 49 -r

...is not very helpful, and basically tells us all to look deeper in the client logs.

Windows being Windows, did you reboot the problem client after installing the v6.5.3 kit?

[Karthikeyan_Sun]

http://entsupport.symantec.com/docs/295732

http://seer.entsupport.symantec.com/docs/268347.htm

Not sure this will  help in ur case, just found this in Search !

[J_H_Is_gone]

UPdate

I got this tech note from support. Option 1 did not work for me. Option 2 did, but not a good option for me Option 3 did- the one I am currently working… Still have the call open with support but do not have a solution yet.  It also works if you do option 1 but turn off (uncheck) the open file backup. Anybody else find a solution yet?  Document ID: 318225
  After upgrading Netbackup Windows 2008 x64 clients to Netbackup 6.5.3 multi-stream backup jobs immediately end in status code 49 Details:=====
Details
=====
- The client is a Windows 2008 x64 machine
- Previously upgraded from Windows 2008 x64 proliferation package http://support.veritas.com/docs/304421

==========
Work Around
==========
Option #1

1. Open the admin console
2. Expand host properties
3. Select master server
4. Open the master server host properties
5. On the left go to "Client Attributes"
6. Add the client in question to the list of "clients"
7. Click on the "Windows Open File Backup" tab
8. Select the radio button "Use Microsoft Volume Shadow Copy Service)" then apply
9. Retry the operation

Option #2
1. Uncheck multiple data Streams in the policy

Option #3
1. Uninstall Netbackup 6.5.3 and revert to minimum Windows 2008 x64 client proliferation of 6.5.2

[CRZ]

If I read your excerpted text right, Option 1 is basically saying "make sure you're not using VSP on Win2008 as it isn't supported."  Is that right?

When you switched to VSS, did you still get a status code 49, or was it some other failure?

(How interested are you in troubleshooting VSS?  ;)  )

[J_H_Is_gone]

I changed it to VSP but it still got the 49.  Had to turn open file off to get it do anything.

once off the backup worked.

[CRZ]

---

@J.Hinchcliffe wrote:

I changed it to VSP but it still got the 49.  Had to turn open file off to get it do anything.

once off the backup worked.

---

VSP (Veritas Snapshot Provider) is the unsupported thing that shouldn't even exist on your Windows 2008 system and definitely won't work.

Did you mean "VSS" (Microsoft Volume Shadow Copy Service) above?

[J_H_Is_gone]

We tried both and neither worked.

had to turn open file backup off to use 6.5.3

[J_H_Is_gone]

In my research I found two other people reporting 49’s when running backups after an update.

Both on older versions ( as far back as 3.5)

And both of they say that it just fixed itself.

Well…. Mine has just fixed its self.

I was testing at 4:00 pm and they failed with 49’s

At 4:30 pm they worked.

Upgrade some more servers and they worked.

I asked everybody I could if anything was done.

I have never been able to find a reason for getting the 49 return codes on those servers.

But they are working now

[CRZ]

We haven't documented anything new about Status 49s on 2008 in the previous month, either.  I'd love to blame this on Microsoft somehow, but don't have any smoking guns to show you.  :)  SOMETHING definitely kept the backup from starting, but....but what?

I don't suppose the 6.5.3.1 hotfix ended up on those clients?  Just trying to reconfirm that "nothing changed" part...

[J_H_Is_gone]

It was not 6.5.31 -

thanks for asking CRZ, but I am just now getting 6.5.3.1 on my test site.

the 2008's were running on 6.5.2a just fine, the upgrade to 6.5.3 was failing.

one day i turned on all logging and up to 5 and was going to run the job and have it fail, then search the logs ( as it fails in less then one minute I would not have much to look through)  but that time it worked. So I never got my logs of when it failed.

I upgraded another dev 2008 box and it worked.

I upgraded all my dev 2008 boxes and that night all of them worked just fine!

I will upgrade my prod boxes when I push to 6.5.3.1 next week and see of all of them work.

I don't know why they failed and I don't know what made them start working.

[CY]

I found we encountered the same status 49 issue on Windows 2008 x86 platform, not just on x64 servers.  We are still running 6.5.3, not 6.5.3.1 yet.

I verfied these clients all have good communications with Master and Media servers.  bptestbpcd command from Master are all good.  bpclntcmd command from clients are all good.  I also can run User backups fine (backups initiated from the clients)  Only backups initiated from the Master failed with status 49.

Interestingly, once I changed the backup policy to NOT "allow multiple data streams" (as J. Hinchcliffe said the "option 2" in Document ID: 318225
After upgrading Netbackup Windows 2008 x64 clients to Netbackup 6.5.3 multi-stream backup jobs immediately end in status code 49), the backup jobs of these clients all worked successfully.

However I can no longer find Document ID 318225 on http://seer.entsupport.symantec.com.  I don't know why that document was gone.  :(   CRZ, does Symantec have new docuemnt for this issue?

So thanks to J.Hinchcliffe for posting this information.  You desered the 2 points.  :)

[J_H_Is_gone]

For 2008 servers you MUST set it up to use VSS.

Once I got all of my 2008's using VSS instead of VSP by default it works.  NO more 49's

[Andy_Welburn]

I thought you said that you tried VSS (as well as VSP) but had to switch off WOFB as it didn't work?

Just seeking clarification ;)

[J_H_Is_gone]

I I try VSS and it still did not work,

but after working with support they again told me to to set it to use VSS

and it worked.

I still think there was some setting on windows that was stoping it from working and the admins changed what ever it was that then allowed it to work.

there is a support doc that says the different things to do, there is a new one that says to just put it to VSS.

I have not been able to find any other reason why it did not work.  So I tried the VSS AGAIN, and it worked.

When I first opened this thread we had just started putting in 2008 servers.  They have worked out there setups and now it works when I put it to VSS.