Primary Storage

As I understand vol_copy is immediate , and the data copy then happens in the background.

We want to use this vol_copy to make a safe copy of the volumes which we are going to migrate, and just in case we have to use them, if the migration fails. So, want to know and calculate how early prior to intervention window, I should run this command, so that it has as latest copy of the data as possible.  Like, I run it one hour before the window, so that it copies 2TB LUN by that time.  And, I don't want to be in situation that background copy was still happening at that time. Need to make sure that full copy has been done.
Do you info on this. I came to know from support that The copy is purely metadata which points to the state of the volume at the time the vol_copy was initiated and any 'new' data in the original volume is tracked separately.
vol_copy creates a set of pointers which essentially fork a volume and changes to the original are tracked in the first prong of the fork while changes to the copy are tracked in the second.

Our idea is to use the new copy in case , we had to after the migration, or in case there is some issue in the migration.

Will the clone copy can be used in that case. Like, we want to them map the clone volumes to the hosts and bring it up like it was at the start of migration. This is the only goal here.

Thanks.

As I understand vol_copy is immediate , and the data copy then happens in the background.

We want to use this vol_copy to make a safe copy of the volumes which we are going to migrate, and just in case we have to use them, if the migration fails. So, want to know and calculate how early prior to intervention window, I should run this command, so that it has as latest copy of the data as possible.  Like, I run it one hour before the window, so that it copies 2TB LUN by that time.  And, I don't want to be in situation that background copy was still happening at that time. Need to make sure that full copy has been done.
Do you info on this. I came to know from support that The copy is purely metadata which points to the state of the volume at the time the vol_copy was initiated and any 'new' data in the original volume is tracked separately.
vol_copy creates a set of pointers which essentially fork a volume and changes to the original are tracked in the first prong of the fork while changes to the copy are tracked in the second.

Our idea is to use the new copy in case , we had to after the migration, or in case there is some issue in the migration.

Will the clone copy can be used in that case. Like, we want to them map the clone volumes to the hosts and bring it up like it was at the start of migration. This is the only goal here.

Thanks.

As I understand vol_copy is immediate , and the data copy then happens in the background.

We want to use this vol_copy to make a safe copy of the volumes which we are going to migrate, and just in case we have to use them, if the migration fails. So, want to know and calculate how early prior to intervention window, I should run this command, so that it has as latest copy of the data as possible.  Like, I run it one hour before the window, so that it copies 2TB LUN by that time.  And, I don't want to be in situation that background copy was still happening at that time. Need to make sure that full copy has been done.
Do you info on this. I came to know from support that The copy is purely metadata which points to the state of the volume at the time the vol_copy was initiated and any 'new' data in the original volume is tracked separately.
vol_copy creates a set of pointers which essentially fork a volume and changes to the original are tracked in the first prong of the fork while changes to the copy are tracked in the second.

Our idea is to use the new copy in case , we had to after the migration, or in case there is some issue in the migration.

Will the clone copy can be used in that case. Like, we want to them map the clone volumes to the hosts and bring it up like it was at the start of migration. This is the only goal here.

Thanks.