- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: Storage EVA4000
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2010 08:54 AM
тАО08-25-2010 08:54 AM
I have a storage EVA and some Windows servers in the same SAN.
I created a VDISK-01 and presented for server-1 (MSSQL Database server). Can I to presente the same VDISK-01 for server-02 (Backup server)?
These servers are not in cluster.
Thanks,
Cleber
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2010 10:34 AM
тАО08-25-2010 10:34 AM
SolutionA plain Windows server does not have a shared file system implementation and expects exclusive access to a volume. When the backup server mounts a volume it sees that it is "open" (has not been dismounted) and starts rollback operations to make it 'consistent'. Then it 're-opens' the volume for its own use.
But the database server is not aware of these changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2010 10:56 AM
тАО08-25-2010 10:56 AM
Re: Storage EVA4000
Can I to present the volume read only?
Thanks,
Cleber
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2010 11:19 AM
тАО08-25-2010 11:19 AM
Re: Storage EVA4000
And even if it were possible, there are two other problems:
Windows usually requires read-write access to a disk in order to mount an NTFS volume (the 'open' thing). I have not checked recent versions, but Windows 2000 even hang during boots when a data volume was read-only.
The other problem is that the database server continues to write to the disk. It can even make changes to the file system's meta data.
The backup server does not pick up all or only part of those changes, because it does not expect somebody else to make changes. So it will see inconsistencies.
That is one of the reasons why storage arrays (including the EVA) provide clones or snapshots. Those are copies or 'frozen views' of the data and changes by the database server are not visible on the clone/snapshot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2010 11:30 AM
тАО08-25-2010 11:30 AM
Re: Storage EVA4000
Thanks
Cleber
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2010 11:36 AM
тАО08-25-2010 11:36 AM
Re: Storage EVA4000
while Linux can mount a filesystem read-only, the problem is that the writer will make changes that the reader does not expect. Read-only will only ensure that the backup server does not actively cause corruptions, but the backup server can see very inconsistent data (due to writer's changes) which could even result in system crashes.
The workarounds would be the same:
- use a shared filesystem (ext2/3 is not)
- make use of controller-based clones/snapshots
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2010 11:41 AM
тАО08-25-2010 11:41 AM
Re: Storage EVA4000
Cleber