UNSOLVED

James Bellaart

updated

17 years ago

0

4277

November 4th, 2009 14:00

ASM/ME and Exchange Backups

Running an Exchange 2007 CCR cluster on Win2k8 SP2 (not R2) sitting on a HyperV R2 cluster. M610 Blades, PS4000 iSCSI SAN.

The SAN is on firmware 4.2.1 and Host Integration Toolkit 3.3 is installed on the hosts.

ASM is configured with a schedule to take a smart copy of the storage group every 6hrs, however I see it is not clearing log files after backup.

I also found this in the ASM/ME user guide:
"A Full copy requires a clean-up of the log files, which is a feature not supported by ASM/ME."

Does this mean that I need to use a 2nd backup tool to clear the log files or do I need to enable circular logging?

What is the recommended method for backing up Exchange using the ASM/ME ?
  • 214

    0

    Posted November 5th, 2009 11:00

    Hey James,

    I ran your question by one of our EqualLogic/Exchange contacts, and this was their response:
    First ASM/ME is not a backup program, rather a utility included at no extra charge for Exchange Administrators (SQL,ect).
    We do not try to replace our backup vendor partners. If for some reason a customer chooses not to use a backup
    vendor, there other options depending on the version of Exchange and OS as well as if any replication is set.
    From the information below I’m not sure what version of Exchange the customer is using. If the customer is using
    Exchange 2007 SP2 then they could use Windows 2008 SP2 backup to truncate the logs or since they are using CCR,
    they could turn on circular logging because unlike a non CCR setup in a CCR environment it’s the replication service
    That truncates the logs and then only when a copy has been written to the passive node.

    Hope this helps!

    Jeff
  • 214

    0

    Posted November 5th, 2009 12:00

    Hi Jeff, thanks for the update.

    Its 2007 SP2 on server 2008 SP2. I have installed windows server backup which is working on one of my nodes, but not the other (only backing up the active node). So more troubleshooting to do.