Mailboxes migration to new partition

Dear Folks,
We had to migrate the mailboxes from one partition to another, (partition 1 got full). We mounted another disk from SAN (600 GB) the double the size of existing partition (300 GB). How ever after the migration (mailboxes migration from old partition to new) , some how the partition size expanded, old partition was 290 GB and now after migrating the mailboxes to the newly mounted disk, partition size is 380 GB......Here is the question, How we can (OR keep the mailboxes compression) compress the mailboxes to keep the size of partition as it was in old partition (disk) ...???
We are running :
Sun Java(tm) System Messaging Server 6.2-4.03 (built Sep 22 2005)
libimta.so 6.2-4.03 (built 04:37:42, Sep 22 2005)
SunOS msgbak1 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V490
Many Thanks

Sp00ky_Geek wrote:
We had to migrate the mailboxes from one partition to another, (partition 1 got full). We mounted another disk from SAN (600 GB) the double the size of existing partition (300 GB). How ever after the migration (mailboxes migration from old partition to new) , some how the partition size expanded, old partition was 290 GB and now after migrating the mailboxes to the newly mounted disk, partition size is 380 GB......How did you move the emails from the old->new partition (single user mboxutil -r / copy/rsync the files across?).
Here is the question, How we can (OR keep the mailboxes compression) compress the mailboxes to keep the size of partition as it was in old partition (disk) ...???
If the expansion has occurred due to single-message copy being expanded by the move, you can use the relinker utility to reset the hard-links between identical messages.
The theory behind single-message copy and the relinker utility are described here:
http://docs.sun.com/app/docs/doc/819-2650/6n4u4dttt?a=view#bgaye
Sun Java(tm) System Messaging Server 6.2-4.03 (built Sep 22 2005)
libimta.so 6.2-4.03 (built 04:37:42, Sep 22 2005)
SunOS msgbak1 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V490I recommend patching to 118207-63 before using the relinker utility to fix bug #6496709 - "relinker should doublecheck"
Regards,
Shane.

Similar Messages

Migrating a new partition table with transportable tablespace

I created a partitioned table with 2 partitions (2010 and 2011) and used transportable tablespace to migrate the data over to a new envionment. My question is, if I decide to add a partition (2012) in the future, can I simply move that new partition along with the associated datafile via transportable tablespace or would I have to move all the partitions (2010, 2011, 2012).

user564785 wrote:
I created a partitioned table with 2 partitions (2010 and 2011) and used transportable tablespace to migrate the data over to a new envionment. My question is, if I decide to add a partition (2012) in the future, can I simply move that new partition along with the associated datafile via transportable tablespace or would I have to move all the partitions (2010, 2011, 2012).Yes why not.
1) create a table as CTAS from 2012 in new Tablespace on source
2) transport the tablespace
3) Add partition to existing partition table Or exchange partition
Oracle has also documented this procedure:
http://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces013.htm#i1007549

How do you migrate the bootcamp partition to new Imac

how do you migrate the bootcamp partition to new Imac

using ghost to make an image of the windows install and then restore it in the new bootcamp setting would seem the way to do it
but cant think of any free way of doing it

Can I install Snow Leopard on a new partition on a Macbook Pro (Late 2011)?

I need to get Pro Tools 9 up and running again after I migrated from PC to Mac, but I know that Pro Tools 9 doesnt work with Lion.. I dont have the money to upgrade to PT10 so my thought was to go downgrade to Snow Leopard to get it working. But I dont want to leave Lion, so my question is if I can make a new partition and install Snow Leopard on the new partition and have both OSs bootable?
The guy in the store I bought my mac from said Snow Leopard probably wouldnt play nice with the mac since its adapted to Lion but I dont trust people that get money for preaching about the constant need for "the latest". So I thought I'd ask the experts instead, so here I am! What do you guys think?

