MSDP Down
Hello Community, We had a OS Upgrade on a Master Server on Win2008 to change it to 2019. It also had an MSDP Pool on F Drive. After Clean 2019 install and Netbackup Master Server 8.2 Setup and Catalog Recovery. We followed Process to reconnect MSDP Pool to Netbackup . https://www.veritas.com/content/support/en_US/doc/25074086-130388296-0/v33188054-130388296 However, we see below in SPAD logs. What Certificate we should look at ? We updated policies for backups to not to go to disk and changed to go to tape . They are backing up and connecting fine, so master server certificate seems ok, Not sure what certificate its talking about, Appreciate any help. ======================================== March 02 02:06:50 INFO: set entire process max log size to 0 March 02 02:06:50 INFO: set entire process max log size to 0 March 02 02:06:50 INFO: CR mode in spa db is normal ! March 02 02:06:50 INFO: Startup: loading configuration from F:\MSDP\etc\puredisk\spa.cfg March 02 02:06:50 INFO: get key from file F:\MSDP\var\keys\auth.key. March 02 02:06:50 INFO: : extended attribute support disabled March 02 02:06:50 INFO: get key from file F:\MSDP\var\keys\auth.key. March 02 02:06:50 INFO: Manager thread stack size: 0 bytes March 02 02:06:50 INFO: Task thread stack size: 0 bytes March 02 02:06:50 INFO: Max DO size: 335544320 bytes March 02 02:06:50 INFO: Fibre Channel configuration is empty. March 02 02:06:50 INFO [000002DB23E29910]: set entire process max log size to 10000000 March 02 02:06:50 INFO [000002DB23E29910]: set entire process max log size to 10000000 March 02 02:06:50 INFO [000002DB23E29910]: Startup: occurred at Tue Mar 2 02:06:50 2021 March 02 02:06:50 INFO [000002DB23E29910]: Successfully loaded configuration from F:\MSDP\etc\puredisk\spa.cfg March 02 02:06:50 INFO [000002DB23E29910]: Startup: 1854: MD5 passwd disabled March 02 02:06:50 INFO [000002DB23E29910]: Encrypted passwords match encryption keys. March 02 02:06:50 INFO [000002DB23E29910]: FIPS mode not ENABLED March 02 02:06:50 INFO [000002DB23E29910]: Startup: Instant Data Access is not enabled March 02 02:06:50 INFO [000002DB23E29910]: Startup: spad type is master March 02 02:06:50 INFO [000002DB23E29910]: Startup: master spad url is March 02 02:06:50 INFO [000002DB23E29910]: Startup: Veritas PureDisk Storage Pool Authority Version 12.0000.0019.0624. March 02 02:06:50 INFO [000002DB23E29910]: Startup: using Veritas: libdct 6.0.0.0, July 7, 2004 March 02 02:06:50 INFO [000002DB23E29910]: Startup: using Veritas PureDisk: libcr 6.1.0.0, December 13, 2006 March 02 02:06:50 INFO [000002DB23E29910]: Startup: upgrade of spa DB skipped March 02 02:06:50 INFO [000002DB23E29910]: Memory Manager: initializing March 02 02:06:50 INFO [000002DB23E29910]: Memory Manager: initialization complete March 02 02:06:50 INFO [000002DB23E29910]: Sched Manager: initializing March 02 02:06:50 INFO [000002DB23E29910]: schedule string for QueueProcess: [20 */12 * * *] March 02 02:06:50 INFO [000002DB23E29910]: alert time for QueueProcess is 21600 March 02 02:06:50 INFO [000002DB23E29910]: lifecycle for QueueProcess is 32400 March 02 02:06:50 INFO [000002DB23E29910]: schedule string for RepOrphan: [*/10 * * * *] March 02 02:06:50 INFO [000002DB23E29910]: alert time for RepOrphan is 300 March 02 02:06:50 INFO [000002DB23E29910]: lifecycle for RepOrphan is 600 March 02 02:06:50 INFO [000002DB23E29910]: schedule string for CatalogBackup: [40 3 * * *] March 02 02:06:50 INFO [000002DB23E29910]: alert time for CatalogBackup is 21600 March 02 02:06:50 INFO [000002DB23E29910]: lifecycle for CatalogBackup is 32400 March 02 02:06:50 INFO [000002DB23E29910]: schedule string for CRStats: [0 * * * *] March 02 02:06:50 INFO [000002DB23E29910]: alert time for CRStats is 300 March 02 02:06:50 INFO [000002DB23E29910]: lifecycle for CRStats is 600 March 02 02:06:50 INFO [000002DB23E29910]: Sched Manager: initialization complete March 02 02:06:50 INFO [000002DB23E29910]: PD_Replication: initializing March 02 02:06:50 INFO [000002DB23E29910]: PD_Replication: initialization complete March 02 02:06:50 INFO [000002DB23E29910]: Task Manager: initializing March 02 02:06:50 INFO [000002DB23E29910]: Task Manager: seeding random number generator March 02 02:06:50 INFO [000002DB23E29910]: Task Manager: initializing DCT Content Routing (TM) March 02 02:06:50 INFO [000002DB23E29910]: _crConfigLoadA: Set the CR context use NBU CA. March 02 02:06:50 INFO [000002DB23E29910]: Task Manager: initialization complete March 02 02:06:50 INFO [000002DB23E29910]: Connection Manager: initializing March 02 02:06:50 INFO [000002DB23E29910]: Connection Manager: initialization complete March 02 02:06:50 INFO [000002DB23E29910]: Catalog auto recovery is enabled. March 02 02:06:50 INFO [000002DB23E29910]: Catalog backup version count: 5, shadow pool size: 64 March 02 02:06:50 INFO [000002DB23E29910]: Catalog backup shadow path: F:\MSDP\databases\catalogshadow March 02 02:06:50 INFO [000002DB23E29910]: CatalogContext::get_storage_path: storage_path=F:\MSDP\data, storage_path_spa=F:\MSDP March 02 02:06:50 INFO [000002DB23E29910]: Startup: completed at Tue Mar 2 02:06:50 2021 March 02 02:06:50 INFO [000002DB23E29910]: set entire process max log size to 10000000 March 02 02:06:50 INFO [000002DB23E29910]: set entire process max log size to 10000000 March 02 02:06:50 INFO [000002DB23E29910]: Increasing maximum number of open files from 512 to 2048 March 02 02:06:50 INFO [000002DB23E29910]: History Manager: start [thread 000002DB24DCB320] March 02 02:06:50 INFO [000002DB23E29910]: Sched Manager: started [thread 000002DB24E9AFF0] March 02 02:06:50 INFO [000002DB23E29910]: DataCheck Manager: started [thread 000002DB24E9BA70] March 02 02:06:50 INFO [000002DB23E29910]: Task Manager: started [thread 000002DB2542D290] March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::SpaDBEventStorage::checkConsistency Starting consistency check March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::SpaDBEventStorage::checkConsistency Ending consistency check March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::SpaDBDSEventStorage::checkConsistency Starting consistency check March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::SpaDBDSEventStorage::checkConsistency Ending consistency check March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::EventManager::EventManager m_orig_dsid = 2 March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::EventManager::newEvent Adding new event. type:4, dsid:0 March 02 02:06:51 INFO [000002DB23E29910]: remove old record file F:\MSDP\databases\spa\database\eventproperties\1. March 02 02:06:51 INFO [000002DB23E29910]: NetBindAndListen: bound myself to <localhost>:10102 using IPv6 March 02 02:06:51 INFO [000002DB23E29910]: NetBindAndListen: bound myself to <localhost>:10102 using IPv4 March 02 02:06:51 INFO [000002DB23E29910]: Connection Manager: started March 02 02:06:51 INFO [000002DB23E29910]: Setting service status to running if service start March 02 02:06:54 INFO [000002DB24E9A730]: NBUAPI::GetSecurityProperties: synced security properties with master server 1, 0 March 02 02:07:24 ERR [000002DB24E9A730]: -1: CURLClient::Execute: failed to perform CURL session, error: Operation timed out after 30000 milliseconds with 0 bytes received March 02 02:07:24 ERR [000002DB24E9A730]: -1: NBUAPI::GetToken: curl error to access https://server.com:1556/netbackup/loginwithcert March 02 02:07:24 ERR [000002DB24E9A730]: -1: NBUAPI::ValidateHost: failed to get token March 02 02:07:24 ERR [000002DB24E9A730]: -1: validate_host_cert: validate the host server.com uuid 4393a0cd-e60f-4f37-bb3b-e3fc8bf42ce7 cert failed. March 02 02:07:24 ERR [000002DB24E9A730]: 25056: Agent at server.com certificate is invalid. ==================================================== Regards,Solved2.6KViews0likes5Comments
How to clean up storage on the DSU for puredisk linux storage (NBU 7.5.0.5)
Good day all, i'm scannign a DSU storage for a puredisk service on a media server for NBU 7.5.0.5 on Linux Redhat 5.6. I've found a lot of HISTORY/SEGMENTS/files very old, 4 or more years ago, occuping space. history/segments/2012-08-07 history/segments/2012-08-08 history/segments/2012-08-09 history/segments/2012-08-10 history/segments/2012-08-11 history/segments/2012-08-12 history/segments/2012-08-13 The retention time for this solution is 2 weeks, for all the backups, so a retention and an history older than, let's say, 1 month just to be fair, is a waste of time. How can i cleanup what's not more needed? Why still it preserves all the segments, without compression or delete them automatically? Thank you. Regards3.2KViews0likes6Comments
How to clean up storage on the DSU for puredisk linux storage (NBU 7.5.0.5)
Good day all, i'm scannign a DSU storage for a puredisk service on a media server for NBU 7.5.0.5 on Linux Redhat 5.6. I've found a lot of HISTORY/SEGMENTS/files very old, 4 or more years ago, occuping space. history/segments/2012-08-07 history/segments/2012-08-08 history/segments/2012-08-09 history/segments/2012-08-10 history/segments/2012-08-11 history/segments/2012-08-12 history/segments/2012-08-13 The retention time for this solution is 2 weeks, for all the backups, so a retention and an history older than, let's say, 1 month just to be fair, is a waste of time. How can i cleanup what's not more needed? Why still it preserves all the segments, without compression or delete them automatically? Thank you. Regards