Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Alternative Backup Solution... Any Suggestions???

Options
  • 27-03-2003 11:36am
    #1
    Moderators, Business & Finance Moderators, Society & Culture Moderators Posts: 9,763 Mod ✭✭✭✭


    Guys,

    Im working for a small company and we are always looking for
    ways to curb spending in some areas so that we can save the money for other more needy areas, yet while trying to maintain a fairly decent network and keep things up and running as much as possible.

    At the moment we are reviewing out backup solutions.

    We currently use backup exec as it was in place from a previous
    IT manager and to be honest its starting to get a bit outdated
    The network has grown as has the number of systems that
    need to be backed up.

    We were gonna upgrade to the latest version of Backup exec and were also looking at ArcServe, but both need agents for every system that you are backing up, and when you add the number of systems that are being backed up, then comes to a fairly substancial amount.

    So Im looking around to see if there is some sort of open source software available that allows systems to be backed up over the
    network and is reliable.. something that can do the job and isnt gonna rip us off..

    It must be capable of backing up Windows NT and 2000 Servers as well as a few Linux servers btw.

    Any ideas?

    Thanks

    Tox


Comments

  • Closed Accounts Posts: 495 ✭✭Beëlzebooze


    I assume that you are backing up "active" resources like databases.

    one way of getting round the agent issue is if you stop the service/daemon before backing up the data. For example if you wanted to backup a database on different machine than your backup solution is running on, what I would have done in the past is to have a scheduled task to stop the database server at say midnight, and restart it at 6 in the morning, that give you ample time to backup the database files using conventional means.


  • Closed Accounts Posts: 88 ✭✭BogoBot


    Amanda is an excellent opensource backup package.

    In the past I've used the native backup app provided by Win2k to dump to a file on a scheduled basis and then backed up the flat file to tape with either amanda, BackupExec or ArcServe.

    SO more info on your environment might be useful. Exchange? SQL? Oracle?

    Bogobot.


  • Registered Users Posts: 651 ✭✭✭sirlinux


    Any decent SQL server will do a dump while still live for backup purposes, only side effetc being the high load, there shouldnt be any need to stop it to back it up, the biggest problem with back up is getting locked/open files, and it's usually the most important files that seem to spend most of their time open. The open files issue is where arcserve goes some way to justifying it's cost, but it's still leaves you scratchin your head sometimes when it decides im not backing up today. If open files arent an issue, nt backup is good enough on both 2k and nt4, and for linux and unix the list is endless right down to good old tar. Personally i drop all the backups to a central machine from there onto DAT.


Advertisement