I opened up a case with NetApp about this, but I figured I should also post here and see what the community has to say.
In a nutshell, I have two separate clusters and a volume with home directories on Filer_A that I was snapvaulting to Filer_B.
During the hurricane, I had to shut down Filer_A, break the snapvault relationship on Filer_B to promote the volume to RW and then started to have everyone use Filer_B as their home.
Folks have been working on Filer_B for 3 or so months now but I am ready to flip back and make Filer_A the primary once again.
What are my options for basically taking all the new data as well as the snapshots that are on Filer_B and syncing them back to Filer_A, without losing any of the snapshots that currently exist on Filer_A?
Right now the only option that comes to mind is the use rsync and copy a snapshot from Filer_B to Filer_A, take a snapshot on Filer_A, and repeat that process over and over until they have all been recreated on Filer_A.
With that, does anyone have any better suggestions?
Thanks in advance
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
If SnapMirror is licensed, I would urge that course: it's probably the least disruptive and is significantly easier than rsync, IMHO.
cheers,
- -=Tom Nail
On Tue, 5 Feb 2013 14:54:24 -0500 Steven Kreuzer skreuzer@freebsd.org wrote:
I opened up a case with NetApp about this, but I figured I should also post here and see what the community has to say.
In a nutshell, I have two separate clusters and a volume with home directories on Filer_A that I was snapvaulting to Filer_B.
During the hurricane, I had to shut down Filer_A, break the snapvault relationship on Filer_B to promote the volume to RW and then started to have everyone use Filer_B as their home.
Folks have been working on Filer_B for 3 or so months now but I am ready to flip back and make Filer_A the primary once again.
What are my options for basically taking all the new data as well as the snapshots that are on Filer_B and syncing them back to Filer_A, without losing any of the snapshots that currently exist on Filer_A?
Right now the only option that comes to mind is the use rsync and copy a snapshot from Filer_B to Filer_A, take a snapshot on Filer_A, and repeat that process over and over until they have all been recreated on Filer_A.
With that, does anyone have any better suggestions?
Thanks in advance
We don't have a license for snapmirror, but maybe I could make the argument its worth getting. It looks like snapmirror resync is what I need to do.
Just to confirm, since I have not worked with snapmirror in the past:
After Filer B became the primary filer for home directories, it has accumulated about 3 months worth of data and snapshots. At the beginning of each month, I take a snapshot of the volume and keep that around forever.
On filer A I 8 years worth of monthly snapshots up until 10/2012 and then on filer B I have monthly snapshot from 11/2012 to 02/2013.
I can not lose the snapshots that are currently on filer A and I would also like to bring over the snapshots from filer b and just kinda merge them into the volume. A snapmirror resync is capable of this?.
While Filer A was offline, I was snapvaulting filer B to filer C so as it currently stands, Filer A and Filer B have no snapvault or snapmirror relationship whatso ever
On Tue, Feb 5, 2013 at 4:39 PM, Thomas Nail tnail@austin.utexas.edu wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
If SnapMirror is licensed, I would urge that course: it's probably the least disruptive and is significantly easier than rsync, IMHO.
cheers,
- -=Tom Nail
On Tue, 5 Feb 2013 14:54:24 -0500 Steven Kreuzer skreuzer@freebsd.org wrote:
I opened up a case with NetApp about this, but I figured I should also post here and see what the community has to say.
In a nutshell, I have two separate clusters and a volume with home directories on Filer_A that I was snapvaulting to Filer_B.
During the hurricane, I had to shut down Filer_A, break the snapvault relationship on Filer_B to promote the volume to RW and then started to have everyone use Filer_B as their home.
Folks have been working on Filer_B for 3 or so months now but I am ready to flip back and make Filer_A the primary once again.
What are my options for basically taking all the new data as well as the snapshots that are on Filer_B and syncing them back to Filer_A, without losing any of the snapshots that currently exist on Filer_A?
Right now the only option that comes to mind is the use rsync and copy a snapshot from Filer_B to Filer_A, take a snapshot on Filer_A, and repeat that process over and over until they have all been recreated on Filer_A.
With that, does anyone have any better suggestions?
Thanks in advance
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAlERfAAACgkQH7E81Q7leo7yLQCcDA59moNaiqMBBoGB86LUatGT G1IAn3rAgFtqg8fJlhxthbAkaEoIfQRo =i0UE -----END PGP SIGNATURE-----
I was going to suggest that you convert the SnapVault relationship into a SnapMirror Relationship (snapmirror convert - in priv set diag mode)
BUT you've been promiscuous (or rather Filer B)... vaulting to Filer C broke the relationship for good. They were separated, you divorced them (irreconcilable differences - i.e. no common SnapVault snapshot anymore, probably).
Another question to clarify: Filer B *doesn't* have the 8 years of monthly snapshots, that are on Filer A? I thought you said you snapvaulted to Filer B. I would have expected the 8 years *plus* the new stuff on Filer B.
With a Volume SnapMirror you could have easily transferred the missing bits back to Filer A (as long as there's still a 'common' SnapShot)
Short of a PS engagement I don't see a (publicly available) way to merge the volumes again. I'd probably go along the line of 'archiving' the Filer A volume, making a clone on the base of the last common SnapShot with Filer B, and SnapMirror resync'ing the current contents of Filer B (including all snapshots) back to A. Thereafter you might even flip the mirror again and re-convert the SnapMirror relationship to a SnapVault...
my 2cents
Sebastian
On 06.02.2013 19:41, Steven Kreuzer wrote:
We don't have a license for snapmirror, but maybe I could make the argument its worth getting. It looks like snapmirror resync is what I need to do.
Just to confirm, since I have not worked with snapmirror in the past:
After Filer B became the primary filer for home directories, it has accumulated about 3 months worth of data and snapshots. At the beginning of each month, I take a snapshot of the volume and keep that around forever.
On filer A I 8 years worth of monthly snapshots up until 10/2012 and then on filer B I have monthly snapshot from 11/2012 to 02/2013.
I can not lose the snapshots that are currently on filer A and I would also like to bring over the snapshots from filer b and just kinda merge them into the volume. A snapmirror resync is capable of this?.
While Filer A was offline, I was snapvaulting filer B to filer C so as it currently stands, Filer A and Filer B have no snapvault or snapmirror relationship whatso ever
On Tue, Feb 5, 2013 at 4:39 PM, Thomas Nail <tnail@austin.utexas.edu mailto:tnail@austin.utexas.edu> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If SnapMirror is licensed, I would urge that course: it's probably the least disruptive and is significantly easier than rsync, IMHO. cheers, - -=Tom Nail On Tue, 5 Feb 2013 14:54:24 -0500 Steven Kreuzer <skreuzer@freebsd.org <mailto:skreuzer@freebsd.org>> wrote: > I opened up a case with NetApp about this, but I figured I should > also post here and see what the community has to say. > > In a nutshell, I have two separate clusters and a volume with home > directories on Filer_A that I was snapvaulting to Filer_B. > > During the hurricane, I had to shut down Filer_A, break the snapvault > relationship on Filer_B to promote the volume to RW and then started > to have everyone use Filer_B as their home. > > Folks have been working on Filer_B for 3 or so months now but I am > ready to flip back and make Filer_A the primary once again. > > What are my options for basically taking all the new data as well as > the snapshots that are on Filer_B and syncing them back to Filer_A, > without losing any of the snapshots that currently exist on Filer_A? > > Right now the only option that comes to mind is the use rsync and > copy a snapshot from Filer_B to Filer_A, take a snapshot on Filer_A, > and repeat that process over and over until they have all been > recreated on Filer_A. > > With that, does anyone have any better suggestions? > > Thanks in advance -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlERfAAACgkQH7E81Q7leo7yLQCcDA59moNaiqMBBoGB86LUatGT G1IAn3rAgFtqg8fJlhxthbAkaEoIfQRo =i0UE -----END PGP SIGNATURE-----
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Due to space constraints on Filer B, the 8 years worth of snapshots are only on Filer A. It doesn't appear that I have any common snapshots anymore that I can even attempt to use as a starting point
It sounding more and more like the rsync approach, while tedious, is going to be the safest way to migrate all this stuff over. I guess the silver lining is that since I don't need to worry about mismatched versions of ontap with snapmiror, I can upgrade Filer A to 8.1.2 before I cut back over
Many Thanks to everyone for their help. I really appreciate it
On Wed, Feb 6, 2013 at 4:02 PM, Sebastian Goetze spgoetze@gmail.com wrote:
I was going to suggest that you convert the SnapVault relationship into a SnapMirror Relationship (snapmirror convert - in priv set diag mode)
BUT you've been promiscuous (or rather Filer B)... vaulting to Filer C broke the relationship for good. They were separated, you divorced them (irreconcilable differences - i.e. no common SnapVault snapshot anymore, probably).
Another question to clarify: Filer B *doesn't* have the 8 years of monthly snapshots, that are on Filer A? I thought you said you snapvaulted to Filer B. I would have expected the 8 years *plus* the new stuff on Filer B.
With a Volume SnapMirror you could have easily transferred the missing bits back to Filer A (as long as there's still a 'common' SnapShot)
Short of a PS engagement I don't see a (publicly available) way to merge the volumes again. I'd probably go along the line of 'archiving' the Filer A volume, making a clone on the base of the last common SnapShot with Filer B, and SnapMirror resync'ing the current contents of Filer B (including all snapshots) back to A. Thereafter you might even flip the mirror again and re-convert the SnapMirror relationship to a SnapVault...
my 2cents
Sebastian
On 06.02.2013 19:41, Steven Kreuzer wrote:
We don't have a license for snapmirror, but maybe I could make the argument its worth getting. It looks like snapmirror resync is what I need to do.
Just to confirm, since I have not worked with snapmirror in the past:
After Filer B became the primary filer for home directories, it has accumulated about 3 months worth of data and snapshots. At the beginning of each month, I take a snapshot of the volume and keep that around forever.
On filer A I 8 years worth of monthly snapshots up until 10/2012 and then on filer B I have monthly snapshot from 11/2012 to 02/2013.
I can not lose the snapshots that are currently on filer A and I would also like to bring over the snapshots from filer b and just kinda merge them into the volume. A snapmirror resync is capable of this?.
While Filer A was offline, I was snapvaulting filer B to filer C so as it currently stands, Filer A and Filer B have no snapvault or snapmirror relationship whatso ever
On Tue, Feb 5, 2013 at 4:39 PM, Thomas Nail tnail@austin.utexas.eduwrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
If SnapMirror is licensed, I would urge that course: it's probably the least disruptive and is significantly easier than rsync, IMHO.
cheers,
- -=Tom Nail
On Tue, 5 Feb 2013 14:54:24 -0500 Steven Kreuzer skreuzer@freebsd.org wrote:
I opened up a case with NetApp about this, but I figured I should also post here and see what the community has to say.
In a nutshell, I have two separate clusters and a volume with home directories on Filer_A that I was snapvaulting to Filer_B.
During the hurricane, I had to shut down Filer_A, break the snapvault relationship on Filer_B to promote the volume to RW and then started to have everyone use Filer_B as their home.
Folks have been working on Filer_B for 3 or so months now but I am ready to flip back and make Filer_A the primary once again.
What are my options for basically taking all the new data as well as the snapshots that are on Filer_B and syncing them back to Filer_A, without losing any of the snapshots that currently exist on Filer_A?
Right now the only option that comes to mind is the use rsync and copy a snapshot from Filer_B to Filer_A, take a snapshot on Filer_A, and repeat that process over and over until they have all been recreated on Filer_A.
With that, does anyone have any better suggestions?
Thanks in advance
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAlERfAAACgkQH7E81Q7leo7yLQCcDA59moNaiqMBBoGB86LUatGT G1IAn3rAgFtqg8fJlhxthbAkaEoIfQRo =i0UE -----END PGP SIGNATURE-----
Toasters mailing listToasters@teaparty.nethttp://www.teaparty.net/mailman/listinfo/toasters
Steven> Due to space constraints on Filer B, the 8 years worth of Steven> snapshots are only on Filer A.
Wow, you must have a wonderfully low rate of change by your users to be able to keep that much stuff online. I'm lucky if I can keep five days, since my users can generate a Terabyte a day when they're on a roll. Just wow...
John
John Stoffel wrote:
Steven> Due to space constraints on Filer B, the 8 years worth of Steven> snapshots are only on Filer A.
Wow, you must have a wonderfully low rate of change by your users to be able to keep that much stuff online. I'm lucky if I can keep five days, since my users can generate a Terabyte a day when they're on a roll. Just wow...
I second this. 8 years, wow... The total growth rate in all our "Primary" storage (100% NetApp counted here only and there are quite a few systems), at the site in Stockholm which is by far our largest R&D Centre, is ~23 TB/month. So that's all in all ~1 TB / working day. But this is aggregated by many 1000s of users
The total volume is ~600 TB (net) now and there's a very high number of inodes in total
/M
-
John Stoffel -
Michael Bergman -
Sebastian Goetze -
Steven Kreuzer -
Thomas Nail