Autoarchive Exchange database

Home Forums Messaging Software Exchange 2000 / 2003 Autoarchive Exchange database

This topic contains 6 replies, has 4 voices, and was last updated by Avatar pizov75 8 years, 1 month ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • Avatar
    GSXr1000
    Member
    #154048

    Dear members,

    I have a urgent question.
    My Exchange 2003 database has got 300MB of space left.
    For a few users I setup autoarchive, now I have moved 6GB but the free space on the disk is still 300MB.

    Can somebody please help!

    Kind regards.

    #344979

    Re: Autoarchive Exchange database

    Do you mean the disk volume which your Exchange database resides on only has 300MB left?

    I believe you need to run an offline defrag of the database to reduce the size of the database files, deleting content from within the database won’t do this.

    Avatar
    pizov75
    Member
    #381293

    Re: Autoarchive Exchange database

    gforceindustries;234888 wrote:
    Do you mean the disk volume which your Exchange database resides on only has 300MB left?

    yes, that’s correct.

    I believe you need to run an offline defrag of the database to reduce the size of the database files, deleting content from within the database won’t do this.

    Offline defrag is not possible, read this:
    Offline defragmentation creates a new database by copying all records and tables from the old database into the new database. Because this is a copy, defragmentation requires free disk space equal to the size of the database (actually, youll need 110% of free space).

    I don’t have this kind of free space.

    When I use the Online Defrag would that make the database smaller?

    #344980

    Re: Autoarchive Exchange database

    No, you need to do an offline defrag to reduce the file size. If the current volume doesn’t have enough space to do that and you can’t move things off that volume to make more space, then you’d have to look into extending the volume or temporarily moving the Exchange database to another disk.

    2TB USB disks are available for peanuts now – one of those would do as a temporary measure (keep in mind the lack of fault tolerance) provided you took a reliable backup beforehand. eSata would be preferable given the extra bandwidth and doesn’t add much to the cost of external disks.

    Avatar
    pizov75
    Member
    #381294

    Re: Autoarchive Exchange database

    gforceindustries;234900 wrote:
    No, you need to do an offline defrag to reduce the file size. If the current volume doesn’t have enough space to do that and you can’t move things off that volume to make more space, then you’d have to look into extending the volume or temporarily moving the Exchange database to another disk.

    I found this on the Internet:

    Run ESEUTIL with the /p switch to configure ESEUTIL to create the new defragmented database on an alternate location (for example, to a location on a different hard disk). This switch lets you preserve your original defragmented database (which lets you revert back to your original database if necessary). This switch also significantly reduces the amount of time it takes to defragment a database, because you are rebuilding to a new location, rather then rebuilding the database in place.

    I will defrag the database to another location and then copy back to the default disk :)

    Thank you for your support.

    Avatar
    FischFra
    Member
    #365984

    Re: Autoarchive Exchange database

    The switch /p is not for defragmenation it’s the repair switch for corrupted databases. You want to use the /d switch in order to defrag.

    You can run this command from another location you can even use a network share if your network speed and bandwidth isn’t a issue.

    Avatar
    pizov75
    Member
    #381295

    Re: Autoarchive Exchange database

    Did solved my problem:


    1. Connect USB drive (G:/)
    2.
    eseutil /d /p “d:exchsrvrmdbdatapriv1.edb” /t”g:Exchangetempdfg.edb”
    3. copy tempdfg.edp (stm) to default location
    4. mounted database


    Everything works fine now and the EDB and STM files are 10GB smaller.

    Thank you all for your support.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.