[cisco-voip] backup strategy - pub and tftp? (V7)

[Matthew Saskin]

A DB sync will still occur whether you do a restore or build a sub from
scratch.  The issue with a subscriber rebuild is, as Ed points out, you'll
need to step through and recreate/edit any software media resources using
that server, as well as make changes to CM groups, etc.

Matthew Saskin
msaskin at gmail.com
203-253-9571



On Thu, Mar 3, 2011 at 8:16 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

> Yeah, fair enough, files are not database entries. But restoring a
> subscriber only from a backup that could be up to 23 hours out of date would
> make the database out of sync, irregardless, so some sort of resync still
> has to happen.
>
> I'll have to read up on the PDF some more.
>
> Thanks Ed.
>
> Sent from my iPhone
>
> On Mar 3, 2011, at 8:07 PM, Ed Leatherman <ealeatherman at gmail.com> wrote:
>
> > I'm totally guessing here, but maybe its partly to cover any MOH or
> > other files you have on the particular server, and partly to make sure
> > the database keys already all match up so there is less work on the
> > pub wrt db replication. If you added the sub as a new server, wouldn't
> > that cause a lot of updates across the cluster when you go to add it
> > back into a CM group, mrg, etc?
> >
> > On Thu, Mar 3, 2011 at 3:33 PM, Lelio Fulgenzi <lelio at uoguelph.ca>
> wrote:
> >> Thanks Ed. After running the actual backup, it answered a lot of my
> >> questions. You enable the backup on the publisher and it backs up
> >> everything. Which is kinda cool. Depending on your situation, you pick
> the
> >> restore mechanism you need.
> >>
> >> Aside from the TFTP server though, I'm still not understanding why you
> would
> >> need to "restore" a sub. Shouldn't everything be stored in the databases
> and
> >> pushed out to the subs as the database gets replicated?
> >>
> >>
> >>
> >> ---
> >> Lelio Fulgenzi, B.A.
> >> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> >> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> Cooking with unix is easy. You just sed it and forget it.
> >>                               - LFJ (with apologies to Mr. Popeil)
> >>
> >>
> >> ________________________________
> >> From: "Ed Leatherman" <ealeatherman at gmail.com>
> >> To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
> >> Cc: cisco-voip at puck.nether.net
> >> Sent: Thursday, March 3, 2011 10:40:08 AM
> >> Subject: Re: [cisco-voip] backup strategy - pub and tftp? (V7)
> >>
> >> I've restored my cluster in the lab by installing each node and then
> >> using DRS to restore from backup, starting with pub (obviously), then
> >> tftp, then the subs. Is there a benefit to adding them as a new sub
> >> versus restoring from backup? One of my subs is also a secondary TFTP
> >> server so I would probably restore that one from the backup also even
> >> if I re-added other subs from scratch.
> >>
> >> Every time i've replaced a sub (hardware replacement), I've installed
> >> CM on the new server and then restored the DRS backup to that sub,
> >> seems to work out just fine.
> >>
> >> On Wed, Mar 2, 2011 at 11:36 AM, Lelio Fulgenzi <lelio at uoguelph.ca>
> wrote:
> >>> Just wondering what people's strategy for backups are. We have a pub, a
> >>> dedicated TFTP server and four subs. In the past I believe the
> recommended
> >>> approach was to recover the pub from backup and rebuild subs from
> scratch.
> >>> Having the TFTP server backed up though would allow us to ensure our
> TFTP
> >>> directories are populated correctly.
> >>>
> >>> What are others doing? Are you simply backing up the pub and ensuring
> you
> >>> have all the files necessary to repopulate the TFTP server?
> >>>
> >>>
> >>>
> >>> ---
> >>> Lelio Fulgenzi, B.A.
> >>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> >>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> >>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >>> Cooking with unix is easy. You just sed it and forget it.
> >>>                               - LFJ (with apologies to Mr. Popeil)
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> cisco-voip mailing list
> >>> cisco-voip at puck.nether.net
> >>> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Ed Leatherman
> >>
> >
> >
> >
> > --
> > Ed Leatherman
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110306/0eb37a8a/attachment.html>