My apologies, I should have added that. In my live environment, I have two servers: ziggurat - Master/Media RHEL4 obelisk - media RHEL4
For "DNS" I'm just relying on the /etc/hosts file as I'm only trying to recover 5 systems. The source system that I'm restoring from is not here, not have we built a replica on it. I'm trying to browse files that were backed up on server-A in my live environment and restore them to server-B here in the DR environment. I can browse down the directory tree, it just takes 20 minutes to do what I can do in 10 seconds in prod. I'm assuming it's trying to call out the server-A. I don't see why it should have to do that since the metadata for the restore files should be in the catalog here on my master server. -Thanks. - HKY On Wed, Feb 9, 2011 at 3:38 PM, Infantino, Joseph <jinfa...@harris.com> wrote: > What is the OS of the Master and Media server(s)? > Is DNS working "flawlessly?" > > Thank you, > > Joseph A. Infantino II > BackUp/Recovery Administrator > HARRIS IT Services > Assured Infrastructure Management > Office: 321-724-3011 | Fax: 321-724-3392 > Email: joseph.infant...@harris.com > > > > > -----Original Message----- > From: veritas-bu-boun...@mailman.eng.auburn.edu > [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Heathe Yeakley > Sent: Wednesday, February 09, 2011 4:24 PM > To: NetBackup Mailing List > Subject: [Veritas-bu] Backup Archive and Restore taking forever on DR server > > I'm at a DR exercise. I've installed, patched, configured NBU and > successfully imported a catalog. I'm in Backup, Archive Restore and > using the "Directory Structure" pane to drill down to the files I want > to restore. I'm restoring files to an alternate server than the one > where the original files were taken from. I've set the parameters for > source and destination and everything looks good. When I pull up my > list of available backups, the list takes like 5 minutes to pull up. I > select the policy I want to restore from and it takes like 5 minutes > to put the directory tree in the "Directory Structure" pane. I select > the icon next to root to expand root, and it takes like 5 minutes to > show me the next layer. > > You get the idea. On my master server back home, this process takes > seconds. Boom, boom, boom. I drill down select my file and go. > > Here I expand root, then 5 minutes later I expand /dirA, then 5 > minutes later I expand /dirA/dirB... > > I've been digging around for about 30 minutes to see if there's some > type of a timeout setting or something that's causing this. > > Have any of you seen this before? > > - Heathe Kyle Yeakley > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu