Now THAT is an interesting question James.
I quickly checked the KB but did not see anything.
I could be wrong so come to your own conclusion, but if the files in question have <local file> status, I do not think the backup will contain them because the files have not been added to the file server yet.
However, once the file is added to the vault, the file is given a file id & meta data assigned to it in the archive server & a copy is made on the file server. I believe then it could be backed up even if not checked in because the backup program is backing up the file & archive servers. I "think" this is possible because at that point in the file's lifecycle it is merely flagged as checked out and the file is part of the database.
You could also check your backups if you have a known <local file> and see if it is in there.
Let me know what you find! Very interesting challenge for a Monday.
My understanding is the same as Tim's; if it's been added (ie, not listed as <Local>) then at least some version of the file is in the archive on the server and so should be available for backup. If local changes have been made and are not yet checked in, though, those changes will not be available for backup.
Thanks Brian. I contacted my VAR and confirmed that this was the case. New files and changes to checked out files are NOT backed up by EPDM.