No, you don't need to activate the session. When you restore your data you create a brand new session in the opposite direction and activate it immediatly. You can monitor copy progress querying the disk group. But since clones uses pointers, recreating and activating the session is almost immediate.
after restore is finished you will need to run symclone split -g and after that you can run either establish or recreate to start syncing again from source to target.
Thanks for the replys. But, I'm still a bit confused. dynamox stated that I need to run split: - Does the split have to be executed when the data or Database is stopped or put into backup mode?
Stefano said that I don't have to ACTIVATE the session: - But then says: "When you restore your data you create a brand new session in the opposite direction and activate it immediatly." - So, does that mean that the RESTORE command starts the target to source copy, and when it's done, i.e. all pairings display as "RESTORED", then no further action is needed?
Other follow-ups: - Is SPLIT required only if I want to start another CLONE session of the same data? - Do I need to immediately run ESTABLISH or RECREATE, or can I wait until next time a CLONE of the same data is requested? - What happens if updates were made to the target? Are the changes copied to the source upon RESTOREing?
1) symclone terminate (you split symmir pairs, you terminate symclone pairs) You need to terminate existing (restored) relations in case you need to re-create new pairs .. You can terminate your pairs whenever you want (just look the manuals and check prerequisites).
2) symclone restore will take care of both steps .. symclone restore will create relations in the opposite direction and activate them. As soon as the command completes you can access data on the source, while the copy process is still running in the background. You reach the "restored" state when the copy process reaches 100% .. But you can access data as soon as "symclone restore" command completes.
3) you run recreate or establish depending on your needs .. restoring data doesn't need either the first or the second ...
4) If you changed your target between activating original clone session and restoring data to source, you'll propagate changes to the sources. if you change target volumes AFTER the restore, changes won't propagate.
xe2sdc
4 Operator
•
2.8K Posts
0
January 9th, 2009 15:00
When you restore your data you create a brand new session in the opposite direction and activate it immediatly. You can monitor copy progress querying the disk group. But since clones uses pointers, recreating and activating the session is almost immediate.
dynamox
9 Legend
•
20.4K Posts
1
January 9th, 2009 15:00
xe2sdc
4 Operator
•
2.8K Posts
0
January 9th, 2009 15:00
sragusa
6 Posts
0
January 12th, 2009 07:00
dynamox stated that I need to run split:
- Does the split have to be executed when the data or Database is stopped or put into backup mode?
Stefano said that I don't have to ACTIVATE the session:
- But then says: "When you restore your data you create a brand new session in the opposite direction and activate it immediatly."
- So, does that mean that the RESTORE command starts the target to source copy, and when it's done, i.e. all pairings display as "RESTORED", then no further action is needed?
Other follow-ups:
- Is SPLIT required only if I want to start another CLONE session of the same data?
- Do I need to immediately run ESTABLISH or RECREATE, or can I wait until next time a CLONE of the same data is requested?
- What happens if updates were made to the target? Are the changes copied to the source upon RESTOREing?
Thanks again!
xe2sdc
4 Operator
•
2.8K Posts
0
January 12th, 2009 08:00
You need to terminate existing (restored) relations in case you need to re-create new pairs .. You can terminate your pairs whenever you want (just look the manuals and check prerequisites).
2) symclone restore will take care of both steps .. symclone restore will create relations in the opposite direction and activate them. As soon as the command completes you can access data on the source, while the copy process is still running in the background. You reach the "restored" state when the copy process reaches 100% .. But you can access data as soon as "symclone restore" command completes.
3) you run recreate or establish depending on your needs .. restoring data doesn't need either the first or the second ...
4) If you changed your target between activating original clone session and restoring data to source, you'll propagate changes to the sources. if you change target volumes AFTER the restore, changes won't propagate.