Extend ZFS zpool Volume Size Without Any Data Loss
-
In customer place they have 2 freenas server. One Freenas act as a primary and another one act as a secondary. Primary to secondary running rsync process for backup. I do not have any VM snapshots regularly. Based on your suggentions , before add the physical hard disks on vmware Esxi server. we will power off the freenas server and take snapshots for backup , if any problem occurs its help.
I do not have any current status and devices status of freenas server?
-
@Ghani said in Extend ZFS zpool Volume Size Without Any Data Loss:
I do not have any current status and devices status of freenas server?
Not sure what you mean.
-
@Ghani said in Extend ZFS zpool Volume Size Without Any Data Loss:
In customer place they have 2 freenas server. One Freenas act as a primary and another one act as a secondary. Primary to secondary running rsync process for backup.
So the secondary has much more data than the primary?
-
Believe it or not, documentation on a ZFS span is effectively non-existent, partially because this should kind of never exist. It's not really how this is intended to be used.
However, I've got a ZFS admin sitting with me and we both feel that this is the right command...
zpool add zeepool c2t1d0 c2t2d0Where zeepool is your pool name and the devices are your device names.
-
@Ghani said in Extend ZFS zpool Volume Size Without Any Data Loss:
In customer place they have 2 freenas server. One Freenas act as a primary and another one act as a secondary. Primary to secondary running rsync process for backup. I do not have any VM snapshots regularly. Based on your suggentions , before add the physical hard disks on vmware Esxi server. we will power off the freenas server and take snapshots for backup , if any problem occurs its help.
I do not have any current status and devices status of freenas server?
@scottalanmiller, this sounds like they are using the FreeNAS 1 to hold the VM datastore and that the RSYNC is their backup.
OMFG that just is scary if true.
-
@JaredBusch said in Extend ZFS zpool Volume Size Without Any Data Loss:
@Ghani said in Extend ZFS zpool Volume Size Without Any Data Loss:
In customer place they have 2 freenas server. One Freenas act as a primary and another one act as a secondary. Primary to secondary running rsync process for backup. I do not have any VM snapshots regularly. Based on your suggentions , before add the physical hard disks on vmware Esxi server. we will power off the freenas server and take snapshots for backup , if any problem occurs its help.
I do not have any current status and devices status of freenas server?
@scottalanmiller, this sounds like they are using the FreeNAS 1 to hold the VM datastore and that the RSYNC is their backup.
OMFG that just is scary if true.
That's what I am afraid of. You CAN configure RSYNC to be a transport mechanism for backups, RBackup is based on it. But it's not what most people mean when they say that. I'm a bit worried.
-
@scottalanmiller said in Extend ZFS zpool Volume Size Without Any Data Loss:
@JaredBusch said in Extend ZFS zpool Volume Size Without Any Data Loss:
@Ghani said in Extend ZFS zpool Volume Size Without Any Data Loss:
In customer place they have 2 freenas server. One Freenas act as a primary and another one act as a secondary. Primary to secondary running rsync process for backup. I do not have any VM snapshots regularly. Based on your suggentions , before add the physical hard disks on vmware Esxi server. we will power off the freenas server and take snapshots for backup , if any problem occurs its help.
I do not have any current status and devices status of freenas server?
@scottalanmiller, this sounds like they are using the FreeNAS 1 to hold the VM datastore and that the RSYNC is their backup.
OMFG that just is scary if true.
That's what I am afraid of. You CAN configure RSYNC to be a transport mechanism for backups, RBackup is based on it. But it's not what most people mean when they say that. I'm a bit worried.
Sure, you make a snapshop and then rsync the static disk. then merge. That is how RBackup works to my understanding. It watches the files system and grabs files when they have changed, but are in a valid state.
-
Customer server was placed on branch location. we do not have any remote opitions for take screenshots and display to you
-
No .. we enabled rsync with delete opitions. so primary and secordary space was common.
-
yes rsync not a backup solutions
-
@Ghani said in Extend ZFS zpool Volume Size Without Any Data Loss:
Customer server was placed on branch location. we do not have any remote opitions for take screenshots and display to you
Then how do you work on the machine?
-
@Ghani said in Extend ZFS zpool Volume Size Without Any Data Loss:
No .. we enabled rsync with delete opitions. so primary and secordary space was common.
So NO backups. That's a replicant, not a backup. You actually deployed a big storage appliance without backups?
-
@Ghani said in Extend ZFS zpool Volume Size Without Any Data Loss:
yes rsync not a backup solutions
So in a "read back" mode, this tells us that the data stored here isn't important so there isn't really anything to worry about. If you do the expansion and it causes data loss, they can't be upset as they don't see value in the data. This also tells us that the servers shouldn't be there, because if they aren't backed up and they aren't a caching system then you shouldn't have them at all.
So there is clearly something wrong.
