Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SRT ersion 6.5 is incompatible with client config version 6.5.5

Created: 15 Aug 2012 | 57 comments

I am trying to run a prepare to restore process on a client but receive an error.  I've attached a screenshot of the error.  I'm wondering how I can update the SRT it mentions in the error.

I'm running NetBackup Enterprise 6.5.6 on Windows Server 2003.

Comments 57 CommentsJump to latest comment

Marianne's picture

See page 126 of BMR Admin Guide:

 

Adding software to a Windows SRT
 
You can install the following into an existing Windows SRT:
■ Windows service pack (Legacy SRTs only)
■ NetBackup client software
■ Veritas Storage Foundation for Windows
■ NetBackup Security Services
 
To add software to a Windows SRT
 
1 On the Start menu on the Windows BMR boot server that hosts the SRT, click Programs > Veritas NetBackup > Bare Metal Restore Boot Server Assistant.
.....
......

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Moeman's picture

The error says I need to update the version of SRT.  Where do I get a compatible version of SRT?  I know how to install software into an existing SRT but the error says my version is wrong.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Andy Welburn's picture

Continue with the steps that Marianne suggested - that was just step 1 of 6.

Step 5 includes:

■ Add or update NetBackup client software images in an SRT. An SRT must contain a NetBackup client image that is the same version as the system(s) to be protected.

 

This T/N says the same thing, but differently:

http://www.symantec.com/business/support/index?pag...

Moeman's picture

My SRT does contain the same NetBackup client version as the system to be protected.  I use the same version for all my clients.  My client version hasn't changed in 3 years.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Andy Welburn's picture

But what client version is on the SRT?

The error seems to indicate it is only running at 6.5 - did you upgrade (i.e. patch to a newer release) after you first set it up in July?

Moeman's picture

Thanks.  I will verify my client is at 6.5 like the SRT and not 6.5.6.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Marianne's picture

NO! Do not dowgrade your client! Update your SRT!

 

PLEASE take note of the fact that support for 6.x will end in less than 6 weeks....

TECH77075: The official EOSL statement for NetBackup 6.x (originally sent 1/19/2009, updated 2/1/2010)
 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Moeman's picture

I don't understand how I update my SRT.  Where do I get the latest software to update the SRT?

I tried a client with NetBackup client 6.5 (instead of 6.5.6) and now I get a different set of errors pertaining to the boot server version.

BMR_Error2.jpg

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Marianne's picture

I have learned with BMR that EVERYTHING needs to be on the same version, Master, Boot server and ALL clients being protected with BMR.
Please patch all bmr boot server as well as clients to 6.5.6. 

You have 6.5.6 patch, right?
Install that into the bmr boot image. Please follow steps in the manual or in the TN that Andy has posted above.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Moeman's picture

That's what is odd. My master, boot server and test client were all on 6.5.6 when I got the original error about the SRT version being incompatible.

If I try to update the version of the NetBackup client in the SRT and point it to the MSI file it errors saying it's not a valid NetBackup client install image.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

This error thrown is saying BMR master server and boot server versions are not compatible to each other. But looking at their version strings this should not happen. Looks weird and a bug to me.

Can you paste output for below command executed on your master server?

1. bmrs -o query -r database -table currentversion

2. bmrs -o query -r database -table NbuVersionSupport

 

Thanks.

mandar

 

Moeman's picture

Sure thing, here you go.

1.  5 vCurrentVersion Entries:
    Id = 1
    Name = SCHEMA
    Version = 6.5.6.0
    Checksum = 1855
    DateTime = 1288797182

    Id = 2
    Name = PREVIOUS_SCHEMA
    Version = 6.0.0.0
    Checksum = B0F9D16066BCD8CBD2CF7A371EDF618A
    DateTime = 1252696516

    Id = 3
    Name = PREVIOUS_SCHEMA
    Version = 6.0.4.0
    Checksum = B60182D4531A810E7701EDA1BF20B393
    DateTime = 1275419533

    Id = 4
    Name = PREVIOUS_SCHEMA
    Version = 6.0.7.0
    Checksum = 1713
    DateTime = 1288791801

    Id = 5
    Name = PREVIOUS_SCHEMA
    Version = 6.5.0.0
    Checksum = 1813
    DateTime = 1288797182

