Migrating SBS Starter Pack to new hardware

I have searched the entire forum and knowledgebase for an answer to this
and haven't found one. I have a very small business client (2 users)
that is currently using SBS 6.5 Starter Pack. I have convinced them to
upgrade to better hardware from a clone tower. My question is can I
migrate the starter pack server without affecting the activation that is
already in place? Or will I have to reactivate after the move? If
reactivation is necessary, can that even still be done since the starter
pack has been discontinued?

This is NOT a Microsoft Server so you should be
able to just take the Hard disk out of the old box and put in the new box
(done this zillions of times!)
BUT, to play it safe...
Put in a 2nd hard disk and make a dos partition
format with /s and xcopy the dos partition
Load NSSMU and Mirror the sys and data and any other
When complete - You have a COPY to put into the new server !
<[email protected]> wrote in message
news:RlYZg.16355$[email protected]..
>I have searched the entire forum and knowledgebase for an answer to this
> and haven't found one. I have a very small business client (2 users)
> that is currently using SBS 6.5 Starter Pack. I have convinced them to
> upgrade to better hardware from a clone tower. My question is can I
> migrate the starter pack server without affecting the activation that is
> already in place? Or will I have to reactivate after the move? If
> reactivation is necessary, can that even still be done since the starter
> pack has been discontinued?

Similar Messages

How to migrate os x server to new hardware

I am looking for the quickest easiest way to migrate OS X server to new hardware that I purchased. I currently have both DHCP and DNS services actively running. I have VPN services running when needed.

Reid,
Thanks for your response. I actually migrated everything that I needed over about an hour after I posted. For DNS I simply copied all of the zone files in /Library/Server/named and restarted the DNS service. DHCP took a little more investigation as I had to find where the configuration file was being stored. I eventually found the configuration in /etc/bootpd.plist file that contains all of the DHCP info and copied it over to the new system. Once I restarted all services everything was working fine.
I took this approach rather than a direct cloning as I wanted a clean install of everything on the target system. Also, as I mentioned before, I didn't have many services running that I needed to have running on the new configuration. The VPN services that I was running had only one test user so recreating it from scratch was a non-issue.
Regards,
André

Migrating OS X install to new hardware?

I've just gotten a Mac Pro to replace my Mac Mini. Is there a supported method of moving an OS X installation onto new hardware rather then having to reinstall and reconfigure all my software and settings?

When you turn on your Macbook Pro it will ask you if you own another Mac and it will start the migration either over the network or via FW as the MB Pro still has this port.
If you are already set up then go to your HD>applications>utilities and then migration assistant

Migration of BW system to New Hardware and Upgrade to NW04s

Hi,
I'm not sure this is the forum for this post but here goes...
We have recently started a project to migrate our current BW3.5 system to new hardware (HP Superdome) and then upgrade to NetWeaver 2004s.
To do this, we've taken a copy of our current Dev 3.5 system and moved it to the new hardware and will unicode and upgrade to NW04s. Once this is complete, we plan to install NEW instances of QA and Prod with NW04s. We will TRANSPORT all our configuration and reload all the providers in QA and Prod. This will be a MASSIVE task as we have hundreds of infoproviders. Additionally, I'm concerned we will not pick objects currently in 3.5 Prod system (e.g. custom queries/workbooks, infopkgs, process chains, variables, etc.) but not in current 3.5 Dev system.
My question is this - can we instead take copies of the current QA and Prod (3.5) systems and migrate, unicode, and upgrade in the new Superdome hardware. Per Basis, this is NOT possible due to the size of the current systems - approx 2.5 Terabytes. But maybe half of the database is consumed by old PSA's, unused providers, etc. If we were to clean up our current system and do a database reorg to reduce the database size, is it possible to do a system copy (Dev to Dev, QA to QA, Prod to Prod) --> any help/insight is much appreciated.
Thanks,
Senthil

I had this experience in my previous project and i wanna share a with you. we have migrated our total bw landscape from alfa servers to HP superdome servers.
we took all the copies of all the boxes( dev,QA,PRO) and migrate to superdome and upgrade to NW04. but in your case you are not taking copies QA and PRODUCTION. This is not realistic scenario. you got to move all the objects and configuration from dev to respective systems and load the data in the production.
so you have to take all the copies of all the boxes and migrate to superdome and upgrage to NE04, is the right way of doing.

Migrate (N)AMP server to new hardware

Hi,
I have been looking for documentation on how to move an AMP configuration to
new hardware (practically same OS-install, NW65SP7).
Is there any info around 'cause I wasn't able to find any. And before I
start dumping MySQL databases and Apache virtual hosts, I thought i'd ask
here.
On the origin server, webcontent and SQL db are placed on different volumes
than SYS. I looked at MigrationWizard as well, but my replacement server is
already in the same tree (new name).
Any info, links or directions, appreciated.
Regards,
Marcel

BakxM,
> I have been looking for documentation on how to move an AMP configuration to
> new hardware (practically same OS-install, NW65SP7).
I'd transfer the database and adjust Apache and PHP settings manually.
- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)
Discover the new Novell forums at http://forums.novell.com
Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Move / Migrate A Managment Server to New Hardware

I want to move / migrate my existing SCOM 2012 SP1 Management Servers to new hardware running Server 2012 R2. We're going to leave the DBs where they are for now.
It looks like I could just 'add' a new Management Server and then remove the older ones. Is it that simple?
Orange County District Attorney

HI,
1. Install a new Management server in your management group.
2, Move all SCOM agents from old MS to new management server.
3. Move if there is any dependencyes on old MS to new MS (Like Exchange corelation engine serivce on MS for Exchange 2010 MP / Proxying for web application monitoring/ SMTP relay for SCOM email notification etc)
4. properly uninstall Old MS to avoid issues (if not objects will left in resource pools)
Kind Regards,
~Bommi

Migrate Sun Cluster (+RACdisks to new hardware running Sun Cluster ( + RAC)

Hello,
We have old hardware (v490s) running Sun Cluster 3.2 + Oracle RAC 10.2.0.4.0 connected to SAN. We need to move to T4. Oracle advised against including new hardware into existing cluster, so we are planning on building a new cluster with T4's, same software (Solaris 10, Sun Cluster 3.2, RAC 10.2.0.4.0).
When ready, we plan to shut down existing cluster, zone new cluster to existing disks and bring up everything on new hardware (simply stated).
Will it work?
Any gotchas - like need to clear disk ids or Sun Cluster panicking? RAC panicking? Any reference docs out there?
Thanks
user12961096

Do we absolutely need that in our new setup or could we forgo that additional layer? Would Sun Cluster give us anything that the OS + RAC doesn't give us?Yes, Oracle Solaris Cluster does make things a lot easier. It looks after your device space and gives you consistent DID devices for CRS/RAC. It gives you the choice to use sQFS, raw metasets, or ASM. It has clprivnet which is a lot easier and performs better than an IPMP solution. The node failure detection time is <= 10 seconds which is quicker than CRS on it's own and it uses SCSI fencing instead of a STONITH approach. Finally, you have all the off the shelf agents that Solaris Cluster offers.
However, if you are only doing RAC and you just want ASM and you don't need the last few seconds of failure detection that OSC gives you and you think STONITH is good enough for your fencing purposes, then CRS on its own is perfect. There are many, many deployments both with and without OSC, it's not a simple yes/no answer.
Having worked for the Solaris Cluster group, I'm still slightly bias to including it rather than going without. Others have the alternate view! :-)
Hope that helps,
Tim
---

SBS 2008 - SBS Console and AD errors after migration to new hardware

Hi there,
I'm trying to work out how to fix some of the errors and random behaviour I'm experiencing with the SBS 2008 console and AD related matters since I had to quickly migrate SBS 2008 to new hardware using Windows Server Backup after a failure of the old server.
In my haste to get our email and ftp services back up and running (which use Smartermail and Filezilla respectively instead of Exchange etc) I overlooked the fact that the new server had 3 NICs installed and not one and so restored SBS 2008 and loaded up new
drivers for those and other hardware that had changed (such as the graphics card and mobo. I have since removed the two additional NICs by disabling them on the mobo).
Whilst I got the server up and running again with email and ftp services, even though I currently don't use any AD related stuff directly I have since noted that if I try to say view a list of users that I had previously created via the SBS console, more often
than not it will show no users, and then randomly it will (but when you do see them you can't edit or delete them. I'm aware that I have probably broken a number of golden rules in doing this 'migration' but having a metaphorical gun to my head meant that
I rushed things out of desperation.
Common errors that I experience generally will say things like 'Current security connect is not associated with an Active Directory domain or forest' if I try to list users, or DC not found for domain "xyz.local' etc. I have been searching the net and
trying out some things to fix this but I'm like a dog chasing its tail as I'm not so clued up on server related issues as I am with workstation problems, so if anyone could at least point me in the right direction I would be very grateful. If you require any
info from me (eg diag logs etc) I will be happy to provide them!
Regards,
Dave

Hi Dave,
Based on current situation, please run SBS BPA and fix all that it can find, then monitor the result. For more details, please refer to the following KB.
Windows SBS Best Practices Analyzer (BPA)
Meanwhile, please refer to the following article and repair SBS console.
Repair the Windows SBS 2008 Console
By the way, I noticed that you had got some error messages (such as: “DC not found for domain” and so on). Would you please let me know complete error messages? In addition, when you migrate SBS 2008 to the new hardware, had you done any preparation for
that Source Server? For more details, please refer to the following article.
Migrate Windows Small Business Server 2008 to New Hardware
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Migrating 10g disco to new linux server(new hardware)

We are planing to migrate 10g discoverer applications to new hardware with same OS,
source os: OEL4.7 and target OS: 4.7(with new hardware), how to make it...?
EBS : 11.5.10.2 with 11g R2 DB .
any references notes or links appreciate it.

any references notes or links appreciate it.10 Cloning Application Server Middle-Tier Instances
http://docs.oracle.com/cd/B14099_19/core.1012/b13995/cloning.htm
Thanks,
Hussein

Migrate SBS 2008 to new hardware

We have an SBS 2008 installation and are testing a disaster recovery solution by re-installing in Migration Mode.
Step 5 in the migration document from Microsoft discusses;
Demote and remove the Source Server from the network
We'd like to fully test this and get the backup box up and running before signing it off as a working solution.
Our concern is that, even if we isolate the test machine on a difference subnet from our production LAN, there is some kind of licensing consequence for our running box - via some kind of de-activation signal sent over the net, perhaps - should we continue
through the final steps.
Can anyone confirm or deny whether any kind of de-activation occurs? Perhaps paranoia, but thought best to check since we really can't have our live systems shut down.

Hi,
Before going further, would you please provide more detailed information about your concern? It’s difficult to understand your needs for me with the information you mentioned. For details about
how to migrate SBS 2008 to new hardware, please refer to the following articles.
Migrate Windows Small Business Server 2008 to New Hardware
http://technet.microsoft.com/en-us/library/cc664208(v=ws.10).aspx
Moving SBS to new hardware
http://msmvps.com/blogs/kwsupport/archive/2005/06/18/53958.aspx
Hope it helps.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Best Practice to migrate existing Message/Central Instance to new hardware?

I've done some searching for this, but it all seems to be fairly old (I found one decent thread from 2008, but it just seemed outdated). I would like to get some updated info & suggestions on a process to follow for this task.
Here is some info about the current config:
I have an existing SAP ERP 6.0 EHP5 system. SID "XYZ"
Everything is currently running on Windows x64.
ABAP only config.
It is currently setup as a distributed system.
DB server is SQL, which is running on its own hardware as a dedicated DB server. I don't need to touch this.
Uses logon groups to distribute the load between 3 App servers.
One of the App Servers is setup as the Message/CI server. This is what I am wanting to move to VM hardware.
The other two App Servers are setup just as Dialog Instances. VM already. I don't need to touch these.
What I am wanting to do:
I am wanting to migrate the existing Message/CI server to VM hardware to get the current Message/CI system off of very old hardware.
I need to keep the system with the same name & IP.
I do not need/want to mess with the DB server at all.
Need to minimize downtime as much as possible.
I do NOT want to go to an HA environment. That is a different project for the future.
Suggestions? I would like to hear what some of you have done.
Minimize downtime? I have a short maintenance window of a few hours coming up in the next few months, and would like to do this changeover during that downtime.
How do I handle setting this up on the new hardware using the same name & IP, especially with the existing system still running.
What I think I need to do: (Some of these may be out of order, which is why I'm asking for suggestions)
Setup new Windows VM server, named differently than current Message/CI server (Done already).
Run SAPINST to run Global Host Preparation on the new Windows VM server.
Run SAPINST to setup ASCS Instance on the new Windows VM server.
Skip the Database Instance installation, since I already have one running.
Run SAPINST to setup Central Instance on the new Windows VM server.
Copy all of the appropriate profile parameters that were on the old server.
Start SAP and make sure everything is running and working correctly.
Copy all job, spool files, etc. from the old server.
What needs to be done in between those steps for the server rename & IP changes?
Which of these steps can I do in advance of my maintenance downtime window, without it affecting the currently running system?
I have a test environment that I am going to test this with. I'm just trying to get a jump start on my instructions, so that I can hopefully do this quickly and easily. I'm very comfortable doing the installs. Just needing some guidance on how to handle this case.
I'm open to suggestions, and any links you can send my way that show some more recent success at doing this. Everything I keep finding talks about doing the migration for the DB. I am not migrating my DB. It is staying where it is. I'm just wanting to migrate my Message/Central Instance to a VM, without affecting the users, and hopefully them never noticing the changes.
Thanks!

If you're using VMWare, there is a tool provided to virtualize existing systems. Basically it makes a copy of the old system (while it is down) and recreates it as a VM with the same name, IP, etc. I haven't double-checked to see if this process is 'officially' supported by SAP, and I don't know the technical details about how it's done or how long it will take (VMWare is managed by the Network Operations group in my team, so as the SAP sysadmin I'm basically a customer of theirs). However, we have virtualized a few smaller systems that needed to get off failing hardware in a hurry and it worked very well, so I would expect it would for an SAP dialog instance as well. As you're not copying a database, just the app server, it probably would fit within your maintenance window.
If this route works for you, then there is no need to actually install the SAP system on the VM instance... you just copy the old server as-is, then make any adjustments required due to no longer needing old drivers, etc, plus potentially having different memory parameters.

SQL cluster 2008 R2 migration to new Hardware in VM

Hi,
We have a task to migrate existing Physical SQL Cluster DB to new Hardware but in VM. (cannot argue with the client)
hence our plan is to install new Cluster in VM with same Windows and SQL version i.e Win 2K8 R2 ENT w/SP and SQL 2K8
R2 STD w/SP and use SQL mirroring option for the DB to migrate on the new Server (keeping the downtime to as low as possible and advantage of bringing the old server online in case of any issues..)
Below points are for a single instance, couple of DB to migrate:
Keep the physical production server running
In-Parallel build New SQL Cluster in VM (keep same version windows/sql)
Keep Same drive letter for Quorum, MSDTC, DATA, LOG & Backup
Keep the same Instance Name, SQL Network Name can be different (will be changed to old network name once the PROD is shutdown)
Check all logins windows and SQL to be same on both the clusters
Copy all the jobs, SSIS packages etc.. .create the location folder as per current server on the VM SQL Cluster
Perform full backup of old cluster company-db databases or use the existing latest backup (full, differential, transaction)
Restore databases in the new cluster with no recovery so additional log file or differential backup can be restored
Create SQL Mirroring for the Database and select the principal server (old cluster) and the mirror server (new VM cluster)
Choose mirroring without witness ( no auto failover as we don’t need the old server later)
Start the mirroring – (hopefully everything synchronized and working)
During the downtime –
Stop the application/ client connection – if possible
Failover the DB through Mirroring option
Once the mirrored server becomes Principal and data is accessible – stop the mirroring
Now the new VM SQL Cluster DB is online
Shutdown the old cluster company-db (Node1 & Node2)
Come back to VM SQL Cluster and change the Network name to the old server network name (so that client connections are not affected)
Check if the DNS entries are updated with correct name and IP address
Delete DNS entries for old company-db on DNS Servers if not deleted, delete the old server SQL network name in computer object
Stop SQL Resources on the new VM SQL Cluster (take it offline all the resources)
Bring online the SQL Resource and make sure the SQL resources are online and new network name is reachable
Wait till you see machine name company-db in active directly (AD) and DNS server will have entry for company-db
Verify connectivity for company-db from outside.
If things are not going as per the plan then shut down the new VM cluster
Revert back the DNS settings
Power up the Old SQL Server
The DB will show “restoring mode” – use command to make it online “RESTORE DATABASE (dbname) WITH RECOVERY”
Check the DB
Start using the OLD server again
Troubleshoot the failed scenario ;)
Need to know if the above steps are okay, and any consideration once the new VM SQL Cluster is online.
Kindly let me know if there anything else to transfer apart from the logins, jobs, folder location etc.. !!
Many Thanks

Hello,
Well if you don’t change the instance name (name = ABC) then its OK.
Try the following resources about transferring SQL Server logins:
http://support.microsoft.com/kb/918992/en-us
http://www.mssqltips.com/sqlservertip/2081/transfer-sql-server-jobs-task-and-transfer-sql-server-logins-task-in-ssis/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Migrate user data from SLES10sp3 OES2sp3 to new hardware

Hi,
I am trying to migrate user data on a nss volume from a SLES10sp3 and
OES2sp3 server to new hardware already setup with SLES10sp3 and OES2sp3.
Authentication and configuration of the data selection is sorted. After
starting the data transfer I get a message saying the migration failed.
Below is the error from the log file:
FATAL -FILESYSTEM:migfiles:Fatal: Cannot migrate source path
/media/nss/DATA/Users/JohnG/: nbackup: Failed to open dataset
/media/nss/DATA/Users/JohnG/ for backup
WARNING - FILESYSTEM:migfiles:Warning: Going to next data set
ERROR - FILESYSTEM:migfiles:Error: nbackup: (libtsafs.so 6.50.0 291) An
invalid path was used.
Regards
John

Hi kjhurni,
I have not setup to get update from the Novell channel as I have an issue
with connecting to the update channel but I will deal with that later.
I tried to run a miggui to migrate my data to the new server with SLES10sp3
and OES2sp3. Below is the entire log file, I have highlighted the error at
the end of the log file. (Names and addresses have been changed to protect
the innocent)
Regards
John
2012-01-12 11:15:17,394 INFO - Migration
Framework:getSourceServerConfigDetails():Finding Source Server eDirectory
Tree Name using command: ndsstat -h SERVER1
2012-01-12 11:15:17,474 INFO - MigUtil:ResolvIP:Resolving IP address from
hostname SERVER1
2012-01-12 11:15:17,539 INFO - Migration Framework:Getting Source Server
certificate:Using 10.1.3.1 to retrieve Source Server certificate
2012-01-12 11:15:17,539 INFO - Migration Framework:Getting Source Server
certificate:executing command: LC_ALL=en_US.UTF-8 /usr/bin/ruby
/opt/novell/migration/sbin/getServerCert.rb --server-ip "10.1.3.1"
--ldap-port 636 --file /opt/novell/migration/plugin/conf/SourceServerCert
2012-01-12 11:15:20,795 INFO - Migration Framework:Getting Source tree
certificate:using getSSCert command
2012-01-12 11:15:20,801 INFO - Migration Framework:Getting Source tree
certificate:Using 10.1.3.1 to retrieve Source tree certificate
2012-01-12 11:15:20,801 INFO - Migration Framework:Getting Source tree
certificate:executing command: LC_ALL=en_US.UTF-8
/opt/novell/oes-install/util/getSSCert -a "10.1.3.1" -t "TREE_NAME" -u
"admin.b"
2012-01-12 11:15:21,087 INFO - Migration
Framework:MigController:getSourceServerTreeCert(): :Copied certificate to
/opt/novell/migration/plugin/conf/SourceCert.der
2012-01-12 11:15:21,127 INFO - Migration
Framework:importSourceTreeCert():Using 10.1.3.1 to import Source Tree
certificate
2012-01-12 11:15:21,127 INFO - Migration Framework:Importing Source Tree
certificate:Importing certificate to Java keystore
(/opt/novell/migration/plugin/conf/novellStore.keystore)
2012-01-12 11:15:21,911 INFO - Migration
Framework:importSourceTreeCert()eleting existing source tree certificate
using command: /usr/bin/keytool -delete -noprompt -alias 10.1.3.1 -keystore
/opt/novell/migration/plugin/conf/novellStore.keystore
2012-01-12 11:15:21,911 INFO - Migration Framework:importSourceTreeCert():
command: /usr/bin/keytool -import -alias 10.1.3.1 -file
/opt/novell/migration/plugin/conf/SourceCert.der -noprompt -keystore
/opt/novell/migration/plugin/conf/novellStore.keystore
2012-01-12 11:15:22,577 INFO - Migration Framework:SourceServer
Authentication:Attempting to Connect to Source with the parameters
2012-01-12 11:15:22,587 INFO - Migration Framework:SourceServer
Authentication:Authenticating using LDAP(secure)
2012-01-12 11:15:23,263 INFO - Migration Framework:SourceServer
Authentication:Authenticating to the Source Server returned true
2012-01-12 11:15:23,270 INFO - Migration Framework:SourceServer
Authenticationetecting the source server version
2012-01-12 11:15:23,315 INFO - Migration Framework:Authentication:Using SMS
to validate root password for server 10.1.3.1
2012-01-12 11:15:23,315 INFO - MigUtils:Authentication:Executing
command:/opt/novell/sms/bin/nbackup -U root -R 10.1.3.1 -cf
/var/opt/novell/migration/NewProj5/migsrc.sidf /etc/SuSE-release
2012-01-12 11:15:37,876 INFO - Migration
Framework:getTargetServerConfigDetails():Finding Target Server eDirectoty
Tree Name using command: ndsstat -h 10.1.3.2
2012-01-12 11:15:37,930 INFO - Migration Framework:Getting Target Server
certificate:Using 10.1.3.2 to retrieve Target Server certificate
2012-01-12 11:15:37,930 INFO - Migration Framework:Getting Target Server
certificate:executing command: LC_ALL=en_US.UTF-8 /usr/bin/ruby
/opt/novell/migration/sbin/getServerCert.rb --server-ip "10.1.3.2"
--ldap-port 636 --file /opt/novell/migration/plugin/conf/TargetServerCert
2012-01-12 11:15:40,115 INFO - Migration
Framework:getTargetTreeCertificate():Attempting to connect to Target with
the parameters
2012-01-12 11:15:40,116 INFO - Migration
Framework:getTargetTreeCertificate():Copy certificate to
/opt/novell/migration/plugin/conf/TargetCert.der for CLI usage
2012-01-12 11:15:40,122 INFO - Migration Framework:Importing Target Tree
certificate:Attempting to connect to Target with the parameters
2012-01-12 11:15:40,122 INFO - Migration Framework:Importing Target Tree
certificate:Importing certificate to Java keystore
(/opt/novell/migration/plugin/conf/novellStore.keystore)
2012-01-12 11:15:40,122 INFO - Migration
Framework:importTargetTreeCert():keytool delete command to be executed to
delete target tree certificate
2012-01-12 11:15:40,122 INFO - Migration
Framework:importTargetTreeCert():Executing command : /usr/bin/keytool
-delete -noprompt -alias 10.1.3.2 -keystore
/opt/novell/migration/plugin/conf/novellStore.keystore
2012-01-12 11:15:40,788 INFO - Migration
Framework:importTargetTreeCert():Using keytool to delete existing
alias10.1.3.2
2012-01-12 11:15:40,789 INFO - Migration
Framework:importTargetTreeCert():keytool command to be executed to store
target tree certificate
2012-01-12 11:15:41,486 INFO - Migration
Framework:importTargetTreeCert():Return Value true
2012-01-12 11:15:41,486 INFO - Migration Framework:TargetServer
Authentication:Attempting to connect to Target with the parameters
2012-01-12 11:15:41,487 INFO - Migration Framework:TargetServer
Authentication:Authenticating to the Target Server(secure)
2012-01-12 11:15:41,550 INFO - Migration Framework:Authentication:Using SMS
to validate root password for server 10.1.3.2
2012-01-12 11:15:41,550 INFO - MigUtils:Authentication:Executing
command:/opt/novell/sms/bin/nbackup -U root -l /etc/SuSE-release
2012-01-12 11:16:35,254 INFO - FILESYSTEM:migfiles:Validating data from
source path(s) to target path(s) using migfiles
2012-01-12 11:16:35,254 INFO - FILESYSTEM:migfiles:Executing command:
/opt/novell/migration/sbin/migfiles --source-server 10.1.3.1 --verbose
--source-path "@/var/opt/novell/migration/NewProj5/fs/sourcepaths.in"
--destination-full-path
"@/var/opt/novell/migration/NewProj5/fs/targetpaths.in" --precheck
--progress --progress-interval 1 --source-ldap-port 636
--delete-file-on-restore-error
2012-01-12 11:16:35,618 INFO - FILESYSTEM:migfiles:Enter the username (e.g
cn=admin,o=mycompany)
2012-01-12 11:16:35,618 INFO - FILESYSTEM:migfiles:for the server 10.1.3.1:
Enter cn=admin,o=b password:
2012-01-12 11:16:35,618 INFO - FILESYSTEM:migfiles:Enter the username (e.g
root)
2012-01-12 11:16:35,619 INFO - FILESYSTEM:migfiles:for the server 10.1.3.2:
Enter root password:
2012-01-12 11:16:39,225 INFO - FILESYSTEM:migfiles:Information: Validation
for migfiles is done successfully
2012-01-12 11:16:39,230 INFO - FILESYSTEM:migfiles:
2012-01-12 11:16:39,230 INFO - FILESYSTEM:migfiles:Successfully validated
data
2012-01-12 11:16:39,245 INFO -
FILESYSTEM:Information:****************Migrating files and/or
trustees****************
2012-01-12 11:16:39,246 INFO - FILESYSTEM:migfiles:Migrating data from
source path(s) to target path(s) using migfiles
2012-01-12 11:16:39,246 INFO - FILESYSTEM:migfiles:Executing command:
/opt/novell/migration/sbin/migfiles --source-server 10.1.3.1 --verbose
--source-path "@/var/opt/novell/migration/NewProj5/fs/sourcepaths.in"
--destination-full-path
"@/var/opt/novell/migration/NewProj5/fs/targetpaths.in" --session-file
"/var/opt/novell/migration/NewProj5/fs/migfiles.session" --progress
--progress-interval 1 --source-ldap-port 636
--delete-file-on-restore-error
2012-01-12 11:16:39,534 INFO - FILESYSTEM:migfiles:Enter the username (e.g
cn=admin,o=mycompany)
2012-01-12 11:16:39,534 INFO - FILESYSTEM:migfiles:for the server 10.1.3.1:
Enter cn=admin,o=b password:
2012-01-12 11:16:39,534 INFO - FILESYSTEM:migfiles:Enter the username (e.g
root)
2012-01-12 11:16:39,534 INFO - FILESYSTEM:migfiles:for the server 10.1.3.2:
Enter root password:
2012-01-12 11:16:45,078 INFO - FILESYSTEM:migfiles:Information: nbackup:
precomputing for displaying progress...
2012-01-12 11:16:45,157 FATAL - FILESYSTEM:migfiles:Fatal: Cannot migrate
source path /media/nss/DATA/Users/JohnG/: nbackup: Failed to open dataset
/media/nss/DATA/Users/JohnG/ for backup
2012-01-12 11:16:45,167 WARN - FILESYSTEM:migfiles:Warning: Going to next
data set
2012-01-12 11:16:45,168 ERROR - FILESYSTEM:migfiles:Error: nbackup:
(libtsafs.so 6.50.0 291) An invalid path was used.
2012-01-12 11:16:45,242 FATAL - FILESYSTEM:migfiles:Fatal: nbackup command
failed to complete
2012-01-12 11:16:45,246 INFO - FILESYSTEM:migfiles:
2012-01-12 11:16:45,247 ERROR - FILESYSTEM:migfiles:migfiles command
failed!
2012-01-12 11:16:45,247 INFO -
FILESYSTEM:Information:****************End******** ********

Upgrading the new hardware, data migration

Dear Forum;
I need to upgrade the hardware for the IPCC solution we have without changing the versions, the following servers need to have the new hardware:
1) Call Managers (Publisher + Subscribers).
2) RGRs
3) PGs
4) HDS + ICM + Admin + Web view
As versions will not be changed for all the above, what is the best method to migrate the configurations and scripts in a safe fast way? Can someone advise?
Regards
Bilal

