indivision
Guru
- Joined
- Jan 4, 2013
- Messages
- 806
Thank you. Good to know.
Virtualized under Windows, perhaps? With anti-virus software that blocks various key ports?I've install a fresh BETA 10,but can't login,
when entering the name and password to the GUI. I spend two days installing this....and now can't login...
(Chrome Browser)
The currently supported replication method in 10 is more complex, doesn't use SSH for actual replication (it has side-channels now) and provides replication statistics from both sides, not just one.
Replication is different from "backup" in this respect - a replicant is a "live" copy of your data on another machine, which may (if you change the settings appropriate) actually take over for you in the event of an outage. Backup is supported on the CLI but not yet in the GUI - that's coming soon, and will always encrypt the data as it leaves your machine.With this new method of replication in 10, would it be possible to optionally encrypt the data replicated?
I want to replicate my snapshots to a friend's Freenas and his snapshots to my Freenas, but we don't want access to the data.
That would require changes to ZFS, whereas @jkh implies they're just using a different transport for the replication stream.With this new method of replication in 10, would it be possible to optionally encrypt the data replicated?
I want to replicate my snapshots to a friend's Freenas and his snapshots to my Freenas, but we don't want access to the data.
Either or both, depending on how the backup is configured.@jkh That makes sense. Would the backup include snapshots or just current data (single snapshot)?
Hmmm. I haven't even *seen* an AMD system in at least 10 years, and we certainly don't have any around the office to test on (AMD still makes CPUs?? Huh! Who knew! :D) so if you could tell us what kinds of errors you get, maybe we can at least add some additional checks that print more useful errors when trying to run something that requires VT-x functionality on a system which just doesn't support it. I know that the middleware flags Intel CPUs without VT-x and prints a diagnostic when any VM operation is attempted, which should also be transitive to Docker, but AMD... that's a poser! Thanks.
HP Microserver Gen 7 is still a pretty popular home lab NAS server and it uses an AMD CPU. Will it just not work with an AMD CPU full stop?Hmmm. I haven't even *seen* an AMD system in at least 10 years, and we certainly don't have any around the office to test on (AMD still makes CPUs?? Huh! Who knew! :D) so if you could tell us what kinds of errors you get, maybe we can at least add some additional checks that print more useful errors when trying to run something that requires VT-x functionality on a system which just doesn't support it. I know that the middleware flags Intel CPUs without VT-x and prints a diagnostic when any VM operation is attempted, which should also be transitive to Docker, but AMD... that's a poser! Thanks.
This did this for me on previous versions with only a 4GB USB stick or with certain USB sticks. Make sure you have a minimum of 8GB stick and a decent brand.Please file a ticket - someone will attempt to diagnose! Thanks
I never said that, I just wanted to poke a stick at AMD users a bit.Whaaaat? AMD has to have at least 20% of the market share still. Are there no plans to make the VMs/Containers AMD compatible?
No, FreeNAS uses an entire drive. You cannot use partitions.And is there a way to install it to my boot SSD alongside 9.10 so that I can choose 9.10 or 10 BETA?