Well, no backup plan is perfect, and there are some common sense self-imposed limitations.
My off-site storage is worthless if my corner of Maryland/DC gets nuked. Or course, I would be vaporized, but point being is how far does one take their backup strategy?
As far as backing up data that doesn't change very often, I skip that. My Kontakt libraries are almost always static - I do not add new content very often. When I do, I back it all up, but otherwise, it exists on the local active drive, the internal backup drive, and on the off-site drive, but only gets backed up when sample content changes.
I use the same approach for Cakewalk Projects. I keep a copy of all project folders on all 3 drives, but only back up the static projects to the internal backup drive once every 3 months, and to the off-site drive once every 6 months.
All new project folders get backed up to the internal backup drive as soon as I have finished the Sonar session in which they were created, then to the off-site drive on the 1st weekend following their creation.
Any project I am going to modify gets backed up to the internal backup drive prior to my opening the project up for modification, and to the off-site drive on the 1st weekend following its modification.
Non-Cakewalk documents and downloads and such get backed up to the internal drive every weekend, and once a month to the off-site drive.
It's really all about whatever makes sense to you - you are the one who best understands your work habits, frequency of change, and criticality of data.
Bob Bone