Catalog import from another Master server

[markdavies1978]

Hi Guys,

I have a catlog tape from 1 of my other sites (independent Master Server) which I hope to import into my Master Server.

I have gone through the initiate/import phase as per the instructions from the Netbackup Admin Guide but when using the Netbackup Restore application I would have expected to be able to add a source client from my other site & then select a point in time to restore data.

Have I missed a trick?

Thanks.

 

[markdavies1978]

No one have any advice?

Basically I need to restore Gigs of data from about 20 tapes & would like to know the best way to restore from these tapes.

Do I really need to catalog each & every tape???

 

[ericzhang]

Hi, Mark

for my point of view , I dont think you can just directly import the catalog tape to a different master server . I think I wont be work.

and I think you might need to import each of the 20 tapes .

Eric Zhang

 

[markdavies1978]

Ok.

Well another problem.

I have completed phase 1 of the import by running "initiate import" which works fine however, I'm unable to run an "import".

I receive the message "INF - Found no images matching the selection criteria that were ready for phase 2 import."

Any ideas?

I'm running Netbackup 6 on Windows Server 2003.

 

[MaineDCAdmin]

Doing a Google of "NetBackup Recovery without Import" yielded the following link:

http://www.symantec.com/connect/forums/recovery-without-import-fails

Looks like the forum link was done with NBU 6.5.4, so I'd lean toward the process outlined on the forum's page.

Not sure if this works with NetBackup 6.x, but I have used it with 5.1.


Pasted from <

http://seer.support.veritas.com/docs/266673.htm>

Document ID: 266673

http://support.veritas.com/docs/266673

E-Mail this document to a colleague
Recovery without Import
Details:
VERITAS now supports a method of recovering image information without having to import from a tape. There are some very important caveats; please carefully read the entire procedure before attempting it.

The goal of this document is to establish the procedure to allow for quicker recovery of a system or VERITAS NetBackup (tm) domain for backup tapes without importing the individual backup images. Implied in this procedure, is that the receiving site has a fully functional master. If this is being done as part of a disaster recovery plan, there are many other steps that are required and which must be addressed. This procedure is only intended to allow tapes to be moved between master servers.

There are many different ways to recover data on a different master than the one used for the original backups. Several of these methods are documented by consulting, and one method -- catalog replication using VERITAS Volume Replicator (tm) -- is being formalized in the near future. This document will give a specific procedure to follow along with the restrictions and caveats. This should allow customers to accomplish their goals in a manner that will be safe, reliable, and supported.

If data is being moved from one active NetBackup domain to another for recovery purposes only or being sent to a disaster recovery site, this procedure can be used. You must follow all the restrictions and caveats.

Restrictions:

1. All tapes being moved must have unique barcodes.
2. All client names must be unique.
3. None of the tapes being moved will be used for backups at the new location.
4. There exists a library at the new location to support the correct tape format.
5. Both masters must be running the same release of NetBackup.
6. Both masters must be of similar architecture (both UNIX or both Windows).

Procedure:

1. Perform a catalog backup on both masters. This will allow you to recover from any errors that might occur during this process.
2. Configure a special volume pool at the new site that will never be used for backups.
3. Setup barcode rules for the incoming tapes to put them in the special volume pool.
4. Ensure there are no active backups for the desired clients. One way to ensure this is to stop the NetBackup services/daemons on the master server.
5. Copy the desired client directories at the originating site. This would be the contents of /usr/openv/netbackup/db/images/<client name> or \Program Files\VERITAS\netbackup\db\images\<client name>.
7. You can now move the client data (tapes) and catalog data to the new site.
8. Merge the copied images into the catalog at the new location.
9. Put the tapes in the library at the new location.
10. To ensure none of the moved tapes can be overwritten, you might want to write-protect them.
11. Inventory the robot containing the moved tapes.
12. Put the appropriate FORCE_RESTORE_MEDIA_SERVER entry or entries in bp.conf. When you put this entry in bp.conf, you will need to recycle bprd.
13. If you moved primary copies of the tapes, then you are ready to restore. If you moved non-primary tapes, then you will need to change the primary copy for all the images being moved.

Caveats:

Since this procedure assumes you will not be using the moved tapes for backups, it did not require moving the volume database or the media database. If these tapes are to be returned to the original site, the image directory will not be gracefully cleaned up. When the image or images expire, they will be deleted from the image directory but there will be an error logged in the bptm log that states: "Could not find media ID xxxxxx in database, nothing to delete."

It would be advisable to delete the images from the catalog, preferably by removing the data when the restores are finished and the tapes are removed from the library. When you eject the tapes, you should also consider removing the entries from the volume database. If you want to permanently move the tapes and images, then you are looking at a master merge which is a documented service offered by VERITAS Enterprise Consulting Services.

To make this entire process more easily managed, it would be advisable to ensure that the policies are correctly configured on the originating master. Some things to consider are, having the target backups not multiplexed to ensure only the desired images are sent offsite. Also, directing the target backups to a specific unique volume pool should be done to make it easier to identify and track the required media. This will also ensure that only the desired images are taken offsite. If the originating site has multiple storage units, it would be easiest to define this special volume pool on one storage unit. Another way to achieve this would be to duplicate the images that are going to be sent to the new location using either Vault or bpduplicate and directing the duplicate images to a special volume pool. Careful planning in the configuration at the originating site can make this process work more smoothly.

