VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
So our company is growing, and planning for the future we are moving our VEEAM to a new server, and of course decommission the old one. With this move we want to start fresh, but retain access to the old repository. Is there a certain process we can do, so that the old jobs will not be migrated to the new server, thus reducing clutter, and allow us to restore from the old repository?The reason for this is the backup job infrastructure was created, and adapted to a fast growing company so it was sort of a reactionary solution. We now have the storage and plan on moving to the cloud. This will hopefully allow us to move away from our aging tape drive a good bit.Thank you all for your help in this matter.
We are beginning to put together a cloud based backup infrastructure, so we want to insure that we are leaving some bandwidth available for our employees, and not hobbling our internal backups. I have been doing some light research, and was wondering if there was a way to throttle only the backups that go up to the cloud, while leaving the on premise back up to disk jobs running at full. I have seen how to setup the global rules, but they seem to apply to all jobs unless I am mistaken. Thank you in advance for any advise you can give me, or point me in the right direction.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
