The Job Processor update for Vault 2011 is now posted.
We are running Vault Pro 2011 still and will be upgrading to 2013 soon. We are running out of disk space on the server and I was about to perform the SQL maintenance tomorrow. Part of what I wanted to do was to run a purge first and then run the SQL maintenance script after that.
Must I wait or can I go ahead?
What advice do you have for me as the disk is getting full very fast so its quite urgent!
The immediate issue here is that you need to have enough disk space on the server to actually permit a migration to occur - during the upgrade process there is considerable short term growth in the ldf files etc, so I would look at making space or adding capacity prior to upgrading wherever you can.
Ensure you have a valid backup of course but if you are storing backups on the Vault server I would remove those to a remote location prior to the upgrade - these usually take a fair amount of space.
Now, the good news is once you have completed the upgrade to 2013 Vault will automatically remove file duplication from your filestore which will actually decrease the overall disk usage. Depending on current size and design behavior this reduction can be very significant.
Vault 2013 has restricted purge as has the updates applied to 2011, 2012 and we do not recommend using purge in any case until we have released an update to address potential issues. This is actively being worked on.
Hope this helps
Ok thanks for the prompt reply!
The issue here is actually that I need to reclaim some disk space. We would not be able to do the upgrade to 2013 just yet as this is quite a big step and we normally wait for at least the first majour update to be released before we even consider it. When will this be roughly do you think?
Is there any way for me to shrink the space used by Vault besides doing a purge? Will the SQL maintenance scripts help with space?
Actually running a maintenance plan does not really reduce size, at least not to any large degree, we no longer reccomend removing free space as part of the maintenance plan as essentially as soon as the DB grows again it takes the space back...
There is an article here which may give you some ideas (minus the purging) on how to reduce size:
Moving forward please contact me directly so we can raise this with support if necessary or look at other options for your specific case.
Ok thanks for that. This is causing a bit of a problem for us. It looks like there is no real way to shrink the database. This looks like a short-term solution and it might give me a bit of extra space if I follow that blog.
Is purging posible in 2013 and 100% functioning?
A couple of questions:
1. Will this update also apply to Vault 2012?
2. When are the details going to be available?
Start with some of our most frequented solutions to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!