@sheldoom: Based on the docs that's correct, in reality you're wrong though.
You do not necessarily need a default TFS in order for the system to "survive" a reboot contrary to what the documentation is saying.
If no default TFS is set the vectors process will try to re-activate the previously active TFS which can be seen in the logs quite nicely (take special note of the TFS IDs):
VEC_General
Activating Default-Vectoring with Id=0x0000000000000000 ... LastActive-Vectoring Id=0000000011011000
VEC_General
No Default-Vectoring set. Try to use LastActive-Vectoring with Id=0x0000000011011000 ...
VEC_General
VecTimer::setHolidayAddress: Setting Address=0xd008318
VEC_General
iVManager::activateGroup called for VectoringGroup 0x0000000011011000
TC_General
007.000.1300 SUCCESS: Kernel successfully connected.
TC_General
007.000.2100 MESSAGE: Taskflow group activation started...
TC_General
(AbsOrbNaming::rebind) success - rebound: /DefaultSystemName.System/vectors.Server/VManager.Object
TC_General
007.000.1002 SUCCESS: Successfully registered at ORB naming service.
VEC_General
Initialized VManager.
VEC_General
---- Startup finished. Vectors is now up. ----
TC_General
007.000.2000 SUCCESS: Startup finished. Process is now up.
VEC_General
iVManager::activateGroup: VectoringGroup 0x0000000011011000, name='XXXXXXX' activated
TC_General
007.000.2101 MESSAGE: Taskflow group activation successful.
EDIT: Small formatting changes