All about backup

How to make a backup in Linux

2012-08-22T16:59:00.000-07:00

Many are wondering about how to keep your system settings, and personal data so that then in case of emergency you can easily restore them. As far as I know, with Windows and Mac OS X this is no problem, as a means for pre-installed copy rezervonogo in both operating systems. None of the Linux distributions I've tested I have not seen default tools coming from the system provides this functionality. To be precise, the money to back up in Linux, by default, but not all newcomers are aware of them, much less know how to use these tools.

There are three ways to back up your data and systems in Linux

Use the archiver to create a compressed copy of
Removing the hard disk image
The use of special, additional utilities
I think the first way is the most versatile and is applicable to almost any situation. The advantages of this method is that the backup archive is not too much space and you can choose what to include in the backup, and what to exclude.
For the first method, we need the target system is installed on a partition / hard disk partitions and USB flash drive / DVD drive from the Live system. Such as Live CD from which you set the system. It is noteworthy that also need a partition on which you want to store the data. It also wanted to mount
So assume that the OS is installed on the first partition of the first hard disk (/ dev/sda1). Boot from the Live CD and install this section say in / mnt

sudo mount / dev/sda1 / mnt
Mount the partition on which you want to place a backup

sudo mkdir / backup
sudo mount / dev/sda3 / backup
The Linux command ls-a / mnt will confirm that we have a partition mounted. If you got an error, run cfdisk and find the partition and then mount it as shown above.
Next, go to the directory partitions are mounted to the system and see what directories it will be the backup.

cd / mnt
ls-a
Seeing the list of directories to include the necessary backup.

sudo su
tar-cvjpf / backup/Backup.tar.bz2 bin boot dev etc home lib lib32 lib64 media mnt opt proc root sbin sys tmp usr var
If you have a slightly different set of directories, such as the directory is missing lib32 and lib64, I advise you to just back up all the directories were not created by you. With directories you created, proceed at your discretion. Some guides recommend to exclude from the backup / proc, / dev, / sys, but I taught own experience I would say that it should not do. Backup should be complete and include all system directories. When you mount a directory with virtual file systems such as / proc and / sys their contents will be empty, but it will save you from making them again and assigning them to the correct permissions (rights). The result of these actions will be the appearance in the destination directory / backup archive contains Backup.tar.bz2 backup system that can always be restored.

Restore backup is not too tricky. For a successful recovery, we need all the same Live CD, myself and a number of backup time. Boot from the Live CD and install sections of the already well-known scheme described above. If you do not carry a backup to another hard disk, the existing system needs to be deleted first.

sudo rm-rf / mnt / *
Copy the archive backup to the target partition

sudo su
cp / backup/Backup.tar.bz2 / mnt /
Become our future system backup and Unpack

cd / mnt
tar-xvjpf Backup.tar.bz2
The key is "v" recommend keeping as you can see the errors and the process unpacking. Everything on this backup restore completed.

Move on to another method which is less convenient because of the possibility of large-sized image and inability to throw out of it obviously unnecessary data. Plus as this method is that the image is created is an exact copy of the existing system of repeating, and file systems and the data contained therein. This method is used to defragment the file systems that do not have their own tools for this.
In this method, you need to boot from the Live CD and mount the partition on which we want to store the image. Mount the partition to which we want zabekapit - mount is not necessary! Please pay attention to this. Create an image using the following command

sudo su
dd if = / dev/sda1 bs = 8M of = / backup / Backup.img
If the volume is large, stocking patient and go have tea / coffee or something stronger while you are creating the image. The main thing is not to drink "something stronger" in large quantities before its restoration.
Recovery even easier: You must boot from the Live CD, mount the partition on which is a backup and restore it to the team (as long as the system is still being restored to / dev/sda1. Errors in the best case in danger of losing Pron collection of carefully selected by you for the past few years spent in stage of puberty, and at worst - broken monitor keyboard when you realize what lost:-D).

dd if = / backup / Backup.img bs = 8M of = / dev/sda1
After completing the task, you get an exact copy of the system that was at the time of the backup.

