Closed Bug 1054490 Opened 11 years ago Closed 11 years ago

Public IP for new Crashplan Server

Categories

(Infrastructure & Operations Graveyard :: NetOps, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1054053

People

(Reporter: jen, Assigned: dcurado)

Details

Hi - We will be setting up a new Crashplan server in the Santa Clara datacenter. Can we please have a public IP address assigned to us so the Infra team can add clientbackup.mozilla.com to DNS for us? We don't currently have the server in inventory because we haven't received it yet. But we want to add the future hostname into our existing config so that when we bring the new server up the clients will just fail over to it. Sorry- not sure if this the right way to do it - but this is the first time I'm doing this. Please let me know if there's any additional information I can provide or anything else I need to do. https://bugzilla.mozilla.org/show_bug.cgi?id=1054033 Thanks!
Also - not sure if you need this - but these are the ports users will be connecting to this host once its up: 443, 4282, 4285 http://support.code42.com/Administrator/3.6_And_4.0/Planning/TCP_And_UDP_Ports_Used_By_Code42_Products
One second - do other crashplans servers have a public IP?
Flags: needinfo?(jhayashi)
Hi Michal - no - currently the other crashplan servers do not have a public IP address. But we are adding a new crashplan appliance in the santa clara data center that would be publically accessible to allow remoties the ability to have a client backup the same way that office employees do. The remote employees would then backup to cloud storage we have purchased from Code42.
Flags: needinfo?(jhayashi)
Assignee: network-operations → dcurado
I believe this request is being handled in bug 1054053. Closing this as a duplicate. If that is incorrect, just let me know. Thanks.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.