theoretically, it should work - but the guy at the Apple Store is correct....computers that ship with the latest operating system do not support being downgraded.
You might not get past the spinning beach ball & gray screen if you try to boot from the Snow Leopard install disc.
It's worth a shot though if you want to try it. Just don't try to 'downgrade' the current Lion installation back to Snow Leopard. Try instead to create a new partition specifically for Snow Leopard. Disk Utility - select the top HD (probably reads Hitachi something)...select it, click on the Partition tab. Select the top partition, and you should then be able to see the + so you can add a new partition. I would probably make it about 20GB give or take depending on how much space you think you will need - but i believe the Snow Leopard installation by itself takes up around 8-10GB.
Once this partition is created, insert your Snow Leopard installation disc, restart the computer and hold the C key down to start from the install disc. When it walks you through the steps for installation, select the newly created Snow Leopard partition. Install. Be sure to go through all the Software Updates (numerous times) after the installation is done.
You can select which startup disc you want to boot from by holding the Option button down at startup until you see the gray startup manager that shows your Lion partition, Recovery Disc partiton, and your Snow Leopard partition.
If for whatever reason this doesn't work, simply just erase the partition. It likely will not work but you should be able to just erase that newly created partition without any other problems.

ActiveSync is not working properly after migrating to new Exchange 2013 SP1 server?!

Few weeks ago we have added new Exchange 2013 SP1 onto our existing Exchange 2007 environment. I have migrated my mailbox to the new Ex2013 server. Everything (send/receive - internally/externally, OWA, OutlookAnywhere) for me and the existing Ex2007
users works fine. The only thing I have trouble with is the ActiveSync! After migrating to the new Ex2013 server my phone stops getting new emails…, existing Ex2007 users don’t have any problems with their mobile phones.
I did ActiveSync test for my user account with ActiveSync Tester and here is what I have:
As you can see from the error above ActiveSync Tester detects ActiveSync on Ex2013 server however something wrong there with form-based auth?! I can’t see any differences in settings for ActiveSync virtual folders in Ex2007 and Ex2013
virtual folders?!
What I’m missing here?! Please help.

Check if the Exchange Servers group does not have the appropriate permission to the mailbox object in Active Directory.
To check whether inheritance is disabled on the user:
1.Open Active Directory Users and Computers.
2.On the menu at the top of the console, click View > Advanced Features.
3.Locate and right-click the mailbox account in the console, and then click Properties.
4.Click the Security tab.
5.Click Advanced.
6.Make sure that the check box for "Include inheritable permissions from this object's parent" is selected.
Ref:
http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx
Also check the Virtual directory authentication
Microsoft-Server-ActiveSync
•Basic authentication
•SSL required
•Requires 128-bit encryption
Ref:
http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
Check the IIS log if you are able to find any error message on it
Exchange Queries

Time Machine after migration to new Mac

So, I just got a new Mac, and used the option to copy settings and files from a Time Machine volume to the new machine. Now that everything's run, though, I can't use Time Machine to backup the new Mac -- it says "Volume not found". I've Googled a bit, but most of the troubleshooting seems to assume that the drive is missing or won't mount -- the drive is there, but the Time Machine software won't use it.
What are my options here?

Hi VK
A supplementray question:
I have one i-mac happily backing up with Time Machine to an external hard drive.
I have just bought a second i-mac (stops the fighting!) and propose to use migration assistant to move my [admin] account from the old to the new i-mac leaving two other accounts on the old one. I see from your posts that it seems as if Time Machine will start a new back up series for the new i-mac's back ups. But what about the old i-mac? Will that continue to extend the existing Time Machine back up files, albeit without my transferred account and its files? If so, should I partition the external drive and start the new back ups from the new i-mac on this new partition. I'd like to end up with the old i-mac continuing to build its Time Machine back ups (less my account and its files) and have a new back up series from the new i-mac building to a separate partition on the external drive.
Does this make sense? I can't see an answer in the forum to what must be a reasonably common issue in this expandin mac world.
MVBW
Mervyn

Exchange 2007 - Exchange 2013 Mailbox Migration Issues

Exchange 2013 - Mail Flow is working. OWA Access is great. We have issues connecting Outlook 2010 Clients. If I create a new user and mailbox Outlook 2010 works fine. However, if we migrate a user's mailbox to the new Exchange
2013 server. Outlook Web (OWA) works and mail flow but "OUTLOOK 2010 can not connect to the new server" There is something different about a newly created account and a migrated account. Any help would be great. I did check
inheritance in AD and it was on for these accounts. This occurs with any account migrated to the new server.

