Here is what you need to do, in a nutshell more details are available below :. It will be safely stored in your Amazon S3 Cloud Storage. This part takes a while, of course. Once the initial backup is complete, it will keep backing up any changes that happen on the server.
So if you change a file, or install a new application, your backup will be updated accordingly. This is all done completely automatically. Of course, the real reason you have a backup is the restore part. How do you restore a single file that got misplaced? And how do you restore everything, including applications, if the server crashes? Read on to find out. Here is what you do:. You will first need to determine where you are restoring that backup to.
The first step you have to do is to install Windows on the target server. With a FullBack Server Pro restore, you can choose to install a completely different Windows version. Even if the original server was, for example, Server R2, you can restore it to a Server deployment. To do that, install Zinstall FullBack on the replacement server. Select your Amazon S3 as backup source, and follow the prompts for complete restore.
While FullBack Server Pro is able to restore applications, settings, profiles, shares and all data, there are some things that it will not be able to recover automatically. Here is what is not restored:. What if you want to restore not to a physical server or local VM, but to a Cloud server instance — can that be done? In terms the restore process itself, it is pretty much identical to restoring to a local server. Install Windows, run through the FullBack Server Pro restore process, get your apps and data back, make the final adjustments you need.
This will be very quick, too, since the restore will happen inside the same Amazon datacenter as long as you choose the same geographical location for your server as your S3 account. You can of course restore to non-Amazon Cloud servers as well. The main caveat compared to local server is going to be connectivity. Change the shell scripts to backup your actual folders. Run the scripts manually first to ensure everything is working properly.
Remember, the upload script will be limited to the upload speed of your ISP, which can be very slow. If you have a typical Cable internet connection upload speed of k it will take approx.
Once you are sure the script is working for your uploads, you can automate the task by creating a cron job to run once a week, day or month. I have it run once a week, because I do nightly backups locally to my Desktop machine using rsync.
Now you can relax, if your laptop battery explodes and burns down your house, you know your data is safe sitting on Amazon's geo-redundant servers right between some bits describing a new book from Oprah and a bad review on latest Ben Affleck movie! Credit Kelvin below.
Also, updated the information about the tools I use. I no longer use cockpit to verify success, but I mostly rely on the s3sync command line tools there were not present at the time I wrote the original article. Without him, this entire process would not be possible, thanks again. How I automated my backups to Amazon S3 using s3sync. STEP 2: Install a management tool update, I no longer use cockpit, now I use the command line tools that come with s3sync that were not available at the time I wrote this original article, see Option 1.
If you use, this option, make sure you have the correct version of ruby installed on your system and you have downloaded the s3sync package See step 3 List all the buckets your account owns: s3cmd. STEP 3: Install s3sync ruby s3sync is an open source ruby script that acts similar to rsync, the linux file sync program.
Lets move on. First, make sure you have ruby 1. Test download. Obviously, monitor to make sure everything is working. Other ways also include setting the starting path for the scheduled task in its properties under the Task Scheduler:. On Server Under the Actions tab, edit the appropriate action and set the "Start in optional :" accordingly.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 9 years, 8 months ago. Active 9 years, 6 months ago. Viewed 2k times. Any help greatly appreciated. Improve this question. PaparazzoKid PaparazzoKid 1 1 gold badge 3 3 silver badges 15 15 bronze badges.
Add a comment. Active Oldest Votes. Other ways also include setting the starting path for the scheduled task in its properties under the Task Scheduler: On Server Under Task tab, edit the "Start in" input box accordingly On Server Under the Actions tab, edit the appropriate action and set the "Start in optional :" accordingly.
Hope it helps!
0コメント