Zone MIgration from V440 with Solaris 10 (118833-20) to M4000

Has anyone successfully migrated zones from V440 running Solaris 10 (118833-20) onto M4000 running Solaris 10 08/07?
Thanks!

If you make sure the M4000 is running Solaris 10 10/08 then the zone should be upgraded the moment you attach the zone on the M4000.

Similar Messages

Migration from PC with MA did not end. Had to shut down MacBookPro. After restart no new user was created. Can't find the transferred data (35 GB). Would like to delete it.

Migration from PC with MA did not end. Had to shut down MacBookPro. After restart no new user was created. Can't find the transferred data (35 GB). Would like to delete it.

iTunes is required to initially activate the phone. Back when the iPhone 3G was sold, you would take it out of the box and see a "Connect to iTunes" screen. She HAD to connect to a computer in order to begin using the phone. Does she remember what computer this was?

Retain SAMBA permissions while migrating from linux to solaris 10 x86

Hello,
We are migrating a system from Redhat to Solaris 10 x86 and this has brought up a question on how we can restore our SAMBA files and retain our permissions that are associated by the users name rather then their numeric ID(UID/GID). So far my research hasnt produced anything that gives a solid answer to how we do this and is it even possible.
The problem is that Windows user and group accounts are mapped locally per host by default. That mapping is defined as the accounts are referenced, so unless there is a way to guarantee the order of accounts being referenced, the mappings from Windows SIDs to Unix UIDs will be different between old and new.
If the data restoration option we choose for the new server is naive and restores only by UID and GID, the permissions in the ACLs will not map to the correct Windows accounts. We either must find a restoration option which restores permissions by name rather than ID or we must create a script which can automate pushing the ACLs into the restored filesystem correctly by name.
Initially I thought ufsdump could handle this but we are on ext3 filesystem going to vxfs. I have read a little on star but havent heard about it before. Has anyone used star for backup/restore for the purpose of retaining ACL ownership/permissions? It seems like its an old utility, maybe not used much anymore. Does anyone have a utility they have used for this purpose?
Your help is much appreciated!!
LR

The problem is that Windows user and group accounts are mapped locally per host by default. That mapping is defined as the accounts are referenced, so unless there is a way to guarantee the order of accounts being referenced, the mappings from Windows SIDs to Unix UIDs will be different between old and new.Is there anyway that you can sanitize and post a small snippet of what's going on with the mapping files? I think I can follow this but I'm a bit confused by the username/UID thing since usually if a username is defined in /etc/passwd than the files will display the username. If a username is not defined in /etc/passwd then the ls command will revert to just showing the numbers which I take it is what you don't want to happen.
If you could also sanitize and post even one of the acl's that might help clear up that portion of the problem as well.
alan

Migrated from MBP with moutain lion to new macbook pro retina display and now I have lion os

After migrating from a time machine backup and logging in (had problems with that too and had to restart user password) the os version is 10.7.4 when it should be 10.8.2
Went to the app store and I have to pay again to get the upgrade.. Do i have to pay again???
Thanks!

Hi again, Juan.
OK this is just a guess but I believe that when you set up your rMBP from your old MBP you used TM restore not Migration Assistant. What happened is that you installed your old system OS10.7.4 and all files.
Using Migration Assistant (MA) would not have overwritten your OS.
See this taken from Finder Help....
Recover your entire system
If you use Time Machine to back up your computer, you can recover your system’s contents if your system or startup disk is damaged.
Important: Only use your Time Machine backup to restore your system to the computer that is the source of the backup. If you want to use your backup to transfer your information to a new computer, use Migration Assistant.
Transfer your info from a computer or disk
If you’re restoring your system because of a problem with your startup disk, repair or replace the disk before following these instructions.
Make sure your Time Machine backup disk is connected and turned on. If your backup disk is on a network, make sure your computer is on the same network.
Choose Apple menu > Restart. Once your Mac restarts (and the gray screen appears), hold down the Command (⌘) and R keys.
Select “Restore from a Time Machine Backup,” and then click Continue.
Depending on your type of backup disk, do one of the following:
If you use an external disk, select it and click Continue.
If you use a Time Capsule, choose your AirPort network from the AirPort menu on the right side of the menu bar, and then select your Time Capsule and click “Connect to Remote Disk.”
If you use a network disk, select it and click “Connect to Remote Disk.”
If necessary, enter the name and password you use to connect to your backup disk, and then click Connect.
Select the date and time of the backup you want to restore, and then follow the onscreen instructions.
After you restore your system from a Time Machine backup, Time Machine may perform a full backup at the next scheduled backup time. This is normal. Time Machine resumes incremental backups after the full backup is completed.
I suggest you make an appoint at the Genius Bar at a local Apple Store and they will help you restore your computer. Make sure you take in your old MBP and your Time Machine back up disk as well.
Do not use instructions above for a TM restore now, because it will only reinstall Lion 10.7.4 not ML 10.8.X.
You need to reinstall ML first and then I think all of your problems will go away.
So did I guess right? Did you launch TM and restore or did you launch Migration Assistant to move files?
Hope this helps, if you cannot get to the Apple Store, I can try to walk you through reinstalling ML, but first we need to download a copy of ML.

