It is a matter of knowing what the disk is being used for.
It depends on the Operating System and Application using the disk, if this [the OS & app] perform SCSI-3 Persistent Reservations then you need to set the bit (which is on by default in the latest code)
However, if the OS & app do not need SCSI-3 Persistent Reservations then it is no harm leaving it on.
So, IF:
- OS & app need it: ON (else you might impair functionality of OS & app)
- OS & app not need it: OFF or ON (it doesn't matter for functionality)
Hence we have chosen to have it on by default, as it does no harm.
It will only do harm when you turn it off and you need it....
HTH,
Edwin.
If this answer was useful, please "Mark as Answer" and "Like"
It was'nt a recommendation from the vendor but the delivery team want to understand the risks for disabling or enabling the PER and how to remediate against same risks.
EdwinVanMierlo
39 Posts
1570
0
Posted November 25th, 2014 01:00
Hi Steve,
It is a matter of knowing what the disk is being used for.
It depends on the Operating System and Application using the disk, if this [the OS & app] perform SCSI-3 Persistent Reservations then you need to set the bit (which is on by default in the latest code)
However, if the OS & app do not need SCSI-3 Persistent Reservations then it is no harm leaving it on.
So, IF:
- OS & app need it: ON (else you might impair functionality of OS & app)
- OS & app not need it: OFF or ON (it doesn't matter for functionality)
Hence we have chosen to have it on by default, as it does no harm.
It will only do harm when you turn it off and you need it....
HTH,
Edwin.
If this answer was useful, please "Mark as Answer" and "Like"