> Does anyone know if they made any changes to how DSU's are
> utilized in 6.5.1 ?
> 
> We recently upgraded to NBU 6.5.1.  That is the only
> difference in our backup environment.  The hardware,
> network settings, policies and schedules are all exactly
> the same as our 6.0 MP4 setup.  Everything was imported
> via full catalog restore. 

What was your process?  You seem to be saying you upgraded [from 6.0MP4]
to 6.5.1, then restored or in some way imported your [old?] catalog.
Unless I missed the memo, that isn't the correct process.  AFAIK,
NetBackup has never supported restoring/importing/whatevering an older
catalog version into a release.  You can 

o  upgrade NetBackup to the new version and run on it

o  backup the catalog and recover it to a NetBackup system of the same
version, then upgrade that new system to the new release of NetBackup

o upgrade the current NetBackup version in place, backup the upgraded
catalog and recover it to a system running the new release of NetBackup

You probably already know that.  Can you clarify what process you used
to get to 6.5.1?

> We send all of our backups to 2 Data Domain disk storage
> devices which then replicate to our DR site.
> 
> Since the 6.5.1 upgrade, huge swathes of our backups have
> been sitting queued until their backup window closes before
> returning a 196.  We don't really want to start playing
> around with the schedules as they were working just fine
> prior to the upgrade.  We are looking into the Open Storage
> option (OST) but this is more from the point of view of
> adding additional functionality rather than bringing 6.5.1
> up to par with 6.0 when using disk storage !!
> 
> Does anyone have any ideas on what might have changed
> regarding policy execution, job scheduling or NBU's handling
> of disk Storage that could be causing this new and very
> annoying issue ?  


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu