Hi Alexander,
I had a similar issue at a customer when we converted to MirrorAndVault, and noticed missing snapshots. The workaround below worked and does not requite a new baseline. The mirror needs to be recreated though using the “-source-snapshot” parameter specifying the oldest snap using the “MirrorAndVault” policy, then you change back to “MirrorAllSnapshots” after resync and you will be all set.
Procedure to bring missing snapshots back to XDP MirrorAllSnapshots If a SnapMirror is setup with a poicy other than MirrorAllSnapshots, to convert back you will not get all snapshots. This is important to have for a cascaded mirror for example to resync with another tertiary cluster. The method below will bring back older snapshots.
Steps · Break the mirror · Delete the snapmirror · Recreate the mirror with -policy MirrorandVault and -source-snapshot pointing to the oldest snapshot · Snapmirror resync and older snapshots will vault · Change the policy to MirrorAllSnapshots · Snapmirror update
On Apr 17, 2019, at 9:19 PM, Alexander Griesser AGriesser@anexia-it.com wrote:
Hi toasters,
I’ve setup an XDP snapmirror relation on one of our customer systems yesterday with the default MirrorAndVault policy (which includes daily and weekly snapmirror labels). After the baseline transfer, I recognized that no daily and weekly snapshots have been transferred to the destination and after deeper investigation I found out that the customer did set up a custom snapshot policy which was missing the snapmirror labels:
Custom-policy 3 true - Schedule Count Prefix SnapMirror Label ---------------------- ----- ---------------------- ------------------- daily 7 daily - weekly 4 weekly -
I’ve now modifed the policy (for all future snapshots) and did also modify all existing snapshots to add the labels:
snap modify -vserver vserver -snapshot weekly.* -snapmirror-label weekly -volume * snap modify -vserver vserver -snapshot daily.* -snapmirror-label daily -volume *
All snapshots do now show the correct snapmirror label, so I ran `snapmirror update` on the destination, but the old snapshots have not been transferred, which is most likely because they’ve been created „before“ the XDP snapshot on the source volume. Newly created snapshots though, the one which got created overnight now with the new sm „daily“ prefix, got transferred with the most recent update.
What are my options now to also bring all the old snapshots to the destination? Do I need to reinitialize the relation?
Thanks,
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.com mailto:AGriesser@anexia-it.com Web: http://www.anexia-it.com http://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.net mailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters http://www.teaparty.net/mailman/listinfo/toasters