Migrating from G4 with multiple internal drives

i'm trying to migrate from my old G4 to my new Mac Pro. I have only 1 monitor so I can only 'see' the new computer. I have connected both machines and restart holding down the 'T' key. Since I can't 'see' the old machine to tell when the firewire logo disappears i hold down the key till I see the start up disk appear on the desktop. Up till this point everything seems fine but none of the other drives appear and migration assistant will not let me go to the next step. Any ideas what's happening?

I ended up doing most of the transfer manually (via external USB drive).
That way, I made sure everything was copied, and I had a backup at the same time
Alternately, you should be able to network the machines via ethernet cable, and move files that way.

Unable to update zones after migrating from SRU13 to Solaris 11 Release

When attempting to migrate to 11-release, I ran into a bizarre problem when I began to migrate my zones to the new format. It would appear that there is an erroneous and hardcoded pkg publisher somewhere in the toolchain. During a zoneadm attach -u:
[Saturday, November 12, 2011 05:40:38 AM UTC] Sanity Check: Passed. Looks like a Solaris system.
[Saturday, November 12, 2011 05:40:38 AM UTC] Zone BE root dataset: data/zones/rooter/rpool/ROOT/zbe-8
[Saturday, November 12, 2011 05:40:39 AM UTC] Cache: Using /var/pkg/publisher.
[Saturday, November 12, 2011 05:40:39 AM UTC] Updating image format
pkg: 1/2 catalogs successfully updated:
http protocol error: code: 400 reason: Bad Request
URL: 'http://localhost:10000/za100/catalog/1/catalog.attrs'.
[Saturday, November 12, 2011 05:40:51 AM UTC] ERROR: Updating image format failed
Note that I do not have any such publisher configured:
# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online http://pkg.oracle.com/solaris/release/
Any thoughts?

In the global zone, run:
# svcs svc:/application/pkg/system-repository:default svc:/application/pkg/zones-proxyd:defaultIf one of those services is not online, you will see this problem. If the service is in maintenance:
# svcadm clear <service>If it is disabled:
# svcadm enable <service>

Migrating from HP to Solaris

Hi All,
Could any of you please point me to some document/whitepaper for migrating an Oracle 9i database currently on a HP server to an Oracle 9i database on Sun?
Regards,
Sriraman

Hi,
Thank you for your reply.
What I am looking for is a kind of general outline of the procedure to do the migration and also any major issues that I will have to look out for.
All the info that I have been given till date is that the database is about 250GB in size, with about 3000 stored procedures and about 500 packages.
The project is not thru yet, but I want to be prepared. Also, from the research I have done so far, will using Transportable Tablespaces be of use, or should I do a full DB export?
One last question, would I have to recompile the procedures and packages?
All guidance is appreciated.
Thanking you once again,
Regards,
Sriraman

Help Migrating from eMac with 10.4 to Mac Mini with 10.5.8

Hi All,
I'm stumped. My friend has an old eMac with 10.4 on it, and when I upgraded my machine from a Mac Mini, I decided to donate it to her. I thought I'd be able to use Migration Assistant, but it apparently needs at least 10.5 on both machines. I tried to upgrade her eMac to 10.5, but it's so old and clunky, it just freezes when you try (it's only got 256MB of RAM).
Any ideas? Since there's no time machine on 10.4, that's not an option - but she does have an external hard-drive that I could use.
Thanks all -

