-
- Enthusiast
- Posts: 94
- Liked: 6 times
- Joined: Apr 21, 2011 7:37 pm
- Contact:
LUN size best practice
What is better practice for lun sizing for a Veeam backup target if all storage is on the same SAN, one large lun or multiple smaller luns?
-
- Chief Product Officer
- Posts: 31805
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: LUN size best practice
One large LUN, otherwise too much wasted space collectively across multiple LUNs. Not to mention that small targets are calling for all those additional management headaches - you would have to be carefully sizing backup jobs, watching backup size constantly to prevent overfill, etc.
-
- Enthusiast
- Posts: 94
- Liked: 6 times
- Joined: Apr 21, 2011 7:37 pm
- Contact:
Re: LUN size best practice
This is because Windows only does file level locking and not lun level?
-
- Chief Product Officer
- Posts: 31805
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: LUN size best practice
Sorry, I was already updating the post above with more details while you typed this.
Sure, locking is file level with NTFS.
Sure, locking is file level with NTFS.
Who is online
Users browsing this forum: Bing [Bot], Google [Bot], mdiver, nickfurnell and 154 guests