MSDP creation error.

Hi 

Master and media are on same server, windows 2008 R2, NBU 8.1.2

Master server ad media server are running fine. 

I am trying to create MSDP on this server. I have two drive C & D drive. 

On D drive there is already existing data (many folders & subfolders), I created a folder named MSDP  at the root level of D drive and trying to use it as destination of backups and dedup config/DBs.

But my configuration is failing with system call (11) error.

1 Solution

Accepted Solutions
Accepted Solution!

Re: MSDP creation error.

9 Replies

Re: MSDP creation error.

Hello,

review D:\MSDP\log\pdde-config.log if exists.

Regards

Michal

Re: MSDP creation error.

@NBU35 

You need a dedicated volume for MDSP. 

Please review the requirements in the Dedupe Guide carefully. 
See this extract: 

NetBackup requires the exclusive use of the disk resources. If the storage is also
used for purposes other than backups, NetBackup cannot manage disk pool capacity
or manage storage lifecycle policies correctly. Therefore, NetBackup must be the
only entity that uses the storage.

Re: MSDP creation error.

Below is log:

 

Wed 09/11/2019 15:51:14.35 Starting PDDE configuration
Wed 09/11/2019 15:51:14.60 Validating parameters...
Wed 09/11/2019 15:51:14.63 Parameters used:
Wed 09/11/2019 15:51:14.63 STORAGE = "D:\NB Setup\MSDP"
Wed 09/11/2019 15:51:14.63 SPAID = 502
Wed 09/11/2019 15:51:14.63 SPALOGIN = netbackup
Wed 09/11/2019 15:51:14.63 SPALOGPATH = "D:\NB Setup\MSDP\log"
Wed 09/11/2019 15:51:14.63 SPALOGRETENTION = 90
Wed 09/11/2019 15:51:14.63 VERBOSELEVEL = "long",thread""
Wed 09/11/2019 15:51:14.63 INSTPATH = "C:\Program Files\Veritas\pdde"
Wed 09/11/2019 15:51:14.64 DBPATH = "D:\NB Setup\MSDP"
Wed 09/11/2019 15:51:14.64 HOSTNAME = Mymachine
Wed 09/11/2019 15:51:14.64 ENCRYPTION= false
Wed 09/11/2019 15:51:14.64 KMSENABLE = false
Wed 09/11/2019 15:51:14.64 KMSTYPE = 0
Wed 09/11/2019 15:51:14.64 KMSSERVERNAME =
Wed 09/11/2019 15:51:14.64 KEYGROUPNAME =
Wed 09/11/2019 15:51:14.64 KEYNAME =
Wed 09/11/2019 15:51:14.64 AWSREGION =
Wed 09/11/2019 15:51:14.64 AWSKEYID =
Wed 09/11/2019 15:51:14.64 AWSTOKEN =
Wed 09/11/2019 15:51:14.64 PROXYSERVER =
Wed 09/11/2019 15:51:15.05 Creating directories...
Wed 09/11/2019 15:51:15.11 Directory creation completed.
Wed 09/11/2019 15:51:15.12 Creating encryption conversion marker file...
Wed 09/11/2019 15:51:15.12 encryption conversion marker file creation completed.
Wed 09/11/2019 15:51:15.12 Configuring pdregistry.cfg...
The operation completed successfully.

