|
Home > Archive > Data Storage > September 2006 > EMC CXseries and snapview
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
EMC CXseries and snapview
|
|
| jon.newsgroups@gmail.com 2006-09-01, 1:16 pm |
| OK, fairly new to this stuff, can someone clarify exactly what the deal
is with snapview, sessions and snapshots and when to start each of them
What i first thought was you could take a snapshot and that would be
it, but i believe you need to create a session first, is this correct
And how would one plan for a daily snapshot/session to take place so
that one could return to a point in time over the last couple of days?
Would one start a session and keep taking snapshots
Basic overview would be great
Jon
| |
| Jon Metzger 2006-09-05, 1:18 pm |
| jon.newsgroups@gmail.com wrote:
> OK, fairly new to this stuff, can someone clarify exactly what the deal
> is with snapview, sessions and snapshots and when to start each of them
>
> What i first thought was you could take a snapshot and that would be
> it, but i believe you need to create a session first, is this correct
> And how would one plan for a daily snapshot/session to take place so
> that one could return to a point in time over the last couple of days?
> Would one start a session and keep taking snapshots
>
> Basic overview would be great
> Jon
>
The whole thing is confusing if you're new to it, they really could have
chosen a more intuitive naming convention. A SnapView "session" is what
represents the point in time copy of a single LUN or multiple LUNs.
Every point in time copy you create will require another session. Each
of the LUNs in the session has also has a "snapshot", which you can
manipulate with Navisphere as if they are individual LUNs themselves.
Once these LUNs are in a storage group (and this visible to the host(s)
in that storage group) they must be "activated" before the host will be
able to mount them. The order generally goes this way:
Create snapshots of the LUNs you want a point in time copy of. Do this
by right-clicking each LUN in Navisphere and choose Snapview -> Create
Snapshot.
Add your snapshots to the Storage Group of the host you want to have
access to your point in time copies.
Create a snapshot session. The LUNs which are listed as available to
add to the session will only be LUNs with snapshots already created.
When the session is created, that's the point in time you'll end up with.
Your host won't be able to see the point in time copy until you activate
the snapshot. When you activate a snapshot for a particular LUN you are
asked to choose a session. If there are multiple sessions created, you
get to pick which one the snapshot will represent.
Rescan LUNs on your host and mount up the snapshot.
| |
| jon.newsgroups@gmail.com 2006-09-06, 1:15 pm |
| Thanks for the reply, its was a great summary and a starting point for
me to move forward
Jon.
Jon Metzger wrote:
> jon.newsgroups@gmail.com wrote:
>
> The whole thing is confusing if you're new to it, they really could have
> chosen a more intuitive naming convention. A SnapView "session" is what
> represents the point in time copy of a single LUN or multiple LUNs.
> Every point in time copy you create will require another session. Each
> of the LUNs in the session has also has a "snapshot", which you can
> manipulate with Navisphere as if they are individual LUNs themselves.
> Once these LUNs are in a storage group (and this visible to the host(s)
> in that storage group) they must be "activated" before the host will be
> able to mount them. The order generally goes this way:
>
> Create snapshots of the LUNs you want a point in time copy of. Do this
> by right-clicking each LUN in Navisphere and choose Snapview -> Create
> Snapshot.
>
> Add your snapshots to the Storage Group of the host you want to have
> access to your point in time copies.
>
> Create a snapshot session. The LUNs which are listed as available to
> add to the session will only be LUNs with snapshots already created.
> When the session is created, that's the point in time you'll end up with.
>
> Your host won't be able to see the point in time copy until you activate
> the snapshot. When you activate a snapshot for a particular LUN you are
> asked to choose a session. If there are multiple sessions created, you
> get to pick which one the snapshot will represent.
>
> Rescan LUNs on your host and mount up the snapshot.
|
|
|
|
|