04-13-2015 12:29 PM
I have a peculiar problem where DFSR is backed up successfully on one server, but fails on the other one. I created a separate policy for DFSR for the working server, but did not exclude DFSR on the client for either policy. So I copied those policies for a new server running the same OS and NetBackup versions and SCC backup fails on the DFSR data. As far as I can tell, settings are pretty much the same on both servers. I was just curious if anyone had seen this behavior and determined the cause. I've read the TECHNOTEs for DFSR backups, but nothing seems to apply.
04-13-2015 01:28 PM
1) Compare the client configs:
> bpgetconfig -M server1 > server1.cfg
> bpgetconfig -M server2 > server2.cfg
> fc server1.cfg server2.cfg
Anything obvious?
.
2) Compare the master server client attributes:
> bpclient -L -client server1 > server1.att
> bpclient -L -client server2 > server2.att
> fc server1.att server2.att
Anything obvious?
.
3) Compare the policies:
> bppllist policy1 -L > policy1.lis
> bppllist policy2 -L > policy2.lis
> fc policy1.lis policy2.lis
Anything obvious?
04-13-2015 01:30 PM
4) Master server NetBackup version, and OS family and server pack or patch level?
5) NetBackup version of both clients, and Windows OS and service pack of each?
04-13-2015 08:53 PM
04-14-2015 06:17 AM
See attachments. I changed the timeout values to match, but I can't figure out some of the entries:
From the MS-Windows policy comparison:
< Generation: 17
---
> Generation: 5
From the DFSR policy comparison:
46c46
< Generation: 3
---
> Generation: 4
From the client config comparison:
193,194c177,178
< Policy_Type = 13
< Client_Version = 500
---
> Policy_Type = 0
> Client_Version = 31
04-14-2015 06:33 AM
Master server NetBackup version, and OS family and server pack or patch level?
7.6.0.3
Red Hat Enterprise Linux Server release 5.7 (Tikanga)
Linux alxaptb07xs 2.6.18-274.12.1.el5 #1 SMP Tue Nov 8 21:37:35 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
NetBackup version of both clients, and Windows OS and service pack of each?
7.6.0.3
C:>wmic os get /format:list
BootDevice=\Device\HarddiskVolume1
BuildNumber=7601
BuildType=Multiprocessor Free
Caption=Microsoft Windows Server 2008 R2 Standard
CodeSet=1252
CountryCode=1
CreationClassName=Win32_OperatingSystem
CSCreationClassName=Win32_ComputerSystem
CSDVersion=Service Pack 1
CSName=ALXAPTB72
CurrentTimeZone=-300
DataExecutionPrevention_32BitApplications=TRUE
DataExecutionPrevention_Available=TRUE
DataExecutionPrevention_Drivers=TRUE
DataExecutionPrevention_SupportPolicy=3
Debug=FALSE
Description=
Distributed=FALSE
EncryptionLevel=256
ForegroundApplicationBoost=0
FreePhysicalMemory=20973200
FreeSpaceInPagingFiles=35501704
FreeVirtualMemory=57022564
InstallDate=20131119131705.000000-360
LargeSystemCache=
LastBootUpTime=20150312092310.596796-300
LocalDateTime=20150414082207.857000-300
Locale=0409
Manufacturer=Microsoft Corporation
MaxNumberOfProcesses=-1
MaxProcessMemorySize=8589934464
MUILanguages={"en-US"}
Name=Microsoft Windows Server 2008 R2 Standard |C:\WINDOWS|\Device\Harddisk0\Partition1
NumberOfLicensedUsers=0
NumberOfProcesses=91
NumberOfUsers=4
OperatingSystemSKU=7
Organization=Southern Company Services
OSArchitecture=64-bit
OSLanguage=1033
OSProductSuite=272
OSType=18
OtherTypeDescription=
PAEEnabled=
PlusProductID=
PlusVersionNumber=
Primary=TRUE
ProductType=3
RegisteredUser=Information Technology
SerialNumber=00477-001-0000421-84299
ServicePackMajorVersion=1
ServicePackMinorVersion=0
SizeStoredInPagingFiles=35638360
Status=OK
SuiteMask=272
SystemDevice=\Device\HarddiskVolume1
SystemDirectory=C:\WINDOWS\system32
SystemDrive=C:
TotalSwapSpaceSize=
TotalVirtualMemorySize=60789100
TotalVisibleMemorySize=25152600
Version=6.1.7601
WindowsDirectory=C:\WINDOWS
C:\Users\a-dtwillin>wmic os get /format:list
BootDevice=\Device\HarddiskVolume1
BuildNumber=7601
BuildType=Multiprocessor Free
Caption=Microsoft Windows Server 2008 R2 Standard
CodeSet=1252
CountryCode=1
CreationClassName=Win32_OperatingSystem
CSCreationClassName=Win32_ComputerSystem
CSDVersion=Service Pack 1
CSName=ALXAPTB73
CurrentTimeZone=-300
DataExecutionPrevention_32BitApplications=TRUE
DataExecutionPrevention_Available=TRUE
DataExecutionPrevention_Drivers=TRUE
DataExecutionPrevention_SupportPolicy=3
Debug=FALSE
Description=
Distributed=FALSE
EncryptionLevel=256
ForegroundApplicationBoost=2
FreePhysicalMemory=29861340
FreeSpaceInPagingFiles=33477156
FreeVirtualMemory=63653632
InstallDate=20140626130014.000000-300
LargeSystemCache=
LastBootUpTime=20150402152108.582794-300
LocalDateTime=20150414082357.502000-300
Locale=0409
Manufacturer=Microsoft Corporation
MaxNumberOfProcesses=4294967295
MaxProcessMemorySize=8589934464
MUILanguages={"en-US"}
Name=Microsoft Windows Server 2008 R2 Standard |C:\WINDOWS|\Device\Harddisk0\Partition1
NumberOfLicensedUsers=0
NumberOfProcesses=81
NumberOfUsers=7
OperatingSystemSKU=7
Organization=Southern Company Services
OSArchitecture=64-bit
OSLanguage=1033
OSProductSuite=272
OSType=18
OtherTypeDescription=
PAEEnabled=
PlusProductID=
PlusVersionNumber=
Primary=TRUE
ProductType=3
RegisteredUser=Information Technology
SerialNumber=00477-001-0000421-84299
ServicePackMajorVersion=1
ServicePackMinorVersion=0
SizeStoredInPagingFiles=33554432
Status=OK
SuiteMask=272
SystemDevice=\Device\HarddiskVolume1
SystemDirectory=C:\WINDOWS\system32
SystemDrive=C:
TotalSwapSpaceSize=
TotalVirtualMemorySize=67107004
TotalVisibleMemorySize=33554432
Version=6.1.7601
WindowsDirectory=C:\WINDOWS
04-14-2015 06:34 AM
Please see my post below...
Please post bppllist output for failing policy as well as all text in Details tab of failing job.
04-14-2015 06:37 AM
I excluded DFSR folders for the Windows policy only and the DFSR policy is successful now. I just don't understand why I have to do it for the new policy, but not the original one I copied it from. The original policy was create in version 7.1.0.4.
04-14-2015 06:43 AM
We can only assist if you share all relevant info....................