What I've done is use CIFS server for Windows users, then use autosnapshot to take regularly scheduled snapshots. For windows users this has the advantage of the snapshots showing up under "Previous Versions" tab when right clicking on a file or folder. :)
I've used iSCSI for VMs, but as I understand it the zfs snapshot of the iscsi volume would be a point in time image, as if the machine just stopped. Most of the time it's probably not going to be a problem, except when it is. :) I also prefer NFS for exporting to Linux/Solaris/Unix. Can use to export to Mac as well, though AFP would allow the mac to use the share as a time machine; I dont think NFS does. Greg On Jun 10, 2011, at 12:31 PM, Gabriele Bulfon wrote: > Hi, I'm in the middle of a brainstorm over backup strategies and snapshots > affidabilities. > What are your final words on backup strategies of ZFS storages? > What makes me brainstorm is expecially snapshots. > How can I consider an iscsi snapshotted raw device safe, when I don't know > what the virtual machine > is doing on it with its own file system? > This question makes me feel unsure of any backup strategy I may implement > over exported volumes, > where systems just write what they think it's their own file system. > That's why I want to do CIFS for Windows servers, instead of giving the > filesystem as a raw device > to the primary domain controller. > That's why I think it would be better to share volumes through NFS to linux > and solaris servers. > How can I be safe? > :) > Gabriele. > _______________________________________________ > OpenIndiana-discuss mailing list > [email protected] > http://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
