Video Screencast Help
Backup and Recovery Community Blog
Showing posts tagged with Best Practice
Showing posts in English
GFK | 09 Apr 2009 | 0 comments

Keep your business up and running - by discovering backup and storage management inefficiencies you can cut costs, while making sure that your data is fully protected. Highly beneficial at a time when budgets are under strain.

It is really useful to go through the process of trying to find out:

  • How well your data is protected

  • If you are missing backing up critical data
  • How prepared you are for increasing data volumes
  • Whether your strategy supports business growth or lowers performance
  • If you are taking advantage of the most cost-effective solutions available

It never ceases to amaze me how well we don’t know ourselves. To quote Polonius, “unto thine own self be true”; the more honest you are with yourself the more accurate and the more useful the results will be. We know our business, don’t we? We know that we are doing the best we can, aren’t we? It’s not...

GFK | 03 Apr 2009 | 4 comments

One of the really cool functions of BE is the Granular Recovery Technology (GRT). By the way, anytime you need more information on any aspect of BE please see the Backup Exec for Windows Servers Administrator’s Guide. In fact, don’t take my word for it, download from here: a few tips to help you get the best out of BE’s GRT:

  1. Review the requirements for staging locations in the Administrator’s Guide.
  2. You must use a staging location for GRT-enabled jobs in the following scenarios:
    • You back up to or restore from a volume with file size limitations.
    • You restore granular items from tape.
    • You run an off-host backup job.
  3. You are better off creating a separate backup-to-disk folder specifically for all GRT enabled backup jobs - this really simplifies media management....
TrevorD | 27 Mar 2009 | 3 comments
  1. Align business and IT requirements
  2. Prioritize requirements
  3. Determine true costs for delivery options
  4. Predict the impact of data loss
  5. Establish service levels
  6. Modify infrastructure to meet agreed service levels
  7. Test the recovery process regularly
  8. Analyze logs
  9. Perform incident management
  10. Perform root cause analysis