The second one are the various backup jobs I noticed they all failed. The first attachment is a screenshot of what I have navigating to Home > Backups. Is there something i haven't done or I'm the one not getting it you for this. So I tried deleting the old repository since all the jobs has been moved to the new one, then try to point to the new one and the target storage but was unable to delete the old repository. So, when I click on 'Configuration backup' from the screenshot u shared, the old repository was still showing in the drop down as the target storage and not the new one I created. So I expected my backup jobs from other servers to point to the new repository which inturn archive/replicate my on-premise data to Azure but noticed the jobs keeps failing. So, after creating another repository, I was able to complete the creation of the SOBR. I have created an Azure repository and it was when I tried creating an SOBR with the repository on the veeam server that I encountered the issue you that led to this thread. I want to archive/replicate my on-premise datato Azure. Have a look at the guides, how it works and how to configure could not add an attachment to the private message. The Backup Chains will NOT be changed by creating a SOBR. The existing Backup Jobs will be updated and doing there normal incremental and Full Backup Schedule like always. When you create the SOBR with your existing Backup Repo, the Repo will be added as a extend to the new SOBR. It depends on your choosen Policy, how this will be happening. MOVE, COPY or both together. The SOBR will offload the backup data to Azure Blob, your capacity Tier.Backup writes the data to Performance Tier.Performance Tier -> your existing Backup Repo OnPremise The SOBR will have a performance tier and a capacity Tier. Backup Job (or Backup copy Job) write the backup file to a SOBR.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |