Ah, that’s interesting, seem to have missed that. Thanks for the pointer, looks exactly like what we’re looking for 😊
Best,
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Tim Stiller tim.stiller@gmail.com Gesendet: Montag, 22. März 2021 14:09 An: Alexander Griesser AGriesser@anexia-it.com Cc: toasters@teaparty.net Betreff: Re: Move fabric pool enabled aggregate to new disks
Hi Alexander,
if you are on ONTAP 9.6+ and you want to use the same S3 bucket with your new disks, vol move will only move the hot data to the new aggregates. The cold data will remain on the cloud tier. just take a look at this KB: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP...
best regards Tim
Am Mo., 22. März 2021 um 14:04 Uhr schrieb Alexander Griesser <AGriesser@anexia-it.commailto:AGriesser@anexia-it.com>: Hey there,
we’ve quite some fabric pool enabled aggregates and would want to move them to different disks. As far as I can see, there’s no good way to do that. Using vol moves will require to download all the data from our S3 backend and re-upload it on the destination aggregate then. So say we want to „upgrade“ our fabric pool aggregate from 12x1TB SSD to 12x4TB SSD and let’s further assume that we have 20 volumes on the FP-enabled aggregate with a total of 1PB of storage in the S3 backend, do we really have to go through downloading and re-uploading all the data or is there an easier way (besides adding the new disks to the aggregate in the first step as spare disks and manually failing disk by disk) and afterwards increase the capacity in the raidgroup by addiding additional partitions?
Best,
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net https://www.teaparty.net/mailman/listinfo/toasters
Am Mo., 22. März 2021 um 14:04 Uhr schrieb Alexander Griesser <AGriesser@anexia-it.commailto:AGriesser@anexia-it.com>: Hey there,
we’ve quite some fabric pool enabled aggregates and would want to move them to different disks. As far as I can see, there’s no good way to do that. Using vol moves will require to download all the data from our S3 backend and re-upload it on the destination aggregate then. So say we want to „upgrade“ our fabric pool aggregate from 12x1TB SSD to 12x4TB SSD and let’s further assume that we have 20 volumes on the FP-enabled aggregate with a total of 1PB of storage in the S3 backend, do we really have to go through downloading and re-uploading all the data or is there an easier way (besides adding the new disks to the aggregate in the first step as spare disks and manually failing disk by disk) and afterwards increase the capacity in the raidgroup by addiding additional partitions?
Best,
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net https://www.teaparty.net/mailman/listinfo/toasters
-
Alexander Griesser