Baron,

 

You have to separate SME and SMSQL for this discussion.

 

Latest versions of SME have added an optional disk space savings when combining the logs and SnapInfo directories together on the same lun, using NTFS Hard Links. This can be a great savings feature that answer youe requirement.

 

SMSQL - As far as my experience goes, you have to back it up by design when using SMSQL - the SnapInfo is an integral part of the backup - so in a way - you can compare with backing up the backup catalog of a backup application - it's an additional information that you need to keep track of the backups, so that you can easily browse and perform the recovey. This is the reason you purchased it isn't it?

 

So - if you care about disk space savings, you can still reduce the reservation amount unrelated to my discussion above - you will just have to monitor it more closely. Snapshots will continue to run, and SME and SMSQL will happily leave with that.

By the way - most people tend to believe that an "aweful thing" happens if you reduce the space reservation and then a disk write cannot be accepted - but in fact what happens is that the lun is taken offline. It's downtime, but in a way it's a very simple one - you clean up some space, most likely by removing old backups (snapshots) and then take the lun online again, and you're up.

 

Eyal.

 

On 8/17/06, Hadrian Baron <Hadrian.Baron@vegas.com> wrote:

So I had many replies about creating a separate LUN to store smsql (or sme) log files / installation directory. 

I had one question though:

For this extra smsql LUN,  do I need space reservation / snapshotting enabled?

Why have a backup of a backup of a backup right?

Hadrian Baron
Network Engineer
VEGAS.com
Office: 702-992-4853
Cell:    702-553-5699