Jump to content

kbisignani

Members
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About kbisignani

  • Rank
    Newbie

Recent Profile Visitors

63 profile views
  1. kbisignani

    Replicate Onsite Backup to the Cloud

    Spoke to support and yes, that is in fact the case - store to S3, then Lifecycle moves it to Glacier. I'll have to see what the pricing implications are of this - for all I know this is standard operating procedure for storing things in the iceberg. I have a phone call slated for next week to start the formalization of this with a vendor, so I'm sure I learn more from that as well. Thank you again David!
  2. kbisignani

    Replicate Onsite Backup to the Cloud

    So just to post an update, and follow up on some points you made David, I work for an entity that has some unique (translation: archaic) purchasing limitations. Unfortunately for me, it ends up eliminating the availability of many cloud storage providers like Backblaze (which I personally use and love). As such, I'm kind of limited. Amazon Glacier (while not necessarily the best option) has similar pricing to Backblaze B2 and is something my employer can figure out how to pay for (via a third party, of course). Question though specific to Glacier - the Retrospect KB Article here that you showed me talks about the data "Lifecycle" options - and setting the option to Archive to Glacier after 1 day. Does that mean that I wouldn't be storing directly from Retrospect directly into Glacier? And, if so, subsequently incurring high data storage costs for one day each time I back up to the cloud? (Again, I apologize for my ignorance - just want to learn as much as possible before I jump into the deep end!)
  3. kbisignani

    Replicate Onsite Backup to the Cloud

    Thank you David for the reply - and the links! I did a cursory review of them last night but there's a lot of good information and follow up conversation that I want to really parse through. SO thank you for all of that. You are correct - this is a Windows server running the backups of other Windows (and one Mac) servers. I'm going to start from scratch with a new NAS, I'll keep old NAS's offline for previous backups - they only have about 6-8 months on them anyway before they ran out of space and Retrospect started to complain. The pure intention here is to replicate what I have being stored on the local NAS to a remote location. The Buffalo's actually can do this natively, but I'm not sure if that's a good idea since I don't know what kind of "transactions" will be occuring and don't want to incur extra charges because of my ineptness. I need to do more research on the topic and have a meeting on Tuesday with one of my vendors who I'll be going through to help me as well. Again, thank you David. I'll follow up with what we did, and how we did it, for the good of the order.
  4. Hello all, So I'm curious if someone can point me in the direction of "best practice" when it comes to backing up to a NAS and then replicating that backup off-site to the cloud (say something like Amazon Glacier or the like). Is it as simple and straightforward as Step 1: Backup to NAS. Step 2: Copy Backup Sets to Cloud Or is there a more streamlined approach or something that helps to ensure I'm not using excess space in cloud? I'd love not to have any of this operate during normal business hours and so I think incremental is the best approach here, but not sure what my exact configuration would be. Any thoughts or pointers are appreciated. Thank you! (If helpful, I'll be using a Buffalo NAS) ~ Kyle
×