How To Move Backup Exec From One Server To Another

How to move Backup Exec for Windows Servers from one system to another with the sa...
Page 1 of 18
Support Home | Supported Products A to Z
Knowledge Base X
Document ID: 319367 E-Mail this document to a colleague Search

http://support.veritas.com/docs/319367
Advanced Search Options
How to move Backup Exec for Windows Servers from one system to another with
Other Support Resources
the same or different computer names
 Support Forums
Ask an expert. Join collaborative
product discussions within our
Details: Forum community.
 Manage Cases Online
Instructions for moving Backup Exec (tm) 10d, 11d, 12.0, or 12.5 to another Submit and manage your support
cases using MySupport.
computer system of the same versions. The target systems can have the same
 Contact Technical Support
computer name or a different computer name. Find the support phone number
for your region.
The information in this TechNote applies to the following scenarios:

Was this article helpful to you?
Yes No
 Moving an installation of Backup Exec from one 32-bit system to another 32-bit
system. If any information was unclear, or the
information you were seeking was not
 Moving an installation of Backup Exec from one 64-bit system to another 64-bit provided, please let us know. Your
system. feedback will help us improve this
service.
 Moving an installation of Backup Exec from a 32-bit system to a 64-bit system.
(Enter comment here)
 Moving Backup Exec to another system where the Backup Exec Database (BEDB)
is installed on a SQL 2000, 2005, or 2008 instance.
 Moving Backup Exec to another system where the system being moved is a (Optional Email Address)
Central Administration Server (CAS).
 Moving DLO from one Backup Exec system to another Backup Exec system. Submit
NOTE: Comments entered here will

NOT receive support services. If you
need Symantec Enterprise product
Do not follow this procedure if any of the following are true: support, please click here.
 Backup Exec is clustered.

 The Backup Exec Shared Storage Option (SSO) is installed.
 The Backup Exec Server Free Option is installed.
 The computer where Backup Exec is installed and the computer where it will be
installed are running two different versions of the Windows Operating System.
 If planning to move Backup Exec to a different drive/directory on the server.
 If upgrading from one version/revision (build) of Backup Exec to another.
NOTE: If any of the above mentioned conditions are true, this procedure cannot be
performed and Backup Exec will need to be re-installed and re-configured.
NOTE: Prior to moving Backup Exec versions from one system to another the
following upgrade paths need to be followed:
 When moving from a 32-bit system to a 64-bit system it is recommended that any
