has catalog recovery method been changed on 7.5.0.6?

[FlyMountain]

Our Netbackup images (.f, /usr/openv/netbakcup/db/images) is around 800GB. Before when we need to restore on DR, we run "bprecover" and select "P", we will restore anything else except images (.f & hearer files). Then import the tapes we need. This old method save us a few hours to restore whole image database.

Looks started from 7.5.0.6,  "A PARTIAL catalog recovery includes the images directory containing the dotf files and staging of the NetBackup relational database (NBDB) for further processing".

Not sure what is the reason Symantec to make this change. Is there any way we can run the old way?

Here is my real plan for DR recovery. (1. recover all relational databases, configurations but without /usr/openv/netbackup/db/images 2. manually copy selected /usr/openv/netbackup/images 2. restore for my selection)

[revarooo]

When you say changed on 7506 compared to which version?

[mph999 · Accepted solution]

I'm guessing prior to 7.5, as nothing has really changed until 7.5

The header file (the file in images with thesame name as the .f file, but without the .f) is now migrated into NBDB, for performance reasons.

They can be exported (cat_export) to the old format, but this is only for viewing really (you can import them as well, but it can get messy).

[mph999]

Looking at this again, the only change is the header files are now on nbdb, so all of them get recovered as part of the relational database ....

So, can't you just continue as normal, but just copy back the required.f files, as the header files are effectively there already.

Apologies if of have misunderstood ...

[Marianne]

It actually started with 7.5 and is well documented in the 7.5 Upgrade Guide.

[FlyMountain]

Thanks all for your information. I may not explain my problem clearly.

I remember on 7.1, we can use "bprecover -wizard" with "Partial" restore option to recover relational dadabase and configuration files only, leave all image files alone.

From 7.5. looks i cannot do it any more. Here is the output.

[root@MVLABFS02 admincmd]# more /usr/openv/netbackup/version
HARDWARE LINUX_RH_X86
VERSION NetBackup 7.5.0.6
RELEASEDATE Mon Jun 10 21:08:59 CDT 2013
BUILDNUMBER 20130610

[root@MVLABFS02 admincmd]# ./bprecover -wizard

Welcome to the NetBackup Catalog Recovery Wizard!

Please make sure the devices and media that contain catalog disaster recovery
data are available
Are you ready to continue?(Y/N)
y

Please specify the full pathname to the catalog disaster recovery file:
/DATA/catalog_1425489730_FULL
MVLABFS02.chsli.org_1425489730
All media resources were located

Do you want to recover the entire NetBackup catalog? (Y/N)
n

A PARTIAL catalog recovery includes the images directory containing the dotf files
and staging of the NetBackup relational database (NBDB) for further processing.

Do you also want to include policy data?(Y/N)
y

Do you also want to include licensing data?(Y/N)
y

Catalog recovery is in progress. Please wait...
Completed successful recovery of NBDB in staging directory on MVLABFS02.chsli.org

This portion of the catalog recovery has completed.
Because this was a PARTIAL recovery of the NetBackup catalog,
any remaining files included in the catalog backup can be restored
using the the Backup, Archive, and Restore user interface.

The image metadata that is stored in NBDB in the staging directory
can be exported using "cat_export -staging", and, imported using "cat_import".

The "nbdb_unload -staging" command can be used to unload one or more
database tables from NBDB in the staging directory.

The "nbdb_restore -recover -staging" command can be used to replace
NBDB in the data directory with the contents from the staging directory.

WRN - NetBackup will not run scheduled backup jobs until NetBackup is restarted.

For more information, please review the log file:
/usr/openv/netbackup/logs/user_ops/root/logs/Recover1425655685.log
[root@MVLABFS02 admincmd]#

[FlyMountain]

This is the output from 7.1.

[root@MVLABFDS01 ~]# more /usr/openv/netbackup/version
HARDWARE LINUX_RH_X86
VERSION NetBackup 7.1
RELEASEDATE Thu Feb 03 18:02:17 CST 2011
BUILDNUMBER 20110203
[root@MVLABFDS01 ~]# /usr/openv/netbackup/bin/admincmd/bprecover -wizard

Welcome to the NetBackup Catalog Recovery Wizard!

Please make sure the devices and media that contain catalog disaster recovery
data are available
Are you ready to continue?(Y/N)
y

Please specify the full pathname to the catalog disaster recovery file:
/apps/DATA/catalog_1425659675_FULL
MVLABFDS01_1425659675
All media resources were located

To recover the FULL catalog including the relational database (NBDB), select (F),
to recover the PARTIAL catalog including only the NetBackup catalog image
and configuration files as designated by the disaster recovery file, select (P), or
to recover only the RELATIONAL database (NBDB), select (R).
p

Catalog recovery is in progress. Please wait...
INF - Catalog recovery has completed.
WRN - NetBackup will not run scheduled backup jobs until NetBackup is restarted.

For more information, please review the log file:
/usr/openv/netbackup/logs/user_ops/root/logs/Recover1425659915.log
[root@MVLABFDS01 ~]#

[Marianne]

We understand your issue perfectly. Image headers were moved as from 7.5 into Emm database. All well documented. Partial recovery now needs to extract these headers from Emm portion of the catalog backup which need to be imported afterwards as per above output.

[FlyMountain]

I still didn't get the solution what i need for my coming DR :(

May be i should ask another way.

Is that possible to back up catalog for selected time frame instead of entire history?

Like i explained, our catalog image is around 800G, we don't want to restore the entire folder "/usr/open/netbackup/db/images" for a few selected restore request for our DR drill.

[revarooo]

800gb shouldn't take a massive amount of time to recover

[mph999]

No, not possible.

If you recover NBDB Relational DB only, this will give you back all the header files for all backups, but these are small, so you have some you don't need, but that is no issue.

You can then set the BAR GUI to policy type nbu-catalog, and browse the catalog backup like a normal backup, and select to restore the images data for the clients you want to tun restores for.

Eg.

/usr/openv/netbackup/db/images/client1

/usr/openv/netbackup/db/images/client5

Martin

[FlyMountain]

Thanks Martin.

I am also thinking we may make a DR only catalog backup to make the DR testing quicker and simpler. (archive and remove catalog images, run a DR catalog backup, then restore back the archived images after DR catalog backup).

does it make sense?

[Marianne]

You can also have a look at 'Recovery Without Import' where you can copy across selected folders along with cat_export. 

See: http://www.symantec.com/docs/TECH28722

[mph999]

You could, but to be honest, I'd avoid playing with a catalog as much as possible, it's the most important thing you have.