1. Could you double check your Exchange 2007 Internal Autodiscover URI - it should be pointing to Exchange 2013. All clients should be receiving their autodiscover config from the Exchange 2013 server. Based on the client's mailbox location, Exchange 2013
generates and provides the correct information.
2. If the autodiscover URI is "autodiscover.yourdomain.com" and you've configured Split-Brain DNS or Pin-Point DNS zones on the local network, make sure the name is resolved to Exchange 2013 internal IP address.
Step by Step Screencasts and Video Tutorials

Slow Mailbox Migration

Hello All
We are in coexistence with 2007 and exchange 2013 and everything is working fine except mailbox migration, which is taking very long.
Mailbox size is average 200MB and migration for 10 mailboxes takes about 12 hours, even within the same LAN and across WAN link
The architecture is
DataCenter 1
2007 Environment
2013 CAS1
2013 Mailbox1
2013 Edge
DataCenter 2
2013 CAS2
2013 Mailbox2
2013 Edge2
Has anyone experienced problems like this before?
Thanks

Hi,
If the servers are performing other higher priority jobs, the mailbox movements will be stalled. When the servers get freed up from higher priority jobs, the mailbox movement resumes.
I recommend you use the New-MoveRequest cmdlet with the Priority parameter to check the result.
If only some mailboxes are affected, you can set the BadItemLimit parameter to a higher value to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Partitioned Incremental Table - no stats gathered on new partitions

Dear Gurus
Hoping that someone can point me in the right direction to trouble-shoot. Version Enterprise 11.1.0.7 AIX.
Range partitioned table with hash sub-partitions.
Automatic stats gather is on.
dba_tables shows global stats YES analyzed 06/09/2011 (when first analyzed on migration of data) and dba_tab_partitions shows most partitions analyzed at that date and most others up until 10/10/2011 - done by the automatically by the weekend stats_gather scheduled job.
46 new partitions added in the last few months but no stats gathered on in dba_tab_partitions and dba_table last_analyzed says 06/09/2011 - the date it was first analyzed manually gathering stats rather than using auto stats gatherer.
Checked dbms_stats.get_prefs set to incremental and all the default values recommended by Oracle are set including publish = TRUE.
dba_tab_partitions has no values in num_rows, last_analyzed etc.
dba_tab_modifications has no values next to the new partitions but shows inserts as being 8 million approx per partition - no deletes or updates.
dba_tab_statistics has no values next to the new partitions. All other partitions are marked as NO in the stale column.
checked the dbms_stats job history window - and it showed that the window for stats gathering stopped within the Window automatically allowed.
Looked at Grid Control - the stats gather for the table started at 6am Saturday morning and closed 2am Monday morning.
Checked the recommended Window - and it stopped analyzing that table at 2am exactly having tried to analyze it since Saturday morning at 6am.
Had expected that as the table was in incremental mode - it wouldn't have timed out and the new partitions would have been analyzed within the window.
The job_queue_processes on the database = 1.
Increased the job_queue_processes on the database = 2.
Had been told that the original stats had taken 3 days in total to gather so via GRID - scheduled a dbms_scheduler (10.2.0.4) - to gather stats on that table over a bank holiday weekend - but asked management to start it 24 hours earlier to take account of extra time.
The Oracle defaults were accepted (and as recommended in various seminars and whilte papers) - except CASCADE - although I wanted the indexes to be analyzed - I decided that was icing on the cake I couldn't afford).
Went to work - 24 hours later - checked dba_scheduler_tasks_job running. Checked stats on dba_tab_stats and tba tablestats nothing had changed. I had expected to see partition stats for those not gathered first - but quick check of Grid - and it was doing a select via full table scan - and still on the first datafile!! Some have suggested to watchout for the DELETE taking along time - but I only saw evidence of the SELECT - so ran an AWR report - and sure enough full table scan on the whole table. Although the weekend gather stats job was also in operation - it wasn't doing my table - but was definitely running against others.
So I checked the last_analyzed on other tables - one of them is a partitioned table - and they were getting up-to-date stats. But the tables and partitions are ridiculously small in comparison to the table I was focussed on.
Next day I came in checked the dba_scheduler_job log and my job had completed within 24 hours and completed successfully.
Horrors of horrors - none of the stats had changed one bit in any view I looked at.
I got my excel spreadsheet out - and worked out whether because there was less than 10% changed - and I'd accepted the defaults - that was why there was nothing in the dba_tables to reflect it had last been analyzed when I asked it to.
My stats roughly worked out showed that they were around the 20% mark - so the gather_table stats should have picked that up and gathered stats for the new partitions? There was nothing in evidence on any views at all.
I scheduled the job via GRID 10.2.04 for an Oracle database using incremental stats introduced in 11.1.0.7 - is there a problem at that level?
There are bugs I understand with incremental tables and gathering statistics in 11.1.0.7 which are resolved in 11.2.0 - however we've applied all the CPU until April of last year - it's possible that as we are so behind - we've missed stuff?
Or that I really don't know how to gather stats on partitioned tables and it's all my fault - in which case - please let me know - and don't hold back!!!
I'd rather find a solution than save my reputation!!
Thanks for anyone who replies - I'm not online at work so can't always give you my exact commands done - but hopefully you'll give me a few pointers of where to look next?
Thanks!!!!!!!!!!!!!

