Quantcast
Channel: Symantec conecta - Backup and Recovery - Discusiones
Viewing all articles
Browse latest Browse all 5780

Migrating NBU 7.1.0.4 from Solaris to RHEL 5.7

$
0
0
Necesito una solución

Hi All,

We've attempted to move our NBU 7.1.0.4 from a T2000 Sparc to a HP (intel based) RHEL 5.7. Below is the procedure we took.

* From the old solaris, we performed DB catalog backup and saved it to disk (shared NFS). Then, disconnected the old system from the network.

* Installed RHEL 5.7 in the new server. Used the same hostname and IP address.

* Installed NBU 7.1.0.4. Then, performed the catalog recovery. AFAIK, it went really smooth. In fact, the logfile (see excerpt below) and even in the activity monitor, it showed that the recovery was successful.

* The catalog size was almost, if not the same, as the CATDB backup/image files.

************************************************************************************************************************************

14:45:36 (2.001) Status of restore from copy 1 of image created Tue Apr  9 06:10:02 2013 = the requested operation was successfully completed

14:45:36 (2.xxx) INF - Status = the requested operation was successfully completed.

14:45:41 INF - Database restore started

Restore started Tue Apr  9 14:45:42 2013

14:45:42 (3.001) Restoring from copy 1 of image created Tue Apr  9 06:09:20 2013

14:45:43 (3.001) TAR STARTED 20821

14:45:44 (3.001) INF - Beginning restore from server mojito to client mojito.

14:45:46 (3.001) /opt/openv/db/staging/DARS_DATA.db

14:45:46 (3.001) /opt/openv/db/staging/DARS_INDEX.db

14:45:46 (3.001) /opt/openv/db/staging/DBM_DATA.db

14:45:46 (3.001) /opt/openv/db/staging/DBM_INDEX.db

14:45:47 (3.001) /opt/openv/db/staging/EMM_DATA.db

14:45:47 (3.001) /opt/openv/db/staging/EMM_INDEX.db

14:45:53 (3.001) /opt/openv/db/staging/NBAZDB.db

14:45:54 (3.001) /opt/openv/db/staging/NBAZDB.log.1

14:45:54 (3.001) /opt/openv/db/staging/NBDB.db

14:45:54 (3.001) /opt/openv/db/staging/NBDB.log.1

14:46:08 (3.001) /opt/openv/db/staging/databases.conf

14:46:08 (3.001) /opt/openv/db/staging/server.conf

14:46:08 (3.001) /opt/openv/db/staging/vxdbms.conf

14:46:08 (3.001) INF - TAR EXITING WITH STATUS = 0

14:46:08 (3.001) INF - TAR RESTORED 13 OF 13 FILES SUCCESSFULLY

14:46:08 (3.001) INF - TAR KEPT 0 EXISTING FILES

14:46:08 (3.001) INF - TAR PARTIALLY RESTORED 0 FILES

14:46:08 (3.001) Status of restore from copy 1 of image created Tue Apr  9 06:09:20 2013 = the requested operation was successfully completed

14:46:09 INF - Server status = 0

14:46:09 (3.xxx) INF - Status = the requested operation was successfully completed.

14:46:14 INF - Database recovery started

14:46:14 INF - Shutting down databases

14:46:14 INF - Moving database files from /usr/openv/db/staging

14:46:14 INF - Source /usr/openv/db/staging/EMM_DATA.db

14:46:14 INF - Destination /usr/openv/db/data/EMM_DATA.db

14:46:14 INF - Source /usr/openv/db/staging/DBM_DATA.db

14:46:14 INF - Destination /usr/openv/db/data/DBM_DATA.db

14:46:14 INF - Source /usr/openv/db/staging/DARS_DATA.db

14:46:14 INF - Destination /usr/openv/db/data/DARS_DATA.db

14:46:14 INF - Source /usr/openv/db/staging/NBDB.db

14:46:14 INF - Destination /usr/openv/db/data/NBDB.db

14:46:14 INF - Source /usr/openv/db/staging/NBAZDB.db

14:46:14 INF - Destination /usr/openv/db/data/NBAZDB.db

14:46:14 INF - Source /usr/openv/db/staging/EMM_INDEX.db

14:46:14 INF - Destination /usr/openv/db/data/EMM_INDEX.db

14:46:14 INF - Source /usr/openv/db/staging/DBM_INDEX.db

14:46:14 INF - Destination /usr/openv/db/data/DBM_INDEX.db

14:46:14 INF - Source /usr/openv/db/staging/DARS_INDEX.db

14:46:14 INF - Destination /usr/openv/db/data/DARS_INDEX.db

14:46:14 INF - Applying transaction log:  /usr/openv/db/staging/NBDB.log.1

14:46:15 INF - Applying transaction log:  /usr/openv/db/staging/NBDB.log

14:46:15 INF - Applying transaction log:  /usr/openv/db/data/NBDB.log

14:46:15 INF - Applying transaction log:  /usr/openv/db/staging/NBAZDB.log.1

14:46:16 INF - Applying transaction log:  /usr/openv/db/staging/NBAZDB.log

14:46:16 INF - Applying transaction log:  /usr/openv/db/data/NBAZDB.log

14:46:16 INF - Creating /usr/openv/db/data/vxdbms.conf

14:46:16 INF - Creating /usr/openv/var/global/server.conf

14:46:16 INF - Creating /usr/openv/var/global/databases.conf

14:46:16 INF - Starting up databases

14:46:19 INF - Database recovery successfully completed

14:46:19 INF - Recovery successfully completed

14:46:19 INF - Catalog recovery has completed.

14:46:19 WRN - NetBackup will not run scheduled backup jobs until NetBackup is restarted.

************************************************************************************************************************************

* We then proceeded to configure/change the new robotic path.

* All test backups as well as some "pre-selected" test restores went fine.

I thought everything went really smooth until the next morning when we receved a restore request from our user. Apparently, when we searched for the files (under backup, archive, and restore), it didn't list the files we were expecting. In fact, in some parts, it didn't show anything. But when we check/search the catalog, we see a bunch of images. In the end, we ended up rolling back to our old server, which is just, disconnecting the new system and reconnecting the old one to our network. True enough, that when we searched for the same files in the old server, it listed them out as expected.

Any inputs or ideas on this? We plan to perform another cutover next week. By the way, the catalog size we'll dealing with is about 180GB.

Cheers,

Dennis

 

 

 


Viewing all articles
Browse latest Browse all 5780

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>