Bonjour Mary, and everyone;
Merci pour votre sympatique réponse
I am not sure the discussion is complete though...
Helen very rightly refers to this documentation, which I also refered to here.
The flowchart goes like this (I numbered the steps to make reference easier):
1 Start restore MBZ
2 Is it an alias ?
-YES
3 Stash if for later
4 Next file
5 Iterate over all stashed aliases
6 Same site?
-NO
7 Alias to Server files or Legacy course files?
-YES
8 Is there such repository instance available?
-YES (in all my test it was the case)
9 Use the repository instance
10 Alias to Server files or Legacy course files
-YES (!? Hadn’t we got that at step 7 already, or is it different?)
11: Reference files also included in backup? _is it ever possible to have a YES answer to this question, I have never seen my “Private files” or “Legacy files” in the “Private” or “Legacy” folder of the Moodle where I performed the restoring_ Is not that possible? Will it at some point? What if I upload the folder manually, would Moodle be able to catch up? (at this stage, it can’t, I tried)
12: Restore the alias so that it refers to the file in the backup
So it seems backing up aliases is really possible IF step 11 is fullfilled. My questions are:
"Is this retoring of private (server?) files _or Legacy files_ possible and how?
"Are the aliases to the files strored in the backup in their transient state (draft) of permanent (pluginfile)?
I understand these are programmer's answers unless there is some (hard to find) parameter that needs ticking, and our special attention
Thanks again/Merci beaucoup
Philippe