[OpenAFS] Volume backup in distinct server

[Neulinger, Nathan]

Basically that's what you'd do if you wanted to create a completely new
distinct volume on the other server.=20

There was some thought a while back about adding a "vos copy" type
command that would allow copying a volume, but it has not been
implemented.

Alternatively, just add another Read-Only replicate to that server, and
vos release once a day. You'd need to force a read-write mount point for
accessing the read-write version of the volume though.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
UMR Information Technology             Fax: (573) 341-4216


> -----Original Message-----
> From: Joao Pedro Barreto [mailto:jpbarreto@gsd.inesc-id.pt]=20
> Sent: Tuesday, June 24, 2003 8:47 AM
> To: Derek Atkins
> Cc: openafs-info@openafs.org
> Subject: Re: [OpenAFS] Volume backup in distinct server
>=20
>=20
> Hi,
>=20
> But, after creating the clone in the same server/partition as the=20
> original volume, how can I copy its contents accross the net to the=20
> other server/partition?
> Is there any way I could do this using exclusively AFS=20
> commands? Or do I=20
> have to copy everything by my own hands, for example using a=20
> simple Unix=20
> cp command? And how can I configure it to be periodic, for=20
> instance, to=20
> be performed daily?
>=20
> The best thing I can think of is to issue a 'vos dump' command to the=20
> readonly clones, and piping its output to a 'vos restore' on=20
> the other=20
> server/partition. Putting this line for each volume I want to=20
> backup in=20
> a shell script and configure it in chron, I might have my=20
> problem solved.
> Do you find any problems with this solution? Or is there any better=20
> approach?
>=20
> Thank you.
> Joao
>=20
>=20
> Derek Atkins wrote:
> > Hi,
> >=20
> > The backup volume is meant for user access to backup data, not for
> > "replication across servers".  It's on the same server to reduce
> > the amount of disk space that is used.  It's purpose is not=20
> to protect
> > against lost disks, it's purpose is to protect against "rm".
> >=20
> > What you seem to want is ReadWrite replication, which is something
> > that AFS does not do.
> >=20
> > One thing you CAN do is make a RO clone on the same server/partition
> > as the RW (as well as on the other server).  The local RO clone wont
> > take up much disk space (it's a clone after all, just like=20
> the Backup
> > volume), but it does help in terms of the locking.  The RW only gets
> > locked in order to make the clone, and then the clone is=20
> copied across
> > the net.  This means your RW volume isn't locked for the=20
> whole release
> > process, only during the clone.
> >=20
> > -derek
> >=20
> > Joao Pedro Barreto <jpbarreto@gsd.inesc-id.id> writes:
> >=20
> >=20
> >>Hi,
> >>
> >>I administer an AFS domain which has two servers storing=20
> file volumes.
> >>I wanted to configure volume backup, so that each volume=20
> stored in one
> >>server's disk would be replicated (or backed up) in the=20
> other server's
> >>disk.
> >>My first approach was to create read-only replicas of each=20
> volume. For
> >>instance, if a volume was stored in server A, I would create a
> >>read-only volume for it on server B. However, I soon discovered that
> >>the release of volumes (which I'd perform daily in order to=20
> update the
> >>read-only volumes) NEEDS TO LOCK the original volume, which can be a
> >>serious drawback if we consider that most volumes are=20
> sufficiently big
> >>to take some hours to be released.
> >>I then found about the backup functionality which, according to AFS
> >>documentation, should be the best choice for my problem.=20
> Mainly, this
> >>solution doesn't require locking of the original volumes to=20
> update the
> >>backup volumes. However, this option only allows creation of backup
> >>volumes in the SAME PARTITION (AND SERVER) as the original
> >>volume. Which, of course, is insuficient to my requirements=20
> of having
> >>backup volumes in distinct computers from their original volumes (so
> >>that, if a computer fails and its data are lost, the volume=20
> can still
> >>be obtainable from the other computer).
> >>
> >>Does anyone can help me on this? how should I solve my problem?
> >>
> >>Thank you in advance.
> >>
> >>Joao
> >>jpbarreto _AT_ gsd _DOT_ inesc-id _DOT_ id
> >>
> >>
> >>_______________________________________________
> >>OpenAFS-info mailing list
> >>OpenAFS-info@openafs.org
> >>https://lists.openafs.org/mailman/listinfo/openafs-info
> >=20
> >=20
>=20
>=20
>=20
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20