I know this is an older video, but what is the best practice to organize your data protection collections? By application awareness/non-awareness? By snapshot growth rate?
@ZachEck-l6w Жыл бұрын
Is it possible to store only snapshots on the replication partner, without initially copying the dataset in the volume?
@jdhITguy Жыл бұрын
Nope. ROW snapshots are simply locked blocks within the volume dataset. It is not new or copied data. This is what allows them to be created so quickly with no perf impact and take up so little storage capacity. Snapshots cannot exist without the volume dataset on the primary array or the replication partner.
@zlobelije Жыл бұрын
Thank you for great content. Just need some clarification: basically, what is the difference between handover and demote? Does demote also perform resynchronization, prior to giving control to other storage?
@jdhITguy Жыл бұрын
That is correct. The demote process does not sync with the other system before giving up control. This is how you can failover when network connectivity is down between the two systems. Whenever possible, handover is always the better option.
@andyMSH700 Жыл бұрын
hp storage has simply not progressed the way it should have...we lost focus on our customer..
@jdhITguy Жыл бұрын
That is an interesting takeaway from this video. I'm curious how you think HPE storage should have progressed and what customers are being ignored by the direction HPE has chosen.
@Rocky08396 Жыл бұрын
Power Point reference?
@jdhITguy Жыл бұрын
If you contact me via my HPE email, I am happy to share slides with you.
@Rocky08396 Жыл бұрын
@@jdhITguy hi can I get your Email?
@isvargase Жыл бұрын
Hello, its possible to scheduled the snapshots in Alletra 6000?
@jdhITguy Жыл бұрын
Yes, the A6K runs the v6.x of the Nimble OS. IT has just been updated for marketing and is now called Alletra OS v6.x. The UI and configuration options are the same except for the added capabilities from managing Alletra from DSCC.
@davidyang7462 Жыл бұрын
Quick question, how to delete a replication volume while the primary volume has been deleted, GUI give an error, "Replication Volume can't be deleted". Thanks!
@jdhITguy Жыл бұрын
This requires some volume "surgery". Contact HPE Nimble support. They can help you get it done.
@aryehbarron4067 Жыл бұрын
This is excellent, I’ll be reaching out to you for a updated version of this!!
@jdhITguy Жыл бұрын
glad you found it useful.
@emmanuelokojesu2 жыл бұрын
Great explanation, thank you
@jdhITguy Жыл бұрын
Glad it was helpful!
@Radiowarsaw2 жыл бұрын
Thank you for this video, this helped me solve my issue, I cabled an HFXX the way you would the AFXX and that did not work
@jdhITguy Жыл бұрын
glad I could help.
@peauxb0y2 жыл бұрын
Hi Jonathan, can you tell me where I can find the other videos in this series? For instance, this is Module 8....I was hoping for modules 1 - 10 or however hi it goes
@jdhITguy Жыл бұрын
The entire content from NTS has not been officially posted anywhere public. I created these videos to augment the NTS training I did for my customers, focusing on training modules some of the students missed.
@pasquinobocci2 ай бұрын
@@jdhITguy hello, OK, but is there is any chance to have the videos on youtube or shared by PM? Thanks.
@yeremyparedes78082 жыл бұрын
Thanks for your content!. I have a question, if a configure a partner, but this partner have anothers volumes and services in production, it lose already configuration or it's transparent for this. Thank you!
@jdhITguy2 жыл бұрын
Not sure that I fully understand the question... but I'll take a shot at an answer. Once the partner relationship is configured between two systems, any volumes (exisiting or new) can then be configured within a volume collection to replicate snapshots. The replication is not automatic. it must be configured within a volume collection as part fo the snapshot schedule.
@whoanelly-2 жыл бұрын
do you have to evacuate? Can you not just leave them in the group?
@jdhITguy Жыл бұрын
You can leave them in the group, but after a time the older system will not be supported and that will affect the supportability of the group. Also, all group members must run the same level of code. So, keeping older systems in the group could impede the ability to upgrade and take on new features. There is a limit of four systems in a group.
@danielmcgann53693 жыл бұрын
Thank you for creating this video. It was really helpful! 👍