A third way to create / restore backups, I absolutely did not use as unnecessary. I can only assume that by using this method you will not be able to control the content of such software backup and still pull a variety of relationships necessary for its operation. If all of the above did you find difficult, you can try to find yourself in the Google repository ispolzumomogo or distribution of such software. Vskidku can advise Bacula or Amanda

Installing Windows Server Backup tool in Windows Server 2008

2012-08-20T19:42:00.007-07:00

NTBackup - not the most convenient backup mechanism, but in general it works well, including those based on simple scenarios. In Windows Server 2008 instead of NTBackup utility Windows Server Backup.

Of course, every system administrator has killed at least one scenario NTBackup some part of the server, which can be applied to any version of Windows. Unfortunately, in Windows Server 2008, this scenario does not work, so that the local backup mechanism should be revised to include the server utility Windows Backup.

Many components of Windows Server 2008 is not part of the base installation and added to the system separately as additional elements of functionality. Ris.Utilita adds to the Windows Server Backup Wizard component (Add Features Wizard).

Image A

When you add Windows Server Backup utility sure to add and command line tools - by default, they are not set. In most configurations, reboot after adding components is not required, so after installing the utility, you can immediately start backing up your data.

If, in addition to the utility have been installed and the command line tools to backup data, you can use the wbadmin. Compared with NTBackup this team is more functional and allows for all the backup tasks from the command line. In addition, Windows Server Backup utility supports shell PowerShell, which contributes to greater integration with backup software products such as Exchange or SQL.

And utility Windows Server Backup, and wbadmin command can be used to communicate with remote computers and remote backup systems, which until now has been impossible.

Read more about the new backup can be found in the article TechNet «Step by step guide to using Windows Server Backup Utility for Windows Server 2008» (Windows Server Backup Step-by-Step Guide for Windows Server 2008).
Dedicated Servers!

Why do I need Windows Server Backup?

2012-08-20T19:37:00.003-07:00

Orin Thomas
Microsoft has often reminded consumers that the NTBackup utility in the Windows NT 4.0, Windows 2000 and Windows Server 2003 is not a full-featured backup solution offerings. However, if you need many administrators used it that way. However, they can not use the new built-in tool Windows Server 2008 for large-scale archiving within the company as easy as NTBackup. The reason is a component functionality Windows Server Backup, which replaced the NTBackup utility in the Server 2008. This article discusses several differences between NTBackup and Windows Server Backup, and shows how, in some cases, you can bypass the appropriate limits. In addition, I will explain why it is useful to think about using a full-featured backup solution.

Problem 1
Windows Server Backup is not installed by default
Unlike utility NTBackup, which is installed by default with Windows 2003 and Windows 2000, Windows Server Backup is not installed by default in the operating system Server 2008. To use Windows Server Backup, please refer to the master Add Features, which allows you to install Windows Server Backup, and command-line utility wbadmin. Exe, used to back up your computer in Server Core.
In some cases the lack of built-in backup program delivers significant inconvenience. For example, asked to see the server administrator, whose behavior is questionable, but it appears that he has never been archived and new programs can not be installed on it. Before making any changes, make sure to back up the server, and the absence of the default Backup Server additionally difficult to diagnose. It is known that companies, especially small, often forget to back up until the accident occurred.
The only way to avoid the trap - install Windows Server Backup and wbadmin. Exe during deployment Server 2008. Yet the IT professional may have to examine the servers are never archived, and may not have the tool Windows Server Backup. Unfortunately, Server 2008 does not warn of the need to regularly back up with the same persistence as an automatic update. Thanks for such a warning only the most careless administrators could ignore Backup.

