Netbackup 5.1 Unix Catalog import to Windows Netbackup platform

Hi Folks,
Apologies if this has been asked before, but is it possible to import a Netbackup 5.1 catalog which is sitting on a AIX 5.2/5.3 platform onto a Windows Netbackup xx platform?

Many thanks

7.1.x and Earlier

Backup and Recovery

NetBackup

Tip-How to

Even
16 years ago
This might help you.... my notes from a few years back.
- UNIX to WINDOWS NetBackup Master Convert - (PS pre NBU 6.0)

0. The new Windows master should/could have same hostname, just different IP during conversion.

1. Catalog backup.

2. Deactivate policies, ensure no starting jobs.

3. Logically move all tape media in the robot to "standalone" location.

4. Delete your Robot, Tapedrive and StorageUnit definitions, these are to reconfigured later.

5. Decompressed the catalog: bpimage -decompress -allclients

6. Cleaned up the catalog: /usr/openv/netb*/bin/bpimage -cleanup -allclients

7. Catalog backup. (VERY nice to have)

8. Stop all Netbackup deamons.

9. Convert the catalog from Binary to Ascii:
   # /usr/openv/netbackup/bin/cat_convert -o -s -b2a /usr/openv/netbackup/db/images

10. Use ex. FlashFXP to copy the catalog/database files the new server.
(Must have the capabilities of converting UNIX2DOS)

The following paths/files was transferred as ASCII files:

/usr/openv/volmgr/vm.conf
/usr/openv/volmgr/database/poolDB
/usr/openv/volmgr/database/ruleDB   (not found)

/usr/openv/netbackup/bp.conf
/usr/openv/netbackup/db/INDEXLEVEL   (not found)
/usr/openv/netbackup/db/IDIRSTRUCT
/usr/openv/netbackup/db/class/
/usr/openv/netbackup/db/client/          (not found)
/usr/openv/netbackup/db/config/behavior
/usr/openv/netbackup/db/images/

The following files was transferred as BINARY files:

/usr/openv/volmgr/database/volDB
/usr/openv/netbackup/db/media/mediaDB

11. Downed and turned off the UNIX server.

12. Ensure new Windows NetBackup Master have SAME master hostname.

13. Install NetBackup Master, patch to same level, (Catalogbackup)

14. Stop all Netbackup services.

15. Moved all files from the temporary directory to the new NetBackup installation.

16. If not able to replace/delete VolDB, set NBU services to manual, reboot.

17. cd C:\Program Files\VERITAS\NetBackup\db
cat_convert -o -s -a2b images

18. Deleted the client folder for the master server ...\netbackup\db\images.

19. Restarted the NetBackup services.

20. Controlled the catalog-backup, media-listings, volume manager, restore browsing etc.

21. opened bp.conf in notepad and manually pasted the configuration options thru the Master Server Host Properties dialog

22. Configured the robot and tape devices, and performed a Robot Inventory to update the media database.

23. Tested restore of "old" data on several servers, wich was found OK.

Mouse
Moderator
16 years ago

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

DOCUMENTATION: How to migrate the NetBackup catalog information from one platform to another (UNIX to Windows or vice versa), rename a Master Server, cluster an existing Master Server, or merge multiple NetBackup domains.

Details:

Manual:
NetBackup DataCenter 4.5 System Administrator's Guide for Windows, Page: N/A
NetBackup DataCenter 4.5 System Administrator's Guide for UNIX, Page: N/A
NetBackup 5.0 System Administrator's Guide, Volume I for Windows, Page: N/A
NetBackup 5.0 System Administrator's Guide, Volume I for Unix, Page: N/A
NetBackup 5.1 System Administrator's Guide, Volume I for Windows, Page: N/A
NetBackup 5.1 System Administrator's Guide, Volume I for UNIX, Page: N/A
NetBackup 6.0 System Administrator's Guide for Windows, Volume 1, Page: N/A
NetBackup 6.0 System Administrator's Guide for UNIX, Volume 1, Page: N/A
NetBackup 6.5 Administrator's Guide for Windows, Volume 1, Page: N/A
NetBackup 6.5 Administrator's Guide for UNIX and Linux, Volume 1, Page: N/A

Modification Type: Supplement.

Modification:
As the needs and requirements for a NetBackup environment change, it may be necessary to migrate the NetBackup catalog information from one Master Server or platform to another or to combine two or more NetBackup domains to form a single domain.

While migration and merging is possible, NetBackup Support does not have the necessary resources and experience to properly execute this process. NetBackup Support can assist in restoring the data back to the same original platform in the event of a failed attempt, but is not equipped to assist in these sorts of activities. To insure data integrity and seamless operation, operations of this type must be performed by Symantec Consulting Services.

