I have just joined a company with Server 2003 Small Business Server. The company contains only an handful of staff and needs a backup system.
I would like to restore a tape backup (including system state, Exchange server, etc) to a second server. The aim is to have a verified set of backups and be able to swap the servers if necessary.
Am I right in thinking that the second server could not be on the SBS network?
Whatever method you choose, be sure to TEST the restore process using the actual backup media you keep on site.
you have a couple of options with SBS, you can have additional servers in the SBS domain such as win2003 servers. You can only have a additional SBS server on the same domain for a limit of seven days, this is for migration situations.
In you situation I would have a additional win2003 server connected to the domain to act as a backup domain controller, then if your SBS systems goes down you can still do Active directory auth. and access any resources still on your network.
We create a base acronis image of the SBS server, then if anything goes wrong you restore the acronis image and then apply the backup file (We use NTBackup provided in SBS) to bring you up to date. using the combination of acronis and backups cuts down the time to recover significantly.
Hope this helps.
Related
does anybody know a way to perform a periodic remote backup of the full environment (so comprehensive of the application servers and SQL databases) in Jelastic?
I wanted to use Google Drive to store the backups as I was already using it with Plesk.
Thanks.
List of unidentified sql jobs
Our SQL Server 2008 R2 has lots of auto generated jobs from nowhere as can be seen from image above. I strongly suspect this causes our server password keeps reset daily for no reasons (I had untick those 'Enforce password policy' checkboxes). For now I had delete the jobs but I am not sure can this really solve the root of the problems. Any idea on this? Thanks guys...
Your server has most likely been compromised. The most appropriate thing to do in this situation is to either reinstall everything from scratch and restore your last known good data backup (prior to getting compromised), or perform a bare metal restore of the server from the last known good (uncompromised) backup. At this point you don't know what malicious software is still on that server, so you have to assume that it's riddled with it.
Do this after you've ensured that the server will be secured from network attacks and don't leave it exposed to the public internet. If it wasn't previously exposed, you may have malicious software on your company network.
I'm sure there's a good amount of developers here that use DirectAdmin and I had a quick question.
I've always used cPanel and I'm not on a server that is using DirectAdmin instead. Where in DirectAdmin can you generate a full backup of the account at the user level?
Also, do DirectAdmin backups include everything related to the account like cPanel backups do? For example, not only the files and databases but also the cron jobs, DNS zones, email accounts, etc.?
And where are the backups stored by default? Is there an option to send the backups to a remote server via FTP like you can with cPanel?
There are two different backup systems built into DA:
Admin Tools | System Backup. This tool lets you backup configuration data and arbitrary directories, locally or using FTP or SCP.
Admin Tools | Admin Backup/Transfer. This tool is oriented toward backing up data account by account, in one archive per account, in a format that you can use to restore from (in the same tool) on the original or another DA server (i.e. if you want to transfer to a new server). You can back up locally and/or via FTP.
Both options can also be scheduled via cron.
Depending on your level of access, only one of these might be available to you. This page has further info for non-administrators: http://www.site-helper.com/backup.html.
You can improve your DirectAdmin backup with an incremental backup plugin that includes local and remote backup location, please check the setup guide here
I finally decided to make a proper backup setup for my home computers.
I have 2 laptops, mine and my wife's, both PC and two desktops one (PC) for multimedia purposes and one (Ubuntu Linux) for local backup.
So currently i am using Crashplan to backup everything to the Linux server and all looks fine and dandy but i decided to back up my server to the web with CrashPlan Central. I have no problems with backing up random stuff on server, but when i want to backup those encrypted files that are the backups from other comuters made by Crashplan i get a probelm.
I installed Crashplan with default locations and my backups are stored in /usr/local/crashplan/backupArchives folder. When i check it for online backup it doesn't backup anything.
Am i doing something wrong or it is not possible to upload the files created by other Crashplan clients?
As far as I know, you can not backup CrashPlan Backup Archives at CrashPlan Central.
I think they do this to prevent customers to buy a licence for one machine to backup multiple computers.
There are hard coded exclusions in CrashPlan preventing it from backing up CrashPlan files:
http://support.crashplan.com/doku.php/articles/admin_excludes
You cannot change that excludes, but I suggest a look at this
hard coded exclusions to avoid surprises.
We have a DB server with a couple web app db's on there (don't get a ton of traffic). We'd like to make use of the server and allow it to be the DB server for sharepoint. I'm assuming it's not good practice and that sharepoint should have it's own exclusive db server. Am I right in that conclusion, or is it alright if we put the database on a server that already hosts other databases.
You can install SharePoint on an existing DB server, sure. Unless your environment is going to be huge, I don't see why you would give it its own DB server. It will use an embedded SQL Server instance if you want, but you'll get better performance if you have the full-blown version. We're running a few SharePoint apps on our DB server with a number of other applications.
The way in which I solve this is to install a second SQL Server instance dedicated to SharePoint, as SharePoint likes to have a lot of control over the database and spews all sorts of stuff such as logins, etc. across the instance, which you really want to separate from your standard line of business instance.
The added bonus is multiple SQL Server instances on the same physical machine are included in your licence.
Be careful with the SQL Server collation. I think SharePoint requires a particular setting for this. See http://www.moss2007.be/blogs/vandest/archive/2007/07/24/sharepoint-2007-and-sql-server-collation-latin1_general_ci_as_ks_ws.aspx for one reference.
Prior to centralizing our environment we had many Sharepoint sites located on servers with existing applications. I'm not a fan of adding an additional named instance as this increases the administrative overhead for the DBA. You have to know how much use you expect of your Sharepoint instance then measure the resource utilization of your existing applications balance it from there.