#Vcenter 6.5 pulled patch archive#
#Vcenter 6.5 pulled patch full#

Rubrik is one of them, they can utilize the same NetApp snapshots which greatly cuts down the impact to production, the amount of time of processing to scan for changes, and thus quicker backups. NetApp APS's: like most storage vendors the inner secrets have been exposed to third parties for a more efficient ecosystem. This option cannot be changed midstream, if one changes their mind the SLA needs to be deleted, the data deleted or aged off, and recreate the SLA and backup the target as if it was new.

#Vcenter 6.5 pulled patch archive#

If the direct archive location is chosen during SLA creation the data bypasses the Rubrik, goes to the archive location, and only the meta-data lives on Rubrik. This is great if current and prompt restores are needed, however it does eat into ones storage plans. When setting up the SLA's if one doesn't select this option the most current data is stored on the Rubrik and all of the old changed data is on the archive location. I will mix up the terminology here but 'direct archive' isn't necessarily direct-archive. Rubrik has a checkbox that can only be chosen when creating a SLA. being stored on the Rubrik then having old backups age off to secondary storage. 'Direct Backup to Archive' means that the backups are stored directly on the secondary storage vs.

#Vcenter 6.5 pulled patch full#

IE instead of backing up every 3 hours, which means a new backup would occur every 8 days, change it to backup every 12 hours so it only does a full every 30 days. One way to make this less painful is to scale back the number of backups. When those jobs take over a 24 hour period to ingest the impact to the production infrastructure and other backup windows can be a concern. Not a big deal except when one has multiple 10TB volumes to backup.

Rubrik's way around this is collapse all of the deltas, them and make another full backup. The delta chain gets to be too long and time consuming to traverse, so restores become messy. So if one is using something 'cheap and deep' in terms of storage, say a Synology NAS, Cloudian, or any S3 blob storage, a full backup will occur every 60 jobs or so. EXCEPT when using another storage device for archiving.

Rubrik is a 'forever delta' technology, meaning it will do one full backup, then from that point forward only backup the changed blocks. A couple of random notes on the product if I got something out of place or newer version addresses the issue, let me know.