Nologging on table

Hello,

Oracle 19 on Windows Srv 2019...

Helping a customer with an application that 24/7 insert rows into one table, this is electric meters inserting data very frequent, we are now on 24000 meters and plan to go to 44000.

The table has now >3 billion rows, they do run weekly deletes of old data, keep around 6 months of data. We generate a huge amount of redo, which causes issues with backups, basically requires huge backup discs to store archive and full backups.

The amount of data stored is not that much of an issue as the high redo generation.

The data stored in this table is moved on within 1 hour, to another system. We can ask for the system to send the data again (up to 30 days back), if needed. So loosing the data is not that critical, it can be regenerated. To shrink the amount of redo I was thinking that maybe we can set that table to nologging, move it to its own tablespace and when we take backup we omit that tablespace. Full backups will be smaller/faster and amount of redo should go down.