Hello, I am trying to recover a NetBacukp catalog from an old server on a new one with another OS but same name and different IP address.
I get the following error, when I chose the NetBackup Catalog Recovery Wizard right after successful installation of NetBackup 8.2 to a Windows Server 2016 virtual machine.
The output of the log D:\Veritas\NetBackup\logs\user_ops\SERVERNAME\Administrator\logs is only 2 bytes in size.
Any idea?
Hey, looks like ...
backup-st2008_1707942111_C1_TIR
... is missing in ...
C:\OLD_SERVER\DR_BACKUP
Good luck!
I have similar issue, not able to do restore and it is test environment and no support with netbackup.
I did backup to basic disk moved the files and DR files and rebuild the master server with DR option.
I am admin of the system and I have full access to C:\OLD_SERVER\DR_BACKUP already but it does not help.
Feb 26, 2024 1:22:44 PM - Critical bpdm (pid=1672) image open failed: error 2060013: no more entries
Feb 26, 2024 1:22:44 PM - Error bpdm (pid=1672) ERR - Cannot open TIR file C:\OLD_SERVER\DR_BACKUP\backup-st2008_1707942111_C1_TIR.
media open error (83)
Ok, I got a lot of things in place, attached a new VMware vCenter to this new Master Server and tried to restore a virtual machine, but it failed telling me ...
NetBackup VMware policy restore error (2820)
Before decommissioning the old Master Server a colleague of me deleted a lot of policies no longer used and only a handful of policies left over. The backup of the selected VM was done with a policy, which no longer exists, even with recovering the catalog.
Do I need to recreate a policy, when it no longer exists to restore a virtual machine into a VMware vCenter environment? Sounds strange to me.
Further note: I must admit this is still a virtual machine and all those tape devices and physical Media Servers (reconfigured by recovering the catalog) do no longer exist. I have to re-create a new tape device configuration for a much smaller tape library, as the original bigger tape library also no longer exists. So this Master Server will be also Media Server in one machine, when this whole environment will be re-installed on a physical server. NetBackup even tells me, which tape media is necessary to restore the virtual machine, but of course NetBackup has no access to this tape media currently, as the new server is only a virtual machine and the old physical media servers no longer exist.
Sorry, I could not read your last post. I had to copy your text and convert it into audio :p
*********************************************************************
Seriouly, after many tests this is the first time the catalog was successfully recovered. Now, I can write my own docu and continue with tape drives, so that I will be able to recover VMs into my hypervisor environment.
So far I learned ...
0) Open your eyes or clean your glasses and make sure directory names are correct ;)
1) Using the same server name as the old server is helpful
2) Using the same NetBackup <installdir> as on the old server is helpful
In former tests I used a different server name but also named the old server in the local HOSTS file, but I also installed NetBackup in the default path and tried to trick the 'NetBackup Catalog Recovery Wizard' by manually creating the d:\veritas\netbackup\db\images path etc.
I will have some more tests now but nevertheless thanks for pointing me in the right direction.
Appreciated.
Hello quebek,
Well NBU is not trivial thing :) I know ;)
so this file do exist, right?
E:\NBU_Catalog_Backup\desg-dc2wi195_1635493171_C1_TIR
My bad! The directory name was wrong (_Backup was missing). I must have been blind! So no ACL problems ;)
The catalog restore is working currently. Last time I did this test, it didn't finish though. Let's see, what happens this time.
Hey
yea put your glasses on ;) hahaha
good luck...
Does this say anything to you?
Aug 25, 2022 2:45:22 PM - Info bpdm (pid=4984) started
Aug 25, 2022 2:45:22 PM - started process bpdm (pid=4984)
Aug 25, 2022 2:45:22 PM - Info bpdm (pid=4984) reading backup image
Aug 25, 2022 2:45:23 PM - Critical bpdm (pid=4984) sts_get_lsu_prop_byname on LSU E:\NBU_Catalog_Backup failed: 2060013 no more entries
Aug 25, 2022 2:45:23 PM - Critical bpdm (pid=4984) Invalid storage device: E:\NBU_Catalog_Backup no more entries
Aug 25, 2022 2:45:23 PM - Critical bpdm (pid=4984) failure to open disk at path E:\NBU_Catalog_Backup: plug-in reports error 2060013
Aug 25, 2022 2:45:23 PM - Error bpdm (pid=4984) ERR - Cannot open TIR file E:\NBU_Catalog_Backup\desg-dc2wi195_1635493171_C1_TIR.
media open error (83)
Do I need to configure anything in advance, before I can restore the catalog? Why is this so complex? I have the catalog and dr files and according to the 'NetBackup Catalog Recovery Wizard' I have all media resources as the wizard reports ...
OLDSERVERNAME_1635493171
All media resources were located
Well NBU is not trivial thing :)
so this file do exist, right?
E:\NBU_Catalog_Backup\desg-dc2wi195_1635493171_C1_TIR
If so why we see this
ERR - Cannot open TIR file
ACL ?? try to all everyone RW to this folder and its children...
Again open a case... they should be able to jump on zoom session with you and possibly sort it out within minutes ;)
one more to do - add to etc\hosts entry for this box its IP and its hostname - as it was in original setup (hostname only you said IP did change) so like this
current_IP oldhostname oldhostname_fqdn
How can that be? ACLs missing? I am local administrator to that machine, it is not part of any domain, it's just workgroup!
Interesting - looks like basic disk
maybe there are some missing ACLs for this folder... not sure...
Open a case with VRTS.
Furthermore, what does it mean, when the 'NetBackup Catalog Recovery Wizard' reports ...
OLDSERVERNAME_1635493171
All media resources were located
Does it mean, that catalog files and dr files are complete and ready for Recovery?
Loglevel is at 5 now!
Hello quebek,
this is an excerpt of the dr file ...
# FRAG: c# f# K rem mt den fn id/path host bs off md dwo f_flags desc exp mpx rl chkpt rsm_nbr seq_no media_subtype keep_date copy_date fragment_state data_format slp_index_num resumable expiration_count copy_type
FRAGMENT 1 -1 9534 494 0 0 0 E:\NBU_Catalog_Backup\OLDSERVERNAME_1635493171_C1_TIR OLDSERVERNAME 1048576 0 0 -1 0 OLDSERVERNAME 0 0 0 0 0 0 1 0 0 1 0 0 0 1 0
FRAGMENT 1 1 51200000 0 0 0 0 E:\NBU_Catalog_Backup\OLDSERVERNAME_1635493171_C1_F1 OLDSERVERNAME 1048576 0 0 -1 0 OLDSERVERNAME 1636097971 0 65536 0 0 0 1 0 1635494147 1 1 0 0 0 0
FRAGMENT 1 2 25816005 0 0 0 0 E:\NBU_Catalog_Backup\OLDSERVERNAME_1635493171_C1_F2 OLDSERVERNAME 1048576 0 0 -1 0 OLDSERVERNAME 0 0 0 0 0 0 1 0 0 1 0 0 0 1 0
#DR_MEDIA_REC: ver rtype mtype host c# p# policies# policies kbytes nimg vimg hsize off subtype client_type sched_type run_time id/path frag_id media_desc bcode den
DR_MEDIA_REC 1 0 0 OLDSERVERNAME 1 1 0 0 0 0 0 0 1 35 0 1635493171 E:\NBU_Catalog_Backup\OLDSERVERNAME_1635493171_C1_F2 OLDSERVERNAME *NULL* 0
DR_MEDIA_REC 1 0 0 OLDSERVERNAME 1 1 0 0 0 0 0 0 1 7 0 1635493146 E:\NBU_Catalog_Backup\OLDSERVERNAME_1635493146_C1_F1 OLDSERVERNAME *NULL* 0
DR_MEDIA_REC 1 0 0 OLDSERVERNAME 1 1 0 0 0 0 0 0 1 35 0 1635493171 E:\NBU_Catalog_Backup\OLDSERVERNAME_1635493171_C1_F1 OLDSERVERNAME *NULL* 0
DR_MEDIA_REC 1 0 0 OLDSERVERNAME 1 1 0 0 0 0 0 0 1 35 0 1635493171 E:\NBU_Catalog_Backup\OLDSERVERNAME_1635493171_C1_TIR OLDSERVERNAME *NULL* 0
