Having already done, wrongly thinking, a bottom up prototyping of a Bareos community release for a small sized setup in the past, it unfortunately frozen due to other tasks. Now doing new prototyping from scratch. This time contrary to the first time that I did a bottom up approach I decided to do a top down approach and verify whether an implementation is possible considering a budget spent entirely on hardware. To those who are willing to disclose their wisdom please share your experience and views in the following:
- assuming that somebody decides to roll over a community release implementation, how realistic is it to do this just with documentation in hands. I am talking about a fairly simple small business setup. i can't elaborate on the small business setup yet but I can follow-up if there is a rule of thumb for describing complexity in the setup. - when a certain task or property is not too obvious or is implied for an experienced professional or even missed out while reading the docs, is this something the community will help? How fast is such response? - prototype completes, implementation completes successfully, it becomes production grade, and put in operation without problems. When setup needs become demanding and more complex, and experimentation is not an option, moving from community release to a subscription release, how difficult is this in terms of migration? needless to mention that I share the values of open source and I willingly share my experience and knowledge as it is being built with this implementation. 1 -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/bd097d2c-e481-4dff-99aa-2aa3ff37061bn%40googlegroups.com.
