Hi @Thava_91
It's not really clear from you topic what your exact challenge is, but the challenge is that the full backup takes 25 days to complete. So to improve RTO you want to create a second backup set that creates incremental copies? In all honesty, but if the backup takes 25 days to complete than I would become pretty scared knowing that your RTO is going to be the same or worse when you are hit by a disaster. I assume it contains valuable data, so can you survive not being able to use this data for at least 25 days? Have you looked what your bottleneck is currently that is causing the backup to take 25 hours. Would it be possible to add a disk copy?
The best practice should be [First Full, following incremental and then change the full schedule to synthetic full]
This is the idle way, since Synthetic backup does not involve server, it only reads the data from media and writes to media, hence give higher throughput and complete the job, also synthetic full are independent of incrementals, so the incremental backup will run during the synthetic full being in process.
Consider Disk-Based Backups: Transition to a disk-to-disk-to-tape (D2D2T) strategy instead of direct tape backups. Disk backups typically offer faster read/write speeds, reducing backup time.
I would assume the best way forward is to adopt backup plans and let the system configure itself automatically ;-)