Getting ownership from replica
Normally, the replica server that owns some objects is the one to return (relinquish) the ownership to the master server when the objects are no longer needed on the replica. However, the administrators of the corresponding master servers also have means of returning the ownership to their respective sites.
Request ownership from replica
This command attempts to contact the replica server and perform a normal object relinquish process there. If the ownership of the object is on a secondary replica, then the execution is redirected there.
This is safer to perform than taking ownership—when requesting ownership, changes made on the replica cannot be lost.
To use this command:
-
Objects must be checked in on the replica server that owns the object.
-
All the replicas en route to the server that owns the object need to be running, and all the replica servers need to have a working Server public address defined in Update Settings.
-
The administrator's user account's user profile is assigned to the security policy Forcibly cancel checked out status and replica ownership for any object.
For more information on the Request and Relinquish commands, see Ownership.
Take ownership
This command sets the server where the command is executed as the owner of the object, without informing the replica server that used to own the object. When a replica server performs an update with this server, any possible changes the replica may have made to those objects after the previous update are lost.
To use this command:
-
The administrator's user account's user profile is assigned to the security policy Forcibly cancel checked out status and replica ownership for any object.
Note: The Take ownership command is disabled for documents.