This does not mean that you have a team or even a person who has the title "DBA" - however, if you have a database, whether it's relational, or non-relational, then someone has the role of "DBA" - and if they don't know that they do, then a whole bunch of things aren't being done or thought about before problems happen.
Over the last couple of weeks, I've worked with users who ran into major problems, some of which could have been prevented if they had better clarity around "DBA" role. In all but one of those cases, they were able to recover successfully partly because they had recent backups. Some of the tasks owned by the DBA role were happening, even if others were not.
In the remaining case, it turned out the most recent backup was more than three months old. There is no excuse for that, unless you can easily regenerate all of your data!
Luckily, we were able to recover the lost data for this user (straight from the free list in the database files, but you really cannot count of that being possible - they got very lucky in that regard) but I'm willing to bet that they will start keeping track of whose job it is to make sure that the database is backed up.