How do we implement the new default lists in our running versions of DA?
You can add anything manually on the system backup page in the DA admin control panel.
Or you can reinstall sysbk. But if you reinstall sysbk (I haven't looked at the new file so I don't know how to do that) you'll have to go to the DA admin control panel, and make changes anyway, as all your settings will have been replaced by default settings.
Or you can untar, and then find and copy the files that include the directories and files to backup, to your current sysbk installation. You'll still have to check your DA admin control panel, as you might have changed some of the defaults.
Since all settings require you to check the DA control panel, and since I prefer the first method, I'm not covering the other two methods in complete detail. I don't recommend them.
Is there an auto-update that runs or do I need to initiate something on my server?
From Johns email to me it appears he's not updating anything, but only fixing the default on new installs. And I don't blame him. If he attempted to update current installs he'd run into a nightmare, since by now almost all of us have changed those defaults.
It appears you'll need to do a bit of server administration
.
Lem0nHead said:
also, is there some "how to recover server" tutorial?
Specific to DA? I don't think so.
Generic? Probably. Try Googling.
I know it's probably just a bunch of rsync commands (may have many parameters!)... but anyway it would be cool to have a list of them, so we can react fast if something bad happens...
Hopefully not rsync; that's an awful lot of overhead. What's the difference between rsync and ftp for the end result? Nothing.
If I created a list of commands I'm 75% there towards creating an automated system.
I've written this before and I'll repeat it again:
It requires some direct copying and some intelligent merging. It's that intelligent merging that's a pain to script and that can cause problems.
If you search for my past posts on sysbk you'll probalby find the one that explains in fair detail what you have to do (though it probably didn't include all the necessary files/directories as we learn those as we go).
It's also a great question to ask at a local linux users group, where you can ask questions as you attempt it.
I'd try a dry run a few times if I were you. Nothing speeds up a process like experience.
it would also be cool to see something that would allow us to change the sites IP address if it's needed (maybe it would be easier to restore all files and then change the IPs, but it would mean more downtime for all sites... it would be better if the change were done on the fly)
There are multiple places where the IP#s have to be changed.
DA includes a script you can run afterwards that will change one IP# to another. The last time we ran it we had a problem "losing" the main server IP#, but that might have been our own fault.
If/when we create a commercial server/backup solution it will include the ability to change IP#s.
Jeff
