05-16-2009 05:15 AM
05-18-2009 02:11 AM
Snapshot backup would be sufficient in your scenerio.
on the master server.
STEP 1:
create a backup policy
type:Windows-NT
check perform snapshot backup
snapshot client options - select thesnapshot method as "VSS"
select the parameter values are 1, 0, 1
client: client name
backup selection : add the SAN drive of the client
STEP 2:
go to host properties of master server
under client attributes>windows open file backup>
add the client
select enable windows open file backup for this client
snapshot provider > select microsoft volume shadow copy service
snapshot usage: global drive snapshot
snapshot error control>abort backup on error
STEP 3:
login to client
go to computer management
right click under system tool>shared folders
select all tasks>configure shadow copies
selcect the san drive and enable shadow copies, after you enable go to settings and change the size to no limit
repeat the same for the drive which is having more space(this drive will be used for storing changes)
fire the backup from master server
then in client go to cmd
exceute vssadmin list shadowstroage( this will show you the amount of space used for snapshot)
moniter the backup for first time to check, how much space is required for the snapshot; what all the changes that are coming to san drive after you started the backup will be written to this place and will be applied after backup is completed,
this is called copy on write technolgy and differential snapshot.
in my screnio; my san drive is 500 Gb and it is not occuping not more that 1 GB for snapshot during backup.
to under on this go through the section of VSS and microsoft link in the below article.
https://www-secure.symantec.com/connect/articles/low-disk-space
05-18-2009 04:48 AM
05-18-2009 07:55 AM