I've just taken on a new customer who switched to our service. His catalog, when ported over, contained over 2100 items. He has just added another 1000+ items.
The initial snapshot he sent me (on CD) was over 45Mbytes. I have no idea what the new products will add to that, but my guess would be another 20+M.
These files cannot be emailed back and forth.
There has to be a BETTER way.
I'm sure I'm not alone here - catalogs are getting bigger and bigger - we're now in negotiations with a potential customer who needs to build a catalog with over 4000 items.
I'd like to see an incremental snapshot function and some real backup management.
e.g.: We take a FULL snapshot on date x, and then whenever I make changes (or the customer makes changes) we perform an incremental snapshot which only saves files changed or added since x.
Of course, I'm over-simplifying, but, as stated above, there has to be a BETTER way. Other than mailing cds or flash drives back and forth.
ps - anybody want to write rsynch for Windoze?
The initial snapshot he sent me (on CD) was over 45Mbytes. I have no idea what the new products will add to that, but my guess would be another 20+M.
These files cannot be emailed back and forth.
There has to be a BETTER way.
I'm sure I'm not alone here - catalogs are getting bigger and bigger - we're now in negotiations with a potential customer who needs to build a catalog with over 4000 items.
I'd like to see an incremental snapshot function and some real backup management.
e.g.: We take a FULL snapshot on date x, and then whenever I make changes (or the customer makes changes) we perform an incremental snapshot which only saves files changed or added since x.
Of course, I'm over-simplifying, but, as stated above, there has to be a BETTER way. Other than mailing cds or flash drives back and forth.
ps - anybody want to write rsynch for Windoze?
Comment