LOL...complete oversight. Forgot I just said that. On Wed, Feb 6, 2013 at 4:56 PM, Eric Muehleisen <[email protected]> wrote:
> Wait, mikrotik noob here... > > you're telling me that 5.6 is older than 5.12??? > > > On Wed, Feb 6, 2013 at 4:54 PM, Shayne Lebrun <[email protected]>wrote: > >> Yeah, the first line 'more recent versions.' Actually 5.12, not 5.14, but >> that' s definitely higher than 5.6. :-) >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Eric >> Muehleisen >> Sent: Wednesday, February 6, 2013 17:51 >> To: Mikrotik discussions >> Subject: Re: [Mikrotik] Automatic config backup >> >> For some reason, /export compact doesn't work on my RB 750's ROS 5.6. >> >> Am I missing something? >> >> On Wed, Feb 6, 2013 at 3:20 PM, Shayne Lebrun >> <[email protected]>wrote: >> >> > If you're using more recent versions of ROS, 5.14 or something and >> > higher, use '/export compact file=blahblah.rsc' to get only what you >> > actually need to apply to a new router. >> > >> > We use something like: >> > /system scheduler add name="backup" on-event="/export compact >> > file=systembackup" start-date=jan/01/1970 start-time=04:00:00 >> > interval=24h comment="" disabled=no >> > >> > /ip tftp add req-filename=systembackup.cfg >> > real-filename=systembackup.rsc allow=yes read-only=yes >> > ip-addresses=xx.xx.xx.xx >> > >> > Then on a server somewhere, a cron script at 4 am; given a file with a >> > csv of name and address, download file, rename to router name and date, >> save. >> > Delete anything older than however long you want to keep. My backup >> > folder has 1343 files in it ATM, about 11 megs. >> > >> > -----Original Message----- >> > From: [email protected] >> > [mailto:[email protected]] On Behalf Of Eric >> > Muehleisen >> > Sent: Wednesday, February 6, 2013 16:12 >> > To: Mikrotik discussions >> > Subject: Re: [Mikrotik] Automatic config backup >> > >> > These backups and restores are using the same hardware. It's looking >> > like the /export is the better, more reliable method. >> > >> > On Wed, Feb 6, 2013 at 3:05 PM, Josh Luthman >> > <[email protected]>wrote: >> > >> > > The binary backup is super picky. I've had minimal success with it, >> > > though I do use it (but I primarily depend on text backup - /export). >> > > >> > > You'll NEED to have the same number of ports to begin with. There >> > > are additional hassles but I can't remember them it has been so long. >> > > >> > > Josh Luthman >> > > Office: 937-552-2340 >> > > Direct: 937-552-2343 >> > > 1100 Wayne St >> > > Suite 1337 >> > > Troy, OH 45373 >> > > >> > > >> > > On Wed, Feb 6, 2013 at 4:03 PM, Eric Muehleisen <[email protected]> >> > > wrote: >> > > >> > > > I currently do MT backups using the scheduler to do a "system >> > > > backup save name" then a FTP fetch. This all works correctly but >> > > > the file fails when >> > > I >> > > > try to upload the config and restore to a new router. Does the >> > > > backup >> > > file >> > > > become corrupt during this process? >> > > > -------------- next part -------------- An HTML attachment was >> > > > scrubbed... >> > > > URL: < >> > > > >> > > http://mail.butchevans.com/pipermail/mikrotik/attachments/20130206/4 >> > > 9d >> > > 8b59b/attachment.html >> > > > > >> > > > _______________________________________________ >> > > > Mikrotik mailing list >> > > > [email protected] >> > > > http://mail.butchevans.com/mailman/listinfo/mikrotik >> > > > >> > > > Visit http://blog.butchevans.com/ for tutorials related to >> > > > Mikrotik RouterOS >> > > > >> > > -------------- next part -------------- An HTML attachment was >> > > scrubbed... >> > > URL: < >> > > http://mail.butchevans.com/pipermail/mikrotik/attachments/20130206/6 >> > > f6 >> > > 87358/attachment.html >> > > > >> > > _______________________________________________ >> > > Mikrotik mailing list >> > > [email protected] >> > > http://mail.butchevans.com/mailman/listinfo/mikrotik >> > > >> > > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> > > RouterOS >> > > >> > -------------- next part -------------- An HTML attachment was >> > scrubbed... >> > URL: >> > < >> > http://mail.butchevans.com/pipermail/mikrotik/attachments/20130206/cbd >> > d8bf0 >> > /attachment.html> >> > _______________________________________________ >> > Mikrotik mailing list >> > [email protected] >> > http://mail.butchevans.com/mailman/listinfo/mikrotik >> > >> > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> > RouterOS >> > >> > _______________________________________________ >> > Mikrotik mailing list >> > [email protected] >> > http://mail.butchevans.com/mailman/listinfo/mikrotik >> > >> > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> > RouterOS >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> < >> http://mail.butchevans.com/pipermail/mikrotik/attachments/20130206/e09aafb4 >> /attachment.html> >> _______________________________________________ >> Mikrotik mailing list >> [email protected] >> http://mail.butchevans.com/mailman/listinfo/mikrotik >> >> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> RouterOS >> >> _______________________________________________ >> Mikrotik mailing list >> [email protected] >> http://mail.butchevans.com/mailman/listinfo/mikrotik >> >> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> RouterOS >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.butchevans.com/pipermail/mikrotik/attachments/20130206/4eb157d6/attachment.html> _______________________________________________ Mikrotik mailing list [email protected] http://mail.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
