Subscribe
Accepted Solution

How to remove SM relationship after volume migrations

I have successfully migrated a volume from source to destination filer. Then after that, I did  quiesce and break, as well as release (from the source). However, the SM relationship is still there and shown as "broken off" after I run "snapmirror status" . How do I remove this line?

there is no definition in /etc/snapmirror.conf. I can not remove the base snapshot on the destination, because it is Production now after the migration.

Please help me out!

Re: How to remove SM relationship after volume migrations

You need to remove remaining SnapMirror snapshots on destination.

Re: How to remove SM relationship after volume migrations

Right. I know it'd remove the line by removing snapshots. However, as I said, the destination is already in Production now. Would it cause any issues if I removed snapshots on the destination? and should remove all snapshots including the base?

Looking forward to hear you again.

Re: How to remove SM relationship after volume migrations

You need to remove only SnapMirror snapshots. I am not aware of any issues caused by it- you can delete any snapshot at any time.

Re: How to remove SM relationship after volume migrations

Remove the snapmirror base snapshot from destination volume.Use snapmirror status -l command to get the base snapshot information.

Re: How to remove SM relationship after volume migrations

If I remove the snapmirror base snapshot, do I have to rebase it?

HOw do I distinguish SM snapshots, and none-SM snapshots?

Re: How to remove SM relationship after volume migrations

Snapmirror snapshots have name pattern dest_name(sysid)_name.number. Of course, it may also be created manually, but I have never seen it.

I do not understand second question. What “rebase” means here?

Re: How to remove SM relationship after volume migrations

My 2nd question is , if I remove the base snapshot, Do I then have to run the baseline (initialization) again?

I thought the baseline will create the base snapshot.

Re: How to remove SM relationship after volume migrations

snapmirror snapshot is named as destfilerhostname(sysid)_destvolumename.number.

for 2nd question, i am not really sure the purpose of rebase. If the volume is already used as production volume, why do you need to re initialized.

However, the answer is Yes. You need to re initialized the snapmirror if you remove the base snapshot.

Re: How to remove SM relationship after volume migrations

Not quite. It is always possible to resync as long as some common snapshot exists. SnapMirror snapshots are not special in this respect.