 |
| Help | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1 Overview.1.1 Benefits
1.2 Features
1.3 Security
1.4 System RequirementsServer Software (OBS)
Client Software (OBM)
2 OBM ConfigurationBefore you can start backing up data to Offsite Backup Server, you need to install OBM (OBM) onto your computer. 2.1 InstallationPlease follow the instructions below to install OBM onto your computer.
i.
Select the operating system to which you want to
install OBM ii. Follow the instructions on the installation guide to complete OBM installation Notes on Windows InstallationA quick launcher is now installed in the system tray
(next to your system clock). To open OBM, just right click the quick launcher icon 2.2 UpgradeThis section describes the software upgrade instructions required to upgrade OBM to the latest release. Upgrade instructions of OBM on WindowsDownload the latest installer (obm-win.exe) from the web installation guide and install it over existing installation of OBM. It will upgrade the OBM to the latest version. Notes: You will only be
prompted to reboot your computer if some files are locked and cannot be
overwritten during upgrade. Upgrade instructions of OBM on Netwarea.
Download the latest release bundle
(obm-netware.zip) from the web installation guide. b. Backup existing installation by renaming SYS:\OBM to SYS:\OBM.bak c. Restarting backup scheduler by running SYS:\OBM\bin\Scheduler.ncf d. You can then open OBM by running SYS:\OBM\bin\BackupManager.ncf Upgrade instructions of OBM on Mac OS Xa.
Download the latest release bundle (obm-mac.zip)
from the web installation guide. b. Expand the zip archive and run the OBM installer inside the archive Upgrade instructions of OBM on Linuxa.
Download the latest release bundle
(obm-linux.tar.gz) from the web installation guide b.
Stop running backup scheduler by running c.
Backup existing installation by renaming
$OBM_HOME (default directory is /usr/local/obm) to $OBM_HOME.bak d.
Expand the new client software to $OBM_HOME e. Start backup scheduler by running $OBM_HOME\bin\Scheduler.sh f. You can then open OBM by running $OBM_HOME\bin\BackupManager.sh Upgrade instructions of OBM on Sun Solarisa.
Download the latest release bundle
(obm-solaris.tar.gz) from the web installation guide b.
Stop running backup scheduler by running c.
Backup existing installation by renaming
$OBM_HOME (default directory is /usr/local/obm) to $OBM_HOME.bak d.
Expand the new client software to $OBM_HOME e. Start backup scheduler by running $OBM_HOME\bin\Scheduler.sh f. You can then open OBM by running $OBM_HOME\bin\BackupManager.sh 2.3 Un-installationThis section describes the steps required to uninstall OBM from your computer. Uninstallation instructions of OBM on Windowsa. Open [Start] -> [Control Panel] -> [Add/Remove Programs] b. Select [OBM] from the list and press the [Remove] button Uninstallation instructions of OBM on Netwarea.
Stop running backup scheduler by running b. Remove all program files by removing the directory SYS:\OBM c. Remove all backup settings by removing the directory SYS:\.OBM Uninstallation instructions of OBM on Mac OS Xa.
Stop running backup scheduler by running b.
Remove all program files by removing
/Applications/OBM c.
Remove all backup setting by removing ~/.obm d.
Remove backup scheduler service from system
startup by /System/Library/StartupItems/OBM Uninstallation instructions of OBM on Linuxa.
Stop running backup scheduler by running b.
Remove all program files by removing $OBM_HOME c.
Remove all backup setting by removing ~/.obm Uninstallation instructions of OBM on Sun Solarisa.
Stop running backup scheduler by running b.
Remove all program files by removing $OBM_HOME c.
Remove all backup setting by removing ~/.obm 2.4 AutoStartup on LinuxPlease follow the instructions below to make OBM scheduler auto startup upon computer restart. i.
Copy the startup script of OBM scheduler
(obm-scheduler) to Linux startup script directory (/etc/rc.d/init.d) ii. Open /etc/rc.d/init.d/obm-scheduler with VI editor and make changes to the OBM_HOME environment variable export statement (i.e. export OBM_HOME=/usr/local/obm) if OBM_HOME is not /usr/local/obm iii.
Register the obm-scheduler startup script as
system service by iv. To
startup OBM scheduler, please run v.
(optional) To shutdown OBM scheduler, please run vi. Setup
completed 3 Using OBMThis chapter will describe all features available in OBM and outline how you can use the features of OBM to meet various backup needs. 3.1 System Tray LauncherAfter you have successfully installed OBM to your computer, an OBM icon will be added to the system tray area (next to your system clock) automatically.
This icon is the entry point to OBM. Right clicking the icon will show a menu that provides the following functions:
3.2 Logon DialogBefore you can use OBM, you have to be authenticated by the Offsite Backup Server first. The logon dialog shown below will check if you have the right to access OBM by submitting the username and password you provided to the backup server. For secure communication, you can choose to communicate with Offsite Backup Server in SSL (Secure Socket Layer) by selecting the [https] option. The [Address] field shows the Offsite Backup Server to
which OBM will connect to authenticate your username and password. You can use
either a resolvable host name (e.g. backup.your-domain.com) or an IP address
(e.g. 192.168.1.1). If you need to connect to the server through proxy, just enter your proxy setting in the [Proxy Setting] section. For [SOCKS] proxy, both v4 and v5 without user authentication are supported. 3.3 Language SelectionYou can switch the language of the OBM user interface by choosing the desired language available from the [Language] drop down list. The languages available include English, Czech, Danish, German, Spanish, Icelandic, Dutch, Swedish, Traditional Chinese and Simplified Chinese. 3.4 User ProfileAfter the backup server authenticates you successfully, OBM main window appears. You can then use OBM to update your user profile. You can perform the following update to your user profile. To change your [Password], press the [Change] button next
to the password field. A Change Password dialog will appear. Enter your
original password and new password into the text field of this dialog and press
[OK]. To change your [Display Name], press the [Change] button
next to the display name field. A Change Display Name dialog will appear. Enter
the new display name and press [OK]. To change your [Time Zone], just select your time zone from the drop down list next to the time zone entry. To add a new contact email to this account, press the
[Add] button in the [Contact] section. A [Add New Contact] dialog will appear.
Enter a name and an email address in the text field provided and then press the
[OK] button. To remove a contact email, select the email that is to be removed from the email list and press the [Remove] button. Press [OK] to confirm the removal. To update a contact email, select the email that is to be
updated from the email list and press the [Properties] button. A [Update
Contact Property] dialog will appear. After you have made the changes that you
want, press the [OK] button. 3.5 Backup LogsAll backup activities are logged to backup activity log files. They are available for reviewing from OBM. How to review backup activities?You can review all your backup Jobs by i. Select the [Log] tab available at the bottom of OBM ii.
Select the Backup Job you want to review on the
[Log Controller] panel 4 Setting up backup setA backup set contains all backup settings of a backup operation. This section will describe all features available within a backup set and explain how you can use each of them to achieve various tasks. Each backup account can have multiple backup sets. Each backup set is an individual and independent entity. For example, if you want one directory to be backed up during the day and another directory to be backed up during the night, you can create two backup sets, each with a different backup schedule and backup source, to serve this need. 4.1 Backup Set TypeA backup set can be of one of the following types:
Backup set type is defined at backup set creation and cannot be modified. If you want to change the backup set type, you have to create another backup set. 4.2 Backup SourceA backup source defines the files/directories that are to be included in a backup set. There are two types of backup source: Selected and Deselected. Selected backup source defines files/directories that are to be included in a backup set while deselected backup source defines files/directories that are to be excluded from a backup set. Online Backup Manager will generate appropriate backup source setting for you automatically when you make your backup source selection on OBM. From the [Standard] node available at the top of the [Backup Source] tree, you can easily select the following common folders to be backed up: 1. “My Documents” folder 2. “Outlook” and “Outlook Express” mail store folder 3. “Favorites” folder 4. “Desktop” folder From the [Options] node available below the [Standard] node, you can easily select other common folders to be backed up as well. They include the “Application Data” folder, the “Start Menu” folder, the “Templates” folder, the “All Users’ Documents” folder, the “Temporary Internet Files” folder, the “Cookies” folder, the “Font” folder, the “History” folder, the “Applications Data” folder, the “Nethood” folder, the “Printhood” folder, the “Recent” folder and the “Send to” folder. The checkbox next to the files/directories shown above can be in one of the following mode:
4.3 Backup ScheduleA backup schedule defines the frequency and the time backup will run automatically. Backup schedule can be in one of the following types:
Please note that you can have more than one schedule within a backup set. For example, you can have a daily backup schedule that runs at 13:00 at noon and another daily backup schedule that runs at 00:00 at midnight. The combination of both of these schedules effectively creates a backup schedule that runs daily at 00:00 and 13:00 everyday. 4.4 In-File DeltaPlease refer to the in-file delta section for more information on this topic. 4.5 Backup FilterA backup filter defines the file selection rules that allow user to easily include/exclude files into/from the backup set by applying user defined criteria(s) to the file names or directory names. There are some basic rule regarding backup filters: i. Filters are checked in creation order. Once inclusion/exclusion has been identified, the remaining filters won't be checked. ii. Inclusion/Exclusion made by filter always takes precedence over backup source selections iii. If all filters do not apply to a particular file, this file is then checked for inclusion/exclusion backup source selections
Top Directory =
C:\My Documents Example 2: Top Directory =
C:\Applications Example 3: Top Directory =
C:\ Please note that the [Include all others] setting is not enabled because you don’t want to include all other files (NOT *.jpg, *.gif) under C:\ into the backup set. Example 4: (advanced) If you want to include everything, except the “log” directory, under C:\Applications into a backup set, you should setup your backup filter as follows. Top Directory =
C:\Applications Example 5: (advanced) If you want to include all directories named “log” from the backup set files with file name starting with “B” and ending with “*.doc” under C:\My Documents into the backup set, you can use a regular expression of “^B.*\.doc$” to do your selection. The filter backup can then be setup as follows. Top Directory =
C:\My Documents 4.6 Pre/Post-Backup CommandThe command line tool feature has two major components, the [Pre-Backup] command and the [Post-Backup] command. You can use the [Pre-Backup] or [Post-Backup] commands to run any native OS (operating system) commands before or after running a backup job. Both [Pre-Backup] and [Post-Backup] commands comprise of the following parameters:
4.7 EncryptionBefore your files are sent to Offsite Backup Server, all your files are to be compressed and encrypted by your choice of encrypting algorithm, mode and key. The following table explains all encryption parameters available within a backup set. Note:
4.8 Retention PolicyDuring backup, if OBM finds out that you have deleted a file (or updated a file) on your computer, it will put the corresponding deleted (or updated) file already backed up on the backup server into a retention area. The retention policy setting defines how long files inside the retention area will be kept on the backup server before they are deleted automatically from the server. Retention policy will only affect “retained” file (i.e. files that have already been deleted or updated on your computer and thus are moved to the retention area of the backup server). For those files that have not been updated on your computer, the backup of these files is kept in the data area on the backup server and won’t be affected by the setting of retention policy. These backup files of unchanged files will stay on the backup server forever until the original files are removed (or updated) from your computer. Standard Retention PolicyThe [Standard] retention policy allows you to delete retained files automatically after a user defined number of days or after a user defined number of backup Jobs. To change the retention policy setting of any backup set, please select the [Retention Policy] node on the left panel. You can then make changes to your retention policy under the [Retention Policy] section. After you have made your changes, just press the [Save Setting] button on the toolbar. Advanced Retention Policy The [Advanced] retention policy allows you to configure a more flexible retention policy. It allows you to keep a set of snapshots of all backup files based on the time of the backup Jobs. For example, you can configure the advanced retention policy to keep the following sets of backup files to mimic the retention policy back from the old days when you were still doing tape rotations: u All files available within the last 7 days u All files available on the last 4 Sundays within the last 28 days u All files available on the 1st day of each month within the last 3 months u All files available on the 1st day of each quarter within the last 12 months u All files available on the 1st day of each year within the last 7 years To do so, you need to setup your advanced retention policy as follows: u Type = Daily; Number of copy to keep = 7 u Type = Weekly; Frequency = Sunday; Number of copy to keep = 4 u Type = Monthly; Frequency = Day 1; Number of copy to keep = 3 u Type = Quarterly; Frequency = Day 1 of Jan, Apr, Jul, Oct; Number of copy to keep = 4 u Type = Yearly; Frequency = Date 01-01; Number of copy to keep = 7 Assuming today is 17-Jan-2006, if [Remove retention files for overlap policy] is NOT enabled, a total of 25 snapshots (7+4+3+4+7, provided you have run backup daily for more than 7 years already) will be kept on the server accordingly, i.e.: u Daily: 10-Jan-2006, 11-Jan-2006, 12-Jan-2006, 13-Jan-2006, 14-Jan-2006, 15-Jan-2006, 16Jan-2006 u Weekly: 24-Dec-2005, 31-Dec-2005, 7-Jan-2006, 14-Jan-2006 u Monthly: 1-Nov-2005, 1-Dec-2005, 1-Jan-2006 u Quarterly: 1-Jan-2005, 1-Apr-2005, 1-Jul-2005, 1-Oct-2005 u Yearly: 1-Jan-2004, 1-Jan-2003, 1-Jan-2002, 1-Jan-2001, 1-Jan-2000, 1-Jan-1999 If [Remove retention files for overlap policy] is enabled, only the following snapshots are kept: u Daily: 14-Jan-2006, 15-Jan-2006, 16-Jan-2006 u Weekly: 7-Jan-2006 u Monthly: 1-Nov-2005, 1-Dec-2005, 1-Jan-2006 u Quarterly: 1-Jan-2005, 1-Apr-2005, 1-Jul-2005, 1-Oct-2005 u Yearly: 1-Jan-2004, 1-Jan-2003, 1-Jan-2002, 1-Jan-2001, 1-Jan-2000, 1-Jan-1999 The weekly policy overrides the daily policy so the snapshots of 10-Jan-2006, 11-Jan-2006, 12-Jan-2006 and 13-Jan-2006 are removed. The monthly policy overrides the weekly policy so the snapshots of 24-Dec-2005, 31-Dec-2005 and 7-Jan-2006 are removed as well. The same applies to the quarterly and yearly policy but because there is no other overlapping of the dates above, the snapshots of dates specified by the monthly, quarterly and yearly policy remains the same. 4.9 Extra Backup (Off-line backup, Logout Reminder)Off-line backup is basically designed for notebook users who are off-line most of the time and cannot rely on backup schedule to backup regularly. The "Backup Interval" allows notebook users to specify the interval that they would like their data to backup. If this interval has elapsed, backup will run automatically once this machine is online. The "Off-line Notification Day" setting is the number of days after the off-line backup interval when the backup server will send email notification to the client to remind him to run an off-line backup. 4.10 Network Mapped DriveIf you need to backup a network-mapped drive on Windows (it will only work in Windows NT/2000/XP/2003), you must enter your Windows domain, username and password into the [Network Resources Authentication for Windows] section as shown below. It is required because scheduled backups will always run under the context of windows LocalSystem account (which does not have the privilege required to access network resources) by default. OBM need to collect your Windows username, password and domain name to authenticate itself to the windows domain controller to acquire the required access privileges to the network files which are to be backed up. If you don’t supply a username and password, OBM will have problem accessing network resources in its scheduled backup Jobs. If you need to backup network mapped drive in scheduled backup, please do this: i.
Select the backup set from the left panel and
press the [Properties] button ii.
Enter your Windows domain, username and password
into the dialog shown below iii.
Press the [Save Setting] button on the toolbar The steps above apply only to computers running in a Windows domain. If you don’t have a windows domain with your network and you are using a workgroup or using a NetWare server instead, please use the “net use” command to authenticate the running backup process against the computer hosting the mapped drive. Otherwise, you will get “Access Denied” error from the backup report. For example, if you want to backup \\SERVER\SHARE that is located on a NetWare server (or another computer is a windows workgroup) and you are getting "Network drive is not accessible" error message, please try adding the following command as a [Pre-backup command] net use \\SERVER\SHARE [PASSWORD] /USER:[DOMAIN | MACHINE_NAME]\[USERNAME] E.g. C:\> net use \\Netware\Data password /USER:peter This will authenticate the current process with the NetWare server (or another computer is a windows workgroup). Backup will then be allowed to run correctly. 4.11 Local CopyIf you want to save an extra copy of backup data on your local disk (in addition to a copy of backup data stored on the backup server) to minimize file-restoring time and/or to provide an extra safety precaution, you can do the following: i. Open OBM from the System Tray (see previous sections for details) ii. Setup your backup set (see previous sections for details) iii.
Select [Local Copy] under your backup set from
the left panel iv. Check the [Copy to Local Hard Disk] checkbox v. Enter a directory to where you want an extra copy of your backup files to be stored in the [Copy to] field provided (preferably a directory under another hard disk) vi. (Optional) Select the [Yes] radio button if you want to store your backup files in compressed form to conserve free space usage vii. An
extra copy of backup will be saved in the [Copy to] directory when you run your
backup job If you want to make local copy to a directory located on a NetWare server (or another computer is a windows workgroup) and you are getting "Network drive is not accessible" error message, please try adding the following command as a [Pre-backup command] net use \\SERVER\SHARE [PASSWORD] /USER:[DOMAIN | MACHINE_NAME]\[USERNAME] E.g. C:\> net use \\Netware\Data password /USER:peter This will authenticate the current process with the NetWare server (or another computer is a windows workgroup). Backup will then be allowed to run correctly. How to restore “Local Copy” files“Local copy” files are stored in the [Copy to] directory (under [Local Copy] setting) in encoded filenames (A “.nozip” extension is appended to all filenames if [Zip] setting is not enabled. A “.zip” extension is appended to all filenames if [Zip] is enabled). To restore backup files back to their original filenames (and to their original contents if [Zip] is enabled), please do the followings: i.
Choose [Tools] -> [Unzip Local Copy] ii.
Select the required [Backup Set] from the drop
down list iii. Fill in the [Source Directory] (directory where “Local Copy” files are stored) and [Destination Directory] (directory to where you want “Local Copy” files to be restored) iv. Completed 4.12 Multiple Computers using one backup accountIf you want to backup multiple computers using a single backup account, you need to create different backup sets to backup each individual computer. Also, for each installed copy of OBM, you must configure OBM so that it only runs scheduled backup for its intended backup sets on its computer. If this is not being setup properly, scheduled backup job of the same backup set from different computers will both be started. This will result in lots of checksum errors and files being deleted on the backup server. To allow multiple computers to be backed up under a single backup account, you are required to do the following for each computer that has been installed with OBM under the same backup account: i. Logon to one of the computers that has been installed with OBM under the same backup account ii. Open OBM and select a backup set that is not intended to run on this computer from the left panel iii.
Uncheck the [Run scheduled backup on this
computer] checkbox on the right panel iv. Repeat the previous step for the rest of all backup sets that are not intended to run on this computer v. Repeat step ii to step iv for each computer that has been installed with OBM under the same backup account IMPORTANT If you want to backup an extra computer using the same backup account some time later (this implies that you need to create an additional backup set under this backup account for the new computer), please make sure to repeat the procedure above (unchecking the [Run scheduled backup on this computer] checkbox for the added backup set) for each computer 4.13 Transfer Block SizeTransfer block size defines the block size OBM will use to transfer your backup blocks. Generally, backup job using a larger block size would have a better performance, as there will be less roundtrip involved in connection initialization. However, some firewalls or proxy servers may block out-going network traffic (HTTP/HTTPS POST method) with large block size for security reasons. If you are in a network with this type of restriction, please lower the transfer size value and try again. To change the transfer block size of any backup set, please select the [Setting] node on the left panel to invoke the [Setting] panel on the right. You can then make changes to the [Transfer Block Size]. After you have made your changes, just press the [Save Setting] button on the toolbar. 4.14 Temporary directoryIf you are running a file backup job with in-file delta enabled or a database type backup job, temporary files will be generated by the backup job and directory that will be used to store all these files are defined by [Setting] -> [Temporary directory for storing backup files]. Please set this to a non-system disk partition that has enough free space to avoid problems. You can set the [Temporary directory for storing backup files] to a network mapped drive. If you choose to do this, please use a UNC path (e.g. \\SERVER\SHARE) or don’t forget to configure the [Backup Set] -> [Network Resources Authentication for Windows] setting. To conserve the use of disk space, you can use the [Remove temporary files after backup] option to delete the temporary files automatically after a backup job has finished. 4.15 Follow Symbolic Link (Linux/Unix/Mac only)Under Unix/Linux, users can use symbolic link to create a simple link to a directory from another directory. This setting defines whether you want OBM to traverse any symbolic links encountered on your backup path. To change the transfer block size of any backup set, please select the [Setting] node on the left panel to invoke the [Setting] panel on the right. You can then make changes to the [Follow Symbolic Link]. After you have made your changes, just press the [Save Setting] button on the toolbar. 4.16 Microsoft Volume Shadow Copy (VSS)Microsoft Volume Shadow Copy Service (VSS) allow you to backup files that are exclusively opened. Without VSS, you will get the error message “The process cannot access the file because another process has locked a portion of the file” if you are trying to backup a file that is exclusively opened (e.g. Outlook PST file). Please note that VSS is only available on Windows XP / 2003 and you must have administrative privileges to start the VSS service on a computer. If you are running Windows 2003, please install the Windows 2003 VSS hot fix available in http://support.microsoft.com/default.aspx?scid=kb;en-us;887827 before running VSS. If you are running into problem with running VSS on Windows XP, Microsoft's recommendation is to try re-registering the Volume Shadow Copy Service again. Simply run the script [OBM Home]\bin\RegisterVSS.bat to do so. For more information, please take a look at the following page for a technical introduction to Volume Shadow Copy Services (VSS): http://technet2.microsoft.com/windowsserver/en/library/2b0d2457-b7d8-42c3-b6c9-59c145b7765f1033.mspx 5 Backing up filesThis chapter describes how files are backed up by OBM to the backup server 5.1 How files are backed upThe diagram below describes how OBM backup your files.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
and choose [Open]. 
Note: |
|
| 1. | You can have more than one backup set in backup account. |
2. |
Please write the encrypting key down on paper and keep it in a safe place. If you lost your encrypting key is lost, you will not be able to restore your backup files. |
5.3 Backup files to removable hard disk (seed loading)
If you have a lot of data (e.g. 300GB) to backup to the backup server, it would take a considerable amount of time to perform the first full backup through the Internet. If you run into this problem, you can use the Seed Loading Utility to backup your backup set to local hard disk (instead of directly to the backup server) and then transport the backup data, using removable hard disk, to the offsite backup server. The administrator can then load all your backup files from your removable hard disk into your backup account. This could then save you days (even weeks) of performing your first full backup. Since subsequent backup will be incremental backup (only new or updated files will be uploaded to the server), you should have no problems finishing backing up all files afterwards.
To perform seeding loading, please do the following:
i. Open OBM from the System Tray (see previous sections for details)
ii. Setup your backup set (see previous sections for details)
iii. Select the backup set you want to run on the left panel and press the [Start Backup] button (►) on the toolbar
iv. Select
[Local Hard Disk (Seed Load Utility)] to start backing up your files to local
hard disk and press the [OK] button
v.
Enter a directory where you want all backup
files to be stored in the [Destination Directory] field and press the [Start]
button.
Please make sure you have enough free space in the directory specified. If you
are going to transport a removable hard disk to the offsite backup server,
please enter a directory under your removable hard disk here.
vi. You
should get the message “Backup Completed Successfully” as shown below after all
backup files are spooled to the directory you specified.
vii. Transport the data specified in the [Destination Directory] field to the offsite backup server
6 Restoring files
This chapter describes different ways files can be restored from to the backup server
It is important to write down your encrypting key on paper and keep it in a safe place because there will be no ways to restore your backup files if you lose your encrypting key.6.1 Restore backup files directly from backup server
You can use either OBM or the web restorer to restore backup files from the backup server.
Using OBM
You can restore your data from the backup server by following instructions below.
i. Open OBM from the System Tray (see previous sections for details)
ii.
Select the [Restore] tab at the bottom part of OBM
iii. Select the backup set from which you would like files to be restored from the left panel
iv. Select the snapshot of your backup files that you would like to restore from the backup server by using [Show files after Job] drop down list
v.
Select the files that you would like to restore
and press the [Restore Files] button on the toolbar
vi. Use the [Browse] button to select the directory to where you want files to be restored (or simply select [Original location] to restore files to their original path)
vii.
Files will be restored automatically as shown
below (a file won’t be downloaded from the backup server again if an identical
file exists on local path already)
Using the web interface
You can restore your data from an Offsite Backup Server by following instructions below.
i. Logon to the Offsite Backup Server web interface
ii.
From the top menu, click [File Explorer]
iii. Click the [Backup Set] link that contains the files that you want to restore
iv. Select
the snapshot of your backup files that you would like to restore from the
backup server by using [Show files after Job] drop down list
v.
If you want to see all different versions all
files (shown as gray below), just choose the [Show all files] radio button on
the [File Explorer] page.
Files, which are shown in gray and marked as deleted below, e.g. dell.img
(delete), are being stored in the retention area on the backup server but you
can still restore these files from the backup server.
vi. Select the files that you would like to restore and press the [Restore] button on the toolbar
vii. A
dialog shown below would appear
a. Press the [Restore] button
b.
Enter the directories to which backup files
should be restored in the [Restore File to] textbox
c. Enter the encrypting key which will be used to decrypt your backup files upon restoring your backup files
d. Press the [Start] button
6.2 Restore backup files from removable hard disk
If you want to restore lots of backup files from the backup server and you find it too slow to restore all your backup files from the backup server through the internet. You can ask your backup services provider to send you all your backup files in removable hard disk (or CD/DVD). However, all backup files stored on backup server are in encrypted format. You need to decrypt them back to their original format before you can use them. To decrypt your backup files from removable media, please do the followings:
i. Open OBM from the System Tray
ii.
Select the [Tools] -> [Decrypt Files Wizard]
from the menu
iii.
Use the [Browse] button to locate the “files”
directory (provided by your backup provider in removable hard disk or DVD)
which contains the backup files that you want to decrypt
iv. If you have more than one backup set under the “files”
directory, select the [Backup Set] which contains the backup files that you
want to decrypt
v.
Select the snapshot of your backup files that
you would like to restore from the removable media by using [Show files after
Job] drop down list
vi. If
you want to see all different versions all files (shown as gray below), just
choose the [Show all files] radio button on the [Decrypt Files Wizard] dialog.
Files, which are shown in gray and marked as deleted below, e.g. dell.img
(delete), are being stored in the retention area on the removable media (but
you can still restore these files).
vii.
Enter the directories to which you want backup
files to be restored in the [Decrypt Files to] section and enter the
[Decrypting Key] (the same as the encrypting key of this backup set)
viii.
Press the [Start] button
6.3 Restrict restoring files by IP addresses
Online file restoring operation can be restricted by IP addresses. You can ask your backup provider to restrict online file restoring for your backup sets by IP addresses to allow people from authorized IP addresses to restore files from the backup server. To check if online file restore of any backup set is restricted this way, please take a look at the web interface of OBS, [Online Backup Services Management Console] -> [Backup Set] -> [Online Restore IP restriction] (shown below).
Users are not allowed to update the [Online Restore IP restriction] directly. Please ask your backup services provider to do the changes for you.
7 In-File Delta Technology
The chapter describes what in-file delta technology is and how in-file delta can be used to backup large database files (e.g. a 10GB Outlook.pst file) without uploading the whole database file everyday.
7.1 Overview
In-file delta technology is an advanced data block matching algorithm which has the intelligence to pick up changes (delta) of file content between two files when one of the files is not accessible and use the delta information between two files to rebuild one file from the other. Using this algorithm, daily backing up of large file (e.g. a 10GB Outlook.pst file) over low-speed internet connection is made possible because it requires only the changes of information (should be marginal) since last backup (or last incremental backup) to be sent over a low-speed internet connection to complete the backup of a large file (here we assume that the full backup of the file has been saved on the backup server already).
This is what would happen to the backup of a 10GB Outlook.pst file when it is backed up by OBM with in-file delta technology.
i. The whole files (10GB), along with its checksum (128-bit) file, are backed up to the backup server. This can be done directly through the internet or indirectly using the seed loading utility on a removable hard disk.
ii. When backup runs again later (normally the next day), OBM will download a checksum listing of all data blocks of the full backup file (or last incremental backup file) from the backup server and use it to pick up all changes that have been made to the current Outlook.pst file from the first full backup.
iii. Changes detected are then saved in a delta file which is uploaded to the backup server. (This delta file is assumed to be small because the content of all PST files doesn’t change lot of even after it has been updated)
iv. Subsequent backups of this 10GB Outlook.pst file will go through step ii and step iii again. As explained, only a small delta file will be uploaded to the backup server.
v. With in-file delta technology, daily backing up of large file over low-speed internet connection is now possible
Incremental in-file delta type
Example 1: If you are adding 200MB to Outlook.pst everyday, everyday after the first full backup job, OBM will detect what has been added since last daily backup and upload only 200MB of delta file to the backup server everyday. This will go on until Day 100 because it is the [Maximum number of delta] (default) allowed in this backup set and the whole Outlook.pst file will be uploaded again. You can set the [Maximum number of delta] setting to [Unlimited] if you don’t want to upload the full file again.
All delta files are generated with respect to changes made since the last incremental backup. This means that the last full backup file and ALL incremental delta backup files are required to restore the latest snapshot of a backup file.
The full backup file, its checksum file and all incremental delta files stored on the server are always stored in the data area. This means that these files are not affected by the setting of the retention policy and will always be kept on the backup server. This is done this way because all these files are required to get the latest snapshot of the backup file and they should not be removed from the backup server by the retention area cleanup routine.
Differential in-file delta type
Example 1: If you are adding 200MB to 10GB Outlook.pst everyday, the first delta backup will upload a 200MB delta file and the next delta backup will upload another 200MB delta file. This will go on until Day 50 when the delta file required to be backed up reached 10GB. This delta file size (10GB) is now is 50% of the Outlook.pst that is 20GB (remember that you have added 100MB to this file everyday). If the [Delta Ratio] is set to be 50% (default), the whole Outlook.pst file will be uploaded again.
Example 2: If you are adding 50MB to a 10GB Outlook.pst everyday, the first delta backup will upload a 50MB delta file and the next delta backup will upload a 50MB delta file. This will go on until Day 100 because it is the [Maximum number of delta] (default) allowed in this backup set and the whole Outlook.pst file will be uploaded again.
All delta files are generated with respect to changes made since the last full backup file (i.e. differential backup). This means that only last full backup file and the last delta file are required to restore the latest snapshot of a backup file. This means that other intermediate delta files are only required if you want to restore other snapshots of a backup file.
Differential in-file delta backup has the benefits that a corrupted delta file would only make one particular version of a backup file non-recoverable and all other backups created by other delta files of the same file would still be intact.
The full backup file, its checksum file and the last delta file uploaded (if more than one delta files have been uploaded to the backup server) is always stored in the data area. This means that these files are not affected by the setting of the retention policy and will always be kept on the backup server. This is done this way because all these files are required to get the latest snapshot of the backup file and they should not be removed from the backup server by the retention area cleanup routine. All other intermediate delta files are stored in the retention area.
7.2 Block Size
The block size defines the size of data block being used to detect changes between last full backup file and the file sitting on the local computer right now. In general, the smaller the block size, the more likely a matched data block can be found between the last full backup file and the file on local computer. It, therefore, produces in a smaller delta file but it would require more processing power to detect these changes. On the other hand, in-file delta backup running with larger block size will run faster but this will generally produce a larger delta file.
In most case, the default setting [Auto] will choose the optimal block size for each file (depending on the size of the file) for you.
7.3 Minimum File Size
The [Minimum File Size] setting defines the smallest file size a file must have before the use and application of in-file delta backup technology.
If the size of a file that is being backed up is smaller than the [Minimum File Size] setting, in-file delta backup technology won’t be applied to this file and the whole file, instead of just the delta file, will be uploaded to the backup server. It is not necessary to perform in-file delta backup on small files because backing up the whole file doesn’t take too long anyway. Backing up the whole file instead reduces the time required to restore a backup file.
7.4 Uploading full file again
No. of Delta
The [No. of delta] setting defines the maximum number of delta files from the same full backup file to be generated and backed up to the backup server before a full backup (the whole file) of this file is uploaded to the backup server instead.
For example, if you have created 100 delta files from the full backup file already and the [No. of delta] setting is 100, the next backup will upload a full backup file (the whole file) instead of just the delta file. However, if the [No. of delta] setting is unlimited, it will keep generating delta files and uploading these delta files to the backup server until any of the other delta setting conditions force a full backup (e.g. delta ratio is exceeded). This setting is here to make sure that there will always be a full backup file after a certain number of delta files have been generated.
Delta Ratio
The [Delta Ratio] setting is defined to be the size of a delta file divided by the size of its full backup file (i.e. the percentage of changes detected between the last full backup file and the current file).
If delta ratio calculated from the size of the generated delta file and the size of the full backup is greater than the [Delta Ratio] setting, the whole file, instead of just the delta file, will be backed up to the backup server. It is done this way because the difference between backing up the whole file and the delta file is not significant and it is better to upload the whole file instead to reduce the time required to restore the file.
The default setting of [Delta Ratio] is 50%. This means that if more than 50% changes have been detected, the whole file, instead of just the delta file, will be backed up and uploaded to the backup server.
7.5 Advanced In-file delta type
The [In-file delta] -> [Advanced] setting allows user to override default in-file delta type when on a certain number of days (e.g. all Sundays or the 1st day of each month). This is useful if you want all in-file delta backups to be incremental but you always want to do full backup on Sundays as well as the 1st day of every month. If you want to do this, simply configure [In-file delta] -> [Advanced] -> [Advanced In-file Delta Type Setting] to what is shown below.
With this setting, all backup Jobs starts on Sundays or the 1st day of each month will run a full backup job. In this case, all backup files which have been backed up incrementally/differentially using in-file delta feature will be uploaded in full again. This ensures that all backup files will be backed up in full at a regular interval. One benefit of this is that restore time will run faster because of less delta merging. Another benefit is that the risk of a corrupted incremental delta file resulting in data loss is much lower because a full backup is always available periodically.
8 Backup/Restore Oracle 8i/9i
This chapter will describe in details how OBM backup your Oracle 8i/9i and how you can restore an Oracle 8i/9i database using the backup files.
8.1 Requirements
i. OBM must be installed onto the computer that can connect to your Oracle 8i/9i server using TCP/IP protocol.
ii. Data from Oracle 8i/9i database will be backed up to a temporary directory before they are sent to Offsite Backup Server. Please make sure you have sufficient space on your computer to store these data when you run the backup job.
iii.
Database must be in archived log mode
To switch to archived log mode and enable automatic log archiving, please do
the following:
a.
Set the parameters below in the PFILE to enable
automatic archiving
log_archive_dest = [directory where archived logs will be stored]
log_archive_format = ARCH%S.LOG
log_archive_start = TRUE
b.
Switch to archived log mode
SVRMGRL> connect internal;
SVRMGRL> startup mount;
SVRMGRL> alter database archivelog;
SVRMGRL> alter database open;
c. Enable Oracle JVM for Oracle 8i/9i, please do the following:
1. Please make sure shared pool size is larger than
50MB and java pool size is larger than 20MB in the PFILE. For example:
java_pool_size = 20971520
shared_pool_size = 52428800
2. Run the scripts below
For Oracle 8i
SVRMGRL> connect internal
SVRMGRL> @?/javavm/install/initjvm.sql;
SVRMGRL> @?/rdbms/admin/catalog.sql;
SVRMGRL> @?/rdbms/admin/catproc.sql;
SVRMGRL> @?/javavm/install/initdbj.sql;
For Oracle 9i
SQL> connect sys/change_on_install as sysdba
SQL> @?/javavm/install/initjvm.sql;
SQL> @?/xdk/admin/initxml.sql;
SQL> @?/xdk/admin/xmlja.sql;
SQL> @?/rdbms/admin/catjava.sql;
For Oracle 10g
Oracle JVM is enabled by default. No additional steps required.
iv. JAVASYSPRIV role is granted to system account
You can grant this role to system account by executing:
SQL> grant JAVASYSPRIV to system;
8.2 Overview
OBM will backup your Oracle database by taking the following steps.
i. Connect to the Oracle database using SQL*NET over TCP/IP
ii. Run all Pre-Commands of this backup set
iii. If the backup type to run is [Database Backup type],
a. all data files in each of the tablespace(s) selected are copied to the temporary directory specified by this backup set
b. if there are temporary files in the database, the script to re-create the temporary files are generated to a file located in the temporary directory specified by this backup set
c. all non-default initialization parameters will be spooled to an initializing file located in the temporary directory specified by this backup set
d. all control files will be copied to the temporary directory specified by this backup set
e. all archived log files will be copied to the temporary directory specified by this backup set
iv. If the backup type to run is [Archived Log Backup type],
a. all archived log files will be copied to the temporary directory specified by this backup set
v. Run all Post-Commands of this backup set
vi. Upload all files copied to the temporary directory to the Offsite Backup Server
vii. Remove temporary files from the temporary directory if [Setting] -> [Temporary Directory for storing backup files] is enabled
Note:
If your Oracle database is running on Windows, please install OBM onto the
company running the Oracle database if OBM is to backup this Oracle database.
This would shorten the time required to backup the Oracle database.
8.3 How to backup an Oracle Database
Please follow the instructions below to backup your Oracle database to the Offsite Backup Server.
i. Install OBM onto your computer
ii.
Open OBM
Right click OBM icon available in the system tray and choose [Open]
iii. Create a backup set
a.
From the Menu, Choose [Backup Set] -> [New]
-> [Oracle Database Backup Set]
b. Enter a name for your backup set
c. Enter the system password, the Oracle Database Server Host Name, TNS Port and SID
d.
Select the tablespace(s) you want to backup
e. Enter a temporary location to store the database file(s) before they are sent to an Offsite Backup Server
f.
Set the backup schedule for database backup and
archived log backup
Note: You can have more than one schedule in a backup set, i.e. you can perform intra-day transaction log backup by adding more than one daily transaction log backup schedule to your backup set.
g.
Set the encryption algorithm, encryption mode
and encrypting key for this backup set
Hint: For maximum security, please select AES (Advanced Encryption Standard)
Algorithm, CBC (Cipher Block Chaining) mode and use an encrypting key with more
than 8 characters.
iv. Run Backup
a. Select the backup set you want to run on the left panel and press the [Start Backup] button (►)
b. Select the backup type (e.g. Database Backup, Archived Log Backup) you would like to perform
c.
Select [Off-site Backup Server] to start backing
up your files to an Offsite Backup Server.
8.4 How to restore an Oracle Database
Please follow the instructions below to restore your Oracle 8i/9i databases from an Offsite Backup Server.
i.
Download the backup files from the Offsite
Backup Server
Please refer to the [Quick Start - Backup File] section for information on how
to download backup files from Offsite Backup Server.
ii. Put all data files back to their original locations
iii. Control files, data files and archived logs are stored on Offsite Backup Server along with their full path information. You just need to put all these files back to their original locations when performing a database restore.
iv. Put
the PFILE back to its default location
Oracle 8i: $ORACLE_HOME/dbs/init<SID>.ora
Oracle 9i: $ORACLE_HOME/admin/<SID>/pfile/init.ora
v.
Restore Database
(if Oracle 8i) Use Server Manager to restore you database by doing the
following:
a. Run Oracle Server Manager (svrmgrl)
b. Connect to the target database
c. Startup mount
d. Reapply all transactions from the archived log files
e. Open database
Oracle 8i Example: |
$ svrmgrl SVRMGRL> connect internal SVRMGR> startup mount; ORACLE instance started. Total System Global Area 95874448 bytes Fixed Size 64912 bytes Variable Size 52744192 bytes Database Buffers 40960000 bytes Redo Buffers 2105344 bytes Database mounted.
ORA-00279: change 419671 generated at 06/14/03 02:51:49 needed for thread 1 ORA-00289: suggestion : /data/ora815/vin/archive/ARCH0000000225.LOG ORA-00280: change 419671 for thread 1 is in sequence #225 ORA-00278: log file '/data/ora815/vin/archive/ARCH0000000224.LOG' no longer needed for this recovery Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied. . . . . . . . . . . . ORA-00279: change 547222 generated at 06/18/03 19:58:26 needed for thread 1 ORA-00289: suggestion : /data/ora815/vin/archive/ARCH0000000384.LOG ORA-00280: change 547222 for thread 1 is in sequence #384 ORA-00278: log file '/data/ora815/vin/archive/ARCH0000000383.LOG' no longer needed for this recovery ORA-00308: cannot open archived log '/data/ora815/vin/archive/ARCH0000000384.LOG' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 SVRMGR> recover database using backup controlfile until cancel ORA-00279: change 547222 generated at 06/18/03 19:58:26 needed for thread 1 ORA-00289: suggestion : /data/ora815/vin/archive/ARCH0000000384.LOG ORA-00280: change 547222 for thread 1 is in sequence #384 Specify log: {<RET>=suggested | filename | AUTO | CANCEL} CANCEL Media recovery cancelled. SVRMGR> alter database open resetlogs; Statement processed. |
(if Oracle 9i) Use Recovery Manager to restore you database by doing the following:
a. Run Oracle Server Manager (rman)
b. Connect to the target database
c. Startup mount
d. Reapply all transactions from the archived log files to the last sequence
e. Open database
Oracle 9i Example: |
C:\>rman nocatalog Recovery Manager: Release 9.2.0.1.0 - Production Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved. RMAN> connect target connected to target database (not started) RMAN> startup mount connected to target database (not started) Oracle instance started database mounted Total System Global Area 269556596 bytes Fixed Size 453492 bytes Variable Size 243269632 bytes Database Buffers 25165824 bytes Redo Buffers 667648 bytes RMAN> recover database until sequence=63 thread=1; Starting recover at 24-JUN-03 allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=11 devtype=DISK starting media recovery archive log thread 1 sequence 56 is already on disk as file C:\ORACLE\ORADATA\VIN\ARCHIVE\1_56.DBF archive log filename=C:\ORACLE\ORADATA\VIN\ARCHIVE\1_56.DBF thread=1 sequence=56 archive log filename=C:\ORACLE\ORADATA\VIN\ARCHIVE\1_57.DBF thread=1 sequence=57 archive log filename=C:\ORACLE\ORADATA\VIN\ARCHIVE\1_58.DBF thread=1 sequence=58 archive log filename=C:\ORACLE\ORADATA\VIN\ARCHIVE\1_59.DBF thread=1 sequence=59 archive log filename=C:\ORACLE\ORADATA\VIN\ARCHIVE\1_60.DBF thread=1 sequence=60 archive log filename=C:\ORACLE\ORADATA\VIN\ARCHIVE\1_61.DBF thread=1 sequence=61 archive log filename=C:\ORACLE\ORADATA\VIN\ARCHIVE\1_62.DBF thread=1 sequence=62 media recovery complete Finished recover at 24-JUN-03 RMAN> alter database open resetlogs; database opened |
9 Backup/Restore Microsoft SQL Server 7.0 / 2000
This chapter will describe in details how to use OBM to backup your Microsoft SQL Server 7.0 / 2000 server and how you can restore your Microsoft SQL Server 7.0 / 2000 server from the backup files.
9.1 Requirements
i. OBM must be installed onto the computer running Microsoft SQL Server.
ii. Data from Microsoft SQL Server will be backed up to a temporary directory before they are sent to Offsite Backup Server. Please make sure you have sufficient space on your computer to store these data when you run the backup job.
9.2 Overview
OBM will backup your Microsoft SQL Server database(s) by taking the following steps:
i. Before running any backup activities, OBM will run all Pre-Commands of the backup set.
ii. For each database that is to be backed up, OBM will issue a database / transaction log backup command to Microsoft SQL Server to backup each database to a Microsoft SQL Server database backup file (*.bak file) and save it in the temporary directory you specified.
iii. After all *.bak files have been spooled to the temporary directories, OBM will run all Post-Commands of the backup set.
iv. Upload all files copied to the temporary directory to the Offsite Backup Server.
v. Remove temporary files from the temporary directory if [Setting] -> [Temporary Directory for storing backup files] is enabled
9.3 How to backup Microsoft SQL Server database(s)
Please follow the instructions below to backup your Microsoft SQL Server databases using OBM.
vi. Open OBM
Right click OBM icon available in the system tray and choose [Open]
vii. Create a backup set
a.
From the Menu, Choose [Backup Set] -> [New]
-> [MS SQL Server Backup Set]
b.
Enter a name for your backup set
c. Enter the Microsoft SQL Server administrator username and password
d.
Select the database(s) you want to backup
e. Enter a temporary location to store the backup files before they are sent to an Offsite Backup Server
f.
Set the backup schedule for full database backup
and transaction log backup
(Note: You can have more than one schedule in a backup set, i.e. you can
perform intra-day transaction log backup by adding more than one daily
transaction log backup schedule to your backup set)
g.
Set the encryption algorithm, encryption mode
and encrypting key for this backup set
(Hint: For maximum security, please select AES (Advanced Encryption Standard)
Algorithm, CBC (Cipher Block Chaining) mode and use an encrypting key with more
than 8 characters.)
viii. Run Backup
a. Select the backup set you want to run on the left panel and press the [Start Backup] button (►)
b.
Select the backup type (e.g. Complete,
Differential, Transaction Log) you would like to perform
c.
Select [Off-site Backup Server] to start backing
up your files to an Offsite Backup Server.
9.4 How to restore Microsoft SQL Server database(s)
Please follow the instructions below to restore your Microsoft SQL Server databases from an Offsite Backup Server.
i.
Download the backup files (.bak) from the Offsite
Backup Server
Please refer to the [Quick Start - Backup File] section for information on how
to download backup files from Offsite Backup Server.
ii.
Open Microsoft SQL
You can open Microsoft SQL Enterprise Manager from [Start Menu] -> [Program]
-> [Microsoft SQL Server] -> [Enterprise Manager]
iii. (Optional) Restore “master” database
You need to restore “master” database if you:
a. are rebuilding all your databases from scratch
b. have changing any server-wide or database configuration options
c. have added logins or other login security-related operations.
d. have created or removed logical backup devices.
e. have configured the server for distributed queries and remote procedure calls, such as adding linked servers or remote logins.
You do not need to restore your master database if you just want to restore a user database. For more information on Microsoft SQL Server “master” database, please visit http://www.microsoft.com/sql/.
To restore “master” database, please do the following:
a. Start Microsoft SQL Server in “Single User Mode”
1. Right click your Microsoft SQL Server and select
[Properties]
2. Press the [Startup Parameters] button
3. Add a “-m” parameter to the [Startup Parameters]
4. Restart Microsoft SQL Server
From [Enterprise Manager], right click your Microsoft SQL Server and select
[Stop] and then [Start].
b.
Restore “master” database
1. From [Enterprise Manager] -> [Tools] ->
[Restore Database]
2. Select [master] in the [Restore as database]
drop down list
3. Select the [From device] radio button.
4. Press the [Select Devices] button.
5. From the [Choose Restore Devices], press the
[Add] button.
6. From the [Choose Restore Destination] panel,
press the […] button to choose your master backup (*.bak) from your backup
files
7. Press the [OK] button, to start restoring the “master” database.
c. Restart Microsoft SQL Server in “Normal Mode”
1. Remove “-m” parameter from the [Startup Parameters] as in previous step
2. Restart your Microsoft SQL Server as in previous step
iv. (Optional)
Restore “model”, “msdb” and “distribution” database
You need to restore “model” database if you have changed the database template
of your SQL Server.
You need to restore “msdb” database if you have changed the scheduling
information or you want to restore the backup and restore history of your
databases.
You need to restore “distribution” database if you are running the replication
components of SQL Server.
You do not need to restore these databases if you just want to restore a user
database. For more information on Microsoft SQL Server “model”, “msdb” and
“distribution” database, please visit http://www.microsoft.com/sql/.
You need to restore each of these databases one by one. To restore any of these
databases, please do the following:
a. From [Enterprise Manager] -> [Tools] -> [Restore Database]
b. Select the database to be restored in the [Restore as database] drop down list
c. Select the [From device] radio button.
d. Press the [Select Devices] button
e. Press the […] button to choose your backup files (*.bak) for the database to be restored
f. Press the [OK] button
v.
Restore user database(s)
For each of the database you would like to restore,
a. From [Enterprise Manager] -> [Tools] -> [Restore Database]
b. Select the database to be restored in the [Restore as database] drop down list
c. Select the [Database] radio button.
d. From the [Show backups of database] drop down list, select the database to be restored
e.
From the [First backup to restore] drop down
list, select the snapshot of the database you would like to restore to.
You can restore your database to the snapshot of your database at any point of
the time between the time you did your full backup and the time you did your
last subsequent backup.
f.
Change the [Restore From] entry
If you backup files (*.bak) are not in the default directory, you need to
update the full path to your backup files by pressing the [Properties] button.
g. Press the [OK] button
vi. All database(s) restored successfully
10 Backup/Restore Lotus Domino / Notes
This chapter will describe in details how to use OBM to backup your Lotus Domino server / Notes client 5 / 6 / 6.5 and how you can restore your Lotus Domino server / Notes client 5 / 6 / 6.5 from the backup files.
10.1 Requirements
i. OBM must be installed onto the computer running Lotus Domino server / Notes client.
ii. The computer running Lotus Domino server / Notes client must be on Windows platform.
iii. Data from Lotus Domino server / Notes client will be backed up to a temporary directory before they are sent to Offsite Backup Server. Please make sure you have sufficient space on your computer to store these data when you run the backup job.
iv. Lotus Domino server must runs with archive
transaction logging enabled
To set up transaction logging in archive style, please do the following:
a. Ensure that all databases to be logged reside in the Domino data directory, either at the root or in subdirectories.
b. From the Domino Administrator, click the Configuration tab.
a. In the "Use Directory on" field, choose the server's Domino Directory.
b. Click Server Configuration, and then click Current Server Document.
c. Click the Transactional Logging tab.
d. Complete these fields, and then save the document.
| Field | Enter |
| Transactional Logging | Choose Enabled. The default is Disabled. |
| Log path | Path name location of the transaction log. The default path name is \LOGDIR in the Domino data directory, although it is strongly recommended to store the log on a separate, mirrored device, such as a RAID (Redundant Array of Independent Disks) level 0 or 1 device with a dedicated controller. The separate device should have at least 1GB of disk space for the transaction log. If you are using the device solely for storing the transaction log, set the "Use all available space on log device" field to Yes. |
| Maximum log space | The maximum size, in MB, for the transaction log. Default is 192MB. Maximum is 4096MB (4GB). Domino formats at least 3 and up to 64 log files, depending on the maximum log space you allocate. |
| Use all available space on log device | Choose one: Ÿ Yes to use all available space on the device for the transaction log. This is recommended if you use a separate device dedicated to storing the log. If you choose Yes, you don’t need to enter a value in the "Maximum log space" field. Ÿ No to use the default or specified value in the "Maximum log space" field. |
| Automatic fixup of corrupt databases | Choose one: Ÿ Enabled (default). If a database is corrupt and Domino cannot use the transaction log to recover it, Domino runs the Fixup task, assigns a new DBIID, and notifies the administrator that a new database backup is required. Ÿ Disabled. Domino does not run the Fixup task automatically and notifies the administrator to run the Fixup task with the -J parameter on corrupt logged databases. |
| Runtime / Restart performance | This field controls how often Domino records a recovery checkpoint in the transaction log, which affects server performance. To record a recovery checkpoint, Domino evaluates each active logged database to determine how many transactions would be necessary to recover each database after a system failure. When Domino completes this evaluation, it: Ÿ Creates a recovery checkpoint record in the transaction log, listing each open database and the starting point transaction needed for recovery Ÿ Forces database changes to be saved to disk if they have not been saved already Choose one: Ÿ Standard (default and recommended). Checkpoints occur regularly. Ÿ Favor runtime. Domino records fewer checkpoints, which requires fewer system resources and improves server run time performance. Ÿ Favor restart recovery time. Domino records more checkpoints, which improves restart recovery time because fewer transactions are required for recovery. |
| Logging style | Choose Archive. The default is Circular. |
Notes:
You can only run transaction log backup if you have transaction logging enabled
and you are using archive mode. This command does not apply if you have
transaction logging enabled not in archive mode or if transaction logging is
not enabled at all. If you try to issue it, you will receive an error message.
10.2 Overview
OBM will backup your Lotus Domino server / Notes client by taking the following steps:
i. Run all Pre-Commands of this backup set
ii. If the backup type to run is [Database Backup type],
a. all file(s) / database(s) selected are copied to the temporary directory specified by this backup set
b. the notes.ini file, if selected, will be copied to the temporary directory
c. only filled log extents will be copied to the temporary directory, and the Domino server is notified of their availability for reuse (for Domino server only)
iii. (for Domino server only) If the backup type to run is [Transaction Log Backup type],
a. only filled log extents will be copied to the temporary directory, and the Domino server is notified of their availability for reuse
iv. Run all Post-Commands of this backup set
v. Upload all files copied to the temporary directory to the Offsite Backup Server
vi. Remove temporary files from the temporary directory if [Setting] -> [Temporary Directory for storing backup files] is enabled
10.3 How to backup Lotus Domino / Notes database(s) / file(s)
Please follow the instructions below to backup your Lotus Domino server / Notes client databases / files using OBM.
i.
Open OBM
Right click OBM icon available in the system tray and choose [Open]
ii.
Create a backup set
a.
From the Menu, Choose [Backup Set] -> [New]
-> [Lotus Backup Set]
b.
Enter a name for your backup set
c. Select the Backup Set Type (Lotus Domino Server Backup / Lotus Notes Client Backup)
d. Select the database(s) / file(s) you want to backup
e. Enter a temporary location to store the backup files before they are sent to an Offsite Backup Server
f.
Set the backup schedule for Database Backup
g.
Set the backup schedule for Transaction Log
Backup (for Domino server only)
(Note: You can have more than one schedule in a backup set, i.e. you can
perform intra-day transaction log backup by adding more than one daily
transaction log backup schedule to your backup set)
(Hint: For maximum security, please select AES (Advanced Encryption Standard) Algorithm, CBC (Cipher Block Chaining) mode and use an encrypting key with more than 8 characters.)
iii. Run Backup
a. Select the backup set you want to run on the left panel and press the [Start Backup] button (►)
b.
Select the backup type (e.g. Database,
Transaction Log) you would like to perform (for Domino server only)
c.
Select [Off-site Backup Server] to start backing
up your files to an Offsite Backup Server.
10.4 How to restore Lotus Domino / Notes database(s) / file(s)
Please follow the instructions below to restore Lotus Domino server / Notes client database(s) / file(s) from an Offsite Backup Server.
i. Install Lotus Domino server / Notes client back to its original folder (if required)
ii.
Install OBM
Please refer to the [Installation] section for information on how to install OBM
onto your computer.
iii. Copy LotusMediaRecovery.exe from the bin directory (default to C:\Program Files\OBM\bin) to Lotus Domino installation directory (default to C:\Lotus\Domino)
iv. Shutdown Lotus Domino Server
v. If you want to perform a full domino restore (restore all databases and files):
a. Download the backup files to be restored from the Offsite Backup Server and save them back to its original location. It includes notes.ini, all backup files from the lotus domino data directory and all archived transaction logs
b.
Run LotusMediaRecovery.exe from the Lotus Domino
installation directory (e.g. C:\Lotus\Domino\LotusMediaRecovery.exe) and press
‘Y’ to continue.
For example: C:\Lotus\Domino\> LotusMediaRecovery.exe
This will run media recovery for all databases (*.nsf and mail.box) found under
the Lotus data directory (e.g. C:\Lotus\Domino\Data). You should see something
similar to the screen below.
Media Recovery Example: |
C:\Lotus\Domino>LotusMediaRecovery Media Recovery Utility for Lotus Domino 5.0 or above Please make sure that you have done the following: 1. Reinstall Lotus Domino on this computer in the same directory 2. Restore Notes.ini to the Lotus Domino installation directory (e.g. C:\Lotus\Domino) 3. Restore Domino Data directory back to the directory defined in Notes.ini (e.g. C:\Lotus\Domino\Data) 4. Restore all archived transaction logs to the directory defined in Notes.ini (e.g. C:\Lotus\Domino\Data\logdir) Continue ? (Y) or (N) y Running media recovery ... Please wait, creating new transaction logs in directory: C:\logdir\ 02/12/2003 14:39:19 Recovery Manager: Restart Recovery complete. (0/0 databases needed full/partial recovery) Media Recovery Replay (122 MB): 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 02/12/2003 14:39:22 Recovery Manager: Media Recovery complete for C:\Lotus\Domino\Data\admin4.nsf, last update applied . Backup file C:\Lotus\Domino\Data\admin4.nsf recovered. ………… Media Recovery Replay (122 MB): 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 02/12/2003 14:40:57 Recovery Manager: Media Recovery complete for C:\Lotus\Domino\Data\statrep.nsf, last update applied . Backup file C:\Lotus\Domino\Data\statrep.nsf recovered. C:\Lotus\Domino> |
c. All content of all database(s) are now rolled forward to the last committed transaction found in the last archived transaction log.
d. Restart Lotus Domino server
vi. If you just want to restore a single database:
a. Download the database file to be restored from the Offsite Backup Server and save them back to its original location.
b. (optional) If you need to perform media recovery on this database, please download all archived transaction logs and save them back to its original location
c.
Run LotusMediaRecovery.exe from the Lotus Domino
installation directory with an argument of the full path of database to be
restored.
For example, if you want to restore C:\Lotus\Domino\data\admin4.nsf, please
run:
C:\Lotus\Domino\> LotusMediaRecovery.exe
C:\Lotus\Domino\data\admin4.nsf
You should see something similar to the screen below.
Media Recovery Example: |
C:\Lotus\Domino>LotusMediaRecovery C:\Lotus\Domino\data\admin4.nsf Media Recovery Utility for Lotus Domino 5.0 or above Running media recovery ... Restart Analysis (0 MB): 100% 02/12/2003 14:42:15 Recovery Manager: Restart Recovery complete. (0/0 databases needed full/partial recovery) Media Recovery Replay (122 MB): 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 02/12/2003 14:42:17 Recovery Manager: Media Recovery complete for C:\Lotus\Domino\data\admin4.nsf, last update applied 01/12/2003 00:02:42. Backup file C:\Lotus\Domino\data\admin4.nsf recovered. C:\Lotus\Domino> |
d. All content of the database are now rolled forward to the last committed transaction found in the last archived transaction log.
vii. Restart Lotus Domino Server
11 Backup/Restore Microsoft Exchange Server
This chapter will describe in details how to use OBM to backup your Microsoft Exchange Server 2000 / 2003 and how you can restore your Microsoft Exchange Server 2000 / 2003 from the backup files.
11.1 Requirements
i.
Microsoft Exchange Server 2000 with Services
Pack 3 and post-SP3 update rollup installed. Please refer to http://www.microsoft.com/exchange/ for more information.
or
Microsoft Exchange Server 2003.
ii. OBM must be installed onto the computer running Microsoft Exchange Server 2000 / 2003.
iii. Data from Microsoft Exchange Server will be backed up to a temporary directory before they are sent to Offsite Backup Server. Please make sure you have sufficient space on your computer to store these data when you run the backup job.
11.2 Overview
A Microsoft Exchange Server 2000/2003 stores its data in Windows Active Directory as well as in its databases. To fully backup a Microsoft Exchange Server 2000/2003, you need to backup the following components:
i. Windows System State
The Windows System State contains the information about your Windows system,
including Windows Active Directory. A Microsoft Exchange Server 2000 / 2003
stores some of its configuration, e.g. email accounts and mailbox properties,
inside Windows Active Directory. It is important that Windows Active Directory
is backup properly when backing up a Microsoft Exchange Server.
Active Directory is stored inside a Windows Server running as Windows domain
controller. If your Exchange Server is a domain controller, you can simply
backup the Windows
System State
of your Exchange Server. If your Exchange Server is running as a member server,
you will need to install another copy of OBM onto the domain controller to
backup the Windows
System State
of inside the domain controller.
For more information on Active Directory, please refer to http://www.microsoft.com/windows2000/technologies/directory/ad/default.asp
ii. Microsoft Information
Store
Exchange Server stores all emails and documents inside its databases,
which are grouped together as storage groups inside Microsoft Information
Store. It is important that Microsoft Information Store is fully backup when
backing your Exchange Server.
iii. Microsoft Site
Replication Service
Microsoft Site Replication Service is installed automatically when
exchange server site replication feature is enabled. Microsoft Site Replication
stores its runtime and configuration information inside its own database. If
you are running your Exchange Server with Site Replication Service enabled,
please make sure that you backup the site replication database as well.
iv. Microsoft Key Management
Service (Exchange 2000 only)
Similarly, if you have setup your Exchange Server with Key
Management Services enabled, please make sure that you backup the key
management database as well.
OBM will backup your Microsoft Exchange Server by taking the following steps:
v. Run all Pre-Commands of this backup set
vi. If the backup type to run is [Database Backup type],
a. Windows System State will be backed up to a temporary directory specified in its backup set
b. All exchange database(s) selected are backed up to a temporary directory specified in its backup set
vii. If the backup type to run is [Transaction Log Backup type],
a. New transaction log extents generated since last backup will be copied to the temporary directory
viii. Remove transaction log extents backed up from the Exchange Server
ix. Run all Post-Commands of this backup set
x. Upload all backup files from the temporary directory to an Offsite Backup Server
xi. Remove temporary files from the temporary directory if [Setting] -> [Temporary Directory for storing backup files] is enabled
11.3 How to backup Microsoft Exchange Server
Please follow the instructions below to backup your Microsoft Exchange Server 2000 / 2003 using OBM:
i.
Open OBM
Right click OBM icon available in the system tray and choose [Open]
ii.
From the Menu, Choose [Backup Set] -> [New]
-> [MS Exchange Backup Set]
Create a backup set
b.
From the Menu, Choose [Backup Set] -> [New]
-> [MS Exchange Backup Set]
c.
Enter a name for your backup set
d.
Select the database(s) to be backup
If this Exchange Server is also a domain controller of this Active Directory,
select the [System
State] checkbox as well. Otherwise,
please install OBM to the domain controller of this Active Directory and select
the [System State] checkbox on that computer
e. Enter a temporary directory for storing the backup files before they are sent to an Offsite Backup Server
f.
Set the backup schedule for Database Backup
g.
Set the backup schedule for Transaction Log
Backup (for Domino server only)
(Note: You can have more than one schedule in a backup set, i.e. you can
perform intra-day transaction log backup by adding more than one daily
transaction log backup schedule to your backup set)
h.
Set the encryption algorithm, encryption mode
and encrypting key for this backup set
(Hint: For maximum security, please select AES (Advanced Encryption Standard)
Algorithm, CBC (Cipher Block Chaining) mode and use an encrypting key with more
than 8 characters.)
iii. Run Backup
i. Select the backup set you want to run on the left panel and press the [Start Backup] button (►)
j.
Select the backup type (e.g. Database, Log
Files) you would like to perform
k.
Select [Off-site Backup Server] to start backing
up your files to an Offsite Backup Server and press the [OK] button
l.
You should get something similar to the screen
shot below.
11.4 How to restore Microsoft Exchange Server
Please follow the instructions below to restore Microsoft Exchange Server 2000 / 2003 from an Offsite Backup Server.
i.
Prepare the system for your Exchange Server (if
required)
Install the original version of Windows and Exchange Server (with the same
level of service pack installed as in the original system) back to your
computer
ii.
Restore Windows Active Directory (if required)
If you have re-installed Windows, please download the Windows System State
backup file, named [SystemState.bkf], from Offsite Backup Server and then use [NTBackup.exe]
to restore your Windows System State to its backup time from the backup file by
following the instructions below:
m. Run [NTBackup.exe] from [Start] -> [Run]
n. Press the [Restore Wizard] button and then press the [Next] button
o. Press the [Import] button and use the [Browse] button to select the backup file [SystemState.bkf] downloaded
p. Select the checkbox next to the description that matches your backup file
q. Press the [Next] button and then the [Finish] button
iii.
Install OBM (if required)
Please refer to the [Installation] section for information on how to install OBM
onto your computer.
iv. Startup the [Microsoft Information Store] services from Windows Services
v. Restore exchange database(s) from backup:
a. Download the database backup files to be restored from the Offsite Backup Server (or find the cached copy available in the temporary directory defined in your backup set) and save them to your hard disk (please make sure the directory structure is the same as it appears on the browser)
b. If the database to be restored exists on your computer already, please dismount it from the services using [Start] -> [Program] -> [Microsoft Exchange] -> [System Manager]
c.
Use [ExchangeRestore.exe] from the [bin]
directory under the installation directory of OBM (e.g. C:\Program Files\OBM\bin\ExchangeRestore.exe)
to restore the exchange database(s).
Simply run [ExchangeRestore.exe] to print the usage
ExchangeRestore.exe Usage: |
C:\Program Files\OBM\bin> ExchangeRestore.exe Microsoft Exchange Server 2000/2003 Backup Recovery Utility Usage: ExchangeRestore DIR=path SERVER=server TEMP=tempDir [SERVICE=service [STORAGE=st orage [DATABASE=database]]] DIR Directory containing all backup files SERVER Name of Exchange Server to be restored TEMP Temporary directory to be used during restore Please specific a path with plenty of free space SERVICE Name of Exchange Service to be restored. It must be either "Microsoft Information Store", "Microsoft Key Management Service" or "Microsoft Site Replication Service" STORAGE Name of storage group to be restored DATABASE Name of database to be restored Examples: 1. To restore an exchange server: ExchangeRestore DIR="C:\Backup" SERVER="ExchangeServer" TEMP="C:\Temp" 2. To restore the information store: ExchangeRestore DIR="C:\Backup" SERVER="ExchangeServer" TEMP="C:\Temp" SERVICE="Microsoft Information Store" 3. To restore an exchange storage group: ExchangeRestore DIR="C:\Backup" SERVER="ExchangeServer" TEMP="C:\Temp" SERVICE="Microsoft Information Store" STORAGE="StorageGroup1" 4. To restore an exchange database: ExchangeRestore DIR="C:\Backup" SERVER="ExchangeServer" TEMP="C:\Temp" SERVICE="Microsoft Information Store" STORAGE="StorageGroup1" DATABASE="Database1" where "C:\Backup" is the directory containing all backup files "ExchangeServer" is the server name of an exchange server "C:\Temp" is the temporary directory to be used "StorageGroup1" is the name of a storage group "Database1" is the name of a database |
d.
(Example 1) To restore all databases from backup
available in [F:\Backup] to an exchange server named [WIN2000SVR] using the
temporary directory [F:\Temp], you can use this command:
E:\Program Files\OBM\bin> ExchangeRestore
DIR="F:\Backup" TEMP="F:\Temp"
SERVER="WIN2000SVR"
Exchange Server Recovery Example: |
|
E:\Program Files\OBM\bin> ExchangeRestore DIR="F:\Backup" TEMP="F:\Temp" SERVER="WIN2000SVR" Microsoft Exchange Server 2000/2003 Backup Recovery Utility [Start] Exchange Server - 'WIN2000SVR' [Start] Service - 'Microsoft Information Store' [Start] Storage Group - 'First Storage Group' [Start] Database - 'Mailbox Store (WIN2000SVR)' Restoring file 'E:\Program Files\Exchsrvr\mdbdata\priv1.edb' ... Restoring file 'E:\Program Files\Exchsrvr\mdbdata\priv1.stm' ... [End] Database - 'Mailbox Store (WIN2000SVR)' [Start] Database - 'Public Folder Store (WIN2000SVR)' Restoring file 'E:\Program Files\Exchsrvr\mdbdata\pub1.edb' ... Restoring file 'E:\Program Files\Exchsrvr\mdbdata\pub1.stm' ... [End] Database - 'Public Folder Store (WIN2000SVR)' [Start] Restoring transaction log - 'First Storage Group' Restoring Log File 'F:\Temp\restore.tmp\First Storage Group\E00000B3.log' ... Restoring Log File 'F:\Temp\restore.tmp\First Storage Group\E00000B4.log' ... [End] Restoring transaction log - 'First Storage Group' [Start] Applying transaction log ... [End] Applying transaction log [End] Storage Group - 'First Storage Group' …………… [Start] Storage Group - 'SG2' [Start] Database - 'acct' Restoring file 'E:\Program Files\Exchsrvr\SG2\acct.edb' ... Restoring file 'E:\Program Files\Exchsrvr\SG2\acct.stm' ... [End] Database - 'acct' [Start] Restoring transaction log - 'SG2' Restoring Log File 'F:\Temp\restore.tmp\SG2\E0100072.log' ... Restoring Log File 'F:\Temp\restore.tmp\SG2\E0100073.log' ... [End] Restoring transaction log - 'SG2' [Start] Applying transaction log ... [End] Applying transaction log [End] Storage Group - 'SG2' [End] Exchange Server - 'WIN2000SVR' E:\Program Files\OBM\bin> |
e.
(Example 2) To restore the database named [mail]
in storage group [SG5] from backup available in [F:\Backup] to an exchange
server named [WIN2000SVR] using the temporary directory [F:\Temp], you can use
this command:
E:\Program Files\OBM\bin> ExchangeRestore
DIR="F:\Backup" TEMP="F:\Temp"
SERVER="WIN2000SVR" SERVICE="Microsoft Information Store"
STORAGE="SG5" DATABASE="mail1"
Exchange Server Recovery Example: |
|
E:\Program Files\OBM\bin> ExchangeRestore DIR="F:\Backup" TEMP="F:\Temp" SERVER="WIN2000SVR" SERVICE="Microsoft Information Store" STORAGE="SG5" DATABASE="mail" Microsoft Exchange Server 2000/2003 Backup Recovery Utility [Start] Storage Group - 'SG5' [Start] Database - 'mail' Restoring file 'E:\Program Files\Exchsrvr\SG5\mail.edb' ... Restoring file 'E:\Program Files\Exchsrvr\SG5\mail.stm' ... [End] Database - 'mail' [Start] Restoring transaction log - 'SG5' Restoring Log File 'F:\Temp\restore.tmp\SG5\E0300012.log' ... Restoring Log File 'F:\Temp\restore.tmp\SG5\E0300013.log' ... [End] Restoring transaction log - 'SG5' [Start] Applying transaction log ... [End] Applying transaction log [End] Storage Group - 'SG5' E:\Program Files\OBM\bin> |
f. Repeat the same procedure for each database to be restored to the Exchange Server.
g. You can use [Start] -> [Program] -> [Administrative Tools] -> [Event Viewer] to check if there are any errors generated from the exchange databases restoring activities.
vi. Completed
12 Backup/Restore Windows System State
This chapter will describe in details how to use OBM to backup Windows System State and how you can restore your Windows System State from backup.
12.1 Requirements
i. Microsoft Windows XP Professional / 2003
ii. OBM must be installed onto the computer containing the system state you want to backup
iii. Windows system state will be backed up to a temporary file before it is sent to OBS. Please make sure you have sufficient space on your computer to store the temporary file when you run the backup job.
12.2 Overview
OBM will backup your Microsoft Exchange Server by taking the following steps:
i. Run all Pre-Commands of this backup set
ii. Windows System State will be backed up to a temporary directory specified in its backup set
iii. Run all Post-Commands of this backup set
iv. Upload the Windows System State backup files from the temporary directory to an Offsite Backup Server
v. Remove the Windows System State temporary backup files from the temporary directory if [Setting] -> [Temporary Directory for storing backup files] is enabled
12.3 How to backupWindows System State
Please follow the instructions below to backup Windows System State using OBM:
i.
Open OBM
Right click OBM icon available in the system tray and choose [Open]
ii.
Create a backup set
From the Menu, Choose [Backup Set] -> [New] -> [System State Backup Set]
a.
From the Menu, Choose [Backup Set] -> [New]
-> [System State Backup Set]
b.
Enter a name for your backup set
c.
Use the [Change] button to configure the
[Temporary directory for storing backup files] setting and check the [Remove
temporary files after backup] if you want temporary files to be removed
automatically after backup
d. Enter a temporary directory for storing the backup files before they are sent to an Offsite Backup Server
e.
Set the backup schedule for this backup set
f.
Set the encryption algorithm, encryption mode
and encrypting key for this backup set
(Hint: For maximum security, please select AES (Advanced Encryption Standard)
Algorithm, CBC (Cipher Block Chaining) mode and use an encrypting key with more
than 8 characters.)
iii. Run Backup
a. Select the backup set you want to run on the left panel and press the [Start Backup] button (►)
b. Select [Off-site Backup Server] to start backing up your files to an Offsite Backup Server and press the [OK] button
c.
You should get something similar to the screen
shot below.
12.4 How to restoreWindows System State
Please follow the instructions below to restore Windows System State from an Offsite Backup Server.
i.
Install OBM (if required)
Please refer to the [Installation] section for information on how to install OBM
onto your computer.
ii. Restore the Windows System State Backup File (i.e. SystemState.bkf) from the backup server
iii. Use [NTBackup.exe] to restore your Windows System State to its backup time from the backup file by following the instructions below:
a. Run [NTBackup.exe] from [Start] -> [Run]
b. Press the [Restore Wizard] button and then press the [Next] button
c. Press the [Import] button and use the [Browse] button to select the backup file [SystemState.bkf] downloaded
d. Select the checkbox next to the description that matches your backup file
e. Press the [Next] button and then the [Finish] button
iv. Completed
13 Backup/Restore Individual Mailbox for Microsoft Exchange Server
Please refer to the Online Backup Suite Individual Mail for Exchange 2000 / 2003 Setup Guide for more information.
14 Backup/Restore MySQL Server
This chapter will describe in details how to use OBM to backup your MySQL server and how you can restore your MySQL server from the database backup files.
14.1 Requirements
i. OBM must be installed onto the computer running MySQL server.
ii. Data from MySQL server will be backed up to a temporary directory before they are sent to Offsite Backup Server. Please make sure you have sufficient space on your computer to store these data when you run the backup job.
iii.
There must be a MySQL account can be used to
connect from localhost.
Add two new MySQL accounts for Backup Manager
mysql> GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost'
-> IDENTIFIED
BY 'some_pass';
mysql> GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost.localdomain'
-> IDENTIFIED
BY 'some_pass';
mysql> FLUSH PRIVILEGES;
They are superuser accounts with full privileges to do anything with a password
of some_pass.
14.2 Overview
OBM will backup your MySQL server by taking the following steps:
i. Run all Pre-Commands of this backup set
ii. All database(s) (either local or external) selected are backed up to a temporary directory specified in its backup set
iii. Run all Post-Commands of this backup set
iv. Upload all backup files from the temporary directory to an Offsite Backup Server
v. Remove temporary files from the temporary directory if [Setting] -> [Temporary Directory for storing backup files] is enabled
14.3 How to backup MySQL server on Windows
Please follow the instructions below to backup your MySQL server using OBM:
i.
Open OBM
Right click OBM icon available in the system tray and choose [Open]
ii.
From the Menu, Choose [Backup Set] -> [New]
-> [MySQL Backup Set]
Create a backup set
a.
From the Menu, Choose [Backup Set] -> [New] ->
[MySQL Backup Set]
b.
Enter a name for your backup set
c. Enter the root password, the MySQL server TCP/IP port number and the path to MySQL backup utility (mysqldump)
d.
Select the database(s) to be backup
e. Enter a temporary directory for storing the backup files before they are sent to an Offsite Backup Server, e.g. C:\Backup\MySQL
f.
Set the backup schedule for Database Backup
g.
Set the encryption algorithm, encryption mode
and encrypting key for this backup set
(Hint: For maximum security, please select AES (Advanced Encryption Standard)
Algorithm, CBC (Cipher Block Chaining) mode and use an encrypting key with more
than 8 characters.)
a. Select the backup set you want to run on the left panel and press the [Start Backup] button (►)
b.
Select [Off-site Backup Server] to start backing
up your files to an Offsite Backup Server and press the [OK] button
c.
You should get something similar to the screen
shot below.
14.4 How to backup MySQL server on Linux (command line mode)
If you want to setup OBM to backup MySQL server running on Linux using command line mode, please do the followings:
i. Create a backup account on OBS
ii. Logon to the web interface of OBS using the backup account created in the previous step (doesn’t matter if it is not from the Linux server running the MySQL server to be backed up)
iii. Create a new backup set by pressing the [Backup Set] -> [Add] button
iv. Select the [Backup Set] -> [Type] -> [MySQL Database Server] radio button and press the [Update] button (which can be found at the bottom of the page)
v. Setup all [Backup Set] -> [Database Backup Setting]
| Settings | Descriptions |
| MySQL Username (e.g root) | A MySQL user account that has backup access to the databases to be backed up (e.g. root). Please refer to the [Requirements] section for details |
| MySQL Password | Password of the MySQL user account being used |
| Host | IP address / Hostname of the MySQL Server |
| MySQL Connection TCP/IP Port | TCP/IP port used to access the MySQL Server (default: 3306) |
| Path to MySQL backup utility (mysqldump) | Full path to where mysqldump can be found (e.g. /usr/bin/mysqldump) |
| Temporary Spooling Directory | A temporary directory to be used to store all MySQL database dump files before they are uploaded to the backup server |
| Enable Delete Temp. File | Whether to delete the temporary MySQL database dump files after they are uploaded to the backup server |
vi. Setup the [Backup Set] -> [Backup Source] setting
Ø Add an “MySQL” entry to the [Backup Source] if you want to backup all databases under this MySQL Server
Ø
Add two entries, “MySQL/database1” and “MySQL/database2”,
to the [Backup Source] if you want to backup both “database1” and “database2”
under this MySQL Server
(Please use “\” instead of “/” if the MySQL server to be backed up is running
on Windows instead of Linux)
vii. Setup the [Backup Set] -> [Backup Schedule] by pressing the [Add] link next the the “Backup Schedule” sub-title
viii. Install OBM onto the Linux server running MySQL server (Please refer to the [2.1 Installation of OBM] section for details. The command line mode installation instructions are available on the web interface)
ix. Completed
If you have started up the OBM backup scheduler in the previous step, selected
databases will be backed up automatically at scheduled time
14.5 How to restore MySQL server
Please follow the instructions below to restore MySQL server from an Offsite Backup Server.
i.
Download the database backup files to be
restored from the Offsite Backup Server
Please refer to the [5.3 Restoring file]
section for information on how to download backup files from Offsite Backup
Server.
ii. Restore the database named [db_name] from the database backup file [db_name.sql]:
a.
Connect to the MySQL server
(Windows) C:\> mysql
(Linux) [root@server ~]# mysql
b.
Create the database to be restored
mysql> CREATE DATABASE IF NOT EXISTS db_name
c.
Restore the database backup file back into the
MySQL server
mysql> use db_name ;
mysql> source db_name.sql ;
If db_name.sql is not located in the current directory, please specify the full
path to the db_name.sql file in the command above.
iii. Repeat the same procedure for each database to be restored to the MySQL Server.
iv. Completed
15 Email Reporting
Offsite Backup Server makes use of the email system to keep you informed with the status of your backup activities. Please make sure your contact information within the backup system is correct to receive the reports described in this chapter.
15.1 New User Report
When a new backup account is added to the backup server, a new user report will be delivered to the contact email(s) of the new account. The New User Report contains the following information:
Sample Report |
|
Key |
Description |
Login Name |
Login name |
Password |
Password |
Alias |
Alias |
Language |
Preferred Language for your backup report |
Contact |
Email Address that will be used to contact you |
Backup Quota |
Backup quota |
Backup Server |
Backup server |
15.2 Forgot Password Report
If you have forgotten your password, you can use the [Forgot Password] feature available on the web interface to have your password delivered to you through email. (Please refer to “Retrieve Forgotten Password” section in the next chapter for more information on how to retrieve your forgot password report.) The Forgot Password Report contains the following information:
Sample Report |
|
Description |
|
Login Name |
Login name |
Password |
Password |
Alias |
Alias |
Language |
Preferred Language for your backup report |
Contact |
Email Address that will be used to contact you |
15.3 Backup Job Report
For each backup job you have run, a backup job report will be sent to you by email. This report contains a summary for the backup job that was run and a full listing of all files being backed up by the backup job. The backup summary report contains the following information:
Sample Backup Summary Report |
|
Key |
Description |
Backup Time |
The time when the backup job ran |
Backup Status |
The overall status of the backup job. Normally, you should see “Backup finished successfully” in this field. If you happen to get something else, please consult the attached full report for more information. |
New Files |
Total number and size of backup files added to your backup set |
Updated Files |
Total number and size of backup files updated in your backup set |
Deleted Files |
Total number and size of backup files deleted from your backup set |
Moved Files |
Total number and size of backup files relocated in your backup set |
Login Name |
Login name |
Alias |
Alias |
Language |
Preferred Language for your backup report |
Contact |
Email Address that will be used to contact you |
Backup Source |
All files/directories that will be backed up |
Backup Data Size |
The total backup data stored in the data area |
Retention Area Size |
The total backup data stored in the retention area. Old copies of updated or deleted backup files are retained in the retention area for the number of days as specified by the retention policy of the backup set before they are removed from the system. |
Backup Quota |
Backup Quota |
Remaining Quota |
Remaining Quota |
The full backup report, which contains a full listing of all files backed up by the backup job, is attached to the backup job report email as a zip file. You need to unzip it before you can read the full report.
Sample Report |
|
Key |
Description |
Backup Set |
The name of the backup set |
Backup Job |
The name of the backup job (which is the start time of the backup job) |
Backup Status |
The overall status of the backup job. Normally, you should see “Backup finished successfully” in this field. If you happen to get something else, please consult the attached full report for more information. |
Backup Time |
The time when the backup job ran |
Backup Log |
All messages logged when running this backup job |
New Files |
Total number and size of backup files added to your backup set |
Updated Files |
Total number and size of backup files updated in your backup set |
Deleted Files |
Total number and size of backup files deleted from your backup set |
Moved Files |
Total number and size of backup files relocated in your backup set |
New File List |
Full list of all backup files added to your backup set |
Updated File List |
Full list of all backup files updated in your backup set |
Deleted File List |
Full list of all backup files deleted from your backup set |
Moved File List |
Full list of all backup files relocated in your backup set |
15.4 Setting Change Report
After you have updated your user profile or backup setting, a setting change report will be sent to you. This report allows you to track record of the changes that have been made to your backup account.
Sample Report |
|
Key |
Description |
Login Name |
Login name |
Alias |
Alias |
Language |
Preferred Language for your backup reports |
Contact |
Email Address that will be used to contact you |
Backup Quota |
Backup Quota |
Backup Source(s) |
All backup sources of the backup set |
Backup Schedule(s) |
All backup schedules of the backup set |
Filter(s) |
All backup filters of the backup set |
Retention Policy |
The retention policy of the backup set |
Transfer Size |
The transfer block size of the backup set |
Pre-Command(s) |
All Pre-Command(s) of the backup set |
Post-Command(s) |
All Post-Command(s) of the backup set |
15.5 Inactive User Reminder
You will receive an inactive user reminder in email if your account has been left inactive for the period of 7 days (or the period specified by the system administrator). This is to remain you that you have not been running backup for more 7 days. If you are a free trial user, your account will be removed from the system automatically if the system can track no records of your backup activities in the next 30 days after receiving this report.
Sample Report |
|
Key |
Description |
Login Name |
Login name |
Alias |
Alias |
Language |
Preferred Language for your backup reports |
Contact |
Email Address that will be used to contact you |
Backup Quota |
Backup Quota |
Last Login Time |
The last time you logon to the backup system |
Last Backup Time |
The last time you ran a backup job |
16 Web Features
Other than the features of OBM described in the previous chapter, the web interface of Offsite Backup Server provides you access to some additional features that are not available in OBM. This chapter describes each of these features in details.
16.1 Install OBM
Before you can use OBM, you have to download the OBM installer from the web interface of Offsite Backup Server and install OBM onto your computer. Please refer to the installation section (Chapter 2) for information on how to install OBM onto your computer.
16.2 Update User Profile
You can update your user profile by using the [Profile] panel available on the web interface. To change your profile, just make any changes to your profit on the panel shown below and press the [Update] button.
Key |
Description |
Quota |
Backup Quota |
Data Area |
Total number and size backup files stored in the data area |
Retention Area |
Total number and size of backup files stored in the retention area |
Total Upload |
Total number and size of backup files uploaded to the backup server |
Total Restore |
Total number and size of backup files restored from the backup server |
Login Name |
Login name |
Display Name |
Alias of your backup account |
Language |
Preferred Language for your backup report |
Time Zone |
Your Time zone |
Email Address that will be used to contact you |
|
16.3 Request Forgotten Password
If you have forgotten your password, you can retrieve it by simply entering your login name or your registered email address on the [Password Request] form and press the [Request] button. Your password will be sent to your registered email address automatically.
16.4 Restore/Delete/Undelete Backup Files
Using the [File Explorer], you can browse through the backup data (both current and previous versions) on OBS. You can select any current backup files to Restore or Delete. You can also select any deleted backup files (in gray) to Undelete.
16.5 Review Backup Jobs
In addition to reviewing your backup activities from the email report and from OBM, you can also review any of your backup Jobs by using the [Report] panel available on the web interface. To review a backup job, just select the required backup job from the [Backup Set] and [Backup Job] drop down list.
Key |
Description |
Job Status |
The overall status of the backup job. Normally, you should see “Backup finished successfully” in this field. If you happen to get something else, please click the [Detailed Report] images on the page. |
Backup Time |
The time when the backup job ran |
New Files |
Total number and size of backup files added to your backup set |
Updated Files |
Total number and size of backup files updated in your backup set |
Deleted Files |
Total number and size of backup files deleted from your backup set |
Moved Files |
Total number and size of backup files relocated in your backup set |
Backup Data Size |
The total backup data stored in the data area |
Retention Area Size |
The total backup data stored in the retention area. Old copies of updated or deleted backup files are retained in the retention area for the number of days as specified by the retention policy of the backup set before they are removed from the system. |
Total Upload |
Total number and size of backup files uploaded to the backup server |
Backup Quota |
Backup Quota |
Remaining Quota |
Remaining Quota |
You can open the [Full Backup Report] to review all information logged by a backup job by clicking the [Detailed Report] image on the [Report] panel.
Full Backup Report |
 |
Parameter |
Description |
Backup Set |
The name of the backup set |
Backup Job |
The name of the backup job (which is the start time of the backup job) |
Backup Status |
The overall status of the backup job. |
Backup Time |
The time when the backup job ran |
Backup Log |
All messages logged when running this backup job |
New Files |
Total number and size of backup files added to your backup set |
Updated Files |
Total number and size of backup files updated in your backup set |
Deleted Files |
Total number and size of backup files deleted from your backup set |
Moved Files |
Total number and size of backup files relocated in your backup set |
New File List |
Full list of all backup files added to your backup set |
Updated File List |
Full list of all backup files updated in your backup set |
Deleted File List |
Full list of all backup files deleted from your backup set |
Moved File List |
Full list of all backup files relocated in your backup set |
16.6 Review Storage Statistics
You can review the amount of data you have stored on the backup server and uploaded to the backup server on each day by opening the [Statistics] panel available on the web interface. To review your storage statistics for a different month, just select the month you are after by selecting from the [Month] drop down list.
Key |
Description |
Date |
The date the following statistics are collected |
Data Area |
Total number and size of backup files stored in the data area on a particular date |
Retention Area |
Total number and size of backup files stored in the retention area on a particular date |
Uploaded Size |
Total number and size of backup files uploaded to the backup server on a particular date |
Total Storage |
Total number and size of backup files stored under your backup account on a particular date |
17 Further Information
17.1 FAQs
Please see if your question has already been answered in our FAQs available on our website.
17.2 Contact Us
You can backup your data to an Offsite Backup Server by following instructions below.
i. Open OBM from the system tray
ii.
Choose [View] -> [About] from the top menu
iii.
Contact your backup service provider using the
information shown in the [About] dialog box
