Backup folder and disk names
-
we have backup job's running, and every 6 months we need to copy a couple of our VM's to external storage and store them offline in a secured environment.......
But if we need to recover this data there isnt a way to identify "VM-1" to copy it over to our production environment without XOA.so if i want to only recover VM-1 i would need to connect our entire secured storage to the network so XOA could identify a single VM, what im looking for is a easier way of identifying what drive belongs to each vm in applications such as windows file explorer.
-
@jebrown you could export xva or ova copies. But then those are not exactly identical to backups.
-
@jebrown said in Backup folder and disk names:
we have backup job's running, and every 6 months we need to copy a couple of our VM's to external storage and store them offline in a secured environment.......
But if we need to recover this data there isnt a way to identify "VM-1" to copy it over to our production environment without XOA.so if i want to only recover VM-1 i would need to connect our entire secured storage to the network so XOA could identify a single VM, what im looking for is a easier way of identifying what drive belongs to each vm in applications such as windows file explorer.
Could you use the UUID of a given VM, this would remain the same from your production and backups. You could then search for that UUID or manually track it for your tests.
Separately I whole-heartedly disagree with only making offsite backups ever 6 months, using something like BackBlaze B2 or S3 buckets it way to convenient and cost-effective to not use it continously.
-
@Forza yes that would work but is there a way to automate this... say
step 1 take a snapshot of VM-1, VM-2, ect.
step 2 export them as ova to current data store
then we could run this job and copy them over as needed otherwise its very time consuming to do them 1 at a time and download -
@jebrown said in Backup folder and disk names:
@Forza yes that would work but is there a way to automate this... say
step 1 take a snapshot of VM-1, VM-2, ect.
step 2 export them as ova to current data store
then we could run this job and copy them over as needed otherwise its very time consuming to do them 1 at a time and downloadTo ask, because I feel like I'm missing something, are you attempting to simply copy your backups to a different NFS/SMB share or are you trying to do something else?
XO (source or XOA) are meant to be replaceable, so long as you have a copy of your metadata and configuration you can always restore your VMs.
-
@DustinB we have off site backups taken regularly this is in addition to our normal backup plan
we have
daily, weekly, monthly onsite across 3 data centers and off site along with immutable backups im not even sure why we take these additional backups but its what the boss wants so we do it..
-
@jebrown said in Backup folder and disk names:
@DustinB we have off site backups taken regularly this is in addition to our normal backup plan
we have
daily, weekly, monthly onsite across 3 data centers and off site along with immutable backups im not even sure why we take these additional backups but its what the boss wants so we do it..To ask, would a separate backup job not work for this, or do you specifically want to replicate an existing backup to a different location?
-
@DustinB for this the backups are made then hard drives are removed and stored
-
@jebrown said in Backup folder and disk names:
@DustinB for this the backups are made then hard drives are removed and stored
Are you removing USB drives or drives from you host?
-
@DustinB Drives from a secondary NAS