Problem 2
Lack of support for tape drives
One of the most striking features of the Windows Server Backup - lack of support for tape drives. This is not a typo: Windows Server Backup, and a command line utility wbadmin. Exe unsuitable for writing backups to tape. For this, there is at least one good reason: tape drives share the fate of the floppy disk. Modern hard drives not only provide storage for large amounts of data, but also much faster than the magnetic tape during backup and restore. However, most IT organizations have used magnetic tape, and the price is not good streamer low. In the transition to Server 2008, this expensive equipment may be useless.
When replacing a previous version of Windows Server 2008 on the company may refuse to obsolete equipment and variables to buy hard drives or use backup solution from another vendor. Also, you need to prepare a plan for the restoration of data stored on magnetic tape, after the full transition to Server 2008. Windows Server Backup can not import backups produced using NTBackup, and can not be used to recover NTBackup data archived by using Windows Server Backup. But Microsoft released version of NTBackup, intended only for data recovery, at go. Microsoft. Com / fwlink /? LinkId = 82917. With this version of NTBackup can read data from the tape, but did not record them. Consumers can retrieve previously recorded historical data from the tape, only then tape useless. Designed to use only readable version NTBackup tape drive, you need the correct driver for the tape drive Server 2008. Since Windows Server Backup does not work with the tape, some manufacturers have been reluctant to support tape Server 2008.

Problem 3
For routine requires a dedicated backup disk
To store scheduled backups in Windows Server Backup requires a dedicated disk (not just section). When a new disc is recorded the first backup copy, the disk is divided into partitions and formats. Can not be used for any purpose other than archival data, and can not be seen in Windows Explorer Windows. Using Windows Server Backup to write data to the internal hard drive or on a disc that is compatible with USB 2.0 or IEEE 1394. As recommended by Microsoft, the disk capacity should be approximately two and a half times larger than the amount of data a full backup, and the minimum amount of data being backed up is a volume. Windows Server Backup mode by default: full backup and subsequent incremental backup operations. Windows Server Backup automatically deletes the oldest backup, when the disk runs out of space. The purpose of this approach - to appoint a scheduled backup, and then forget about it until then, until it is time to recover.
This method is quite good for a basic backup solution, but would not like managers who are accustomed to the settings of NTBackup. Can be a time to copy to a network drive or an optical drive, but you can not schedule a backup to these devices. Resourceful administrator can prepare a script called targets, which uses a utility wbadmin. Exe to store the backup, but did not get a message about the presence on the target disk has enough space for the successful completion of the backup. Expanding the boundaries of the planned backup is possible, but should not rely on dangerous techniques, as it is noticed administrators.
Because of the need to allocate disk rotation hindered remote backups. Many companies set backups are transported in a safe place each week to recover data if the building burns down, go under the water and will be destroyed meteorite. Principle of Windows Server Backup is based on the assumption that that is tied to the backup server, and is unlikely to be moved to a remote location. If it is important to restore data after a crash, should look for a comprehensive solution.

Problem 4
Tom - the minimum unit of archival
Unlike utility NTBackup, you can use to back up individual files and folders, the minimum unit of backup using Windows Server Backup - a volume. The reason for this limitation, the following: in Windows Server Backup uses full disk image instead of just writing to files and folders, with a contraction in the binary "lump". However, you can restore individual files and folders.
Many administrators are surprised that using Windows Server Backup can back up only the system state. You can back up the system state using the command start systemstatebackup utility wbadmin. Exe, but not all administrators are used to perform a relatively simple task from the command line.
Why utility Windows Server Backup?

For optimal use Windows Server Backup to remember that the utility is not designed to back up at the company level. Many administrators are unhappy with this fact, because that is how they used NTBackup decade. If we consider the Windows Server Backup, according to its true potential - WordPad archiving of programs - it turns out that the utility is consistent with its purpose. If you apply the Windows Server Backup to schedule a regular backup to a removable disk or internal hard drive, it is very easy to completely restore the operating system Windows. Windows Server Backup should not be used to back up Exchange Server or SQL Server, but the NTBackup utility is not designed for this purpose.
Orin Thomas (orin @ windowsitpro. Com) - Editor of Windows IT Pro, certificate holder Windows Security MVP

Backup Basics in Windows Server 2008 R2

2012-08-20T19:35:00.002-07:00

A free tool from Microsoft can make backing up data in Windows Server 2008 R2 efficient and almost hassle-free. Here's how to use it effectively.

By Jeffery Hicks
04/01/2010

Back in the day, Microsoft's free backup tool was the now venerable NTBackup. However, that utility has gone to the great recycle bin in the sky.

Windows Server 2008 offers a new set of backup tools, and I want to show you how easy it is to use them with the new Windows Server 2008 R2. Be aware that the new backup feature can't manage backups created with NTBackup.

Installation
First off, we need to install the backup feature, as it's not installed by default. Use the Add Features wizard in Server Manager and add the Windows Server Backup Features (Figure 1). I'm going to use the command-line tools sub-feature so that I can use Windows PowerShell, which I will explain in more detail later in this article.

You can also use command-line tools, including ServerManagerCMD.exe, to install the feature:

C:\ servermanagercmd -install backup-features

[Click on image for larger view.]

Figure 1. The backup feature is not installed by default, so you must install it using the Add Features Wizard.

The next step is to identify locations for your backups. You can back up files to a network share, a local volume or a dedicated disk. You can't back up data to tape, but given the growth and widespread availability of inexpensive USB-attached storage, this isn't that much of a setback these days.

Creating a Backup Job
Windows Backup is intended to provide a one-stop setup to protect a server. You can enable a scheduled task to back up files and the system state, or to provide for a bare-metal restore. Microsoft assumes you'll have one scheduled task for this purpose. I'm assuming that you're using the Windows Backup feature because of limited budget and are after maximum protection given the utility's constraints.

After you install the Windows Backup feature, expand the Storage node in Server Manager and select Windows Server Backup. In the Actions pane, select "Backup Schedule," which will start the Backup Schedule Wizard. Then, click Next on the Getting Started screen.

During step two, specify what type of backup you want. Try doing a complete server backup. You can also create a custom backup and pick items such as selected files and system state. I'll show you how to do a quick file backup later, but for now I'm assuming you want complete server protection.

In the third step, specify when you want the backup task to run. Most of the time, a single backup should be sufficient, but you can run it more than once a day. If you're backing up critical files, this might be a good choice.

In step four, determine where to store the backup. Microsoft recommends using a dedicated hard disk. Remember, this drive will be reformatted and unavailable for anything else. You can also use a volume or a network share. Pay close attention to the warnings and limitations. You might see a warning reminding you that the disk will be reformatted. If you don't see all the disks, click the Show All Available Disks button to refresh. When you select a new disk, you'll be warned.

Once selected, you'll have a chance to confirm your backup settings. If anything is incorrect, use the Previous button to go back and correct the error. If all goes well, you should get a summary screen. The next day, you can check the Windows Server Backup node for results or errors.

You can also use Windows Backup to run a one-time backup. Select the Backup Once option in the Actions pane. You can use the same settings as your scheduled job or pick something completely different. If you select the latter, the wizard runs again and you can enter new parameters. For example, you might want to copy files to a network share. Remember, any existing backups to the same folder will be overwritten. The backup will execute immediately. If this is a separate backup task you'd like to do often, then you'll want to take advantage of a scripted solution from the command line or Windows PowerShell. I'll cover that procedure later.

Restoring Data
Windows Backup uses a time stamp as version information. Using the Recover task launches a wizard that's easy to follow. Select the appropriate backup source. The Recovery Wizard will display a datetime control of all available backups (see Figure 2). Select the appropriate one. Depending on the type of backup, you may only have once choice.

[Click on image for larger view.]

Figure 2. Data recovery is easy with the Recovery Wizard.

Moving on, select what type of data you want to recover. If you select Files and Folders, you'll be able to highlight the files you want to recover. Unfortunately, selecting files from multiple directories is next to impossible. You can easily recover everything or recover selected files from one directory. Keep that in mind when you set up the backup job.

When you recover files, you'll need to specify the target folder, which can be the original folder or an alternate location. You can also control what happens when you restore a current file if a current version exists. You can create a copy so that you have both versions; you can overwrite the existing version; or you can skip restoring if an existing version is detected. The recovery process happens immediately.

Windows server Backup

2012-08-20T19:34:00.000-07:00

Windows Server Backup Step-by-Step Guide for Windows Server 2008

120 out of 218 rated this helpful - Rate this topic

Updated: May 11, 2007

Applies To: Windows Server 2008

The Windows Server Backup feature provides a basic backup and recovery solution for computers running the Windows Server® 2008 operating system. Windows Server Backup introduces new backup and recovery technology and replaces the previous Windows Backup (Ntbackup.exe) feature that was available with earlier versions of the Windows operating system.

What is Windows Server Backup?

The Windows Server Backup feature in Windows Server 2008 consists of a Microsoft Management Console (MMC) snap-in and command-line tools that provide a complete solution for your day-to-day backup and recovery needs. You can use four wizards to guide you through running backups and recoveries. You can use Windows Server Backup to back up a full server (all volumes), selected volumes, or the system state. You can recover volumes, folders, files, certain applications, and the system state. And, in case of disasters like hard disk failures, you can perform a system recovery, which will restore your complete system onto the new hard disk, by using a full server backup and the Windows Recovery Environment.

You can use Windows Server Backup to create and manage backups for the local computer or a remote computer. You can also schedule backups to run automatically and you can perform one-time backups to augment the scheduled backups.

Important
Windows Server Backup is available in all editions of Windows Server 2008 (both 32-bit and 64-bit versions). However, the Windows Server Backup snap-in is not available for the Server Core installation option of Windows Server 2008. To run backups for computers with a Server Core installation, you need to either use the command line or manage backups remotely from another computer. In addition, Windows PowerShell is not available for the Server Core installation option, so the cmdlets for Windows Server Backup are also not available on this type of installation.

Important

Windows Server Backup is available in all editions of Windows Server 2008 (both 32-bit and 64-bit versions). However, the Windows Server Backup snap-in is not available for the Server Core installation option of Windows Server 2008. To run backups for computers with a Server Core installation, you need to either use the command line or manage backups remotely from another computer. In addition, Windows PowerShell is not available for the Server Core installation option, so the cmdlets for Windows Server Backup are also not available on this type of installation.

What’s new in Windows Server Backup?

Windows Server Backup includes the following improvements:

