Rsync from Solaris/Linux server to Celerra share?

other alternative - if its just a small number of files or large file you could use a small ftp mirror skript on the clients

the Celerra supports ftp natively and its not bad for large files

you don't need to mount source on the utility server, only the destination (Celerra in this case).  Rsync client on the source machine sends data to rsync daemon running on utility server.

what kind of data ?

can you stand up another linux server ? If yes, you could mount Celerra NFS exports on this "utility" linux server, setup rsync deamon and then use rsync from Solaris/Linux clients and send data to this server without needing to mount anything. I am actually doing that right now only with another vendors backend storage.

dynamox schrieb: you don't need to mount source on the utility server, only the destination (Celerra in this case).  Rsync client on the source machine sends data to rsync daemon running on utility server.

true - I forgot

you're still dragging the data over the network twice though

dynamox schrieb: Btw ..how are you replying with "schrieb" , is that based on your preferences set to Germal Locale ?

yes, thats german for "wrote"

like with the timezone I cant make the language setting stick in the forum - I can change it in the preferences but it keeps changing it back :-(

Thanks for the suggestions and this is were my dilemma lies.

1) The 2 servers are turn-key systems and the vendor prohibits us from installing anything on it and the vendor will not allow any kind of exports to be mounted period nor even have access to login to the servers.

2) We are basically a 99.99% windows shop with the exception of these 2 non-windows boxes therefore we only have windows admins here and nothing else.

3) Reason 1 and 2 is why these 2 systems are turn-key in which the vendor does 100% support on them but they also have all these restrictions.

4) The files are mostly average size application files but it does total to 25GB of data from what the vendor tells us as we don't have access.

5) We thought about FTP but another restriction is that we have to run their proprietary API to prep their server before the backup and then another proprietary API after the backup but there are 2 separate version of the API depending if the backup fails or suceeds.

6) This ONE script needs to be created by us without knowledge of their API and we only know the name of directory to backup given to us by the vendor.  The vendor will only just take the script and drop it on their server and schedule a cron job to run it, again because we don't have access to the servers.

Basically the vendor expect us to work in the dark and magically create something to backup their directory and work perfectly the first time and everytime without any kind of testing.

Why don't we just drop this vendor and move to someone better you may ask.  Well lets just say it's all political at the highest level and us peons have no say.

25 GB isnt much - if you have the local space then just tar&compress the backup data into one file and ftp it to the Celerra

much simpler than anything else

sounds like PGP servers,  am I close ?

if business requirements says you can't mount and they are willing to take performance hit. Btw ..how are you replying with "schrieb" , is that based on your preferences set to Germal Locale ?

it you have ncftp there or can put it there it gets pretty simple

see http://www.ncftp.com/ncftp/doc/ncftpput.html

That's another problem.  I think this vendor finds the smallest drives out there for their systems, they said there is only 20GB of free space and the only thing supposely on their turn-key systems are the OS and their small application and also they won't allow tar'ing to itself.

so what are your options? Rsyc, scp ?

or if you got a least Perl

http://ossw.ibcl.at/FTPSync/