Products Applied:
 NetBackup DataCenter 4.5
 NetBackup Enterprise Server 5.0
Last Updated: February 01 2005 08:01 PM GMT
Expires on: 03-16-2005

Subscribe to this document
Subjects:
 NetBackup DataCenter
   Application: How To, Informational
NetBackup Enterprise Server
   Application: How To, Informational
Languages:
 English (US)
Operating Systems:
Windows 2000
Advanced Server, Advanced Server SP1, Advanced Server SP2, Advanced Server SP3, Advanced Server SP4, Advanced Server Windows Powered, Advanced Server Windows Powered SP1, Advanced Server Windows Powered SP2, Advanced Server Windows Powered SP3, Advanced Server Windows Powered SP4, Datacenter Server, Datacenter Server SP1, Datacenter Server SP2, Datacenter Server SP3, Datacenter Server SP4, Professional, Professional SP1, Professional SP2, Professional SP3, Professional SP4, SAK, Server, Server SP1, Server SP2, Server SP3, Server SP4, Server Windows Powered, Server Windows Powered SP1, Server Windows Powered SP2, Server Windows Powered SP3, Server Windows Powered SP4

AIX
1.1.4, 2.1.4, 2.4, 2.5.1, 2.6, 24.2, 3.0, 3.1, 3.1.1, 3.1.2, 3.1.4, 3.1.5, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.5.1, 3.2.5E, 3.2s, 3.3.2, 3.4, 3.5, 3.5.1, 3.5.2, 3.6, 4.0, 4.0.2, 4.0.3, 4.0b, 4.1, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.4.0, 4.1.5, 4.1.5 sp2, 4.1.5.0, 4.1.x, 4.2, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.5, 4.25, 4.3, 4.3.0, 4.3.1, 4.3.1.0, 4.3.2, 4.3.2.0, 4.3.2.1, 4.3.3, 4.3.3.1, 4.3.3.10, 4.3.4, 4.31, 4.32, 4.4, 4.4.2, 4.5, 4.x, 5.1, 5.1 (32 bit), 5.1 (64 bit), 5.1-01, 5.1-02, 5.1ML03, 5.2, 5.3, 6.0, 6.2, 6.3, 6.4, 6.5

HP-UX
1.1.0, 10.00, 10.01, 10.01b, 10.02, 10.04, 10.05, 10.1, 10.11, 10.2, 10.2.0, 10.2/11.0, 10.20 / 11, 10.22, 10.230, 10.24, 10.30, 10.40, 10.x 11, 11.0, 11.0 32bit, 11.0 64bit, 11.0., 11.0/64bit, 11.01, 11.11, 11.20, 11.22, 11.30, 11.4, 11i v2 (PA-RISC), 2.0, 2.5, 2.5.1, 2.6, 2.7, 3.0, 3.2, 4.0, 4.1, 4.1.3, 4.1.4, 4.1.5, 4.2, 4.2.2, 5.6, 6.4, 8.0, 8.02, 8.05, 8.07, 8.09, 8.09.01, 8.7, 8.9.4, 9.00, 9.01, 9.02, 9.03, 9.04, 9.05, 9.07, 9.1, 9.10.01, 9.2, 9.3, 9.4, 9.5, 9.7.04.02

Solaris
2.3, 2.4, 2.4.1, 2.5, 2.5.1, 2.6, 7.0, 7.0 (32-bit), 7.0 (64-bit), 8.0, 8.0 (32-bit), 8.0 (64-bit), 9.0, 9.0 (32-bit), 9.0 (64-bit)

Windows NT
3.1 Server, 3.1 Workstation, 3.5 Server, 3.5 Workstation, 3.51 Server, 3.51 Server SP1, 3.51 Server SP2, 3.51 Server SP3, 3.51 Server SP4, 3.51 Server SP5, 3.51 Workstation, 3.51 Workstation SP1, 3.51 Workstation SP2, 3.51 Workstation SP3, 3.51 Workstation SP4, 3.51 Workstation SP5, 4.0 Server, 4.0 Server SP1, 4.0 Server SP2, 4.0 Server SP3, 4.0 Server SP4, 4.0 Server SP5, 4.0 Server SP6, 4.0 Server SP6a, 4.0 Workstation, 4.0 Workstation SP1, 4.0 Workstation SP2, 4.0 Workstation SP3, 4.0 Workstation SP4, 4.0 Workstation SP5, 4.0 Workstation SP6a

Windows Server 2003
DataCenter, DataCenter 64-bit, Enterprise 64-bit, Enterprise Server, Standard Server, Storage Server, Web Server

Citrix MetaFrame
1.8, XPe


VERITAS Software
350 Ellis Street
Mountain View, California 94043
World Wide Web:

http://www.veritas.com/,

Tech Support Web:

http://support.veritas.com/,

E-Mail Support:

http://seer.support.veritas.com/email_forms,

FTP: ftp://ftp.support.veritas.com/ or

http://ftp.support.veritas.com/

THE INFORMATION PROVIDED IN THE VERITAS SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. VERITAS SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL VERITAS SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF VERITAS SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
Was this article helpful to you?
Yes   No

If any information was unclear, or the information you were seeking was not provided, please let us know. Your feedback will help us improve this service.
(Enter comment here)
NOTE: Comments entered here will NOT receive a personal e-mail response. If you need a VERITAS Technical Support representative to respond to your issue, please click here to send us an e-mail.