Your configuration is not going to work as you believe.
The qualified next hop dosnt have the effect you think.
You will see in your configuration both routes with different configuration, under the "show route 184.108.40.206/24" you will see 1 active route (> route). Both will be used, but not at the same time because of your metric configuration.
But, the secondary route will never be used because have highest metric, and both have next hop under the same next hop network or interface. If interface goes down both routes will be hidden. If next hop interface remains up, only primary route (lowest metric) will be used, so you will not have a backdoor or backup route.
Also in the forwarding table (show route forwarding-table family inet destination-address 220.127.116.11/24" , the best metric route will be choosed as best path, so the lowest metric will be hidden and never used.
This way you dont have a backup route, only a cosmetic configuration that looks like to have both routes.
Your cisco configuration, dont use metric configuration, uses Administrative Distance. This is the same that Preference under Junos, but in your configuration you use Junos metrics.
If you want ot use only 1 route at the same time, and through same outgoing interface your configuration have to be more complex.
For example, as next hop will have to use some dynamically learned route through that next hop, and use the resolve option for your static routes.
With this configuration you dont need qualified next hop, and will work as you expected.
interface gigabitethernet 0/0
ip address 10.0.0.1 255.255.255.0
router ospf 1
network 10.0.0.0 0.0.0.255 area 0.0.0.0
! next hops 18.104.22.168 and 22.214.171.124 will be learnd through ospf and different ospf neighbors.
ip route 126.96.36.199 255.255.255.0 188.8.131.52 10
ip route 184.108.40.206 255.255.255.0 220.127.116.11 20
set interface ge-0/0/0 family inet address 10.0.0.1/24
set routing-options protocols ospf area 0.0.0.0 interface ge-0/0/0
set routing-options static route 18.104.22.168/24 next-hop 22.214.171.124 resolve
set routing-options static route 126.96.36.199/24 next-hop 188.8.131.52 resolve
For backup static routes, you have to be sure the primary route will be deleted from routing table. This is why it will be better to use a dynamic next hop under ethernet interfaces. The local ethernet could be up, but the next hop could be down and you will not detect this (a failing switch, port misconfiguration, trunk failure, etc). If not you will have to configure RPM, automation, etc, that will detect the next hop is not reachable and will modify the static route.
Under serial interfaces, frame relay, pos, etc. Usually when the next hop, or neighbor router is down, the local receives a "remote alarm" or some type of indication of the remote status, so local interface goes down.
Under ethernet, there is no this behaviour, you could not know if a next hop is active or not, so will always use the primary static route and will never use the backup route.
If you want to keep resources but have dynamic next hop, then could use rip, from each neighbor send only the next hop route (apply outgoing filtering), this way you will have a a better solution at the best price. Unlike ospf or any other protocol will not use memory or cpu.
I still follow you , but when you have an hub an spoke topology with at least Thousands of spokes it's less expensive (saying you have interfaces that are able to be monitored i.e. down) to use static route than to use a routing protocol.
I know that RIP is still an interesting protocol especially in that topology (hub and spoke).