|
Home > Archive > Data Storage > August 2004 > Programmatically managing SAN/NAS
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Programmatically managing SAN/NAS
|
|
| Niranjan 2004-07-21, 2:45 am |
| Hi All,
I failed to get much information from the Internet, it would be great
if you can help me out.
We are working on a project which involves archiving/copying/taking
backups onto the storage devices such as SAN or NAS
programmatically(using C#). As we do not have any of these devices
right now we are unable to apprehend what extra we need to do.
Are the devices so abstracted from the user that, just using CopyFiles
API call from the program with the SAN/NAS path as the argument will
do the job(in this case for the user/program, SAN/NAS will be no
different from the HDD)? If no should I be using the SDK(if at all it
is provided) provided by the vendor for controlling it
programmatically...
Thanks in advance..
Regards,
Niranjan
| |
| Jesper Monsted 2004-07-28, 5:45 pm |
| knir@sonata-software.com (Niranjan) wrote in
news:8640c2b7.0407210026.5e2beb0f@posting.google.com:
> We are working on a project which involves archiving/copying/taking
> backups onto the storage devices such as SAN or NAS
> programmatically(using C#). As we do not have any of these devices
> right now we are unable to apprehend what extra we need to do.
> Are the devices so abstracted from the user that, just using CopyFiles
> API call from the program with the SAN/NAS path as the argument will
> do the job(in this case for the user/program, SAN/NAS will be no
> different from the HDD)? If no should I be using the SDK(if at all it
> is provided) provided by the vendor for controlling it
> programmatically...
SAN devices are no different than local SCSI/ATA drives. NAS systems are no
different than regular file servers (NFS or CIFS).
The only difference you should see is (hopefully) performance.
--
/Jesper Monsted
| |
| BackupGurus 2004-08-02, 1:11 pm |
| quote:
Originally posted by Jesper Monsted
knir@sonata-software.com (Niranjan) wrote in
news:8640c2b7.0407210026.5e2beb0f@posting.google.com:
> We are working on a project which involves archiving/copying/taking
> backups onto the storage devices such as SAN or NAS
> programmatically(using C#). As we do not have any of these devices
> right now we are unable to apprehend what extra we need to do.
> Are the devices so abstracted from the user that, just using CopyFiles
> API call from the program with the SAN/NAS path as the argument will
> do the job(in this case for the user/program, SAN/NAS will be no
> different from the HDD)? If no should I be using the SDK(if at all it
> is provided) provided by the vendor for controlling it
> programmatically...
SAN devices are no different than local SCSI/ATA drives. NAS systems are no
different than regular file servers (NFS or CIFS).
The only difference you should see is (hopefully) performance.
--
/Jesper Monsted
I concur with Jesper. Staying away from the API for simple file copies makes more sense. However, if you must for Windows-based NAS boxes WMI scripting would make the most sense. MS has plenty of samples in their scripting center. |
|
|
|
|