Backup Exec version upgrades should be performed on the 32-bit system first
prior to following the instructions contained in this TechNote.
Instructions for moving an installation of Backup Exec
The Backup Exec move process consists of five sections:
I. Prepare the current Backup Exec installation on the source computer system.
II. Move Backup Exec data to a temporary storage location.
http://seer.entsupport.symantec.com/docs/319367.htm 6/28/2009
How to move Backup Exec for Windows Servers from one system to another with the sa... Page 2 of 18
III. Install Backup Exec on the new Backup Exec target media server.
IV. Move the Backup Exec data from the temporary storage location to the new target
Backup Exec media server.
V. Verify that the new Backup Exec installation matches the original Backup Exec
installation.
Important Note: Do not remove Backup Exec from the original computer until the
migration of data and media to the new Backup Exec media server is complete. It must be
verified that the new Backup Exec installation matches the original installation.
I. Prepare the current Backup Exec installation:
In order to move Backup Exec from one computer to another, the following preparation
must be performed on the original Backup Exec media server:
1. Backup Exec Version and Revision Number - Write down the Backup Exec version and
revision number listed on the Backup Exec Help | About Symantec Backup Exec for
Windows Servers menu.
2. Update Backup Exec Software - Install all the Backup Exec software updates (hotfixes
and service packs) available for the Backup Exec version and revision currently installed.
Software updates can be obtained from either the Backup Exec Technical Support site
( http://www.symantec.com/enterprise/support/downloads.jsp?pid=15047) or Symantec LiveUpdate.
3. Installed Backup Exec Options, License Keys, and Installation Path - Write down a list
of the installed Backup Exec options, license keys and the installation path from the
existing Backup Exec installation.
To obtain this information, follow these steps:
Open Backup Exec. Select Tools | Install Options and License Keys on this Media
Server from the Backup Exec menu. After the license keys are obtained, precede through
the install screens to obtain the install path. Once this information is obtained, the install
can be canceled.
Figure 1 - Record Backup Exec License Keys
Note: Backup Exec keeps a record of the Backup Exec license keys currently installed in
a file named BESERNUM.XML. This file is located under Documents and Settings\All
Users\Application Data\Symantec\Backup Exec. The license keys listed in this file can be
imported (see Figure 1) during the installation on the new Backup Exec media server
instead of manually entering the license keys. To use this file during the installation of the
new Backup Exec media server, save the file to location on the new Backup Exec media
server so it can be retrieved when needed.
4. Identify backup-to-disk folder locations - Write down the path of all backup-to-disk
folders. To obtain this information, follow these steps:
a. Open Backup Exec.

b. Select the Devices view.
c. Highlight Backup-to-Disk Folders, right click and select properties.
Note location of B2D folder (see figure 2)
Figure 2 - Backup to Disk folder location
II. Move Backup Exec data to a temporary location
Perform the following steps on the original Backup Exec media server:
Note: If the server in question that is being moved is a CAS server, then prior to shutting
down the services ensure that all of the Backup Exec services for each Managed Media
Server that communicates with the CAS are shut down as well.
1. Stop all Backup Exec and DLO (if installed) services - Using the Windows Services
applet; stop the following Backup Exec services: (Figure 3 and Figure 4)
 Backup Exec Agent Browser

 Backup Exec Device and Media Service
 Backup Exec DLO Administration Service (only if DLO is installed)
 Backup Exec DLO Maintenance Service (only if DLO is installed)
 Backup Exec Job Engine
 Backup Exec Remote Agent for Windows Servers
 Backup Exec Server
2. Stop the Backup Exec SQL Server service (a separate DLO Instance will also exist with
10d)
 SQL Server (BKUPEXEC) - This is a SQL Express instance. Stop this instance if it
is the instance that the Backup Exec (BEDB) and DLO (BE_DLO) databases are
using.
 SQL Server (MSSQLSERVER) - This is SQL Server instance (local or remote).
This is a default SQL instance. This can be a SQL 2000, SQL 2005, or SQL 2008
instance. Stop this instance if it is the instance that the Backup Exec (BEDB) and
DLO (BE_DLO) databases are using.
 SQL Server (SQL2005ONE) - This is a SQL Server named instance (local or

remote). This can be a SQL 2000, SQL 2005, or SQL 2008 instance. Stop this
instance if it is the instance that the Backup Exec (BEDB) and DLO (BE_DLO)
databases are using.
Figure 3 - Backup Exec and DLO Services
Figure 4 - SQL Service where Backup Exec and DLO databases are installed
6. Copy Files - Using Windows Explorer, copy the following Backup Exec directories
(files) to a temporary location keeping the directories separate:
 C:\Program Files\Symantec\Backup Exec\Data
IMPORTANT NOTE - Do NOT copy the msgq*.*.dat files over to the temporary location
(see Figure 5)
Figure 5 - BE\CASO message queue files
 C:\Program Files\Symantec\Backup Exec\Catalogs
NOTE: If this is a CAS server, make sure to copy over the Catalog folders for the
Managed Media Servers as well. These should all be listed under the Catalogs folder.
 C:\Program Files\Symantec\Backup Exec\IDR (if present)

 C:\Program Files\Symantec\Backup Exec\Reports\Saved
 Backup-to-Disk folders as mentioned in section I - step #4 above (if created)
Note: The only files that must be copied over are the B2D*.*.bak files. These are the
actual media (see Figure 6)
Figure 6 - Backup to Disk Media
Important Note: At this point, if the source computer name is the same as the target
computer name then turn off the source (32bit computer) and turn on the target (64bit
computer). The domain/workgroup information should also match.
III. Installing Backup Exec on the new Backup Exec media server
Perform the following steps on the new Backup Exec media server:
1. Install Backup Exec - Install the same version and revision of Backup Exec that is
installed on the original Backup Exec media server. If moving to a 64-bit system, use the
64bit Backup Exec installation CD instead of the 32bit installation CD.
NOTE: When prompted for Backup Exec license keys, enter the Backup Exec license
keys from the original Backup Exec media server. If using the Backup Exec license keys
file BESERNUM.XML to enter the license keys, select the Import button (see Figure 7)
and point to the location of the saved license key file.
Figure 7 - Import License Keys from Source System
NOTE: When prompted for the installation path, use the same path as the original
Backup Exec media server. For example, if the path C:\Program Files\Symantec\Backup
Exec\ was used in previous installation, then use the same path.
NOTE: The SQL install path can be changed. If the Backup Exec (BEDB) and DLO
(BE_DLO) databases were installed to a SQL Express instance, the databases can be
moved to another non SQL Express instance. The database files can be moved to any
SQL 2000, 2005 or 2008 instance as long as the database files are being moved to the
same or newer version of SQL (i.e. SQL 2008 files cannot be moved to a SQL 2005
instance and SQL Server files cannot be moved to a SQL Express instance).
2. Reboot - Restart the computer (do not open Backup Exec after rebooting).
3. Install Updates - Install all the Backup Exec software updates (hotfixes and service
packs) available for the Backup Exec version and revision currently installed. Software
updates can be obtained from either the Backup Exec Technical Support site
(http://www.symantec.com/enterprise/support/downloads.jsp?pid=15047) or Symantec LiveUpdate.
4. Reboot - Restart the computer (do not open Backup Exec after rebooting).
IV. Move Backup Exec data from the temporary location to the new Backup Exec
media server
1. Stop all Backup Exec services - Stop all Backup Exec services (a list of Backup Exec
services can be found earlier in this TechNote Section II - Step #1).
2. Stop the SQL Service (a list of Backup Exec services can be found earlier in this
TechNote, Section II - Step #2).
3. Copy Files - Copy the Backup Exec files from the temporary directories, overwriting the
data, catalogs, and Intelligent Disaster Recovery (IDR) folders on the new system.
4. On the new or target system, create a folder where the new Backup to Disk folders will
reside. Copy the saved off .bkf file(s) from the temporary location into this folder.
NOTE: Perform Step 5 only if you are moving the installation to a system with a
DIFFERENT computer name. If the installation is being moved to a system with the SAME
computer name, skip this step and go to the next step, step 6. Step 5 is required because
the new database will have the name of the old database and will have to be changed
before the Backup Exec services can start.
5. Rename the DataPartition name for the Backup Exec Database that was copied.
Refer to the steps mentioned below:
a. Start the SQL Server (BKUPEXEC) service or SQL Service where Backup Exec is
installed.
b. Open a command prompt and type Sqlcmd -E -S servername\BKUPEXEC
c. If successfully connected to the server, the following prompt appears: 1> This indicates
a connection to the Backup Exec instance using Sqlcmd (see Figure 8).
Figure 8 - Make a Connection to the SQL Instance
· Run the following query from either Sqlcmd or from the SQL Management tools:
Use bedb
<Press enter>
Type go
<Press enter>
SELECT partitionname FROM datapartition
<Press enter>
Type go
<Press enter>
After pressing ENTER the original server name is listed. Running this query will yield the
current database partition name that the database has (which is the old one)
Change this name from the original server name to the new Backup Exec server name by
typing the command below. This will update the database with the partition name of the
new server.
UPDATE DataPartition SET PartitionName='<this server name>' WHERE PartitionID

=0
<Press enter>
Type go
<Press enter>
· Run the select statement again and verify that the name was changed to the new server
name:
SELECT PartitionName FROM DataPartition

<Press enter>
Type go
<Press enter>
Figure 9 shows what the process looks like...
Figure 9 - Query Display for Changing Computer Name in the Database
· Type quit to exit Sqlcmd
6. Start all Backup Exec services - Start all the Backup Exec services which were stopped
in Step 1.
V. Verify that the new Backup Exec installation matches the original Backup Exec
installation
1. Start Backup Exec - Start the Backup Exec application and verify that the Backup Exec
data was correctly moved.
· Verify that the Jobs, Selection Lists, Policies, Alerts, and Job History are correct
2. In Backup Exec go to Devices Tab; the old server name with off-line devices should be
listed under the source server name (see Figure 10).
How to move Backup Exec for Windows Servers from one system to another with the s... Page 10 of 18
Figure 10 - Off line devices from the Old System
Delete the old server (source) entry and its devices by right clicking on the device and
selecting Delete.
3. Clean out media not being used - If there is media from devices that are no longer in
use, clean this up from the new Backup Media Server as well (see Figure 11). From the
Media Tab, move all of the offline media that will no longer be used over to the retired
media set and delete it.
Figure 11 - Media from Source that is no Longer being used
4. Create a new Backup to Disk folder under the current (target) server's Backup to Disk
devices and recreate catalogs.
a. Create a new folder for the B2D media and configuration files.
b. Copy the B2D media from the temporary location into the folder just created
c. Create the B2D folder and point to the path of the new folder (see Figure 12)
d. Run an inventory job on the B2D media
e. Run a Catalog job on the B2D media
NOTE: If the Target server is a CAS, run the inventory and Catalog job on the Media after
the CASO Configuration changes (listed in the CASO Configuration section below) have
been performed.
NOTE: If a catalog job is run on Media on the CAS or MMS(s) the media is now
considered imported and may be subject to be overwritten. Check the media overwrite
protection that is currently configured to ensure that media that is needed will not be
overwritten.
Figure 12 - Backup to Disk create on Target System
5. Review the Backup Selections Lists. If the old server was being backed up locally, it will
need to be changed to backup remotely under remote selections. Viewing the selections
in text mode may be necessary to remove the old server local selection. Additionally, the
new server will need to be added to the selection list if it needs to be backed up (see
figure 13).
Figure 13 - Update Source System Local Selections on Target System
6. On each of the remote machines that are backed up (if any), vxmon.exe needs to be
run to point publishing to the new box. Open "C:\Program files\Symantec\Backup exec for
windows\RAWS\Vxmon.exe", click on the Publishing tab, add the new server. If the old
server is listed, remove it.
Configuration Steps for Target Server if it is a Central Administration Server (CAS)...
If the new Media server is a Central Administration Server (CAS) and it has attached
Managed Media Servers than the following additional steps should be performed...
The MMS(s) should be in a no-communication state since its services were shut down
earlier (see Figure 14)
Figure 14 - CASO Managed Media Server in Unavailable State
1. Delete the current msgq files on the Managed Media Server (see Figure 15). These
message queue files are associated with the old CAS and will get regenerated on the
Managed Media Server during service startup. Navigate to the data folder where these
files are stored. The default location is C:\Program Files\Symantec\Backup Exec\Data
Figure 15 - CASO Managed Media Server files
2. Change the Managed Media Setting to communicate with the new CAS
If the new Central Administration Server (CAS) was just moved from one computer system
to another but the name has remained the same, then just start up the services on the
Managed Media Server and it should show as On-Line and Manageable from the Central
Administration Server.
However, if the new Central Administration Server was moved from a system that has a
different name, then some registry keys on the Managed Media Server will have to be
changed in order for the Managed Media Server to communicate with the new Central
Administration Server.
The keys that need to be changed are as follows...
Warning: Incorrect use of the Windows registry editor may prevent the operating system
from functioning properly. Great care should be taken when making changes to a
Windows registry. Registry modifications should only be carried-out by persons
experienced in the use of the registry editor application. It is recommended that a
complete backup of the registry and workstation be made prior to making any registry
changes.
HKLM\Software\Symantec\Backup Exec for Windows\ADAMM\
Change the Database Server Name key to the new server name
If the instance name has changed as well, then the Database Instance Name key will also
have to be changed to the new instance name. If the source system used a named SQL
instance but the target now uses a default instance, then the instance name should be
removed from the instance name key.
Note: If the Managed Media Server is not sharing the database on the Central
Administration Server than changing this ADAMM key should not be necessary. It should
point to the local server, which is the Managed Media Server.
HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Server\
Change the DjmPrimaryServer key to reflect the name of the new Central Administration
Server. Changing this key ensures that communication through the Message Queue can
now take place between the new CAS and the MMS.
3. Start up all of the Backup Services on the Managed Media Server(s). Once these
services are started the MMS(s) should now display as available from the CAS.
4. Catalogs for the CASO environment:
 For the Central Administration Server and for the B2D folder and media that is on
the CAS, run an Inventory and Catalog job to retain the catalogs for the CAS
media.
 If there are MMS(s) that have their catalogs Centralized and the catalogs were
copied, as noted in Step #6 of Section II above, then they should show up under
Restore selections on the CAS. If the catalogs do not show up, then, from the
CAS, run an Inventory Job and Catalog job on the device\media for that
particular MMS.
 If there are MMS(s) that have their catalogs Distributed and the catalogs were
copied, as noted in Step #6 of Section II above, then they should show up under
Restore selections on the CAS. If the catalogs do not show up, then, from the
MMS, run an Inventory Job and Catalog job on the device\media for that
particular MMS.
NOTE: If a catalog job is run on Media on the CAS or MMS(s) the media is now
considered imported and may be subject to be overwritten. Check the media overwrite
protection that is currently configured to ensure that media that is needed will not be
overwritten.
Configuration Steps for Target Server if it is a DLO (Desktop and Laptop Option)
Server...
The DLO database has no configuration requirements on the database name so no

changes will have to be made to the database in order to use DLO on the target server.
However, there are some configuration changes that need to be made to the DLO Server
and Desk Top agent in order to use DLO with the new target server.
Figure 16 - Create new DLO Storage Location
1. If the old Storage Location was on the source server and the source server will be put
of commission, it may be necessary to create a new storage location (see figure 16) on
the target server or on another server that can hold the user DLO Data.
NOTE: If the source server is not being put out of commission, the old Storage location
still can used if the user wishes to do so.
Figure 17 - Move user data from old Storage Location to new Storage Location
2. If it has been determined that the DLO user data needs to be transferred to a new
Storage Location, then the user can transfer the data by opening the DLO Console,
selecting the user, and then select to Move the Network User Data Folder (see Figure
17).
Figure 18 - Change Automated User Assignments to new Storage Location
3. If the Storage Location has been changed, it will be necessary to change the
Automated User Assignments. Select the name from the Automated User Assignments
(See Figure 18), and change the Storage Location to the new Storage Location.
Figure 19 - SQL Server Configuration for Named Pipes
4. Once the DLO database has been moved to another SQL instance it is necessary that
you check the SQL Server protocol Named Pipes and ensure that this protocol is enabled
(See Figure 19). DLO uses this protocol for its Desk Top Agent. If this protocol is not
enabled, the Desk Top Agent will not be able to communicate to the DLO Server.
NOTE: Once the Named Pipes protocol is enabled, it will be necessary to restart the SQL
Service for the change to take place.
5. Once the SQL Protocols are configured, the DLO agents on the Desk Tops and
Laptops should find the new Server and connect to it. Check the options on the Agents to
ensure that the Storage Locations (if moved) are correct (See Figure 20). If they are not
correct, it may be necessary to uninstall and then reinstall the agent so that they properly
pick up the correct configurations from the server.
NOTE: if the Agents are uninstalled, be sure to select NO to the option to uninstall the
user data from the Desk Top\Laptop. If this is not done, the user will only be able to
retrieve data from the server.
Figure 20 - DLO Desktop Agent Properly Communicating with DLO Server
Related Documents:
281824: Backup Exec Database (BEDB) : Procedure to move the .MDF and .LDF files to
non-default locations
286729: How to migrate the Backup Exec Database (BEDB) Data from earlier versions
[9.x and 10.x] of Backup Exec to Backup Exec to 11d or above using Bemig.exe.
287063: How to migrate from BEWS 9.x / 10.x Data and catalogs to a fresh installation of
11d or above on a different server with a different server name using BEMIG.EXE
287939: How to obtain the installation source download and license keys for Backup Exec
for Windows Servers and components.
305456: Symantec Backup Exec (tm) 12.5 for Windows Servers General Information
Products Applied: Last Updated: February 12 2009 06:21 PM

Backup Exec for Windows Servers 10d GMT
(10.1), 11d (11.0), 12.0, 12.5 Expires on: 02-09-2019
Subscribe to receive critical updates
about this document
Application: How To, Installation
Languages:
English (US)
Operating Systems:
Windows Server 2003
Enterprise Server
Windows Server 2008

Enterprise (x86-32bit), Standard (x86-32bit)
Symantec World Headquarters:

20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support:
http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or
http://ftp.entsupport.symantec.com
THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY
OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC
SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT
APPLY.

How To Move Backup Exec From One Server To Another

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

How To Move Backup Exec From One Server To Another

Încărcat de

Drepturi de autor:

Formate disponibile

How to move Backup Exec for Windows Servers from one system to another with the sa...

Support Home | Supported Products A to Z

Document ID: 319367 E-Mail this document to a colleague Search

The information in this TechNote applies to the following scenarios:

NOTE: Comments entered here will

 Backup Exec is clustered.

Instructions for moving an installation of Backup Exec

The Backup Exec move process consists of five sections:

II. Move Backup Exec data to a temporary storage location.

I. Prepare the current Backup Exec installation:

To obtain this information, follow these steps:

Figure 1 - Record Backup Exec License Keys

a. Open Backup Exec.

Note location of B2D folder (see figure 2)

Figure 2 - Backup to Disk folder location

II. Move Backup Exec data to a temporary location

 Backup Exec Agent Browser

 SQL Server (SQL2005ONE) - This is a SQL Server named instance (local or

Figure 3 - Backup Exec and DLO Services

 C:\Program Files\Symantec\Backup Exec\Data

Figure 5 - BE\CASO message queue files

 C:\Program Files\Symantec\Backup Exec\Catalogs

 C:\Program Files\Symantec\Backup Exec\IDR (if present)

Figure 6 - Backup to Disk Media

Figure 7 - Import License Keys from Source System

Refer to the steps mentioned below:

Figure 8 - Make a Connection to the SQL Instance

UPDATE DataPartition SET PartitionName='<this server name>' WHERE PartitionID

SELECT PartitionName FROM DataPartition

Figure 9 shows what the process looks like...

Figure 9 - Query Display for Changing Computer Name in the Database

· Type quit to exit Sqlcmd

Figure 10 - Off line devices from the Old System

Figure 11 - Media from Source that is no Longer being used

Figure 12 - Backup to Disk create on Target System

Figure 13 - Update Source System Local Selections on Target System

Configuration Steps for Target Server if it is a Central Administration Server (CAS)...

Figure 14 - CASO Managed Media Server in Unavailable State

Figure 15 - CASO Managed Media Server files

The keys that need to be changed are as follows...

HKLM\Software\Symantec\Backup Exec for Windows\ADAMM\

HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Server\

4. Catalogs for the CASO environment:

The DLO database has no configuration requirements on the database name so no

Figure 16 - Create new DLO Storage Location

Figure 18 - Change Automated User Assignments to new Storage Location

Figure 19 - SQL Server Configuration for Named Pipes

retrieve data from the server.

Figure 20 - DLO Desktop Agent Properly Communicating with DLO Server

Products Applied: Last Updated: February 12 2009 06:21 PM

Application: How To, Installation

Windows Server 2008

Symantec World Headquarters:

S-ar putea să vă placă și