Symantec Consulting Services have developed comprehensive methodologies to handle a variety of reconfiguration requirements including the following scenarios:

Merging of two or more domains

Splitting of a domain into two or more domains

Clustering of a non-clustered master server

Renaming of a Master Server

Moving a Master Server to a new machine involving a host name change

Moving a Master Server to a different platform/operating system

Un-clustering a clustered master server

Given the nature of the information stored in the NetBackup catalogs and the potential for data loss, the process of moving or merging the NetBackup catalogs from one platform to another without the assistance of Symantec Consulting Services is not supported by the NetBackup Support organization.

Symantec Consulting Services will assist customers by determining the correct approach to take, planning the activity and executing the plan successfully with minimum disruption to the operational environment.

Please contact a NetBackup Sales representative for assistance in engaging Symantec Consulting Services. Please note, a migration of this sort must be a part of a conscious, planned, and permanent transition, and should not be part of a disaster recovery process or any part of a disaster recovery plan.

With proper planning it's achievable, if you have NBU guru somewhere near you. But don't think that it can be simply done by dump/restore
Even
Level 5
16 years ago
This might help you.... my notes from a few years back.
- UNIX to WINDOWS NetBackup Master Convert - (PS pre NBU 6.0)

0. The new Windows master should/could have same hostname, just different IP during conversion.

1. Catalog backup.

2. Deactivate policies, ensure no starting jobs.

3. Logically move all tape media in the robot to "standalone" location.

4. Delete your Robot, Tapedrive and StorageUnit definitions, these are to reconfigured later.

5. Decompressed the catalog: bpimage -decompress -allclients

6. Cleaned up the catalog: /usr/openv/netb*/bin/bpimage -cleanup -allclients

7. Catalog backup. (VERY nice to have)

8. Stop all Netbackup deamons.

9. Convert the catalog from Binary to Ascii:
   # /usr/openv/netbackup/bin/cat_convert -o -s -b2a /usr/openv/netbackup/db/images

10. Use ex. FlashFXP to copy the catalog/database files the new server.
(Must have the capabilities of converting UNIX2DOS)

The following paths/files was transferred as ASCII files:

/usr/openv/volmgr/vm.conf
/usr/openv/volmgr/database/poolDB
/usr/openv/volmgr/database/ruleDB   (not found)

/usr/openv/netbackup/bp.conf
/usr/openv/netbackup/db/INDEXLEVEL   (not found)
/usr/openv/netbackup/db/IDIRSTRUCT
/usr/openv/netbackup/db/class/
/usr/openv/netbackup/db/client/          (not found)
/usr/openv/netbackup/db/config/behavior
/usr/openv/netbackup/db/images/

The following files was transferred as BINARY files:

/usr/openv/volmgr/database/volDB
/usr/openv/netbackup/db/media/mediaDB

11. Downed and turned off the UNIX server.

12. Ensure new Windows NetBackup Master have SAME master hostname.

13. Install NetBackup Master, patch to same level, (Catalogbackup)

14. Stop all Netbackup services.

15. Moved all files from the temporary directory to the new NetBackup installation.

16. If not able to replace/delete VolDB, set NBU services to manual, reboot.

17. cd C:\Program Files\VERITAS\NetBackup\db
cat_convert -o -s -a2b images

18. Deleted the client folder for the master server ...\netbackup\db\images.

19. Restarted the NetBackup services.

20. Controlled the catalog-backup, media-listings, volume manager, restore browsing etc.

21. opened bp.conf in notepad and manually pasted the configuration options thru the Master Server Host Properties dialog

22. Configured the robot and tape devices, and performed a Robot Inventory to update the media database.

23. Tested restore of "old" data on several servers, wich was found OK.
Mouse
Moderator
16 years ago
Did this migration couple of times using almost the same procedure...
Even
Level 5
16 years ago
And if anyone have done a 6.0/6.5 convert Unix -> Win .... or a "Win-Master-Out-Of-VCS"... let me know.

- The EMM can be moved around via another server, but are missing the cat_convert option -b2a in 6.0/6.5
(# /usr/openv/netbackup/bin/cat_convert -o -s -b2a )(love to try the 5.1 binary in a PA-Risc compatible later-HPuX.... but I have only 24 hours each day.)

- And for the Win-Master-Out-Of-VCS - think I've blown too many EMM-db's for a while. . . (symc: give us...)
iskanda
Level 2
16 years ago
Thanks for the help folks. Much appreciated.

Forum Discussion

Netbackup 5.1 Unix Catalog import to Windows Netbackup platform

Related Content

Netbackup Platform Base Limited licensing

Netbackup platform base, limited/complete edition

NetBackup Platform Base - Complete Edition Licensing

NetBackup Platform Base - Complete Edition Licensing / Metrics question

Netbackup Administrator Console