11-17-2015 04:34 AM
I've only ever done back ups to tape drives before, but now that I'm investigating backing up to the cloud it looks like all other forms of backup require a backup to the disk first:
So presuming that is indeed the case, my next question is how much disk space should I expect a full backup to take? On this example server here's the disk capacity:
So would I expect the backup to take exactly 50.2GB or would it take more to allow for meta data etc?
Solved! Go to Solution.
11-17-2015 04:43 AM
Hi,
the option is Backup to Disk and duplicate to cloud...so disk first, then set the next stage to duplicate those backups to cloud.
A full backup would take roughly 50GB's worth of disk space as you'd get no compression of files to disk (unless you're using dedupe), but the amount of disk space you'd require would depend on how long you want ot retain your backups for. 7 days would be about 350GB for instance.
The duplicate part of the backup would be automatic and would run immediately after the backup has completed.
1 way to lessen the amount of disk space on the initial B2D would be to look at either Incremental or Differential backups, so look into what those offer you.
Thanks!
11-17-2015 06:54 AM
11-18-2015 12:43 PM
You sir, don't quite understand how the Internet works, and how latency and bandwidth influence data transfers.
Yes, you will stage to disk, and then clone to the "cloud." Even enterprise solutions like nasuni, Altavault, CloudBoost, Panzura, etc... These are all solutions costing hundreds of thousands of dollars All cloud gateways, have a landing space or cache area, since a WAN connection is so unpredictable.
Then think of your restores... Wold you rather restore from a local disk on your LAN, or from the cloud? By staging to disk, you'll always have a most recent copy available to you.
I have one customer using 10GbE to AWS S3 and an Altavault direct to cloud, but the cache area is something like 200TB in size.
12-03-2015 03:31 AM
Afaik, currently the Cloud Option is available only as "Backup to Disk & then Duplicate to Cloud".
If you are interested in an online lab as to how this works, would recommend signing up at https://veritas.orbitera.com/c2m/customer/signup?_widget=1
CORRECTION - Added on 3rd December 2015 :
When originally providing this answer, documentation was not available (either internally or externally) that provided details of how to perform a Direct to Cloud (D2C) backup job. Therefore as the drop down menu from the Backup Button only showed Duplicate to Cloud options it was believed that only duplication operations were possible. Support are now aware that it is possible to run D2C backup jobs by creating a Backup to Disk (B2D job) and then editing the storage properties within the job so that the target device is the Cloud Device. Apologies for any confusion this may have caused.
Note: We will be looking to provide more formal documentation regarding this ( within a reasonable timeframe ) and are also looking into the possibility of providing some best practices guidelines
11-17-2015 04:43 AM
Hi,
the option is Backup to Disk and duplicate to cloud...so disk first, then set the next stage to duplicate those backups to cloud.
A full backup would take roughly 50GB's worth of disk space as you'd get no compression of files to disk (unless you're using dedupe), but the amount of disk space you'd require would depend on how long you want ot retain your backups for. 7 days would be about 350GB for instance.
The duplicate part of the backup would be automatic and would run immediately after the backup has completed.
1 way to lessen the amount of disk space on the initial B2D would be to look at either Incremental or Differential backups, so look into what those offer you.
Thanks!
11-17-2015 06:54 AM
11-18-2015 12:43 PM
You sir, don't quite understand how the Internet works, and how latency and bandwidth influence data transfers.
Yes, you will stage to disk, and then clone to the "cloud." Even enterprise solutions like nasuni, Altavault, CloudBoost, Panzura, etc... These are all solutions costing hundreds of thousands of dollars All cloud gateways, have a landing space or cache area, since a WAN connection is so unpredictable.
Then think of your restores... Wold you rather restore from a local disk on your LAN, or from the cloud? By staging to disk, you'll always have a most recent copy available to you.
I have one customer using 10GbE to AWS S3 and an Altavault direct to cloud, but the cache area is something like 200TB in size.
11-19-2015 03:41 AM
Many thanks for the replies - split solution pending.
11-19-2015 07:38 AM
Assuming you are asking about the S3 Cloud connector, as I think that is currently the only way to see that cloud icon in BE, then No, you do not have to backup to local disk first. You can go straight to the cloud. You do need to me mindful of the reliability and speeds for straight-to-cloud backups.
The other solutions (disk targets & VTL) do local staging first, as Teiva mentioned.
12-03-2015 03:31 AM
Afaik, currently the Cloud Option is available only as "Backup to Disk & then Duplicate to Cloud".
If you are interested in an online lab as to how this works, would recommend signing up at https://veritas.orbitera.com/c2m/customer/signup?_widget=1
CORRECTION - Added on 3rd December 2015 :
When originally providing this answer, documentation was not available (either internally or externally) that provided details of how to perform a Direct to Cloud (D2C) backup job. Therefore as the drop down menu from the Backup Button only showed Duplicate to Cloud options it was believed that only duplication operations were possible. Support are now aware that it is possible to run D2C backup jobs by creating a Backup to Disk (B2D job) and then editing the storage properties within the job so that the target device is the Cloud Device. Apologies for any confusion this may have caused.
Note: We will be looking to provide more formal documentation regarding this ( within a reasonable timeframe ) and are also looking into the possibility of providing some best practices guidelines