Quantcast
Channel: Symantec Connect - Archiving and eDiscovery - Discussions
Viewing all articles
Browse latest Browse all 3821

users cannot unarchive mail - database EnterpriseVaultMonitoring too big (Events 1827, 1105)

$
0
0
Oui, j'ai besoin d'une solution

Users cannot unarchive mail any more.

When I checked on the server, there seem to have been problems related to the EnterpriseVaultMonitoring databse:

CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database.

Restarting services or ultimately restarting the whole server did not help. On the contrary, meanwhile I cannot start the admin console anymore (it just sticks at the rotating wheels saying "Connecting to servername ...")

My fear and somewhat obvious guess is that the monitoring database might have gone corrupted in one way or other. How can I get access to my gazillions of past mails again?

---

UPDATE:

Meanwhile I managed to start the admin console again - after a restore of the EnterpriseVaultMonitoring database.

However, unarchiving is still not possible as even the restord database version suffers from these problems:

Event 1827 : CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database.

Event 1105 : Could not allocate space for object 'dbo.ServiceMonitoringHistory'.'PK_ServiceMonitoringHistory' in database 'EnterpriseVaultMonitoring' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

How could I overcome theses problems? (Apart from uplicensing, if possible)

Is there a safe way to reduce dbo.ServiceMonitoringHistory in size? (Significantly and permanently?)

Regards

Hagen


Viewing all articles
Browse latest Browse all 3821

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>