1) In the DC storey, I did not understand the meaning of: promote them to ADs? By the way: Do u mean to install the Domain Controller and AD first and then to promote them to ADs?
You did not say if you wanted a tech refresh on the Domain Controllers or not. In fact you did not say if ICM has a dedicated domain or is using the corporate domain.
If you do have to add new hardware for the Domain Controllers, then I gave you the method:
1. Add the servers to the existing domain.
2. Promote them to DCs (using dcpromo) - now your domain has 4 DCs.
3. Move the FSMO roles from the machine they are now on (probably DC2) to DC4
4. Move the GC (global catalog) from the machine it is now on (probably DC1) to DC2. Wait a few days for replication of AD and DNS to settle down.
5. Use dcpromo to demote DC1 and DC2 to become ordinary servers.
6. Change these machines to be out of the domain (workgroup)
7. Remove servers. Clean up DNS.
2) About the AWs, why to "Add to domain, make into AWs, not HDS"? I mean, why not the HDS? Also what do u mean by promote them to be HDS?
You should always make your AW/HDS in two phases. First, run setup from the media and make a real-time distributor - primary, no secondary. Install the SR. Make sure the real-time feed to your CCs is working. Set it to manual. Now run ICMSetup.exe from the ICM bin and "promote" to an HDS - check the HDS box. It will complain that you have not finished the install because you have not created the HDS DB with ICMDBA. Ignore this but don't start the Distributor. Use SQL backup/restore to build the HDS. Now start the Distributor and check that Replication is all working - increase the trace on rpl to 0xfff so you can see the msgs - check on the logger side with similar trace mask.
3) About the Central Controller: there are the Logger DB, will this DB has some missing as there is not method to recover this for the last moments (before moving live)?
If you do it correctly using SQL backup/restore you will not lose data. If you have to keep the contact center running on side B while you do side A, things will be a bit more complicated - read the Upgrade Guide to see how logger synchronization solves this.
As I said, if you can have a 12 hour maintenance window for the migration of the CC and bring the whole contact center down to migrate, life will be easier.
As I see the most critical part in this upgrade is not loosing the configuration and it is not the need to build every thing manual (as the moving for registry is easy, and the restore for the database is easy) but the system to become up and running is also easy, but the hard part is the avoid loosing the data. Correct? All the need to have the training is to be around how to avoid loosing the data? But no worry that service will be up and running by having the restore for the database and moving the registry.
I don't follow that paragraph. Backup and restore and import of the registry solves this. Nothing will be lost. Read the Upgrade Guide again.
Do you have a lab system you can practice the migration on? Without this, the risk is huge. You must get a step by step plan written down, and trial this on the lab system.
Regards,
Geoff