2.  159 vNbuVersionSupport Entries:
    Id = 1
    MasterNbuVersion = 6.0
    ClientNbuVersion = 6.0

    Id = 2
    MasterNbuVersion = 6.0MP1
    ClientNbuVersion = 6.0

    Id = 3
    MasterNbuVersion = 6.0MP1
    ClientNbuVersion = 6.0MP1

    Id = 4
    MasterNbuVersion = 6.0MP2
    ClientNbuVersion = 6.0

    Id = 5
    MasterNbuVersion = 6.0MP2
    ClientNbuVersion = 6.0MP1

    Id = 6
    MasterNbuVersion = 6.0MP2
    ClientNbuVersion = 6.0MP2

    Id = 7
    MasterNbuVersion = 6.0MP3
    ClientNbuVersion = 6.0

    Id = 8
    MasterNbuVersion = 6.0MP3
    ClientNbuVersion = 6.0MP1

    Id = 9
    MasterNbuVersion = 6.0MP3
    ClientNbuVersion = 6.0MP2

    Id = 10
    MasterNbuVersion = 6.0MP3
    ClientNbuVersion = 6.0MP3

    Id = 11
    MasterNbuVersion = 6.0.4
    ClientNbuVersion = 6.0.0.0

    Id = 12
    MasterNbuVersion = 6.0.4
    ClientNbuVersion = 6.0.1.0

    Id = 13
    MasterNbuVersion = 6.0.4
    ClientNbuVersion = 6.0.2.0

    Id = 14
    MasterNbuVersion = 6.0.4
    ClientNbuVersion = 6.0.0

    Id = 15
    MasterNbuVersion = 6.0.4
    ClientNbuVersion = 6.0.1

    Id = 16
    MasterNbuVersion = 6.0.4
    ClientNbuVersion = 6.0.2

    Id = 17
    MasterNbuVersion = 6.0.4
    ClientNbuVersion = 6.0.3

    Id = 18
    MasterNbuVersion = 6.0.4
    ClientNbuVersion = 6.0.4

    Id = 19
    MasterNbuVersion = 6.0.5
    ClientNbuVersion = 6.0.0.0

    Id = 20
    MasterNbuVersion = 6.0.5
    ClientNbuVersion = 6.0.1.0

    Id = 21
    MasterNbuVersion = 6.0.5
    ClientNbuVersion = 6.0.2.0

    Id = 22
    MasterNbuVersion = 6.0.5
    ClientNbuVersion = 6.0.0

    Id = 23
    MasterNbuVersion = 6.0.5
    ClientNbuVersion = 6.0.1

    Id = 24
    MasterNbuVersion = 6.0.5
    ClientNbuVersion = 6.0.2

    Id = 25
    MasterNbuVersion = 6.0.5
    ClientNbuVersion = 6.0.3

    Id = 26
    MasterNbuVersion = 6.0.5
    ClientNbuVersion = 6.0.4

    Id = 27
    MasterNbuVersion = 6.0.5
    ClientNbuVersion = 6.0.5

    Id = 28
    MasterNbuVersion = 6.0.6
    ClientNbuVersion = 6.0.0.0

    Id = 29
    MasterNbuVersion = 6.0.6
    ClientNbuVersion = 6.0.1.0

    Id = 30
    MasterNbuVersion = 6.0.6
    ClientNbuVersion = 6.0.2.0

    Id = 31
    MasterNbuVersion = 6.0.6
    ClientNbuVersion = 6.0.0

    Id = 32
    MasterNbuVersion = 6.0.6
    ClientNbuVersion = 6.0.1

    Id = 33
    MasterNbuVersion = 6.0.6
    ClientNbuVersion = 6.0.2

    Id = 34
    MasterNbuVersion = 6.0.6
    ClientNbuVersion = 6.0.3

    Id = 35
    MasterNbuVersion = 6.0.6
    ClientNbuVersion = 6.0.4

    Id = 36
    MasterNbuVersion = 6.0.6
    ClientNbuVersion = 6.0.5

    Id = 37
    MasterNbuVersion = 6.0.6
    ClientNbuVersion = 6.0.6

    Id = 38
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.0.0

    Id = 39
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.1.0

    Id = 40
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.2.0

    Id = 41
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.0

    Id = 42
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.1

    Id = 43
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.2

    Id = 44
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.3

    Id = 45
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.4

    Id = 46
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.5

    Id = 47
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.6

    Id = 48
    MasterNbuVersion = 6.0.7
    ClientNbuVersion = 6.0.7

    Id = 49
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.0.0

    Id = 50
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.1.0

    Id = 51
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.2.0

    Id = 52
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.0

    Id = 53
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.1

    Id = 54
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.2

    Id = 55
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.3

    Id = 56
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.4

    Id = 57
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.5

    Id = 58
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.5.0

    Id = 59
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.0.0

    Id = 60
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.1.0

    Id = 61
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.2.0

    Id = 62
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.0

    Id = 63
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.1

    Id = 64
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.2

    Id = 65
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.3

    Id = 66
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.4

    Id = 67
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.0.5

    Id = 68
    MasterNbuVersion = 6.5.0
    ClientNbuVersion = 6.5.0

    Id = 95
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.0.0

    Id = 70
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.0.0.0

    Id = 71
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.0.1.0

    Id = 72
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.0.2.0

    Id = 73
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.0.0

    Id = 74
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.0.1

    Id = 75
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.0.2

    Id = 76
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.0.3

    Id = 77
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.0.4

    Id = 78
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.0.5

    Id = 79
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.0.6

    Id = 80
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.5.0

    Id = 81
    MasterNbuVersion = 6.5.1
    ClientNbuVersion = 6.5.1

    Id = 82
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.0.0.0

    Id = 83
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.0.1.0

    Id = 84
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.0.2.0

    Id = 85
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.0.0

    Id = 86
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.0.1

    Id = 87
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.0.2

    Id = 88
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.0.3

    Id = 89
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.0.4

    Id = 90
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.0.5

    Id = 91
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.0.6

    Id = 92
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.5.0

    Id = 93
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.5.1

    Id = 94
    MasterNbuVersion = 6.5.2
    ClientNbuVersion = 6.5.2

    Id = 96
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.1.0

    Id = 97
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.2.0

    Id = 98
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.0

    Id = 99
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.1

    Id = 100
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.2

    Id = 101
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.3

    Id = 102
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.4

    Id = 103
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.5

    Id = 104
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.6

    Id = 105
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.0.7

    Id = 106
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.5.0

    Id = 107
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.5.1

    Id = 108
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.5.2

    Id = 109
    MasterNbuVersion = 6.5.3
    ClientNbuVersion = 6.5.3

    Id = 110
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.0.0

    Id = 111
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.1.0

    Id = 112
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.2.0

    Id = 113
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.0

    Id = 114
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.1

    Id = 115
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.2

    Id = 116
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.3

    Id = 117
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.4

    Id = 118
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.5

    Id = 119
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.6

    Id = 120
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.0.7

    Id = 121
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.5.0

    Id = 122
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.5.1

    Id = 123
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.5.2

    Id = 124
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.5.3

    Id = 125
    MasterNbuVersion = 6.5.4
    ClientNbuVersion = 6.5.4

    Id = 126
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.0.0

    Id = 127
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.1.0

    Id = 128
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.2.0

    Id = 129
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.0

    Id = 130
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.1

    Id = 131
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.2

    Id = 132
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.3

    Id = 133
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.4

    Id = 134
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.5

    Id = 135
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.6

    Id = 136
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.0.7

    Id = 137
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.5.0

    Id = 138
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.5.1

    Id = 139
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.5.2

    Id = 140
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.5.3

    Id = 141
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.5.4

    Id = 142
    MasterNbuVersion = 6.5.5
    ClientNbuVersion = 6.5.5

    Id = 143
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.0.0

    Id = 144
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.1.0

    Id = 145
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.2.0

    Id = 146
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.0

    Id = 147
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.1

    Id = 148
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.2

    Id = 149
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.3

    Id = 150
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.4

    Id = 151
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.5

    Id = 152
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.6

    Id = 153
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.0.7

    Id = 154
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.5.0

    Id = 155
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.5.1

    Id = 156
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.5.2

    Id = 157
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.5.3

    Id = 158
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.5.4

    Id = 159
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.5.5

    Id = 160
    MasterNbuVersion = 6.5.6
    ClientNbuVersion = 6.5.6

 

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Mark_Solutions's picture