Faster backup technology. Windows Server Backup uses Volume Shadow Copy Service (VSS) and block-level backup technology to back up and recover your operating system, files and folders, and volumes. After the first full backup is created, you can configure Windows Server Backup to automatically run incremental backups by saving only the data that has changed since the last backup. Even if you choose to always perform full backups, your backup will take less time than it did in earlier versions of Windows.
Simplified restoration. You can restore items by choosing a backup and then selecting specific items from that backup to restore. You can recover specific files from a folder or all the contents of a folder. In addition, previously, you needed to manually restore from multiple backups if the item was stored on an incremental backup. But this is no longer true—you can now choose the date of the backup version for the item you want to restore.
Simplified recovery of your operating system. Windows Server Backup works with new Windows recovery tools to make it easier for you to recover your operating system. You can recover to the same server—or if the hardware fails, you can recover to a separate server that has similar hardware and no operating system.
Ability to recover applications. Windows Server Backup uses VSS functionality that is built into applications like Microsoft® SQL Server® to protect application data.
Improved scheduling. Windows Server Backup includes a wizard that guides you through the process of creating daily backups. System volumes are automatically included in all scheduled backups so that you are protected against disasters.
Offsite removal of backups for disaster protection. You can save backups to multiple disks in a rotation, which enables you to move disks from an offsite location. You can add each disk as a scheduled backup location and, if the first disk is moved offsite, Windows Server Backup will automatically save backups to the next disk in the rotation.
Remote administration. Windows Server Backup uses an MMC snap-in to give you a familiar and consistent experience for managing your backups. After you install the snap-in, you can access this tool through Server Manager or by adding the snap-in to a new or existing MMC console. Then, you can manage backups on other servers by clicking the Action menu in the snap-in, and then clicking Connect to Another Computer.
Automatic disk usage management. After you configure a disk for a scheduled backup, Windows Server Backup automatically manages the disk usage—you do not need to be concerned about running out of disk space after repeated backups. Windows Server Backup will automatically reuse the space of older backups when creating new backups. The management tool displays the backups that are available and the disk usage information. This can help you plan for provisioning additional storage to meet your recovery objectives.
Extensive command-line support. Windows Server Backup includes the wbadmin command and documentation, which enable you to perform all of the same tasks at the command line that you can perform by using the snap-in. For more information, see the Command Reference (http://go.microsoft.com/fwlink/?LinkId=93131). You can also automate backup activities through scripting.

In addition, Windows Server 2008 contains a collection of Windows PowerShell™ commands (cmdlets) for Windows Server Backup that you can use to write scripts to perform backups. For more information, see http://go.microsoft.com/fwlink/?LinkId=93317.
Support for optical media drives and removable media. You can manually back up volumes directly to optical media drives, such as DVD drives, and also to removable media. This offers a solution if you want to create backups that can easily be moved offsite on a one-time basis. This version of Windows Server Backup retains support for manual backups to shared folders and hard disks.

Who should use Windows Server Backup?

Windows Server Backup is intended for use by everyone who needs a basic backup solution—from small business owners to IT professionals in large enterprises. However, the design makes it especially well-suited for smaller organizations or individuals who are not IT professionals.

Special considerations

You must be a member of the Administrators group or Backup Operators group to use Windows Server Backup.

In Windows Server 2008, the firewall has been enabled by default. If you are managing the backups of another computer using the Windows Server Backup snap-in, your connectivity to the remote computer may be affected and can be resolved by changes in the firewall rules. While working on the local computer, you are not affected.

Also, if you are a current user of the previous backup feature (Ntbackup.exe) that shipped in earlier versions of Windows, and plan to switch to the new Windows Server Backup, you might be affected by the following issues and changes:

Settings for creating backups will not be upgraded when you upgrade to Windows Server 2008. You will need to reconfigure settings.
You will need a separate, dedicated disk for running scheduled backups.
Only NTFS-formatted volumes on a locally attached disk can be backed up.
You can no longer back up to tape. (However, support of tape storage drivers is still included in Windows Server 2008.) Windows Server Backup supports backing up to external and internal disks, DVDs, and shared folders.

You cannot recover backups that you created with Ntbackup.exe by using Windows Server Backup. However, a version of Ntbackup.exe is available as a download to Windows Server 2008 for users who want to recover data from backups created using Ntbackup.exe. The downloadable version of Ntbackup.exe is only for recovering backups for older versions of Windows and cannot be used to create new backups in Windows Server 2008. To download Ntbackup.exe, seehttp://go.microsoft.com/fwlink/?LinkId=82917.

How to install Windows Server Backup

To access backup and recovery tools for Windows Server 2008, you must install the Windows Server Backup, Command-line Tools, and Windows PowerShell items that are available in the Add Features Wizard in Server Manager. This installs the following tools:

Windows Server Backup Microsoft Management Console (MMC) snap-in
Wbadmin command-line tool
Windows Server Backup cmdlets (Windows PowerShell commands)

Note
To install Windows Server Backup features in Server Manager, you must be a member of the Backup Operators or Administrators group. You can also access Windows Server Backup from Server Manager, under the Storage node.

To install backup and recovery tools

Click Start, click Server Manager, in the left pane click Features, and then in the right pane click Add Features. This opens the Add Features Wizard.

In the Add Features Wizard, on the Select Features page, expand Windows Server Backup Features, and then select the check boxes for Windows Server Backupand Command-line Tools.

You will receive a message that Windows PowerShell is also required to be installed with these features.

Note
If you just want to install the snap-in and the Wbadmin command-line tool, expand Windows Server Backup Features, and then select the Windows Server Backup check box. In this case, Windows PowerShell is not required.

Click Add Required Features, and then click Next.
On the Confirm Installation Selections page, review the choices that you made, and then click Install. If there is an error during the installation, it will be noted on the Installation Results page.
Then, to access these backup and recovery tools, do the following:
- To access the Windows Server Backup snap-in, click Start, click Administrative Tools, and then click Windows Server Backup.
- To access and view the syntax for Wbadmin, click Start, right-click Command Prompt, and then click Run as administrator. At the prompt, type: wbadmin /?
- For instructions to access and view the Help for the Windows Server Backup cmdlets, see GettingStarted.rtf at: <systemdrive>:\Windows\System32\WindowsPowerShell\v1.0\Documents\<language>.