11-28-2012 07:48 AM
I am running NetBackup 7.5.0.4 and I have completed a phase 1 import of a whole lot of BackupExec Tapes (35 tapes in total) using :
vmphyinv.exe -rn 0 -slot_range 1 45 -d hcart2
It completes the physical inventory and I have done an intiate import for each of the tapes that were inventoried.
If I run a report of "Images on Media" I get a whole lot back.
In the C:\Program Files\Veritas\NetBackup\db\images\ there are a whole lot of directories with the server names, though inside each of those directories are a whole lot of lck files that are 0kb in size.
If I try run an "Import" from the catalog tree (Phase 2) I get the error :
INF - Found no images matching the selection criteria that were ready for phase 2 import.
Has anyone come across this or can give me an idea what is going on.
Thanks
Solved! Go to Solution.
01-04-2013 03:10 PM
What came out was that actually NetBackup does NOT support encrypted tapes written in Backup Exec,
For what it's worth (and I'm sure you don't want to hear this and I apologise in advance), this was spelled out pretty plainly in the bullet list of what ISN'T supported in the previously linked Statement of Support:
Encrypted images are not supported
Unfortunately I don't think we were let on that these were encrypted images anywhere in this thread, so we weren't able to save you a couple months. Sorry again!
11-28-2012 09:03 AM
what version of backup exec were the tapes taken from?
There are a lot of restirctions - check the Admin Guide 1 for full details incase there is any incompatibility - Page 794 onwards in my copy
11-28-2012 02:24 PM
..or in this TechNote:
11-29-2012 12:19 AM
The version of Backup exec was 12. So looking at the docs it definitely looks like it is compatible.
The bpimport error is :
11-29-2012 06:02 AM
I did see one like this a while ago and seem to remember that it had been a glitch during the phase 1
On that occasion they cleared the temporary catalog files for that client and started again after which it worked
There can also be tape drive compatibility issues sometime (written to HP, read by IBM)
11-29-2012 07:36 AM
How do I clear the temporary catalog files ?
Do I have to then use the vmphyinv again ?
I am using the exact same library that was previously used to create the tapes, so there should be no hardware incompatibility.
11-29-2012 07:52 AM
if that client(s) have never been backed up by NetBackup then under netbackup\db\images the only thing in that clients folders should be the phase 1 import data - do check carefully though
The vmphysinv is not needed as the NBU volume database is up to date for that part - just the Phase 1 again
I assume that you definately do have all of the tapes involved? If any fragments were missing a phase 2 could not work
11-29-2012 07:57 AM
Ok so you mean delete all folders in there ? and remove all tapes from the library and re-inventory it ?
I initially used vmphysinv which is where the phase 1 details came from ?
should I have used the bpimport -create_db_info ?
11-29-2012 08:06 AM
Only delete the folder for the client to be restored (lpkcochg01.old.local) - and only if it has never been seen by NetBackup before otherwise you will delete its other known backups.
You do not need to remove the tapes - just do a phase 1 for the Backup Exec tapes via the catalog section of the admin console
11-30-2012 05:18 AM
To add to this I ran bpimport and it is starting to do phase 2 but it keeps erroring with :
11-30-2012 05:19 AM
I have started all from the beginning again as none of the tapes were importing and giving errors. All basically media read errors, which I find hard to believe seeing that these tapes have worked perfectly fine in the Backup Exec System a few weeks ago.
I had to do a vmphyinv first as the the tape GUID's would be different from just a normal inventory. Then I am doing the phase 1 import from the catalog section as suggested. All the backups are password protected, and the password seems to be fine since it seems to be completing the phase 1 imports on the tapes without any failures.
When I do a phase 2 import is there anything I need to make sure of if these backups are password protected ? Do I have to give NetBackup the password again for the phase 2 imports ?
Thanks
12-01-2012 01:14 AM
Ok after all of that it is still not working.
I have gone through the bptm log file and I can see this :
12-03-2012 07:18 AM
Now I think I have got a little further.
I think there is an issue with how NetBackup imports BackupExec Data from WORM tapes.
In the db/images directory under each of the servers that have been done under phase 2, there is a tmp directory. In that tmp directory is ALL the catalog files.
For some reason NetBackup does not add it to its database to complete the import for some reason.
Can someone please tell me how I will be able to import these individual catalog files ? Or moving them somewhere and firing off a command for NetBackup to update its DB ?
Thanks ....
Probably worth Symantec raising a bug report for this if they can.
01-04-2013 05:35 AM
Have you logged a Support call with Symantec?
Please let us know what the outcome was...
01-04-2013 05:49 AM
Hi Marianne,
I did end up raising a support call with symantec.
What came out was that actually NetBackup does NOT support encrypted tapes written in Backup Exec, which is really frustrating because I don't understand why the import process asks for the password initially used to create those encrypted backups in backup exec in the first place.
So now we have to restore the data to another location and re-back them up within netbackup.
Really poor on Symantec side to not have a way to export the key from backup exec and use it in NetBackup KMS if that is the case.
01-04-2013 03:10 PM
What came out was that actually NetBackup does NOT support encrypted tapes written in Backup Exec,
For what it's worth (and I'm sure you don't want to hear this and I apologise in advance), this was spelled out pretty plainly in the bullet list of what ISN'T supported in the previously linked Statement of Support:
Encrypted images are not supported
Unfortunately I don't think we were let on that these were encrypted images anywhere in this thread, so we weren't able to save you a couple months. Sorry again!
03-28-2018 08:27 PM