Possible save shadowstorage on a Different drive?

[krescent]

Hello,

I am running windows7 on a 100GB SSD C: , and want to leave as much free space as possible.

I have a 1TB storage/backup drive S: .

I would like to know if it is possible to store the system restore data for my C: drive on my S: drive.

I have tried to do vssadmin resize shadowstorage /For=C: /On=S: /Maxsize=10GB but it says the specified volume shadow copy storage was not found.

It works if i do for=c on=c or for=s on=s. but not for=c on=s.


is this possible to achieve?

Thanks!

 

[Brink]

Hello Krescent, and welcome to Seven Forums.

You can set this in System Protection properties now to make it easier. You would turn it on for the drive (ex: S: ) you want it on instead, and turn it off for any other drive that you do not want it on (ex: C ).

Hope this helps,
Shawn

 

[Tepid]

I will give you a guess that, no, not possible, as shadow storage (i believe) is partition specific.

Brink, will that save information for all partitions in a system?

 

[krescent]

Cool!

It DOES help---however I was hoping I could still leave it ON for C:, but have it saving the restore data on the S: drive, rather than the C:.

is this possible? or must the shadow data always be on the same drive?


EDIT: just saw tepid's post. well, I guess the best I can do is just set it to a low percentage....UNLESS brink has an alternative idea!

Thanks guys!

 

[Tepid]

If I am reading this correctly, no, you can not as that is a specific server function of doing Shadow Copy Transporting.

What Is Volume Shadow Copy Service?: Data Recovery

Shadow Copy Transport

With a hardware provider that is designed for use with the Volume Shadow Copy Service, you can create transportable shadow copies that can be imported onto servers within the same subsystem (for example, a storage area network (SAN)). While multiple servers can access the same storage array, they do not share access to the same storage unit or LUN. For servers to share the same data, the traditional solution is to first copy the data on one server and then restore it to a second server. This process can be quite lengthy.


With the Volume Shadow Copy Service and a storage array with a hardware provider designed for use with the Volume Shadow Copy Service, it is possible to create a shadow copy of the source data volume on one server and then to import the shadow copy onto another server (or back to the same server). This process is accomplished in a few minutes, regardless of the size of the data. The transport process is accomplished through a series of steps using a shadow copy requestor (storage-management application) that supports transportable shadow copies. The following is a generalized version of those steps:

1. Create a transportable shadow copy of the source data on a server.
2. Import the shadow copy to a server connected to the SAN (you can import to a different server or the same server).
3. The data is now ready to be used.

Note that shadow copies are read-only. If you want to convert a shadow copy to a read/write LUN, you can use a storage-management application (including some requestors) that is compatible with the Virtual Disk Service, in addition to the Volume Shadow Copy Service. Using this application, you can remove the shadow copy from Volume Shadow Copy Service management and convert it to a read/write LUN.
Volume Shadow Copy Service transport is an advanced solution on computers running Windows Server 2003, Enterprise Edition or Windows Server?2003, Datacenter Edition that works only if there is a hardware provider on the storage array. Shadow copy transport can be used for a number of purposes, including tape backups, data mining, and testing.

In other words,, when you disable VSS on a volume or partition, I think you kill your chances of using Shadow copy on that volume/parition.

 

[Brink]

Tepid, is correct. You will only have shadow copy available for the drive/partition that you have System Protection turned on for.