A cookie for anyone who can diagnose this...
File server running backup exec 2010 fully up to date
3 drives mapped to that file server via iSCSI initator
Whenever the backups take place it runs through all other remotely backed up tasks but once the backups hit the iSCSI storage it fails and this fills the event view for a few minutes:
Worth noting that H: and G: are the iSCSI volumes and B: is a volume on another storage device connected via standard SCSI cable direct.
After the "reset to device" error backup exec stops with the error, ejects the tape and we come in the next day to find the backups failed. The server continues to operate fine after the reset to device.
The server is a HP ML350 G5 running windows server 2008R2.
It was thought that AV was interfering so i've turned that off, no change.
One issue currently is that the server has a constantly hammered memory usage, maximum of 700mb free but normally hovvering around 300mb - ive taken in to consideration the "cached" "free" and "available" sections on task manager, they add up to about 700.
Could it be memory usage? any other ideas?
File server running backup exec 2010 fully up to date
3 drives mapped to that file server via iSCSI initator
Whenever the backups take place it runs through all other remotely backed up tasks but once the backups hit the iSCSI storage it fails and this fills the event view for a few minutes:
Worth noting that H: and G: are the iSCSI volumes and B: is a volume on another storage device connected via standard SCSI cable direct.
After the "reset to device" error backup exec stops with the error, ejects the tape and we come in the next day to find the backups failed. The server continues to operate fine after the reset to device.
The server is a HP ML350 G5 running windows server 2008R2.
It was thought that AV was interfering so i've turned that off, no change.
One issue currently is that the server has a constantly hammered memory usage, maximum of 700mb free but normally hovvering around 300mb - ive taken in to consideration the "cached" "free" and "available" sections on task manager, they add up to about 700.
Could it be memory usage? any other ideas?