DAG member server will remain shutdown for longer period of time.

In my exchange 2010 environment, 3 exchange servers namely (server01, server02, server 03) are in DAG, 2 DAG member servers(server01, server 02)  are in primary site and 1 DAG member server(server 03) is in secondary site. Now storage team will perform upgrade work on the secondary site for that they advised us to shut-down the secondary DAG member server (server03) for 10 hours.
Usually when we perform exchange patching and maintenance activity we put exchange server in maintenance mode, and once tasks become completed then we put out DAG member server from the maintenance mode, and these tasks usually take 2 hrs. And whereby each DAG member servers remain in maintenance mode for 30 minutes, since the storage team is going to perform maintenance activity for at least 10 hrs. And we will have to shut-down secondary DAG member server (server 03) for 10 hrs. I would like to know is there any major impact while we put out the secondary DAG member server (server 03) from maintenance mode after 10 hrs. If so can you please advise for the steps to be followed, initially I am planning the following procedures:
Step 01: Putting the server03 which is in secondary site in maintenance mode:
C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\StartDagServerMaintenance.ps1 -serverName server03
Once the storage upgrade activity will be done, I will run the below command:
Step 02: Put server03 out of maintenance mode:
C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\StopDagServerMaintenance.ps1 -serverName server03
I am not going the redistribute DAG database performing the below command since in our DAG we have 4 databases and it is distributed across 2 primary nodes.
>.\RedistributeActiveDatabases.ps1 -DagName DAG -BalanceDbsByActivationPreference -ShowFinalDatabaseDistribution -Confirm:$false
Can you please advise on my understanding and above procedure and further guideline that I am missing for the activity.