For relational data, would a Model represent a row and a Collection represent a result set? I usually think of an MVC app as having a single model representing a schema. It sounds like Backbone is different.
On the client side, you very rarely have access to the entire table -- often you have different slices of it based on different search queries, or associations -- every Book has its own collection of Notes, for example. So just mimicking the Rails-style 1:1 mapping can be a bit of a fallacy.