I need to know about backup & recovery strategies for partitioned Database in Sybase ASE 15.7 . I am not worried about transaction failure & recovery scenarios.
We have already faced this 2 scenarios previously in un-partitioned database & it took more than 6 hrs for us to recover back [Reason : Low level sybase error]
In case of catastrophic failure like:
- Data corruption (Some low level defect causes a table corruption that went unnoticed for days or weeks)
Failure of a device [A storage system gets corrupted]
Is my idea good to partition my database to achieve better resiliency?
In case I am doing so, is it possible to recover only failed partition? Sybase ASE maintains logical partitions, so is it possible to do piecemeal recovery?
In case my primary partition gets corrupted because of sybase low level error / disk corruption, will my replica also gets corrupted? [After all it's a replication :)]
In response to the initial answer by Catarrunas:
I didn't get point 2. Could you help me to explain that?
So in Sybase ASE, storage structure looks like (Partition --> Segment --> Device --> Extent --> Allocation Unit --> Page). Idea is to store 1 partition per segment. Of course again segment can span multiple devices.
Is it possible now to recover only failed partition held by 1 segment? Can we perform segment level recovery or still we would require to recover whole db?
So currently we don't have any replication. But it was more like due to some low level error, data got corrupted which went unnoticed for few days. In fact the last 2 dumps were also corrupted & we had to go -3th level dump to recover back.