You need to recommend a solution to meet the technical requirements for email message recovery.
Which command should you include in the recommendation? (To answer, configure the appropriate options in the answer area.)
Hot Area:
Correct Answer:
Explanation/Reference:
Set-MailboxTransportService
Use the Set-MailboxTransportService cmdlet to view the transport configuration information for the Mailbox Transport service on Mailbox servers.
Example 1
This example sets the ReceiveProtocolLogPath parameter to C:SMTP Protocol LogsReceive.log for the Mailbox Transport service on server Mailbox01.
Set-MailboxTransportService Mailbox01 -ReceiveProtocolLogPath "C:SMTP Protocol LogsReceive.log"
Set-TransportConfig
Use the Set-TransportConfig cmdlet to modify the transport configuration settings for the whole Exchange organization.
EXAMPLE 1
This example configures the Exchange organization to forward all DSN messages that have the DSN codes
5.7.1, 5.7.2, and 5.7.3 to the postmaster email account.
Set-TransportConfig -GenerateCopyOfDSNFor 5.7.1,5.7.2,5.7.3
Set-TransportServer
Use the Set-TransportServer cmdlet to set the transport configuration options for the Transport service on Mailbox servers or for Edge Transport servers.
EXAMPLE 1
This example sets the DelayNotificationTimeout parameter to 13 hours on server named Mailbox01.
Set-TransportServer Mailbox01 -DelayNotificationTimeout 13:00:00
Set-TransportService
Use the Set-TransportService cmdlet to set the transport configuration options for the Transport service on Mailbox servers or for Edge Transport servers.
EXAMPLE 1
This example sets the DelayNotificationTimeout parameter to 13 hours for the Transport service on a Mailbox server named Mailbox01.
Set-TransportService Mailbox01 -DelayNotificationTimeout 13:00:00
-MaxDumpsterTime
This parameter isn’t used by Microsoft Exchange Server 2013. It’s only used by Microsoft Exchange 2010 servers in a coexistence environment.
-MessageExpirationTimeout
Not a parameter of Set-TransportConfig
-SafetyNetHoldTime
Parameter of Set-TransportConfig
The SafetyNetHoldTime parameter specifies how long a copy of a successfully processed message is retained in Safety Net.
Unacknowledged shadow copies of messages auto-expire from Safety Net based on adding the values of the SafetyNetHoldTime parameter and the MessageExpirationTimeout parameter on the Set-TransportService cmdlet.
To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds.
The default value is 2.00:00:00 or 2 days.
-ShadowMessageAutoDiscardinterval
The ShadowMessageAutoDiscardInterval parameter specifies how long a server retains discard events for shadow messages.
A primary server queues discard events until queried by the shadow server. However, if the shadow server doesn’t query the primary server for the duration specified in this parameter, the primary server deletes the queued discard events.
To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds.
Valid input for this parameter is 00:00:05 to 90.00:00:00. The default value is 2.00:00:00 or 2 days.
STEPS
1. Set-TransportConfig. Need to use Safety Net and this is a parameter of Set-TransportConfig
2. SafetyNetHoldTime Need to configure Safety Net.
How Safety Net Works
Safety Net can be considered to be having two parts- Shadow Redundancy and Safety Net Redundancy.
While the safety Net keeps a redundant copy of a message after it is successfully processed, shadow redundancy keeps a redundant copy of the message which is in transit. All features of shadow redundancy like transport high availability boundary, primary messages, primary servers, shadow messages and shadow servers will be applicable to Safety Net.
The Primary Safety Net is applicable for a Mailbox server that holds the primary message before the Transport service completely processes the message. Once the processing of the message is over, the primary server moves the message to the Primary Safety Net from the active queue on the same server.
The Shadow Safety Net is applicable to the Mailbox server which holds the shadow message. Once the shadow server receives the information that the primary server has successfully processed the primary message, the shadow message is moved to the shadow safety net from the shadow queue on the server. For the
Shadow Safety Net operation, shadow redundancy should be enabled, and shadow redundancy is enabled by default in Exchange 2013.
Set-TransportConfig: Exchange 2013 Help
Explanation/Reference:
Set-MailboxTransportService
Use the Set-MailboxTransportService cmdlet to view the transport configuration information for the Mailbox Transport service on Mailbox servers.
Example 1
This example sets the ReceiveProtocolLogPath parameter to C:SMTP Protocol LogsReceive.log for the Mailbox Transport service on server Mailbox01.
Set-MailboxTransportService Mailbox01 -ReceiveProtocolLogPath "C:SMTP Protocol LogsReceive.log"
Set-TransportConfig
Use the Set-TransportConfig cmdlet to modify the transport configuration settings for the whole Exchange organization.
EXAMPLE 1
This example configures the Exchange organization to forward all DSN messages that have the DSN codes
5.7.1, 5.7.2, and 5.7.3 to the postmaster email account.
Set-TransportConfig -GenerateCopyOfDSNFor 5.7.1,5.7.2,5.7.3
Set-TransportServer
Use the Set-TransportServer cmdlet to set the transport configuration options for the Transport service on Mailbox servers or for Edge Transport servers.
EXAMPLE 1
This example sets the DelayNotificationTimeout parameter to 13 hours on server named Mailbox01.
Set-TransportServer Mailbox01 -DelayNotificationTimeout 13:00:00
Set-TransportService
Use the Set-TransportService cmdlet to set the transport configuration options for the Transport service on Mailbox servers or for Edge Transport servers.
EXAMPLE 1
This example sets the DelayNotificationTimeout parameter to 13 hours for the Transport service on a Mailbox server named Mailbox01.
Set-TransportService Mailbox01 -DelayNotificationTimeout 13:00:00
-MaxDumpsterTime
This parameter isn’t used by Microsoft Exchange Server 2013. It’s only used by Microsoft Exchange 2010 servers in a coexistence environment.
-MessageExpirationTimeout
Not a parameter of Set-TransportConfig
-SafetyNetHoldTime
Parameter of Set-TransportConfig
The SafetyNetHoldTime parameter specifies how long a copy of a successfully processed message is retained in Safety Net.
Unacknowledged shadow copies of messages auto-expire from Safety Net based on adding the values of the SafetyNetHoldTime parameter and the MessageExpirationTimeout parameter on the Set-TransportService cmdlet.
To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds.
The default value is 2.00:00:00 or 2 days.
-ShadowMessageAutoDiscardinterval
The ShadowMessageAutoDiscardInterval parameter specifies how long a server retains discard events for shadow messages.
A primary server queues discard events until queried by the shadow server. However, if the shadow server doesn’t query the primary server for the duration specified in this parameter, the primary server deletes the queued discard events.
To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds.
Valid input for this parameter is 00:00:05 to 90.00:00:00. The default value is 2.00:00:00 or 2 days.
STEPS
1. Set-TransportConfig. Need to use Safety Net and this is a parameter of Set-TransportConfig
2. SafetyNetHoldTime Need to configure Safety Net.
How Safety Net Works
Safety Net can be considered to be having two parts- Shadow Redundancy and Safety Net Redundancy.
While the safety Net keeps a redundant copy of a message after it is successfully processed, shadow redundancy keeps a redundant copy of the message which is in transit. All features of shadow redundancy like transport high availability boundary, primary messages, primary servers, shadow messages and shadow servers will be applicable to Safety Net.
The Primary Safety Net is applicable for a Mailbox server that holds the primary message before the Transport service completely processes the message. Once the processing of the message is over, the primary server moves the message to the Primary Safety Net from the active queue on the same server.
The Shadow Safety Net is applicable to the Mailbox server which holds the shadow message. Once the shadow server receives the information that the primary server has successfully processed the primary message, the shadow message is moved to the shadow safety net from the shadow queue on the server. For the
Shadow Safety Net operation, shadow redundancy should be enabled, and shadow redundancy is enabled by default in Exchange 2013.
Set-TransportConfig: Exchange 2013 Help
