• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2311
  • Last Modified:

Server 2008 R2 / Exchange 2010 wbadmin backup - strange issue

I am testing Server 2008 R2 SP1 with Exchange 2010 SP1 RU 3v3.  The server is a member server on a test domain.

I am testing wbadmin command and the Windows Backup GUI to perform backup of exchange 2010.  I have come across an unusual effect of backing up a specific database.
Using the wbadmin command to perform a (non scheduled) backup of a specific Exchange 2010 database specificallly mbxdb1

wbadmin start backup -backupTarget:\\dc1\backup\mbxdb1 -include:'C:\Program" "Files\Microsoft\Exchange" "Server,D:\Program" "Files\Microsoft\Exchange" "Server\V14\Mailbox\mbxdb1' -vssfull -user:domain\adminuser -Password:xxxxxx

Note - the singular and double quotes that are required to overcome spaces in the folder path!
dc1 is the Windows Server 2003 domain controller that will store the backup.

I am backing up the c:\program files\microsoft\exchange (installation) directory and the mdxdb1 database & logs which are stored of the d: drive path (will seperate them onto a different disk soon).

The path to mdxdb1, mbxdb2, mbxdb3, mbxdb4 and public folders db & logs are stored as:
D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\mbxdb1
D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\mbxdb2
D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\mbxdb3
D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\mbxdb4
D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Public Folder Database

Back to the unusual effect...
When performing the above command completes, the mbxdb1 database is backed up and logs truncated and also shows on the EMC database dialog box the date and time of the last full backup.  And..... All the other databases show that they were backed up according to the database GUI in EMC when they were not targeted and their logs of each of the databases are also truncated too.

Has anyone seen this effect and is there anything to worry about?

Also any EMS commands for counting all the items in public folders in exchange 2003 and on exchange 2010 so that I can see if they match to check replication has worked.
Kind Regards
fosseitsl
0
fosseitsl
Asked:
fosseitsl
  • 2
  • 2
1 Solution
 
LeeDerbyshireCommented:
I know that you have to be careful when specifying path names with spaces in, but I've never seen quotes put around only the spaces like that.  Normally, I think it would be like this:
wbadmin start backup -backupTarget:\\dc1\backup\mbxdb1 -include:"C:\Program Files\Microsoft\Exchange Server","D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\mbxdb1" -vssfull -user:domain\adminuser -Password:xxxxxx
In other words, placing the quotes around the entire string should be sufficient.  On the other hand, you could always use the shortform (MS-DOS - compatible) notation:
wbadmin start backup -backupTarget:\\dc1\backup\mbxdb1 -include:C:\Progra~1\Microsoft\Exchan~1,D:\Progra~1\Microsoft\Exchan~1\V14\Mailbox\mbxdb1 -vssfull -user:domain\adminuser -Password:xxxxxx

so that you don't need to use quotes at all.  I don't know if this is the cause of what you are seeing, but if it finds a match in your includes for something like D:\Program Files (i.e. successfully matching that with your string up to the quotes), then it might simply be backing up everything in that heirarchy.
0
 
fosseitslAuthor Commented:
Lee,

I couldn't get the above command's to work in 2008 R2 SP1.  There appears to be no short name notation for "exchange server"!   and the wbadmin command did not like spaces in it.
Was your command performed on 2008 R2 SP1?
Kind Regards
Paul
 
0
 
fosseitslAuthor Commented:
Lee,

You are correct.
I made the mistake of performing the wbadmin command in PowerShell which didn't like the spaces.
If I perform the wbadmin command on a command prompt it works.
BTW - I found a cool utility for wbadmin: http://www.magikmon.com/mksbackup/index.en.html which allows the ability to add an email notification.

Kind Regards
Paul
0
 
LeeDerbyshireCommented:
Glad you got it working.  I'm not sure why it's any different in PS compared to CMD, but it's something I'll have to try here.  That utility looks interesting, too.  I'll definitely try that.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now