HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Re: Windows 2003 Storage Server R2 single instance...
Windows Server 2003
1833760
Members
2518
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
03-23-2008 04:42 AM
03-23-2008 04:42 AM
Windows 2003 Storage Server R2 single instance issue
Server - Ml310 G4 running windows 2003 storage server R2 with sp1 , it is using sis common storage file system.
when backing up data to tape using backupexec , backup is fine but when restoring data , if data is restored to a another location other than the original location some files are corrupted. If restored to their original location they are ok.
This is due to the single instance storage file system of the storage server. Is there anything i can do to allow succesfull restoration of data to a redirected location.
Ntbackup works fine. Tried restoring to another server on the network still same error.
It is the SIS file system.
Open to suggestions/recommendations / advice.
Thank you
kumar
when backing up data to tape using backupexec , backup is fine but when restoring data , if data is restored to a another location other than the original location some files are corrupted. If restored to their original location they are ok.
This is due to the single instance storage file system of the storage server. Is there anything i can do to allow succesfull restoration of data to a redirected location.
Ntbackup works fine. Tried restoring to another server on the network still same error.
It is the SIS file system.
Open to suggestions/recommendations / advice.
Thank you
kumar
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2008 10:44 PM
04-10-2008 10:44 PM
Re: Windows 2003 Storage Server R2 single instance issue
An old article but still valid I think
http://support.microsoft.com/kb/299726
Basically on your source volume there will be 3 important components:
1) A Groveler service that finds duplicate files and replaces duplicate files with a pointer to the "Master file" that is moved to a common folder
2) The SIS Common Store folder itself that is a hidden folder
3) A SIS filter driver that handles the access to the duplicate files.
Without 2 or 3 the duplicate files will indeed look like 0-length corrupted files.
The reason you do not get any problems restoring to the original location is probably because the hidden folder is there and the SIS filter driver is active.
Note however that if your backup does not include the hidden folder, you may effectively be fooling yourself into thinking you have a valid backup, when you are actually missing an essential piece...
A work-around for backup purposes could be to backup via a network share as described here: http://support.microsoft.com/kb/889714
Cheers,
Rune
http://support.microsoft.com/kb/299726
Basically on your source volume there will be 3 important components:
1) A Groveler service that finds duplicate files and replaces duplicate files with a pointer to the "Master file" that is moved to a common folder
2) The SIS Common Store folder itself that is a hidden folder
3) A SIS filter driver that handles the access to the duplicate files.
Without 2 or 3 the duplicate files will indeed look like 0-length corrupted files.
The reason you do not get any problems restoring to the original location is probably because the hidden folder is there and the SIS filter driver is active.
Note however that if your backup does not include the hidden folder, you may effectively be fooling yourself into thinking you have a valid backup, when you are actually missing an essential piece...
A work-around for backup purposes could be to backup via a network share as described here: http://support.microsoft.com/kb/889714
Cheers,
Rune
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP