I am up on current storage architecture, but I can think of a number of reasons why backup/restore could still be preferrable. For instance, can you attest to the speed an reliability of the connection between the two datacenters? In any event, most SANs will not replicate changes in real time, they create a journal of changes and transfer them at scheduled times. Realtime copies of SANs have multiple potential problems.
Then you have the issues of IP/DNS propagation. For instance, did they move IPs from one DC to the other? Did they change DNS entries? Potentially some of both? They need time to make sure that the routing tables update properly, DNS changes propagate and verify everything is working properly.
Perhaps there are coding changes that needed to be made and or other maintenance they are doing at the same time? If you have a nice large downtime window, it may be a good time to reoptimize db tables, etcetera and further improve performance.
On top of all that, they will want to double and triple check that everything is running smoothly. What is worse than a long maintenance window? FUBARing it and having to move back to the old hardware, dealing with customer support calls, etc.
One final note, since the servers are up already, is that I much perfer they say we will be down from 4am-4pm and get the servers up early rather than saying 4am-10am and then have to update 2-3 times that they are extending the downtime.