2011-04-04 07:26 AM - edited 2015-12-18 01:28 AM
2011-04-04 09:16 AM
The Migration Capable is for the Vfiler, are you trying to migrate entire vfiler ?
Or just the secondary volumes ? If secondary volumes use the Host-.Aggregates-> Secondary Space Management to move the backup or mirror volumes.
If its primary and are from vfilers use Online/Offline Vfiler migration.
2011-04-05 12:57 PM
thanks adai for the quick answer "secondary space management" cool
I think this was the right direction.
I end up now with a screen whe I have to select the destination aggregate.
nothing shows up here , I have to read more..
thanks to point me to this direction.
2011-04-05 01:34 PM
You must add the aggr to a resource pool and attach it to the node of the dataset to which the volume you plan to migrate belongs too.
For example if you have a dataset with backup policy you must attach the aggr to a RP and attach it to the backup node of the dataset.
Secondary Space Management, which migrates individual volume, which are part of dataset.
The rule or conditions that needs to be met for a volume to be migrate capable is the following.
SSM doesn't migrate the following.
If there are client facing protocols.You must remove the client facing protocols you will be able to migrate using SSM, but during the entire duration of initial baseline from old destination to new destination.
After the inital baseline SSM will modify the relationship, you dont have to rebaseline the downstream relationship and also wont loose any already registered backup.