You’re correct, newer versions of
cbbackupmgr will create a lot more files than previous versions for various reasons; most importantly performance.
Regarding what the file formats mean:
.snp files contain DCP snapshot metadata
.fol files contain DCP failover logs
- Rift storage files (briefly covered in the S3 video as it was a requirement for native cloud integration)
index_[\d+].sqlite.[\d+] files are storage indexes, they contain metadata/locations for document data
data_[\d+].rift.[\d+] files contain packed document metadata/data
- General metadata files
backup-meta.json etc. are all JSON files
It’s worth noting that the formats/locations have changed significantly between versions so this information won’t be correct for older versions (for example, those that use SQLite/ForestDB).
Regarding the creation of “many files” for a backup of an empty bucket, this is to be expected;
cbbackupmgr will still open DCP streams to the bucket and persist the failover logs for each vBucket. This metadata is used when calculating the data which should be streamed when creating the next incremental backup.
Hopefully I’ve covered your questions, if I haven’t please let me know.