Hi all,
In a NetBackup 5.1 (MP5) environment (all Win2003 Server), we have a number of Media Servers recently exhibiting a strange problem with scheduled DSSU de-staging (duplication) to locally-attached tape.
When we set the DSSU "Manual Relocation" running (either manually or via a schedule), the parent process for the DSSU duplication begins quite happily, but a child process (duplication) never starts.
If we look at the Media Server involved, it creates the correct "bidfile", but eventually generates a Windows error on the Media Server - such as (Application popup: bpduplicate.exe - Application Error : The instruction at "0x0040e260" referenced memory at "0x00000000". The memory could not be "read").
We have investigated log files on Media and Master Server, gone through all Master Server Catalog images relating to that Media Server's clients. We have deleted and reloaded NetBackup on the Media Server, we have tried MP3, 4, 5 and 6 on the Media Server, and even changed out the physical RAM on the Media Server.
The strange thing is that if we run the Duplication from the Master Server (via Catalog / Duplication of individual images), all works just fine. Similarly, it we take the Media Server's generated "bidfile", then from the Master Server we run the manual "bpduplicate" command with this correct "bidfile", then that all works just great as well !
Seems to point to a problem at the Media Server side of things. Although the de-staging/duplication has been running happily on these Media Servers for about 18 months prior. And most of the other Media Servers on this same Master Server all run perfectly!
Has anyone seen such an issue - or have any suggestions on what additional log entries etc we may need to investigate ?
Thanks.