Just wondering do I need to shut down mis to do a backup or can I just
do a gzip of the whole directory while mystic is running?
Thanks!
Just wondering do I need to shut down mis to do a backup or can I just
do a gzip of the whole directory while mystic is running?
Just wondering do I need to shut down mis to do a backup or can I just
do a gzip of the whole directory while mystic is running?
I do backups with mis running. I accept that it's not the safest method, however what I do to mitigate this risk is to take multiple backups. I
maybe if I ever get a good number of callers I'll have to consider something other than shutting down, I was looking at rsnapshot but I've got to do more reading.
Keep in mind that making a copy of a running process shouldn't do
anything which would cause problems with the running BBS, it just might
Hi all,This is how I complete a backup.
Just wondering do I need to shut down mis to do a backup or can I just
do a gzip of the whole directory while mystic is running?
Thanks!
Hi all,
Just wondering do I need to shut down mis to do a backup or can I just do a gzip of the whole directory while mystic is running?
Thanks!
esc wrote to toofargone <=-
Keep in mind that making a copy of a running process shouldn't do
anything which would cause problems with the running BBS, it just
might result in a wonky backup. So unless someone knows something
which conflicts with my understanding of how file copying works,
I suspect it's probably mostly fine :)
maybe if I ever get a good number of callers I'll have to consider something other than shutting down, I was looking at rsnapshot but I've got to do more reading.
This is how I complete a backup.
bring down the BBS.
with a usb storage stick, backup the entire mystic directory with the
use of windows file explorer.
After the backup is complete, I delete all of the log files from the bbs that is existing on the hard drive (within mystic- they can grow to be quite large) then I complete the process with maintenance mutil maint
from the c:\mystic directory Then restart the BBS
* This is is the same practice (backing it up) that I use before any I make any changes.
Hope this helps.
Agreed on your first sentence... but doesn't having a "wonky" backup
kind of defeat the purpose of making/having a backup in the first place?
go figure) I use VEEAM free agent that works fine, it does[...]
incrementals every night, and a full backup once a week. If I do need
minimal downtime or loss.. You can run VEEAM Free Agent in Windows
also if that is what you are using...
esc wrote to Gamgee <=-
Agreed on your first sentence... but doesn't having a "wonky" backup
kind of defeat the purpose of making/having a backup in the first place?
Yep, 100%. I take multiple backups for redundancy though and
that's how I accept the risk.
Just wondering do I need to shut down mis to do a backup or can I just
do a gzip of the whole directory while mystic is running?
Understood, with the caveat of there's some (preventable) risk
introduced which could be avoided. Also, everyone's threshold of acceptable risk is likely different. It's *possible* that ALL of those redundant backups could be bad.
In the context of the original-ish post of this thread, I can find no valid/acceptable reason to *NOT* stop the BBS/server before doing a backup. Especially an incremental (e.g. 'rysnc' type thing) backup, as the whole process of shutdown/backup/startup likely takes about a single minute. Even a complete backup might take 5 minutes.
esc wrote to Gamgee <=-
In the context of the original-ish post of this thread, I can find no valid/acceptable reason to *NOT* stop the BBS/server before doing a backup. Especially an incremental (e.g. 'rysnc' type thing) backup, as the whole process of shutdown/backup/startup likely takes about a single minute. Even a complete backup might take 5 minutes.
My only concern would be that I don't think Mystic gives any sort
of "we're going to have an outage in 30 minutes" thing, but it's
not like users would really care. *shrug*
My only concern would be that I don't think Mystic gives any sort of "we're going to have an outage in 30 minutes" thing, but it's not like users would really care. *shrug*
paulie420 wrote to esc <=-
I remember back in the day I had some really small software that would simply display a .txt to a user who called, and hang up after 30
seconds. The .txt would be something like;
2o fOr beeRS is currently down for maintenance.
**** you, call back later loser!
I remember back in the day I had some really small software that would simply display a .txt to a user who called, and hang up after 30
seconds. The .txt would be something like;
If running in Windows, you can use a program called BBS Server which is sort of a TCPSER type of program mainly used to answer telnet calls and transfer them via a serial port to another serial port. It is used in
the Commodore world to have a real Commodore computer answer Telnet then transfer to a Swiftlink or serial card via a RS232 cable. It has a
option to answer and send a message, I was using it for just this reason
a while back, I would set it up to answer and send the message "The BBS
is currently down for Maintenance try back in an hour or so. (My Lt
Kernal would take on average 30-40 minutes to back up each partition to Zip Drive.. It's a way...
I love all the work the Commodore [Amiga] scene has put in to making
older OSes run bbSes seamlessly - its actually pretty amazing. I know
you mentioned Windows, but... some of the trickery that ya'll come up
with is amazing.
.≈______ ┌────┐ ┌───┐ ┌─────────┐ ┌────────┐ ╔═════════╗ ┌───────────────┐ _[]_││──││ │TROY│ │HUB│ │ Fidonet │ │FSX Net│ ║S I
N C E║ │Another Message│ { NET 267 │ │ NY │ │800│ │1:267/150│
│21:1/127│ ║ 1 9 9 5 ║ │ by Gregory │ / 00────00'┘¿└0──0┘¿└0─0┘¿└─00───00─┘¿└─00──00─┘¿╚═00═══00═╝¿└───00──────00─
:::::: My Back up Batch :::::::
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,052 |
Nodes: | 17 (0 / 17) |
Uptime: | 08:13:43 |
Calls: | 501,013 |
Files: | 109,383 |
D/L today: |
191 files (12,022K bytes) |
Messages: | 304,715 |