Exchange 2003 /2010 Co-existence plus 2010 migration to new hardware

Hi,
Here is our current scenario;
Exchange 2003/2010 co-existence. This has been running perfectly for a couple of months now.
Exchange 2003 - exch1.domain.lan
Exchange 2010 (SP3) - exch2.domain.lan (local domain name) / mail.domain.com.au (external domain name)
ActiveSync, autodiscover, legacy etc are all working. Our UAC certificate from GoDaddy has all the required names for exch2 - except it doesn't have the local domain name as they don't allow certificates with that anymore. I've configured all the required
services to be the external domain name and am running split DNS.
The first Exchange 2010 server I installed was lower spec'd and only has about 25 users on it. I now need to install a second Exchange 2010 server (exch3.domain.local), which is properly spec'd and will host the entire company. I won't be running DAG as
I need to repurpose the first Exchange 2010 server once it's removed.
My high level questions are;
1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
OR does it matter which way I do it?
I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange
organisation.
1) Do I configure CAS to be externally facing right from the get go or do I do that later?
2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
Any guidance on the above is helpful.
Thanks.
Steve

Hi Steve I will try my best to answer each of these
My high level questions are;
1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
OR does it matter which way I do it?
doesn't matter at all. Since you want to move to a new hardware you can setup a new Server CASH/HUB/Mailbox. Once installed start migrating the mailboxes from Exchange 2003 to this mailbox server. This way you will not have to redo the migration from 2010
to new 2010 sever -- like you mentioned in 1) it will save you a lot of time and repeating procedure.
I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange organisation.
1) Do I configure CAS to be externally facing right from the get go or do I do that later?
Keep your existing 2010 internet facing for now. Once you finished migrating the mailboxes then you will need to do it.
2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
Mail will not flow to 2ndry server unless you add that server as a source serve in the transport.
In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
You can always export the certificate and then import it to the newly installed Exchange 2010.
OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
You will only need to setup the CAS array if you are going to use both the server which can be done later.
Hope that help
Where Technology Meets Talent

Migrating SBS Starter Pack to new hardware

Similar Messages

Maybe you are looking for