01-18-2016 04:55 AM
HI,
We have a Backup job with a Storage Pool as destination. In this storage pool we defined two usb disks:
On a regular base we exchange one usb-disk with the second one defined in the pool. But since we connected the psrv-bcp-01_USB1 back to the server, the disk appears with the following strange symbol (a strikethrough pencil) in Backup Exec and we can't write onto the disk anymore:
What should we do?
Thanks for any help.
Solved! Go to Solution.
02-01-2016 04:39 AM
You don't have to restart the services (or in fact even cancel a job that is waiting) , just open the properties of the device and change the limit to read only operations setting back to disabled.
The setting for how long to leave a disconnected device before making it read only won't change the status against a device that is already read only (assuming this is the setting you changed when up restarted the services)
01-18-2016 05:43 AM
How long has the disk been offline for as there is a setting to make the disk read only that is set automctailly if USB or RDX disks are detached for too long
Basically if you open up the properties of the disk there is a Limit Operations to Read Only setting somewhere and in the Backup Exec Server settings you can adjust the time period that controls when this change occurs.
01-18-2016 06:02 AM
...is your media server virtualised? If this is the case then accessing physical targets like USB disk and tape drives are not supported.
Block-based protocols like iSCSI are.
Thanks!
02-01-2016 01:47 AM
Hi guys,
@Craig: no its a physical server...
@Colin: Thanks for your answer. It seems to be that. But even if I disable this option and restart the BE services, the symbol (a strikethrough pencil) persists and I can't backup onto it.
What should I do?
Thanks for any help.
02-01-2016 03:22 AM
02-01-2016 04:39 AM
You don't have to restart the services (or in fact even cancel a job that is waiting) , just open the properties of the device and change the limit to read only operations setting back to disabled.
The setting for how long to leave a disconnected device before making it read only won't change the status against a device that is already read only (assuming this is the setting you changed when up restarted the services)