Erase and install the Mac Mini and then when prompted at restart tell it to import the data from the eMac - it should just work. It is always better to erase and install if you get a second hand machine anyway both for security purposes (for the old user) and also to ensure that none of the stuff left behind by the previous user will interfere with your usage of your new Mac

Migration from Access with SQL Developer 1.2.2998 Does not migrate Relation

Hi,
I've almost successfully migrated an Access database to Oracle with SQL Developer with Quick Migration Option. Everything went all right, except for the tables relationships... they were not migrated. Have I forgot to do something?
Thanks in advance.
PS: Using SQL Developer 1.2.0.29.98, Oracle 10g XE, MS Access 2000 file.

Hi All,
This is a bug which crept in just prior to release. It has been found, and a fix has been commited to our source tree. The fix will be available in our next patch release. (1.2.1).
Regards,
Dermot.

Migrating from HDD with bad sectors to SSD

My mid-2010 Macbook pro running OSX 10.6.8 (Snow Leopard) has been extremely slow. It passes Disk Utility's Verify Disk step but when I brought it to the Apple store, it failed the diagnostic tests they ran with their ethernet cable. There were bad sectors detected and they figured this was what was slowing me down.
So I decided to switch to an SSD but I have questions about how to restore my files. I tried cloning my HD to an external drive with both Disk Utility's restore and using asr on the command line. In both cases I get an error at the very end
"Checksum failed. Could not restore - cannot allocate memory"
I'm still able to boot from the external drive that was created though. I was also (recently) able to create a Time Machine backup with no error messages. So my question is
1. What is the best way to restore my files?
a) Using the (possibly corrupt) HD clone
b) reinstalling from the OSX Installation DVD and restoring with Time Machine
c) Something else like Carbon Copy Clone

montburns,
Only by doing file-by-file examination against a known good copy, or relying upon a batch process which generates a “I couldn’t copy these” file list (and in the latter case, presuming that the list is due solely to bad sectors).
It means i) — either to put your internal drive in an external enclosure, or to attach it to a SATA-to-USB or SATA-to-FireWire adapter, then connecting it to the appropriate external port, and then using Startup Manager to select it as the boot drive.
If you have appropriate software, you could, but I’m not familiar with what’s available on OS X — I hope that other people can offer a list of apps from which you could choose.
Between ddrescue and rsync, I’d choose ddrescue for copying from a potentially faulty disk. To my knowledge, rsync will just copy whatever it finds; but if it creates a list of “I couldn’t copy these” files, then that could be a way to find out where bad sectors might be having an effect.

Migrating to 2013 from 2007 with Outlook Anywhere disabled

Hello
I'm in the middle of a migration from 2007 With Outlook anywhere disabled.
After I installed 2013 I added the external url to both inside and outside url's on CliantAccess, o-anywhere url and Virtual catalogs.
When I configured the External Access domain on the 2013 it also added this on the external url's on the 2007 server. On the 2007 server i manuelly changed the external url's to the Legacy name which is mail.domain.com. The New server is webmail.domain.com
both internally and externally. The servers real name is xxmail.domain.internal
After this, when I configure an Outlook Client With a user on the old server With autodiscover it configures it With Outlook anywhere, not mapi, but With the external name of the New server, webmail.domain.com under http Proxy settings. When I then
moved this user to the New server it stopped working in Outlook.
Is the best approch to enable Outlook anywhere on the 2007 server before migrating the users or can I og from mapi/rpc to rpc over http in 2013 without Outlook problems?
Regards

Hi,
Firstly, I’d like to explain, all users in Exchange 2013 use Outlook Anywhere. The information of Exchange proxy settings tab is automatically updated by Autodiscover.
I recommend you the following troubleshooting:
1. Check the Autodiscover configuration on both Exchange 2007 and Exchange 2013 servers:
Get-clientaccessserver |fl autodiscoverserviceinternaluri
2. Check if there is any DNS entry about the legacy name points to Exchange 2007 IP address.
3. Check if you can logon OWA with both Exchange 2007 and Exchange 2013 server.
Best regards,
Angela Shi
TechNet Community Support

Migrating from SunFire v1280 to T4 servers