Save the attitude for your friends and family - it isn't appropriate on the forum.
>
I did exactly what it said on the tin:
>
Maybe 'tin' has some meaning for you but I have never heard of it when discussing
an Oracle issue or problem and I have been doing this for over 25 years.
>
but obviously cannot subscribe to individual names:
>
Same with this. No idea what 'subscribe to individual names' means.
>
When I said defaults - I really did mean the defaults given by Oracle - not some made up defaults by me - I thought that by putting Oracle in my text - there - would enable people to realise what the defaults were.
If you are suggesting that in all posts - I should put the Oracle defaults in name becuause the gurus on the site do not know them - then please let me know as I have wrongly assumed that I am asking questions to gurus who know this suff inside out.
Clearly I have got this site wong.
>
Yes - you have got this site wrong. Putting 'Oracle' in the text doesn't enable people to realize
what the defaults in your specific environment are.
There is not a guru that I know of,
and that includes Tom Kyte, Jonathan Lewis and many others, that can tell
you, site unseen, what default values are in play in your specific environment
given only the information you provided in your post.
What is, or isn't a 'default' can often be changed at either the system or session level.0
Can we make an educated guess about what the default value for a parameter might be?
Of course - but that IS NOT how you troubleshoot.
The first rule of troubleshooting is DO NOT MAKE ANY ASSUMPTIONS.
The second rule is to gather all of the facts possible about the reported problem, its symptoms
and its possible causes.
These facts include determining EXACTLY what steps and commands the user performed.
Next you post the prototype for stats
DBMS_STATS.GATHER_TABLE_STATS (
ownname VARCHAR2,
tabname VARCHAR2,
partname VARCHAR2 DEFAULT NULL,
estimate_percent NUMBER DEFAULT to_estimate_percent_type
(get_param('ESTIMATE_PERCENT')),
block_sample BOOLEAN DEFAULT FALSE,
method_opt VARCHAR2 DEFAULT get_param('METHOD_OPT'),
degree NUMBER DEFAULT to_degree_type(get_param('DEGREE')),
granularity VARCHAR2 DEFAULT GET_PARAM('GRANULARITY'),
cascade BOOLEAN DEFAULT to_cascade_type(get_param('CASCADE')),
stattab VARCHAR2 DEFAULT NULL,
statid VARCHAR2 DEFAULT NULL,
statown VARCHAR2 DEFAULT NULL,
no_invalidate BOOLEAN DEFAULT to_no_invalidate_type (
get_param('NO_INVALIDATE')),So what exactly is the value for GRANULARITY? Do you know?
Well it can make a big difference. If you don't know you need to find out.
>
As mentioned earlier - I accepted all the "defaults".
>
Saying 'I used the default' only helps WHEN YOU KNOW WHAT THE DEFAULT VALUES ARE!
Now can we get back to the issue?
If you had read the excerpt I provided you should have noticed that the values
used for GRANULARITY and INCREMENTAL have a significant influence on the stats gathered.
And you should have noticed that the excerpt mentions full table scans exactly like yours.
So even though you said this
>
Had expected that as the table was in incremental mode
>
Why did you expect this? You said you used all default values. The excerpt I provided
says the default value for INCREMENTAL is FALSE. That doesn't jibe with your expectation.
So did you check to see what INCREMENTAL was set to? Why not? That is part of troubleshooting.
You form a hypothesis. You gather the facts; one of which is that you are getting a full table
scan. One of which is you used default settings; one of which is FALSE for INCREMENTAL which,
according to the excerpt, causes full table scans which matches what you are getting.
Conclusion? Your expectation is wrong. So now you need to check out why. The first step
is to query to see what value of INCREMENTAL is being used.
You also need to check what value of GRANULARITY is being used.
And you say this
>
Or that I really don't know how to gather stats on partitioned tables and it's all my fault - in which case - please let me know - and don't hold back!!!
I'd rather find a solution than save my reputation!!
>
Yet when I provide an excerpt that seems to match your issue you cop an attitude.
I gave you a few pointers of where to look next and you fault us for not knowing the default
values for all parameters for all versions of Oracle for all OSs.
How disingenous is that?

Mailbox migration from one server (country 1) to another server (country 2 ) ( exchange 2007)

Hi,
My exchange servers are hosted with my hosting service provider at London, i have 1000 users and each are having 3 Gig mail box size (exchange 2007) and this exchange server is part of our company network which is extended to hosting service provider. I
need to setup new exchange 2007 as part of existing exchange organisation and migrate the users from London to Singapore.
The bandwidth between our company and hosting facility 20 MB.
What is the best method to move the mailboxes from loon service provide to our company ?
I cannot do complete 3 gig mailbox migration from source to destination due to wan bandwidth limitation and time.
I can do only move the mails to local pst then migrate the mailboxes to new server and import the pst mails to exchange mailbox.
Is there any other method available ? backup and restoration ?
Please help me to provide best method for mailbox migration.

For migrating exchange mailboxes from one server to another server (across the country), the suitable approach will be to export mailboxes into pst files.
This job can be simplified even more, take the offline copy of edb file to the destination system (at Singapore) then export all mailboxes (of all sizes) from offline file to separate PST files. Then run PowerShell scripts to import the PSTs. For extracting
mailboxes from offline edb file use a stable edb converter solution that extracts mailboxes (even very large sized) & create new pst file for each of equivalent size.
product overview: http://www.pcvita.com/edb-converter.html

Exchange 2007 mailbox migration question

Hi, I'm using Exchange 2007 and had most of my mailboxes are currently on a single mail server. I recently built two new mail servers and used CCR. I have 7800+ mailboxes and was told that when I move the mailboxes from the old mail server to the new
mail server that this will create a huge amount of additional transaction logs that wouldn't be cleared out until the next backup. We do nightly backup and have 1 TB of free space on our log drive. I can't find anywhere that documents that moving mailboxes
from one mail server to another would create additional transaction logs. I could understand the existing transaction logs would follow the mailboxes to the new mail server, but I don't see where it would create new transaction logs? I'm planning on moving
only 200-300 mailboxes a night, so this wouldn't happen all at once.
Any clarification would be helpful.
         Thanks,
          Andrew

Agree with Cara on this and the transaction logs can be fairly hefty in size when migrating a bunch of data. One other option would be to;
1. do a backup of the associated stores/database right before migration.
2. then run on circular logging for those all databases within a storage group which will keep the logs in check
3. upon completion turn circular logging OFF, do a full backup and proceed along your way.
There is however some risk with using circular logging and you should read the articles below
http://exchangeserverpro.com/ems-enabledisable-exchange-server-2007-circular-logging/
http://technet.microsoft.com/en-us/library/bb331968%28v=exchg.80%29.aspx
http://technet.microsoft.com/en-us/library/bb331951%28v=exchg.80%29.aspx
http://blogs.technet.com/b/scottschnoll/archive/2011/06/27/circular-logging-and-mailbox-database-copies.aspx
Of course you could also keep things as they are and then monitor disk space and log volume during migration and as things rise Execute a Full backup to clear/truncate the logs. Technically its safer to do this then turn on circular logging but its
allot more resource intensive all the way around.   Another option would be to schedule several full backups during the migration process, i.e. every NN hours etc and then the backups will happen automatically and all should be well as long as the
backups complete before the disk runs out of space from log file generation
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Double Contacts Folder after Mailbox Migration

Here’s a new one for you… I’ve done a few Exchange 2007/2010 to 2013 migrations so far, and to my knowledge they’ve been successful… until now…
I migrated my own server from 2007 to 2013 over the weekend. Mailbox migration finished early Tuesday morning my time (Monday was a public holiday). Everything seemed to work just fine.
Yesterday (Tuesday) I noticed on my Win8.1 phone, that a large number of my contacts were missing. Digging deeper I found that my phone was missing the contacts from my main mailbox. I checked my iPad to see if the contacts were there – they
were! I figured somethings up with my Win8.1 phone, so I removed the account and readded it – same problem. I added a user to the contacts on my Win8.1 phone and sync’d it. It showed up in the iPad no problems.
I then went to Outlook and switched the pane to Folder View – I could then see two contacts folder both at the root of my mailbox. The test user was in the first folder. If I try to expand the 2<sup>nd</sup> folder, it sends outlook
into a massive loop and flickers between the two folders as if they are fighting one on one…
If however I switch the view to People – I see the two contacts folders as just fine and can look into each of them. In one of them I can see the Testuser. In the other folder I can see all my other contacts that are "missing"
But wait… it gets better still. In our office several months back, we migrated from Exchange 2010 to 2013. I wondered if others had seen the problem. From what I can see today, it appears that anyone with a Windows 8 phone has this duplicated
contacts folder. They appear to have the exact same problem… right down to the flickering and crash of Outlook 2013…
I'm concerned now because this is now a couple of migrations that we've seen this on and I've no idea whats gone wrong.
I've checked event logs - nothing seems amiss there.
Any thoughts on how to troubleshoot this?
Wayne
Wayne Small

Hi Wayne,
I have seen this issue if original mailbox was in different language than the new mailbox.I have even seen this even if original mailbox had EN-US and new database is EN-UK.
Please run the following command in Exchange powershell:
Get-MailboxFolderStatistics [email protected] | Select Name,FolderSize,ItemsinFolder
Do you see two contact folder here aswell?
Solution for us it to copy all "old Contacts" to new Contact and delete the old one.When try to delete the default Contact you will get error message that it cant be removed.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Mailbox Migration Error

I am operating an Exchange 2013 CU7 in a co-exit environment with an Exchange 2010 server. when I try to setup a mailbox migration through the EAC I receive and Error "Multiple potential Migration mailboxes were found for this organization. Please
specify a particular Partition mailbox to use." and I can go any further or finish performing the migration.
any thoughts would be appreciated.

I contacted Microsoft to work through this error message and we were able to get it resolved.
hear is the solution for this error message.
within "Active Directory Users and Computer" in the
Users OU, find and delete the following accounts. (don't worry we will recreate them in a few moments.)
DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}
FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042
Migration.8f3e7716-2011-43e4-96b1-aba62d229136
SystemMailbox{1f05a927-0acd-45d5-9bc1-1a123e6fc52e}
SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}
Once they are removed, go to your Exchange 2013 server and run the following command from an elevated command prompt
(locate the Exchange Setup File from you CD or download location and run)
Setup.exe /Preparead /IAcceptExchangeServerLicenseTerms (this recreates all the account we just deleted.)
we are almost done. next we have to enable the accounts. This time from 2013 "Exchange Management Shell" run the following commands one at a time.
Enable-Mailbox –Arbitration “DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}”
Enable-Mailbox –Arbitration “FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042”
Enable-Mailbox –Arbitration “Migration.8f3e7716-2011-43e4-96b1-aba62d229136”
Enable-Mailbox –Arbitration “SystemMailbox{1f05a927-0acd-45d5-9bc1-1a123e6fc52e}”
Enable-Mailbox –Arbitration “SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}”
Enable-Mailbox –Arbitration “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}”
Set-Mailbox "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration –Management:$true
once you have completed this you will be able to close the Exchange Admin Centre, then log back in and go to Migration tab without any errors.

[SOLVED] Problem in moving /var to new partition

Hi,
I setup a new systemd Arch instalation on an SSD and migrated successfully from my old initscripts based HDD setup. I have 2 problems now, one leading to another.
I wanted to move /var to a partition on HDD and followed the following steps.
Created a new reiserfs partition for var on my HDD using gparted. Labelled it as "var"
Rebooted to emergency mode and mounted it. (I remounted root as read-write)
# mount /dev/sda8 /mnt/new_var
Copied var contents to new_var
# cd /var
# cp -Rax * /mnt/new_var/
# cd /
# mv var var.old
# umount /mnt/new_var
# mkdir var
# mount /dev/sda8 /var
Added the following line to /etc/fstab
LABEL=var /var reiserfs defaults 0 1
When I reboot after this, systemd is timing out waiting for a var partition. Here is an pic taken during boot.
I restored the old var using the emergency shell and could reboot properly. I tried the same thing as a normal user using sudo after the system was up. (During the moving, I got sudo warnings because the sudo folder in /var/db wasnt there.)
With the new var partition in place, I proceeded to install a few packages. But when I rebooted, I the same thing happened again and had to get into emergency shell and restore the old var.
However, after this, the packages which I installed in the interim are not available in pacman database.
So,
1. How can I move /var to a separate partition and still keep systemd happy?
2. Is there a way to rescan or rebuild the pacman database? Will syncing the 2 different var setups that I've solve the problem? If so, how can I sync them?
Last edited by kungsu (2012-11-04 14:54:25)

I'm thinking in collision propabilities here. How probably might the device node change? I have machines that keep doing this without a real reason. I'd prefer labels on such machines. Other machines don't - without a real reason as well. I'd prefer device node notation on such machines. Labels can be changed manually, new partitions can be added and USB sticks with labled partitions can be inserted. While the USB situation should not be a big deal, both, labels as well as device nodes can be subject to changes, collisions and other arbitrary events. The only thing that is unlikely to change (for no obvious reason), be altered by accident or made collide with another one, are UUIDs.
I would not say using lables is bad, it's just that if you already have an issue, why not rule that out? It seemed to have solved the issue, it can be as easy as playing safe sometimes. Furthermore, the reason why I recommended to change the label from "var" to something else, is how common "var" is. It is like using a keyword in a programming language as a variable name, it may or may not work, so why not make it a habbit of not using such meta-keywords at all?
EDIT: There is no particular reason, I suspect the lable isn't set correctly. Maybe there is a problem with the partition table - that's where I'd suspect the LABLE to be stored.
Or maybe you just did the whole by-label thing wrong.
"/dev/disk/by-label/var" instead of LABEL="var"…
Last edited by Awebb (2012-11-04 15:27:43)

New partition & windows no longer boots

Hey all, up until now i have had 3 partitions on my drive - Snow leopard, General media and Windows 7. I decided to add a linux partition and made a new partition using disk utility. I boot up to the choose disk screen to install ubuntu to find that windows is no longer an option for boot up, so i deleted the new partition and it still won't boot into windows anymore.
How can i restore the booting function? Doing it with a linux partition too would be preferable but it isn't necessary.
Thanks,
Brad

Hi Brad and welcome to Discussions,
Hi John,
A later done partitioning to add additional partitions to a harddisk alters the position of the BootCamp partition in the partition table so that the Windows Bootloader can not 'find' the Windows partition.
With Windows XP it helped to simply edit the Boot.Ini file and point it to the WIndows partition.
With Vista and Windows 7 there no longer is a boot.ini but EasyBCD http://neosmart.net/dl.php?id=1 can do the same.
One thing to remember though is, that even Vista and Windows 7 'suffer' from the limitation of four partitions on one harddisk immenent to the Master Boot Record (MBR) since Apples EFI/GPT/MBR emulation can not handle Extended Partitions and Logical Partitions inside an Extended Partition.
Regards
Stefan

Mailboxes migration to new partition

Similar Messages

Maybe you are looking for