Hi,
Thanks to all those who helped me over the Networking problem...
Now on to bigger/better/harder things.
As I mentioned, the customer had a F720 shipped in. When I configured it, I just threw everything into vol0.
Now when I look to use SNAPMIRROR to mirror from "A" filer to "B" filer, I can do it by volumes only. Am I correct isn ASSuM(E)ing that if I mirror "vol0" I'll clobber the configuration of "B" filer?
I decided to believe this was correct, and reloaded the "B" filer. I created a "vol1" on it with the remaining 5 disks. In attempting to setup the snapmirror, it now complains that the volume is on-line. Um, how is it going to let people still access it if it goes offline?
So to see where I can get myself into more trouble, I offline it, reboot, and now its complaining they are different sizes.
I have a feeling there is A BUNCH of confusion on my part. Maybe if I say what I want, someone can shoot the clue-gun at me.
I want only 1 computer to have update access to filer "A". This will be the host that updates the content on the disk. 3 other computers will have this mounted RO. I will also have filer "B". 4 computers will have this mounted RO. I'd like to have "A" filer copy the content to "B" filer once every (??? not sure yet, say minute to be on the safe side ???).
Thanks, Tuc/TTSG
Hi,
Thanks to all those who helped me over the Networking problem...
Now on to bigger/better/harder things.
As I mentioned, the customer had a F720 shipped in. When I configured it, I just threw everything into vol0.
Now when I look to use SNAPMIRROR to mirror from "A" filer to "B" filer, I can do it by volumes only. Am I correct isn ASSuM(E)ing that if I mirror "vol0" I'll clobber the configuration of "B" filer?
I decided to believe this was correct, and reloaded the "B" filer. I created a "vol1" on it with the remaining 5 disks. In attempting to setup the snapmirror, it now complains that the volume is on-line. Um, how is it going to let people still access it if it goes offline?
So to see where I can get myself into more trouble, I offline it, reboot, and now its complaining they are different sizes.
I have a feeling there is A BUNCH of confusion on my part. Maybe if I say what I want, someone can shoot the clue-gun at me.
I want only 1 computer to have update access to filer "A". This will be the host that updates the content on the disk. 3 other computers will have this mounted RO. I will also have filer "B". 4 computers will have this mounted RO. I'd like to have "A" filer copy the content to "B" filer once every (??? not sure yet, say minute to be on the safe side ???).
Thanks, Tuc/TTSG
Some general snapmirror rules and behaviors.
1) The snapmirror destination must have at least two volumes. The root volume cannot be the read-only snapmirror destination.
2) The snapmirror source volume must be on-line, and can be the root volume.
3) The destination volume must start off-line. After the first transfer, it will be brought on-line. Subsequent transfers will be run while the volume is on-line. Only the first transfer must have the destination off-line.
4) The capacity of snapmirror destination must be greater than or equal to the capacity of the source volume (otherwise, where are you going to mirror the data into when the source fills up?)
5) If replication is between two different filers, they must be able to ping each other.
I think the error messages have been guiding you down the appropriate path, which is what they were meant to do. I suspect you don't have enough capacity on the snapmirror destination. You probably need to add disks...
Stephen Manley Data Availability and Management "Top 5" List Maker
Hi,
Thanks to all those who helped me over the Networking problem...
Now on to bigger/better/harder things.
As I mentioned, the customer had a F720 shipped in. When I configured it, I just threw everything into vol0.
Now when I look to use SNAPMIRROR to mirror from "A" filer to "B" filer, I can do it by volumes only. Am I correct isn ASSuM(E)ing that if I mirror "vol0" I'll clobber the configuration of "B" filer?
I decided to believe this was correct, and reloaded the "B" filer. I created a "vol1" on it with the remaining 5 disks. In attempting to setup the snapmirror, it now complains that the volume is on-line. Um, how is it going to let people still access it if it goes offline?
So to see where I can get myself into more trouble, I offline it, reboot, and now its complaining they are different sizes.
I have a feeling there is A BUNCH of confusion on my part. Maybe if I say what I want, someone can shoot the clue-gun at me.
I want only 1 computer to have update access to filer "A". This will be the host that updates the content on the disk. 3 other computers will have this mounted RO. I will also have filer "B". 4 computers will have this mounted RO. I'd like to have "A" filer copy the content to "B" filer once every (??? not sure yet, say minute to be on the safe side ???).
Thanks, Tuc/TTSG
Some general snapmirror rules and behaviors.
- The snapmirror destination must have at least two volumes. The
root volume cannot be the read-only snapmirror destination.
Ok, "B" does have 2... "vol0" is 2 disks, the root. "vol1" (Ok, so I'm not TOO TOO creative) is 5 disks and where I want the final to be.
- The snapmirror source volume must be on-line, and can be the root volume.
Ok. If I use "vol0", does it mean it'll copy even the "/etc" and other files over?
- The destination volume must start off-line. After the first transfer,
it will be brought on-line. Subsequent transfers will be run while the volume is on-line. Only the first transfer must have the destination off-line.
Ah, ok, I didn't grok this properly from the manuals.
- The capacity of snapmirror destination must be greater than or
equal to the capacity of the source volume (otherwise, where are you going to mirror the data into when the source fills up?)
I realize that does make sense, but I was trying to get A:vol0 to mirror to B:vol1 for now to see if my concern of the "/etc" was valid. If an "A:vol0->B:vol1" only copies everything in /home and down, then thats good. If not, then I'll need to create a vol1 on A also. THEN the issue becomes that I can only use the 5 disks (left, past the initial 2) for both, which SEVERELY cuts down on the free space available. Gets me down to the 500 or so range, with another 125 for .snapshot(??).
- If replication is between two different filers, they must be able to
ping each other.
No problems.
I think the error messages have been guiding you down the appropriate path, which is what they were meant to do. I suspect you don't have enough capacity on the snapmirror destination. You probably need to add disks...
Its more "Do I now have to reload A, and only use 5 disks for the vol1"....
Thanks!, Tuc/TTSG
- The snapmirror source volume must be on-line, and can be the root volume.
Ok. If I use "vol0", does it mean it'll copy even the "/etc" and other files over?
- The destination volume must start off-line. After the first transfer,
it will be brought on-line. Subsequent transfers will be run while the volume is on-line. Only the first transfer must have the destination off-line.
Ah, ok, I didn't grok this properly from the manuals.
- The capacity of snapmirror destination must be greater than or
equal to the capacity of the source volume (otherwise, where are you going to mirror the data into when the source fills up?)
I realize that does make sense, but I was trying to get A:vol0 to mirror to B:vol1 for now to see if my concern of the "/etc" was valid. If an "A:vol0->B:vol1" only copies everything in /home and down, then thats good. If not, then I'll need to create a vol1 on A also. THEN the issue becomes that I can only use the 5 disks (left, past the initial 2) for both, which SEVERELY cuts down on the free space available. Gets me down to the 500 or so range, with another 125 for .snapshot(??).
- If replication is between two different filers, they must be able to
ping each other.
No problems.
I think the error messages have been guiding you down the appropriate path, which is what they were meant to do. I suspect you don't have enough capacity on the snapmirror destination. You probably need to add disks...
Its more "Do I now have to reload A, and only use 5 disks for the vol1"....
I'm not sure I completely understand the question, so forgive me if I don't address your issue.
First, ALL of a snapmirrored volume is mirrored. There is no way to make it finer-grained, or to make it exclude certain files or directories.
Let's say you have machines A and B.
A has one volume: vol0. vol0 has 7 disks and is the root volume. Its /etc files are used for machine configuration.
B has two volumes: vol0 and vol1. vol0 has 2 disks and is the root volume. Its /etc files are used for machine configuration. vol1 has 7 disks and is a snapmirror of A:vol0. It is only readable, and its /etc files are NOT used for machine configuration, unless you break the mirror, make it writeable, and make it the root volume.
So, I don't think you need to be too worried about the mirroring of /etc. However, you still would need 2 more disks on B:vol1 to be able to mirror A:vol0 to it.
Stephen Manley Data Availability and Management Set-Up Reliever