Much time has passed since the question was asked, sorry about that. In case it's still unresolved, or if others have the same issue, here is my answer: Yes. 🙂
It's just always useful to have a couple of different types of backups available, and doing a periodic Calendar Archive is not a bad idea. The good thing about these archives is that they back up all of your calendars whether stored locally (on the internal storage device) or on an external account (e.g. iCloud).
And just to reiterate or clarify my earlier answer, a Calendar Export (File/Export/Export...), on the other hand, is for one calendar at a time, and it exports the events within the calendar, for subsequent import wherever you want them. It's an ics file, whose events can be imported to another Mac Calendar, or Google or Outlook calendar.
Lastly, I'm a big believer in text editors. You can do these Calendar exports and, if you're not sure what you just did, or that you got it right, you can open up your ics or icbu file in the text editor and see the data contained there. Just do a literal text search (say, the title of an event you know should be there) and confirm that it's there.
The editor I use mostly is TextWrangler, a slightly pared down (and free) version of BBEdit. UltraEdit is also awesome (not free but not expensive), especially for cross-platform (Windows/Mac) users. It also has the extra special feature of being able to view/edit files of any size by turning off the "safety net" of having a copy of the data in memory before you alter the stored (disk) version. That is, it gives you the capability to operate directly on the the data file and make changes real-time. Why? You're not limited by amount of your system memory. Think of riding in an elevator in a very tall skyscraper; you can go to any floor along the way, and when the doors open, you're looking at the "data" at that point, without having to store the entire building's data in memory at any one time. Since icbu files can get pretty large, I like to have this tool in my back pocket.