Hi all,
I will be soon tasked with the migration from a SunFire v1280 server to a new T4, not sure if it will be T4-1 or T4-2, server. The v1280 is running Solaris 10 with a number of applications that the client wants to preserve and keep running, they include Oracle DB, WebLogic and a few others.
Is there a way that I can clone the OS on the v1280 and install it on the T4? flash archive maybe or some other method? I've been looking into the Oracle documentation but I cant find what I need, maybe I will find the info I need here.
The problem is that there is a bunch of software components at work here and the client wants minimal downtime. Both machines are Sparc servers, yes I know they are almost a decade apart, but thats where the Solaris binary comparability kicks in, right?
If you need more info let me know :)
p.s: I posted something similar a few months ago, not sure if I did it on this forum, if I did sorry for the double post.

Hi,
I already did some migrations from systems running solaris 10 to a new system.
The best way that i have found is the following.
1) On the new system make sure you have the latest solaris 10 or even solaris 11.
2) On the machine that you want to migrate stop all processes and create a flar from the system.
If there is storage that is connected to that sytem make sure you do an exclude off that filesystem so that you can import those luns in the new system.
3) on the new system create a zone with the same hostid and ip address.
4) import the flar into the zone.
If you want i can give you a conrete example that i have tested already.
Migrated a E2900 + V440 towards an M5000.
The external storage had a zfs fileystem
Regards
Filip

DNS EventID 4015 on PDC since Domain Migration from 2003 R2 = 2012

Hi,
following problem here:
2 Domain Controllers with AD Integrated DNS Zone, migrated from 2003 R2 to 2012. One Single Root Forest.
The Primary Domain Controller shows every 2, 3 or 4 hours the DNS EventID 4015. No further error is available: (which is may emty) "".
Only on the Details pane you can find this Information:
======================================
- System
- Provider
   [ Name] Microsoft-Windows-DNS-Server-Service
   [ Guid] {71A551F5-C893-4849-886B-B5EC8502641E}
   [ EventSourceName] DNS
- EventID 4015
   [ Qualifiers] 49152
   Version 0
   Level 2
   Task 0
   Opcode 0
   Keywords 0x80000000000000
- TimeCreated
   [ SystemTime] 2013-12-10T19:48:17.000000000Z
   EventRecordID 2456
   Correlation
- Execution
   [ ProcessID] 0
   [ ThreadID] 0
======================================
The Migration was made by the following steps:
Bring Up the first 2012 MigrationDC as 3rd DC to the Domain.
Move the FSMO Roles to the 2012 MigrationDC
DHCP Data migrated with Server Migration Tools, IAS Data with iasmigrader.exe exported
DCPromo DC1 (2003 R2) and Format C:
Install a fresh 2012 Installation on old DC1 an rename it again with the original Name DC1
DHCP Data migrated with Server Migration Tools, IAS Data with iasmigrader.exe exported
DCPromo DC2 (2003 R2) and Format C:
Install a fresh 2012 Installation on old DC2 an rename it again with the original Name DC2
Move Back the FSMO Roles to DC1
DCPromo the first 2012 MigrationDC
Metadata Cleanup for MigrationDC
DCDIAG /V /C Shows no Errors, all works good, the funny Thing is, that only DC1 Shows the DNS EventId 4015 in production evironment. The only exception is, that if you reboot DC1 (i.e. for maintenance, upates etc) than the error appears on DC2. Exactly on
that time, if DC1 is temporarily not availble and DC2 is under "load". If DC1 is back again, the Event 4015 Ends on DC2 and Comes back to DC1!!!
I backupped and restored DC1 and DC2 in an lab Environment, the funny Thing is that the EventID 4015 doesnt appear in lab Environment. The difference between prod and lab is: prod is bare metal with 2 teamed nics, lab is hyper-v vm's with 2 virtual teamed
nics. same IP's etc... DNS NIC Settings are the same.
It Looks like you can only produce the error in the production lab if you have the DC under "load".
This Event was discussed here more than one time in the Forum, but the issues doesnt match 100% to my Problem. No RODC is available in my prod Environment, the EventID 4015 has no further Errors "" in the Eventlog like in other Posts.
Ace Fekays blog :" Using ADSI Edit to resolve conflicting or duplicate AD Integrated Zones" was helpful for metadata cleanup, but it could not fix the EventId 4015 away. Because we had no Problems with disappearing zones...
Maybe Enabling NTDS Verbose Logging in the registry is helpful, but i dont know for what i have to Keep an eye out?
The thread
http://social.technet.microsoft.com/Forums/windowsserver/en-US/c0d3adb4-67d2-470c-97fc-a0a364b1f854/dns-server-error-event-id-4015-after-replacing-domain-controller-with-another-using-same-name?forum=winserverDS seems to match to my Problem, but also no
soulution available...
Any ideas what causes this "ugly" Event without noticable consequences?

Zonenname
Typ
Speicher
Eigens
chaf
ten
Cache
AD-Domain
_msdcs.our-domain-name.com
Primary
AD-Forest
Secure
0.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
1.1.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
1.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
1.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
10.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
10.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
128.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
130.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
16.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
16.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
16.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
19.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
19.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
19.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
196.169.193.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
2.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
20.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
20.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
200.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
21.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
21.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
21.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
239.24.217.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.26.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
255.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
27.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
27.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
27.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
29.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
29.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.26.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
31.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
31.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
32.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
33.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
35.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
37.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
39.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
41.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
43.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
45.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
47.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
49.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.19.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
50.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
51.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
52.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
53.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
54.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
55.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
60.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
62.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
64.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
70.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
80.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
88.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
our-domain-name.com
Primary
AD-Domain
Secure
Agi
ng
TrustAnchors
Primary
AD-Forest

Migration from physical server to zone (solaris 10)

Hello all,
I found an old thread about the subject Migrate Solaris 10 Physical Server to Solaris 10 Zone but i have a question.
Using the flarcreare command, will add to the flar archive all the zpools i have in the server?. Right now we have 14 zpools.
If i execute this command "flarcreate -n "Migration File" > -S -R / -x /flash /flash/Migration_File-`date '+%m-%d-%y'`.flar" will take all the zpools?
This is for migrating from a E25k Server to a M9k Server
The E25k (Physical Server) have this release "Solaris 10 10/08 s10s_u6wos_07b SPARC" and the zone server (M9k) have this release "Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC" this could be an issue?
Thanks for any help.
Edited by: 875571 on Dec 9, 2011 7:38 AM

flarcreate will only include data from the root pool (typically called rpool). The odds are that this is what you actually want.
Presumably, on a 25k you would have one pool for storing the OS and perhaps home directories, etc. This is probably from some sort of a disk tray. The other pools are likely SAN-attached and are probably quite large (terabytes, perhaps). It is quite likely that instead of creating a multi-terabyte archive, you would instead want an archive of the root pool (10's to 100's of megabytes) and would use SAN features to make the other pools visible to the M9000.
One thing that you need to do that probably isn't obvious from the documentation is that you will need to add dataset resources to the solaris10 zone's configuration to make the other zpools visible in the solaris10 zone. Assuming that these other pools are on a SAN, the zpools are no longer imported on the 25k, and the SAN is configured to allow the M9000 to access the LUNs, you will do something like the following for each zpool:
# zpool import -N -o zoned=on +poolname+
# zonecfg -z +zonename+ "add dataset; set name=+poolname+; end"In the event that you really do need to copy all of the zpools to the M9000, you can do that as well. However, I would recommend doing that using a procedure like the one described at http://docs.oracle.com/cd/E23824_01/html/821-1448/gbchx.html#gbinz. (zfs send and zfs recv can be used to send incremental streams as well. Thus, you could do the majority of the transfer ahead of time, then do an incremental transfer when you are in your cut-over window.)
If you are going the zfs send | zfs recv route and you want to consolidate the zpools into a single zpool, you can do so, then use dataset aliasing to make the zone still see the data that exists in multiple pools as though nothing changed. See http://docs.oracle.com/cd/E23824_01/html/821-1448/gayov.html#gbbst and http://docs.oracle.com/cd/E23824_01/html/821-1460/z.admin.task-11.html#z.admin.task-12.

Migrating production oracle 9.2.0.6 datawarehouse from HP to Solaris

Hi,
I am planning to move my production data warehouse(oracle 9.2.0.6) with size 600GB from Hp to Solaris.Could you please help me figure out the steps.

Check my note in this Doc on Migration of Oracle 9i database from HP Unix to RedHat Linux

Zone MIgration from V440 with Solaris 10 (118833-20) to M4000

Similar Messages

Maybe you are looking for