Replies posted by Anandu
The TLS version is 1.2, should I change to 1.0? Hi @Anandu TLS setting for storage is cloud side infra \ Azure Thanks for the replies, it turned out to be the TLS version which was set at the Azure end. I set the TLS version to 1.2 in the storage account and it worked ok. The TLS version in customer environment is 1.2
Then you have to keep the statements for the old backup jobs in your RMAN script and add the statements the plugin tells you only. Then both jobs should be executed. But I think it would make sense to create two RMAN scripts. One for Veeam RMAN jobs and one for the old jobs and schedule both at different times. But the issue is when we install plug-in, the SBT_TAPE library will be updated to Veeam and with that backup to tape will stop. Now I am not an oracle expert which is why I am asking.
Hey guys, in this link it says veeam cannot backup failover cluster with CSV and CSV will be excluded if you are backing up that cluster. https://helpcenter.veeam.com/docs/backup/agents/cluster_support.html?ver=110Is there recommended way to backup those volumes? Can volume or file level backup solve this?
Server managed agent is centrally managed and distributed by the Veeam server. It's easier to handle when you have several agents. You have more information about the agents activities. I use the standalone agent in scenarios where the owner of the target machine wants to his own scheduling or wants to start the backup jobs manually…. For me the server managed agent is the first choice in all environments where the backup team is responsible for the backups and the system or application owner does not demand to have influence on the settings and/or schedule of the jobs. But the owner could specify the schedule to the backup team and they can manage it right. Why the need to install agent for that reason?
Do you have some minimal retention times for you objects in azure? So, that some objects are deleted for Veeam but are still present and are accounted in Azure… This is the case for example with Wasabi. It has a minimal object retention of 90 days... We have retention period of 3 days in veeam. Are you talking about retention we set in storage account? Yes, I do. And with some object storage vendors you have a minimal retention time for all of your objects which you cannot decrease. In my example with Wasabi, all objects are accounted for 90 days regardless what you configure… So, it is not the best choice for data with a retention time in Veeam of several days only. So do I have to reduce the retention in object storage?
Do you have some minimal retention times for you objects in azure? So, that some objects are deleted for Veeam but are still present and are accounted in Azure… This is the case for example with Wasabi. It has a minimal object retention of 90 days... We have retention period of 3 days in veeam. Are you talking about retention we set in storage account?
Login to the community
Log in with your Veeam account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.