could anyone please suggest industry standards for archiving.

i have a banking application, and the trnsaction and movements table grows rapidly. i thought of using parttions and then dropping partitions fater taking backup. since after every first drop i should change the partition logic please suggest as to how i should accomplish this. i want to use date as the constraint for partition.

please suggest other techniques for archiving huge data.