OK - fresh to this thread so let me add my advice ....

1. 6.5.x goes end of life very soon - please look to upgrade as soon as you can

2. To upgrade an SRT just run the BMR Boot Server Assistant - select the SRT Wizard - Select Add or Update Packages to an SRT - select  Add Release Update or Maintenance Pack to SRT - browse for the 6.5.6 msi file and follow the wizard through

The 6.5.6 not compatible with 6.5.6.0 is interesting though - have seen something similar somewhere and it was a bug - will see if i can dig that one out

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Moeman's picture

1.  My company is cheap, they will not spend the money to upgrade.

2.  I've already tried that.  When I point it to the 6.5.6 MSI package it returns an error saying it is not a valid NetBackup Maintenance Pack install image.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Mark_Solutions's picture

Make sure you do select the correct one - there are 32 bit and 64 bit ones - that may be where the issue lies

 

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Moeman's picture

My NetBackup environment is 32-bit so I am selecting the x86 folder that contains the NetBackup Update.msi file.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

Can you try below and let me know if it works for you.

Go to master server netbackup/bin directory.

Create a text file call foo.sql and add below line into it.

INSERT INTO BmrDba.BMR_NbuVersionSupport (MasterNbuVersion, ClientNbuVersion) VALUES ('6.5.6', '6.5.6.0');