Wed 09/11/2019 15:51:15.22 pdregistry.cfg configuration completed.
Wed 09/11/2019 15:51:15.25 Generating OpenSSL keys templates...
WARNING: can't open config file: /usr/local/ssl/openssl.cnf
Generating RSA private key, 1024 bit long modulus
....................++++++
...............++++++
unable to write 'random state'
e is 65537 (0x10001)
Wed 09/11/2019 15:51:15.36 Key templates generated, creating spoold certificate next...
1 file(s) copied.
1 file(s) copied.
WARNING: can't open config file: /usr/local/ssl/openssl.cnf
1 file(s) copied.
1 file(s) copied.
Wed 09/11/2019 15:51:15.45 Certificates generated and copied. OpenSSL step is done.
Wed 09/11/2019 15:51:15.45 Creating random seed...
WARNING: can't open config file: /usr/local/ssl/openssl.cnf
unable to write 'random state'
Wed 09/11/2019 15:51:15.48 Creating random seed...Done!
Wed 09/11/2019 15:51:15.48 executing "C:\Program Files\Veritas\pdde\spad.exe" --initdb...
Error: 9: initdb option requires spa login, password, storagepath
Wed 09/11/2019 15:51:15.51 spad.exe --initdb Complete!
Wed 09/11/2019 15:51:15.52 Executing spad self test...
Warning: 25002: __openReaderA: could not open file D:\NB Setup\MSDP\etc\puredisk\spa.cfg
Warning: 25002: __openReaderA: could not open file D:\NB Setup\MSDP\etc\puredisk\spa.cfg
Error: 25002:
BadValue : (none)
File : D:\NB Setup\MSDP\etc\puredisk\spa.cfg
Section : Paths
Entry : Storage
Reason : Expected a non-empty value.
Error: 25002:
BadValue : (none)
File : D:\NB Setup\MSDP\etc\puredisk\spa.cfg
Section : Logging
Entry : HistoryPath
Reason : Expected a non-empty value.
D:\NB Setup\MSDP\etc\puredisk\spa.cfg: 6 error(s)
Wed 09/11/2019 15:51:15.55 ERR: "C:\Program Files\Veritas\pdde\spad.exe" --test encountered an error.
Wed 09/11/2019 15:51:15.56 An error has occured while attempting to configure. Aborting...
Wed 09/11/2019 15:51:15.56 Stopping services...
Wed 09/11/2019 15:51:15.56 Stopping spad service...
Stopping service spad: done
Wed 09/11/2019 15:51:15.59 Stopping spoold service...
Stopping service spoold: done
Warning: 2: __openReaderA: could not open file D:\NB Setup\MSDP\etc\puredisk\contentrouter.cfg

Highlighted

Re: MSDP creation error.

Hi Marriane

My bad, I missed the basics. 
But I am amused to watch following logs, why it is looking UNIX path on my windows system:

 

The operation completed successfully.

Wed 09/11/2019 15:51:15.22 pdregistry.cfg configuration completed.
Wed 09/11/2019 15:51:15.25 Generating OpenSSL keys templates...
WARNING: can't open config file: /usr/local/ssl/openssl.cnf
Generating RSA private key, 1024 bit long modulus
....................++++++
...............++++++
unable to write 'random state'
e is 65537 (0x10001)
Wed 09/11/2019 15:51:15.36 Key templates generated, creating spoold certificate next...
1 file(s) copied.
1 file(s) copied.
WARNING: can't open config file: /usr/local/ssl/openssl.cnf
1 file(s) copied.
1 file(s) copied.
Wed 09/11/2019 15:51:15.45 Certificates generated and copied. OpenSSL step is done.
Wed 09/11/2019 15:51:15.45 Creating random seed...
WARNING: can't open config file: /usr/local/ssl/openssl.cnf
unable to write 'random state'

Also, here volume means physical disk or filesystem in UNIX/ Drive on windows ?

Re: MSDP creation error.

I've checked a pdde-config.log for NBU v8.1.1, and I see the same *nix style paths in the log file.  My MSDP is working fine.  The last line in my log file says "Script completed successfully!".  So, I guess those *nix style names are just a feature  Smiley Tongue

Re: MSDP creation error.

Hello,

 

just a guess - I think that the space in MSDP path ("...\NB Setup\...") could be the cause of this problem.

Agreed with Marianne that MSDP volume should be dedicated, but I think there is no "hard check" for it.

regards

Michal

Re: MSDP creation error.

I agree with youe point.

However I have also tried at root level of D drive like D:/MSDP, still same issue.

So I am assuming by volume in guide means Drive/file system.

But there is no such documentation.

Any suggestions ?

 

Accepted Solution!

Re: MSDP creation error.

Re: MSDP creation error.

Putting it on Win 2008 maybe not a good idea because when Microsoft Support ends so does NBU?  This configuration will only be valid for less than four months.   If this is going to be a permanent fixture I would upgrade the server before attempting anything more.

"On January 14, 2020, support for Windows Server 2008 and 2008 R2 will end."  See : https://www.microsoft.com/en-us/cloud-platform/windows-server-2008