Connecting Cloud Innovators: Building Community at .NEXT 2024
Its not based on time, its based on how many snapshots to retain, it says per interval... Whats your recovery requirement for the remote site? Why not create one schedule and keep local retention higher than the remote?
Why not just get the data over first then setup your schedules so its only the updated blocks need to copy over... If the initial copy of 1.5TB is not at the destination the snaps betweeen will not be correct as the VM data is not at the destination, so when you first initital snapshot is synced at the destination this will be the only availble snapshot...
Hi there, I maybe miss reading your post but how are the remote snapshots expiring? I havent checked lately but you set the amount of snapshots to retain, so the destination should keep the snapshots until its replaced by a new one... "Is there a way to change the min. snap retention count for local site AND remote site" Yes you can have different retention policies for local and remote sites, this option is in the schedule when creating the PD Cheers J
Great, thanks for confirming Jason
Hi, thanks for replying, that would be great if you find a solution and post Cheers Jason
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.