Run below command

bmrpans -o sql -in foo.sql

If this works successfully then re-fire bmrs command i gave already to confirm if you see above entry.

Re-check BMR operation you were trying earlier.

 

Thanks.

mandar

Moeman's picture

Commands all completed successfully with no errors.  Tried restore BMR operation but get the same error.

SameError.jpg

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Moeman's picture

No matter what I try I can't seem to get my SRT up to version 6.5.6.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

Ok. Can you provide debug level 6 log of your BMR master server?

You can find it in logs/bmrd folder. Make sure nblog.conf file has debuglevel set to 6 before you collect the logs.

thanks.

mandar

Moeman's picture

I found two instances of nblog.conf.  One in D:\Program Files\VERITAS\NetBackup, the other in D:\Program Files\VERITAS\NetBackup\bin.6.0.  Both have debug level set to 6.  I tried running a restore on my client so it produced the error but I cannot locate a logs folder called bmrd.  It does not exist on my server.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

Check netbackup log with format *-119-*.log.

mandar

Moeman's picture

Found one instance of a file searching for *-119-*.log.

D:\Program Files\VERITAS\NetBackup\logs\51216-119-3104440586-120210-0000000000.log.

$Header 65543,51216,119,1328889649,18000,fhs-backup1
2,51216,128,119,1,1343399878515,1796,6852,0:,0:,0:,2,(900|)
2,51216,128,119,1,1345227819485,1692,8168,0:,0:,0:,2,(900|)
 

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

Yes, this is the one.

Go to logs dir and fire below command

netbackup/bin/vxlogview -i 119 > 119.log

and attach this generated 119.log

 

mandar

Moeman's picture

Done.  Below is the output.

7/27/2012 10:37:58.515 [Error] V-128-900 Cannot query the BMR database for existing boot servers.

Either the database is not functioning, or the bmrd on the

BMR master server is not running. Fix these problems and retry.
8/17/2012 14:23:39.485 [Error] V-128-900 Cannot query the BMR database for existing boot servers.

Either the database is not functioning, or the bmrd on the

BMR master server is not running. Fix these problems and retry.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

This is weird.

I believe some problem with configuration steps/process.

Can you confirm below:

1. Do you see a process having name bmrd running on your master server?

2. If yes what is o/p of below command?

    bmrs -o list -r bootserver

    Do you see your boot server entry in this output?

If either bmrs does not exists or query in 2 fails, means your bmr master server setup is not done correctly.

3. Cat you paste netbackup/bin/version file o/p exists on your boot server?

 

Also can you provide exact steps you did to get the above log.

 

Thanks.

Mandar

 

Moeman's picture

1.  Yes, I see a process called bmrd and bmrbd

2.  Output of  bmrs -o list -r bootserver

Host        Operating System    Architecture Version Id
----------- ------------------- ------------ ------- --
fhs-backup1 NT Server Class 5.2 x86          6.5.6   1

3.  I don't understand what you want when you say "Cat you paste netbackup/bin/version file o/p exists on your boot server?"

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

sorry for typo in my earlier mail. I meant:

Can you please paste here content of netbackup/version file that exists on your bmr boot server?

Also please attach whole BMRD (119) fresh debug level 6 log by re-producing the issue. Please mention the steps you execute.

thanks.

mandar

Moeman's picture

What netbackup/version file are you talking about?

I've tried generating bmrd (119) logs but nothing gets created even though logging is set to level 6.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

