VeeamON 2024 | #BounceForwardThrowback (Win Custom Shoes!)
After having our network team investigate we have learned that our inspection policy on our Palo firewall permits traffic to our cloud connect environment that matches the signature for Veeam cloud connect traffic using port 6180. The traffic is now presenting as unknown to the Palo and there for dropped. The work around was to disable the inspection. After that change was pushed our v12 Tenants were able to access their cloud resources as expected.
I’m currently reading this Dell article https://www.dell.com/support/kbdoc/en-ph/000019159/expedited-configuration-steps-and-details-for-datadomain-boost-fs while I wait for Dell Support to respond.
@JMeixner Thank you for your response! I read that article before posing here and unfortunately it doesn’t cover how to “seed” the backup files onto the Data Domain (we are using the DDBOOST file system). This storage is used to present repositories to clients via our cloud connect service. I need to run the initial backup copy to a local/portable NAS on the customer’s site, disable the job, ship the portable NAS to our data center, copy backup files onto the Data Domain, update the job to use the cloud repository, and then enable the job to run. I have several customers with backup jobs that are well over 12 TB and trying to push that much data over the internet is not feasible. I will update the topic with the work plan I am attempting to use for more context.
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.