Our Products
 
SureSync
BootBack
Mainframe

BootBack : Frequently Asked Questions

New Features | Features | FAQ | Product Literature | System Requirements

Please click on the question below to see the corresponding answer. If you have a question that is not listed here, please send us an email to info@SoftwarePursuits.com

What happens to all my data files after booting an alternate snapshot?

Traditional snapshot images, such as the recovery CD included with most laptop computers, do not contain the data files and settings that you created on the system. Even in the enterprise environment, workstation images will typically not contain the user's personal settings or any data files that were saved locally to disk. Hence, upon replacing the failed system image with the backup or alternate image, the data files contained in the new snapshot image are typically out of date or non-existent.

To address the issue of old data (current to the last time the image was taken), or losing data because it was not a part of the snapshot image when taken, BootBack utilizes "Data Anchoring" technology, which was specifically designed to address this common problem. Used properly, data anchoring is a very powerful timesaving system rebuild tool.

Top of Page

How much disk space do I need for my snapshots?

Today's disk drives typically have very large storage capacity, which in many cases is not fully utilized. The answer to this question depends upon three considerations:

(1) the number of snapshots you wish to maintain;
(2) the size of your current OS, applications, and data files; and
(3) the amount of data you have anchored.

As an example, let's assume that the current C:\ partition contains 6-Gb of stored information on a 40-Gb disk. During the initial setup of BootBack, you created a copy of this 6-Gb system, so you now have 12-Gb of information stored on the disk. Let's also assume that your 6-Gb system consists of 2-Gb for your OS and applications, and the remaining 4-Gb are your data files. You have subsequently learned about the data-anchoring feature and decide that you wish to use it.

From within BootBack, you set up data anchoring (Tools menu, Data Anchoring - follow the instructions given in the wizard). Do you create a new snapshot to copy this information to, or do you copy to the snapshot that you created during the initial install of BootBack? The answer is to copy the new information (anchored data) to the initial install snapshot. The reason for not copying to a new snapshot is because once you anchor data, it is globally available to all snapshots and you would only be wasting disk space if you created a new snapshot image. Now, with 4-Gb of anchored data, the total used space on your disk is 8-Gb (6-Gb for your pre-install snapshot, and 2-Gb for your anchored data snapshot).

Top of Page

How many snapshots should I maintain on my system?

There are a myriad of possibilities available depending upon disk space, and personal desires. Ideally, three snapshots should be maintained. The first additional snapshot (Snapshot 2) is the copy made during the initial install of BootBack. The second additional snapshot (Snapshot 3) can be a "fresh" install of your operating system and desired applications. This configuration will handle most situations that may arise.

A "fresh install" snapshot is invaluable when you notice that Windows is running slower than normal. Over time, installs, un-installs, temporary files, memory leaks, and the like, cause system performance degradation and possibly corruptions that have not yet surfaced. By booting to the "fresh install" snapshot, the system will once again perform as it did when new. All data files that were anchored in the original system snapshot would of course be available after the re-boot!

To learn how to create a "fresh install" snapshot, see How to create a "fresh install" system image snapshot.

Top of Page

Can I use BootBack to replace my current backup method?

BootBack should be used to complement whatever backup method you currently employ. This utility is designed as a first defense tool, which can significantly save time rebuilding a system following OS or applications software errors. Good backup practices dictate that archived copies of critical data are maintained in a different location.

Learn more about ArchiveSync to maintain archived copies of data, ensuring quick file recovery and improved availability.

Top of Page

Do I need to create a special place on my disk for the installation of BootBack?

No. BootBack installs without the need to create a new partition on your disk. Snapshot copies are stored in hidden files on your system partition (C:\ or any other drive letter where your operating system resides). The importance of "hiding" these critical files is that the operating system or virus attacks cannot write to them, and they are not available to the user (other than from within the program's user interface).

Top of Page

When creating or updating a snapshot, what about files that are open and in use?

BootBack contains a proprietary open file manager to handle any files that are open and in use when making snapshot copies. It functions by "freezing" the system so that a point-in-time snapshot can be taken. With this function, there is no need to create snapshot images outside of the Windows operating environment.

Top of Page

How do I Create a "Fresh Install" System Image Snapshot?

If you have not already done so, please review the section, "How many Snapshots should I maintain on my system," before proceeding to create this "fresh install" snapshot. It is very important to follow the steps outlined below in the order given:

  1. From within the program, set up your data anchoring if you wish to have your current data files available to this new snapshot (recommended).

  2. From the ‘Tools' pull-down menu, select 'Create Empty Snapshot'. Follow the instructions given in the Wizard (name your new snapshot Original XP Load, or OEM Build, etc.).

  3. At the completion of creating your new (blank) snapshot, right-click on the newly created snapshot and select ‘Boot to Snapshot'.

  4. During the re-boot, you will see a message on your screen as follows: "NT Loader Missing." This is normal because there are no operating system files in this newly created snapshot.

  5. Locate your Windows CD and place it in the CD drive. Reboot your system again.

    If you see the message, "NT Loader Missing" again, you will need to enter your BIOS program to set the Boot Sequence to boot from your CD drive first.

  6. Windows will ask you if you want to format the NTFS partition. Answer NO.

    WARNING: DO NOT FORMAT THE NTFS PARTITION. Doing so will erase all data from your disk.

  7. Proceed with the "fresh install" of Windows.

  8. Reinstall BootBack to access the user interface and its functions.

  9. At this point, the system is available to download Windows updates, install user applications, and system preferences.
Although this foregoing process is lengthy, you will find it quite beneficial when you want to refresh Windows to an uncluttered "clean" state. If you have anchored your data in any snapshot, and you boot to this newly created "fresh" install of Windows, all of your anchored data will be available.

You may wish to have a copy of another operating system, such as Windows 2000 if you're running XP, or vise versa. BootBack supports multiple operating systems, from Windows 2000 and up (it does not support Windows 98, Me, or NT).

Top of Page