On your bmr boot server go to directory netbackup. Do you see a file named "version" there? I was talking about this file and interested to know its content.

Setting debuglevel to 6 should genereate 119 debug log. Try restarting BMR master server service or if possbile whole NB master server.

You have not provided the steps that you are executing to reproduce the problem.

thanks.

mandar

 

Moeman's picture

Contents of version.txt:

HARDWARE Windows x86
VERSION NetBackup 6.5.6
RELEASEDATE Fri Apr 23 17:08:38 CDT 2010
BUILDNUMBER 20100423

Set all logs to debug level 5 (highest setting on my version in master server properties).

Steps to reproduce:

1.  Expand BMR Management

2.  Expand Hosts

3.  Click on BM Restore Clients

4.  Right-click on the client on want to restore and select "Prepare to Restore"

4.  Click OK

After that I receive the attached error.

bmr.jpg

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

This is a differnet error message than you pasted earlier. Earlier was related to boot server incompatibility where this is related to NetBackup client within SRT is not compatible to the client being restored.

Can you try patching up your srt NB client version to 6.5.5 and give a try again? Go to boot server and use bmrsrtadm wizard to upgrade nb version within the srt you are using.

thanks.

mandar

Moeman's picture

If my client is running 6.5 I get one error, if my client is running 6.5.6 I get a different error.  I have been unable to update my SRT because each time I point it to the 6.5.6 MSI file it says it is an invalid image file.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Mark_Solutions's picture

Can you show us exactly what you are doing step by step when trying to add the 6.5.6 MSI

If possible screenshot everything and put it in a doc then attach that doc on here for us to see - just feels when it says "image" that you may be in the wrong palce when trying to update the SRT

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Mark_Solutions's picture

Just to clarify the process should be ...

BMR Boot Server Assistant - Add or Update Packages to a Shared Resource Tree - Add Release Update or Maintanance Pack to a SRT to a Shared Resource Tree - browse for msi.

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Moeman's picture

Exactly.  I start BMR Boot Server Assistant.

I choose Shared Resource Tree Administration Wizard.

I click Next.

I choose Add or Update Packages to a Shared Resource Tree then click Next.

At the next screen I've tried selecting Update the version of NetBackup Client in the Shared Resource Tree and Add NetBackup Maintenance Pack to a Shared Resource Tree.  Both of these selections error out.  One says the MSI is not a valid NetBackup Client Install Image while the other says the MSI is not a valid NetBackup Maintenance Pack install image.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Mark_Solutions's picture

It sounds like something is corrupt in that case

Could i suggest you make a new SRT for 6.5 and then try applying the 6.5.6 patch to it - to see if a fresh start resolves it for you

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Moeman's picture

I've already tried that, 3 times.  I've tried creating a new SRT at version 6.5 and even had 6.5 on my client when it was backed up.  That's when I get the error saying the boot server is incompatibile, blah blah blah.  And when I have 6.5 in my SRT and 6.5.6 on my client I get the error SRT version 6.5 is incompatible, blah blah blah.  I can't seem to get my SRT and client at 6.5.6.  I have my doubts it will even work since an SRT at 6.5 and a client at 6.5 doesn't work.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Mark_Solutions's picture

There is clearly something very worng there - if your were on Windows 2008 i would have looked at UAC but your are on 2003 so it is not that either - have you tried doing it when logged in as another user? Odd question i know but i have seen permissions do strange things (user must be at least a local admin)

Without logging on and seeing for myself i am not sure what else to suggest with this one but just in case can you run, from the Start Menu - the BMR Master Server Setup - just in case the database never upgraded properly when the Master was patched / upgraded - it will just run through its upgrade / checks routine again

