unable to select and add drives of Quantum tape library
Hello, Recently I have installed a new Quantum Scalar i3 tape library with one robot, 3 drives, and 50 slots, I have attached the library configuration images, the problem is when I want to "Define New Storage Devices", Netbackup finds the robot and the drives under it but I am unable to select them and I get this error : The following robot(s) are enabled but do not have enabled drives configured. I have tried different drive topology connections (loop preferred, point to point, loop, and point preferred ).Solved6.6KViews0likes20CommentsRestore is failing with error code 2820
Hello Guys, I am trying to restore VM backup .This VM backup was taken when VM was powered-off. Now i am trying to restore this backup to its original location and getting the error code 2820. Restore job logs are attached too. if anybody can help or guide ?Solved5.7KViews0likes17CommentsError 8021: unable to validate the user or group
Hello Netbackup Team, I had a Master Server v8.1.2, When i Authenticate with an account of an AD i had no problems. This account is in an other AD and are in the Admin loacl group of the Master Server. I have upgrade it in v8.3.0.1, since when i log with the same account ihade the error: Error 8021: unable to validate the user or group Same thing with the 8.3 When i authenticate with the nbwebsvc account, all is ok. When i use the command line : vssat.bat authenticate -p user -d nt:<DomainAD> -b localhost:13783 the authentication failed (Unable to connect to Server) Have you an idea to help me ? Thx for help ^^3.1KViews0likes11CommentsMigration backup images of the one policy to another server
This policy is on the master server NBU 7.5.0.6. I want to migrate to another master server NBU 8.1.1. Now I created the new policy on the new master server. But I need saved backups images over the past months from the old server. How do I transfer them so that later I can restore data from them on a new server with this policy?3.1KViews0likes16CommentsError: bptm (pid=1136) cannot open file
Dear All, From past few days i am facing a problem with netbackup 8.1.2 ========= Jan 26, 2021 12:31:33 PM - begin writing Jan 26, 2021 12:37:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2) Jan 26, 2021 12:40:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2) Jan 26, 2021 12:43:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2) Jan 26, 2021 12:46:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2) Jan 26, 2021 12:49:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2) Jan 26, 2021 12:49:06 PM - Error bptm (pid=1136) cannot write image to media id LTO008, drive index 0, The request could not be performed because of an I/O device error. Jan 26, 2021 12:49:06 PM - Info bptm (pid=1136) EXITING with status 84 <---------- ============== Any idea how to fix this issue?Solved3KViews0likes11CommentsMSDP 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.5KViews0likes5CommentsMedia ID
Hi everyone/ I have a question and I would need your help. When I pull out the tape and insert new one after scanning it has been recognised but old media ID remain. In order to make backup job I have to change mediaID in accordance to barcode rule. old media ID is 3329L7 bar code LS3329L7 when I insert new tape old media remain as 3329L7 and new bar code is LS3331L7. How to match media ID and barcode in order to complete backup job? Thank you for your help in advance2.2KViews0likes13CommentsNBU services not starting on server reboot, following in-place upgrade of Windows from 2012 to 2019
NetBackup 9.0 (there was no 9.0 option in the 'Product Version' drop-down above) A few weeks ago I upgraded NetBackup from 8.0 to 9.0. It's been running fine since this. I don't know if a server reboot was performed after the upgrade - can't remember. Today, I've done an in-place upgrade of Windows Server, from 2012 R2 to 2019, which involved several reboots. After the in-place upgrade, at first, I couldn't get the NetBackup console to launch, until I had to manually start the 'Enterprise Media Manager' service. Then I could open the console, but couldn't get any new jobs that I launched to appear in the Activity Monitor. Until I manually started the 'Resource Broker' service. I've now rebooted the server a few times, and these two NetBackup services (possibly more that I haven't noticed) aren't starting automatically. Obviously their 'Startup Type' is still set to Automatic. Any ideas what might be wrong here? If I didn't reboot the server after the NetBackup 8.0 to 9.0 (can't remember if I did or not), then I have no real way of knowing whether this "services not starting on startup" problem is as a result of the NetBackup upgrade, or as a result of the Windows Server upgrade. If it's due to the Windows upgrade, does NetBackup need a 'repair' of some kind? Is that even possible? Thanks.1.9KViews0likes3Comments