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