May also be worth re-running bmrsetupboot as well (can't remember off hand if you needed the -register swicth for 6.5.6)

It is a long thread so you may have already been asked but have you raised a case with Symantec? At least they could maybe do a webex and have a fresh set of eyes to look at it

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

mandar_khanolkar's picture

>> If my client is running 6.5 I get one error, if my client is running 6.5.6 I get a different error.

It is always good to have NB client up-to-date within SRT. But recovery of 6.5.6 client backup using 6.5 NB client within SRT is possible. In other words you would not require to upgrade your NB client within SRT.

So if SRT has 6.5 NB client then what error do you see?

If you can copy debug level 6 log of bmrprep and bmrd (created on master server; log ids are 126 and 119 res.) would help much to quickly find out root cause.

Thanks.

Mandar

 

Moeman's picture

My NB client in my SRT has always been 6.5.  I can't get it to 6.5.6.  So, If my client is at 6.5 I get this error.

 

SameError.jpg

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Moeman's picture

Also, I ran through the BMR setup again.  Attached is a screenshot.  Everything looks ok.

I would have contacted Symantec tech support first but we no longer have a contract with them so that's why I tried the forum.

 

BMR_Setup.jpg

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

>> If you can copy debug level 6 log of bmrprep and bmrd (created on master server; log ids are 126 and 119 res.) would help much to quickly find out root cause.

I had asked for these logs (full log file attached here to this thread) but you have not provided yet. It is difficult to guide you without having this info.

 

thanks.

mandar

Moeman's picture

I previously set my log level to as high as it would go (level 5 for NBU 6.5.6) and ran through the BMR restore process.  No logs were created for bmrprep or bmrd not can I find any on my master server.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

You can find them on your master server in netbackup/logs directory with file name in fashion *-119-*.log and *-126-*.log

Moeman's picture

Here are the logs.  Not much there.

AttachmentSize
51216-119-3104440586-120210-0000000000.txt 233 bytes
51216-126-3104440586-120815-0000000000.txt 2.82 KB

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

mandar_khanolkar's picture

The logs are not produced with debug level 6 but still looking at below bmrprep log snippet (these log lines are generated for your latest PTR try); it is clear that your SRT NB version is not compatible with client NB version.

2,51216,126,126,1,1345818059741,5592,5428,0:,0:,0:,2,(80|A3:6.5|A5:6.5.5|A5:6.5.5|)
2,51216,126,126,2,1345818059771,5592,5428,0:,0:,0:,2,(3|)
2,51216,126,126,3,1345818059771,5592,5428,0:,0:,0:,0,(43|)

The error ID is: BMRPREP_SRT_VERSION_INCOMPATIBLE_WITH_CONFIG_VERSION

And this tells that your client is running at 6.5.5 NB version level and not 6.5.6.

ERROR: "SRT version 6.5 is incompatible with client config version 6.5.5. Please update SRT to at least 6.5.5 version."

Solution:
Please update your SRT version with 6.5.5 patch. Make sure from BMR admin GUI menu -> SRT > your SRT properties shows 6.5.5 NB version. Now re-try PTR. It should work.

thanks.
mandar
 

Moeman's picture

I am back on this.  I am unable to update the SRT to version 6.5.5 because I don't have an installation package for that version.  All I have is 6.5 and 6.5.6.  I've tried finding 6.5.5 on the Symantec website with no luck.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Mark_Solutions's picture

I have Windows x86 and x64 copies - 260MB - do you have anywhere i can upload it for you? (PM me)

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Mark_Solutions's picture

AH! - Just found them!

http://www.symantec.com/docs/TECH76642

 

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Moeman's picture

Thanks but I get the same error as before when I point the SRT to where I unzipped the 32-bit client I downloaded in the link you provided.  Error says "NetBackup Update.msi is not a valid NetBackup Client Install Image."

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Mark_Solutions's picture

You need to apply it as a maintenance release update to the SRT

The install image is the 6.5 and then you edit the SRT to add a maintenance release which is the 6.5.5 patch

Sounds like that is where you are going wrong

So ..

Boot Server Assistant - SRT Wizard - Add or Update Packages to a SRT - Add release update or Maintenace Pack to a SRT

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Moeman's picture

I've tried that, over and over and over and over.  It does not work.  I get the same error every time,  "NetBackup Update.msi is not a valid NetBackup Client Install Image."

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Mark_Solutions's picture

OK - i was just thinking that you may have selected "update the version of NetBackup Client in a SRT" rather than the "Add Release update ..." due to the error saying "Install" image

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Moeman's picture

I tried every option in that list, just to see if one worked.  All of them produce an error.  At this point I am going to look at upgrading NetBackup if I can get the funds.  If not then I will scrap this and look for another BMR option.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached

Mark_Solutions's picture

You are doing 32bit for 32bit SRT / 64 bit for 64 bit SRT?

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Moeman's picture

Yes.  My entire NetBackup environment is 32bit, so I'm only using 32bit packages.  My test client is 32bit.

NetBackup Enterprise 6.5.6 on Windows Server 2003 SP2
StorageTek L80 Tape Library, SCSI Attached