Azure SQL Database backups, PITR and LTR with Failover Groups

Let’s say I have two Azure SQL DB servers which participate in a failover group (one server in east, the primary, and the other in west, the read-only secondary). There are roughly a dozen databases on the servers that belong to the failover group. These databases are a mix of DTU based and Hyperscale.

I know the following:

Hyperscale databases are backed up using snapshots
DTU based are backed using full/diff/log.

My 3 main questions are the following:

If the databases reside on both servers (due to the failover group), are they BOTH backed up, thus doubling my storage costs?

As far as LTR, should that only be configured on one of the servers, and not both?
Should LTR be configured on the primary server of the failover group, or the secondary?
If the databases reside on both servers (due to the failover group), are they BOTH backed up, thus doubling my storage costs?

It just seems redundant to have backups and LTR done on both nodes. Or am I missing something?

I know the following:

Hyperscale databases are backed up using snapshots
DTU based are backed using full/diff/log.

My 3 main questions are the following:

If the databases reside on both servers (due to the failover group), are they BOTH backed up, thus doubling my storage costs?
As far as LTR, should that only be configured on one of the servers, and not both?
Should LTR be configured on the primary server of the failover group, or the secondary?

It just seems redundant to have backups and LTR done on both nodes. Or am I missing something? Looking for best practices for database PITR/LTR when databases reside in a failover group.