Dns backup

Dear All,
Somehow , We have collaborative delegated access on DNS along with client. Several time we see entry missing or modified.
We have window AD -DNS , Is there any way we can pull out DNS report on daily basis which includes everything in text file.
ZOne information , Host A record entry , Reverse , Everything...Kind of dump in text file.
Thanks in advance

Dear All,
Somehow , We have collaborative delegated access on DNS along with client. Several time we see entry missing or modified.
We have window AD -DNS , Is there any way we can pull out DNS report on daily basis which includes everything in text file.
It is best to have auditing in place for DNS to see what is going on. The link below gives you how to enable auditing for your DNS server.
Who Moved the DNS Cheese? Auditing for AD-Integrated DNS Zone and Record Deletions
For exporting part you can use dnscmd command and attach it to a schedule task which runs on daily basis. Refer to this:
Export DNS records to Excel to read time stamps and static records
But in a nutshell, this is the way of exporting using dnscmd:
dnscmd /enumrecords contoso.com @ /Type A /additional > c:\dnsdata\dns.csv
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Similar Messages

Searching in DNS Server

Hi !
This has been a question in my mind since many days ago
Why we cannot search DNS or maybe we can but i do not know how !
we have about 10 zones and about 3000 entries in a 2008 R2 DNS server and many times we need to search for a specific record
how can i search for a specific record in all zones ?
Thanks

I probably wont get credit, looks like this is already closed, but I found something.
I have the same problem, looking for DNS with wildcards, and the export option does not work, it doesn't export the whole tree. For me it is tedious, because I have to remove a bad DC, and the metdata cleanup was not smooth. So I am having to
go through DNS and clean it out manually. With thousands upon thousands of records, and the DNS having random hex names, it is...unpleasant.
MICROSOFT, PLEASE ALLOW A "Right Click" SEARCH ALL for DNS!
Solution:
While trying to export from the command line DNSCMD (which I have not fully explored, maybe there is something here??) I stumbled across this folder C:\Windows\System32\DNS\Backup\ (NOTE IT IS THE BACKUP, SO DELETED entries may already be gone)
and it has one giant text file with all the DNS entries in it.   To get a fresh copy of the file to search, use;
dnscmd /ZoneExport Microsoft.local MSzone.txt
This way I can 'find' with the current or backup file anyway I want, findstr being my preference, AND it will give me the full name.
Missing the backup folder? Try the windows backup, and be sure to include live data. This part I am not so sure, we setup our backups long ago, maybe some more searching for DNS backup ;)
Saving me HOURS of work!
Hope this saves someone else some time too :)
NOTES:
I also found some interesting stuff when I was searching, namely if I searched with FIND or FINDSTR it would return an entry like this;
                        600     SRV     0 100 3268      SERVER.NAME.COM.
so how to find it?? Turns out you need the line above it for the 'call' entry, if you find it in the file, you would find something like this;
_gc._tcp.MYSITE._sites 600     SRV     0 100 3268      SERVER01.NAME.COM.
                        600     SRV     0 100 3268      SERVER.NAME.COM.
Looking in the ZONE you dumped, start at _sites and you will find your entry.
I ended up just using notepad find, and searching that way!
BlankMonkey

Networking Best Practices - Connecting Two Switches

Connecting two switches together is an easy task, which makes it so frustrating when it doesn’t work. Here we will outline a basic scenario of connecting two switches and achieving connectivity. In these scenarios we will be using commands and settings that will work for most modern PowerConnect switches. However this does not cover all possible scenarios and the commands may differ slightly from switch to switch.
For instance, in most cases you can use General or Trunk mode when connecting two switches. However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID. If you use Trunk mode, you will not have the default VLAN on those ports. The ports will only allow tagged traffic.
For more details on the difference between Access, General, and Trunk modes, follow this link.
http://en.community.dell.com/support-forums/network-switches/f/866/p/19445142/20089157.aspx#20089157
It is always a good idea to have the user and CLI guide for your switch, to reference any possible changes in command syntax.
http://support.dell.com/support/edocs/network/
Layer 2
Layer 2 switches operate at the data link layer of the OSI model. Layer 2 is responsible for error checking and transmitting data across the physical media. MAC addressing sources and destination protocols are layer 2 protocols. Layer 2 switches use the MAC address of data packets to determine where those packets should go. It learns the MAC addresses of all devices and creates a segment/forwarding table.
When a switch receives a frame with a destination address that isn't in its forwarding table, the switch forwards the frame to all other ports. If the destination machine responds to the server, the switch will listen to the reply and learn which port the destination machine is attached to. It then adds that MAC address to the forwarding table.
The Dell PowerConnect Layer 2 switches have ports that all operate in VLAN 1 by default. If it is acceptable to have all traffic on the same broadcast domain, then you can simply leave the default alone, connect the two switches and traffic will flow.
If you do not want all traffic on the same broadcast domain, then we need to look at adding additional broadcast domains through the use of VLANs.
We will use 3 VLANs for the following scenario.
VLAN 1=Management
VLAN 2=Client
VLAN 3=Server
To create these VLANs we do the following commands (VLAN 1 is already created by default)
console(config)# vlan database
console(config-vlan)# VLAN 2
console(config-vlan)# VLAN 3
console(config-vlan)# exit
We can then name the VLANs to help keep things organized.
console(config)# interface vlan 2
console(config-vlan)# name Client
console(config-vlan)# exit
console(config)# interface vlan 3
console(config-vlan)# name Server
console(config-vlan)# exit
Once we have the VLANs created we can place a device in that VLAN by placing the port it plugs into, in access mode for the specific VLAN.
So we have a workstation on port e2 we want to be placed in VLAN 2, we would issue the following commands.
console(config)# interface ethernet 1/e2
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 2
console(config-if)# exit
The next port plugs into a server on port e3 we want on VLAN 3, we would issue these commands.
console(config)# interface ethernet 1/e3
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 3
console(config-if)# exit
For the ports connecting the two switches together, we place the ports in trunk mode and specify the native VLAN and allowed VLANs.
For the port e1 that connect the two switches to each other would be configured like this.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 2,3 tagged
console(config-if)# switchport general pvid 1
console(config-if)# exit
Once these VLANs and port settings are made on both switches. A server connected to switch A on VLAN 3 should be able to communicate with another Server connected to switch B that is also in VLAN 3. Without the use of a router the devices in VLAN 3 will not be able to communicate with devices that are outside of their broadcast domain (i.e. VLAN 2 devices could not reach VLAN 3 devices)
Layer 3 + Layer 2
Until recently, routers were the only devices capable of layer 3 protocols. Switches capable of routing are now available and in widespread use. In most cases we will connect our layer 2 switches to a Layer 3 capable switch to perform our routing for us.
On the layer 3 switches we will use the same VLANs and setup that we did with the layer 2 switches. Then we will add to the configuration.
We can assign an IP address to each switch with the following command.
Switch A
console(config)#ip address 172.16.1.1 255.255.255.0
Switch B
console(config)#ip address 172.16.2.1 255.255.255.0
Then we will enable routing only on Switch A
console(config)# ip routing
Switch A we assign an IP address to VLAN 2 and enabling routing on the VLAN.
console(config)# interface vlan 2
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.20.1 255.255.255.0
console(config-if-vlan2)# exit
Switch A we assign an IP address to VLAN 3 and enabling routing on the VLAN.
console(config)# interface vlan 3
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.30.1 255.255.255.0
console(config-if-vlan2)# exit
On both switch A and switch B we will keep things simple and use interface 1/e1 for the connection between each switch. Setting both switches 1/e1 to general mode, allowing the additional VLAN 2,3, and keeping the PVID of 1.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 2,3 tagged
console(config-if)# switchport general pvid 1
console(config-if)# exit
We will have one client computer connect to switch A on port 1/e2 and one client connect to switch B on port 1/e2. These ports will be in access mode for VLAN 2, and the config should look like this on both switches.
console(config)# interface ethernet 1/e2
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 2
console(config-if)# exit
We will have another client computer connect to switch A on port 1/e3 and one client connect to switch B on port 1/e3. These ports will be in access mode for VLAN 3, and the config should look like this on both switches.
console(config)# interface ethernet 1/e3
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 3
console(config-if)# exit
On Clients connected to Switch A we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 2.
IP Address:172.16.20.11
Default Gateway:172.16.20.1
Client connected to access port for VLAN 3.
IP Address:172.16.30.11
Default Gateway:172.16.30.1
On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 2.
IP Address:172.16.20.12
Default Gateway:172.16.20.1
Client connected to access port for VLAN 3.
IP Address:172.16.30.12
Default Gateway:172.16.30.1
External Connection
At some point we may want traffic to have an external connection. To do this we can create a new VLAN for our point to point connection from Switch A to our router. We will use VLAN 7 for this and assign an IP address.
console(config)# vlan database
console(config-vlan)# VLAN 7
console(config-vlan)# exit
console(config)# interface vlan 7
console(config-vlan)# name WAN
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 10.10.10.2 255.255.255.0
console(config-if-vlan2)# exit
On our router we will assign an IP address of 10.10.10.1
Then place the port connecting the switch and router into access mode for VLAN 7. In this case we use port e4.
console(config)# interface ethernet 1/e4
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 7
console(config-if)# exit
We will then need to put in a default route with the next hop as the router IP address. This allows the switch to know where to route traffic not destined for VLANs 2, 3, or 7.
console(config)#ip route 0.0.0.0 0.0.0.0 10.10.10.1
Next on the router we’ll need to add a route back so the router knows about the networks attached to switch A. Generally adding a static route on most routers is done with the following command:
ip route {Network} {Wildcard Mask} {Next Hop-IP}
In our case here are the 2 static routes we could use.
Ip route 172.16.20.0 0.0.0.255 10.10.10.2
Ip route 172.16.30.0 0.0.0.255 10.10.10.2
The routing that we enabled on Switch A will enable traffic from the other VLANs to traverse over port 1/e4 to the router, connecting us to external traffic. The routes we added to the router allow the traffic to flow back to the switch over port 1/e4.
Layer 3 + Layer 3
In some situations we have two switches, each setup to route for its own broadcast domain, which we want to connect together. In this situation we no longer have a need to use Trunk or General mode between the switches. Instead we can create a common VLAN that will be used for the connection between the two switches.
To create this VLAN we will run the following commands on both switch A and B
console(config)# vlan database
console(config-vlan)# vlan 6
console(config-vlan)# exit
console(config)# interface vlan 6
console(config-vlan)# name Connection
console(config-vlan)# exit
On switch A we assign an IP address to VLAN 6 and enable routing on the VLAN.
console(config)# interface vlan 6
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.60.1 255.255.255.0
console(config-if-vlan2)# exit
On switch B we assign an IP address to VLAN 6 and enable routing on the VLAN.
console(config)# interface vlan 6
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.60.2 255.255.255.0
console(config-if-vlan2)# exit
On both switch A and B we place the connecting ports into Access mode for VLAN 6.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 6
console(config-if)# exit
We then need to make some changes to switch B now that it is layer 3 and not layer 2 and has its own broadcast domain.
We will enable routing on Switch B
console(config)# ip routing
What used to be VLAN 2 and 3 will now be VLAN 4 and 5 for our separate broadcast domains.
Switch B we assign an IP address to VLAN 4 and enabling routing on the VLAN.
console(config)# interface vlan 4
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.40.1 255.255.255.0
console(config-if-vlan2)# exit
Switch B we assign an IP address to VLAN 5 and enabling routing on the VLAN.
console(config)# interface vlan 5
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.50.1 255.255.255.0
console(config-if-vlan2)# exit
On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 4.
IP Address:172.16.40.11
Default Gateway:172.16.40.1
Client connected to access port for VLAN 5.
IP Address:172.16.50.11
Default Gateway:172.16.50.1
The end result should look like this.
Troubleshooting
If we are having issues with connectivity, we may need to place some static routes in place to help traffic to the next hop in the network.
On switch A we configure a static route to help traffic to the next hop in the network, which is the router.
console(config)# ip route 0.0.0.0 0.0.0.0 10.10.10.1
The external router will also need a path defined back to all networks/VLANs.
To check the status of a port we can use the command. Show interfaces detail, this will help us see the port status. For example to check the status of port 48, we would run this command.
console# show interfaces detail ethernet 1/g48
To check routing paths:
console# show ip route
The IP address of the network for each VLAN should be listed as C – Connected. Then also a path or default route to your upstream router.
We can use basic ping commands from a client to help test where connectivity is dropping off at. By doing this we can narrow down where in the network to start troubleshooting.
-Ping from client to default gateway, being the VLAN the client is in access mode for. If this fails then we may need to double check our client settings making sure the proper IP and gateway are being used.
-Ping from client to the ip address of the switch the client plugs into. If this fails we may not have VLAN routing enabled on the VLAN the client is in.
-Ping from client to another client on same VLAN, same switch. If this fails we need to check on client settings, IP address and gateway.
-ping from client to another client on different VLAN, same switch. If this fails we need to double check the VLAN routing commands are in place.
-ping from client to the ip address of the next switch in the network. If this fails then check Trunk port configuration from switch to switch, ensuring the VLAN is added to the Trunk port.
-ping from client to another client on same VLAN, different switch. If this fails, check Trunk port settings.
-ping from client to another client on different VLAN, different switch. If this fails then check trunk settings and VLAN routing configuration.

Derek,
I tried to draw my prefered setup for this network configuration.
I would create a Team with the two 1 GBit NICs and use it for Domain, DNS, Backup and any SystemCenter Agents.
I would also Team the two 10 GBit NICs and than assign it to a Hyper-V Switch for the VMs. In Windows Server 2012 it is posible to create vNICs for the Management OS that use this Hyper-V Switch (Converged Network Design). I would create two vNICs SMB1
and SMB2 to use them for Cluster and Livemigration traffic with SMB Multichannel. If your storage system supports SMB Multichannel you can also use both as storage NICs (but this depends wich vendor you have).
Hope this helps.
Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa |
www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

DFSR Replication Event ID 1202 The DFS Replication service failed to contact domain controller Additional Information: Error: 160 (One or more arguments are not correct.)

Hi,
hummmm...
The client had 1 Server with AD and All Apps, IIS, Terminal Servers (30 device Cal), File Server, SQL2008R2 on it
Task: Install new AD server promote it to DC, bring in 2nd server, Replicate the File Server (DFSR) on these 2 servers, and demote it to standard server.
1) Old AD with name "Server" with OS-2008R2 SP1 and is a DC.
2) Brought in a new server "PrimaryAD", Installed 2008R2, done DC Promo, and added it as Additional Domain controller
3) Transferred roles from old server "Server" to "PrimaryAD"
4) Brought in a new File Server replicating server "Backup-Server"
5) Copied all the data from Server to Backup-server as DFS initial file sync with robocopy
6) here the problem started, after the copy finished, next morning the "Server" server crashed.....
7) thank god the data was backed up on Backup-server. but we didnt get the time to Demote the server "Server" and remove AD from it.
8) Since AD was replicated so "PrimaryAD" was are DC, brought 2nd Server "SecondaryDC" as additional domain controller.
9) we cleaned up the metadata and used ASIEDIT to clean the remaining stuff.
10) the "Server" server was formatted and renamed as "Primary-Server" and OS2008R2 SP1 was installed with rest of required apps
11) so now the PrimaryAD the DC, SecondaryAD the Additional Domain controller, Primary-Server the mail server and File server, the Backup-server, the replicated server.
Now configured DFS Replication from Primary-Server to Backup-server and receive following Event ID 1202
If i Configure DFS Replication as follows
PrimaryAD <<>> SecondaryAD -= Works... no errors...
PrimaryAD <<>> Backup-Server = Creates but Dosent works Event ID 5012, error The DFS Replication service failed to communicate with partner BACKUP-SERVER, Additional Information: Error: 9026 (The connection is invalid)
PrimaryAD <<>> Primary-Server = Dosent creates replication job just hangs,
on primaryad continious Eveni ID 10009, DCOM was unable to communicate with the computer "SERVER" using any of the configured protocols
......something on PrimaryAD is still trying to connect to old corrupt AD server "Server"
No errors with AD replication, SYSVOL & Netlogon shares also working fine and accessible.
DFS Diagnose report says
DNS name: backup-server.mydomain.com
Domain name: mydomain.COM
Reference domain controller: -- (HERE there is NO DOMAIN CONTROLLER mentioned)
IP address: 192.168.1.248,192.168.1.251,::1
Site: Default-First-Site-Name
Forgot to mention, gave full rights with ADSIEDIT to DFSR-LocalSettings for all server to Administrator and read permissions to "Authenticated Users"
DFSRDIAG POLLAD throws following error
c:\Dfsrdiag pollad /verbose
[INFO] Computer Name: BACKUP-SERVER
[INFO] Computer DNS: Backup-Server.mydomain.COM
[INFO] Domain Name: mydomain
[INFO] Domain DNS: mydomain.COM
[INFO] Site Name: Default-First-Site-Name
[INFO] Connected to WMI services on computer: Backup-Server.mydomain.COM
[INFO] Invoke PollDsNow() method on Backup-Server.mydomain.COM
[ERROR] PollDsNow method executed unsuccessfully. ReturnValue: 12 (0xc)
[ERROR] Failed to execute PollAD command Err: -2147217407 (0x80041001)
Can anyone point me to any direction which can lead to resolution of this ERROR and make DFS_R work..
Thanks
bikram

Hi,
It seems that DCPROMO did its work without complaints, still the DFSR references remained in AD. You could refer to the article below to clean up the DFS Replication object.
How to remove data in Active Directory after an unsuccessful domain controller demotion
http://support.microsoft.com/kb/216498
In additional, please refer to the following thread to troubleshoot the issue:
DFS is not working anymore.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/953be9ef-e9e3-4885-a5c4-47fc475ba562/dfs-is-not-working-anymore?forum=winserverfiles
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

10Gb Networking best practices

I'm looking for good guidance on Hyper-V 2012 R2 network configuration best practices for a converged server. Meaning, dual 10Gb NICs and using SMB 3.0 file shares for storage. The servers also have two 1Gb NICs. I'm very familiar with VMware, but ramping
up on HV networking best practices.
Blog: www.derekseaman.com, VMware vExpert 2012/2013

Derek,
I tried to draw my prefered setup for this network configuration.
I would create a Team with the two 1 GBit NICs and use it for Domain, DNS, Backup and any SystemCenter Agents.
I would also Team the two 10 GBit NICs and than assign it to a Hyper-V Switch for the VMs. In Windows Server 2012 it is posible to create vNICs for the Management OS that use this Hyper-V Switch (Converged Network Design). I would create two vNICs SMB1
and SMB2 to use them for Cluster and Livemigration traffic with SMB Multichannel. If your storage system supports SMB Multichannel you can also use both as storage NICs (but this depends wich vendor you have).
Hope this helps.
Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa |
www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

Mail bounces from one server only?

I use mail all the time with my .Mac account , as well as a Pop server account, all basically glitch free. I have one customer in Germany however, who when I send to him thru my .Mac account, the msg bounces back immediately from the mail server with (an example) of the message
The original message was received at Mon, 14 Jan 2008 05:40:07 -0800 (PST)
from asmtp002-s [10.150.69.65]
----- The following addresses had permanent fatal errors -----
<[email protected]>
(reason: 550 (result of an earlier callout reused).)
----- Transcript of session follows -----
451 4.4.1 reply: read error from mail.conradjacobson.com.
... while talking to backup-mx.hamburg.cityline.net.:
DATA
<<< 550 (result of an earlier callout reused).
550 5.1.1 <[email protected]>... User unknown
<<< 503 valid RCPT command must precede DATA
Reporting-MTA: dns; smtpoutm.mac.com
Received-From-MTA: DNS; asmtp002-s
Arrival-Date: Mon, 14 Jan 2008 05:40:07 -0800 (PST)
Final-Recipient: RFC822; [email protected]
Action: failed
Status: 5.1.1
Remote-MTA: DNS; backup-mx.hamburg.cityline.net
Diagnostic-Code: SMTP; 550 (result of an earlier callout reused).
Last-Attempt-Date: Mon, 14 Jan 2008 05:40:29 -0800 (PST)
From: YYY <[email protected]>
Date: January 14, 2008 11:40:01 AM GMT-02:00
Who do I contact to see about this? Is it their server that rejects my msg (XXX's added for privacy, just in case) or a .Mac issue? It's one of two addresses, both in Germany oddly enough.
Any help appreciated.
Thanks
Doug

You didn't say whether you've been able to reach your customer using a different SMTP (outgoing) server - though I'd be surprised if you could.
Anyway, as best as I can parse this: mac.com contacted cityline.net which contacted conradjacobson.com. While cityline was talking to conradjacobson, there was a transmission error (probably while sending RCPT, i.e., the "To:" address). When someone (mac.com ?) then tried sending DATA (i.e. the body of the email), cityline said "error, you can't send the message until we've established that the address is valid". Since the "To:" address was never validated, the overall failure was chalked up as a conventional "addressee unknown" error.
If your correspondent works for Conrad Jacobson, you may want to go to their website & use their web-based email form to try contacting him.

How do I create a backup DNS server?

Hi All,
I've got my production server (Xserve Intel) running 10.6 and it is our primary DNS server. I've gotta take it down to do some work on it, but by doing so, no one in the organization will be able to access the internet.
I'd like to set up my old Xserve (G5, running 10.5) as a backup DNS server that can handle the DNS requests whenever I need to take the main server down. Unfortunately, I'm kind of a DNS n00b.
What is the best way to go about this?
Thanks,
Chris

Oh, quite embarrassing. I complained about not understanding the author of the article when I was actually speaking to the author. How rude! Apologies, kind sir.
I've now got it set up correctly with your help, it seems. I've just got a few other questions regarding the Secondary DNS Server if you don't mind:
1) Do I set any forwarder IP Addresses on the secondary server? Should I put the same forwarders that I use on my primary, or should I put the IP address of my primary in there, or should I just leave it blank?
2) *Edit - Ignore question 2; found the answer in your guide*
3) When I look at the secondary zones, they don't seem to be populated with any data. . . Does this mean that the secondary server is completely reliant on the primary server to function correctly? In other words, *when I take my primary server offline, does the secondary server still work?*
Thanks,
Chris
Message was edited by: cscrofani

Backup users, groups, DNS and other settings

Hi,
I was wondering if it is possible to export or backup Users, Groups, DNS, Profile manager, Open Directory and file sharing records and settings?
Thanks in advance

Time machine is the only built in apple way that I know of
All the other export features that snow leopard server had have been removed from ML server as far as I know
You could use superduper or carbon copy cloner to image the server

DPM 2012 R2 UR4 and BMR backup from physical 2008 R2 (DC, DNS, DHCP,WSUS, WDS)

Hi,
I'm completely lost.
We updated from DPM2010 (2008 R2) to DPM 2012 R2 RU4 (2012 R2).
Clean install. Same hardware. Everything went quite smoothly.
Our new (and also old did the same thing) DMP protects some Hyper-V guest on our 2008 R2 Hyper-V cluster, one Exchange (2010) DB's and SQL 2008 R2 DB's and one physical server - 2008 R2 (DC, DNS, DHCP,WSUS, WDS ~160GB of data).
Currently we are using some Buffalo Terastation's III (TS-RIXL) iSCSI SAN storage to hold our DPM protected data.
Configured as RAID 5.
Our new DPM server is connected to those iSCSI devices using built in MS iSCSI initiator via secondary NIC on this server using dedicated iSCSI subnet.
Everything seems to be fine unitil System State and BMR (I'v checked both) runs.
Basically my iSCSI NIC shows Write about ~170Mbit/s and Read about 520Mbit/s when backing up virtual machines, Exchange or SQL.
When it comes to System State and BMR backup the trouhgput is MUCH slower (about 65Mbit/s) and I can not figure out why. I understand that the BMR backup initiates direct writing to the DPM created and shared replica volume on my iSCSI NAS (my wording
might be not correct but basically I understand how this works). But I don't understand why the speed is so much slower. I'v tried everything, googeled around, changed NIC drivers, firmware etc. No luck.
If I just copy some big ISO file from/to server to DPM or vice versa the speed is arount 100MB/s (as reported by windows itself). So it seems to able to utilize full network speed. But why this backup is so slow? I'm excpecting to see speed about ~170Mbit/s
because it corresponds my iSCSI Write speed as seen when backing up hyper-v guests and DB's..
What I'm doing wrong?
Any help is appreciated :)
rgds Sven

Hi Sven,
Sometimes BMR is slower than backing up virtual machines (VHDs). If there is a free local disk, please test to do a backup locally to see the speed. From your description a common backup works much faster so let's see if it is the backup speed which causes
the issue or not.
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

LAN Backup on DNS-320L

Hi,
I am using a DLINK NAS (DNS-320L) and I am trying to set up a local back up of a folder on OS X and I keep getting a fail when I test the link out. I have managed to get it working on a PC, so I know I am on the right path.
I'm obviously in 'Local Backups'. I have 'LAN Backup' checked and have the folder option checked. The IP of the NAS is 192.168.0.15 and the folder I'm trying to backup on the Mac is /Users/joelcampion/Documents, and is set as a shared folder. Therefore, I have tried \\192.168.0.15\User\joelcampion\Documents and this is when I get the fail. I have tried with and without the account details (username and password) and I've added an extra '\' at the end as well.
My questions are, am I doing this correctly? Are there any obvious things I'm doing wrong? Or does this just not work on a Mac. Do my folder paths look correct? Is there a folder before /Users that I should be adding to the link?
Thanks
Joel

Thank you. I was able to test and successfully backup to several network shares in my environment.
After reviewing the logs it does appear to confirm a permissions issue:
10:51:50.286|ERROR|54|Rim.Desktop.BackupRestore|0|Read Access to backup file failed. The backup folder is read only.
Would it be possible to create a new test share permissioned for everyone to have a full acccess to and test? You could then apply permissions from there to narrow the issue.
Did someone help you? Click Like! Did a post solve your issue? Click Accept as Solution!

Sles11 named as OES2-Backup-DNS?

Hi,
I was wondering if it would be possible to use the named service of a Sles11 to work as a backup server for our OES2 DHCP/DNS setup?
I mean, novell-named is not all that different to the default Linux one, right?
If so, how would I go about doing that?
Thanks for your help!

Originally Posted by amacher
Hi,
I was wondering if it would be possible to use the named service of a Sles11 to work as a backup server for our OES2 DHCP/DNS setup?
I mean, novell-named is not all that different to the default Linux one, right?
If so, how would I go about doing that?
Thanks for your help!
DNS would be easy. Create the zone as a slave zone on the sles box, point it to the master, all done.
DHCP is a different issue. OES has a DHCP Failover option, but to properly use the SLES as a DHCP back for OES, you would probably have to cluster the two servers and then the dhcp service. DHCP failover may work, but I haven't mixed environments like that while trying to implement that option.

DNS probelm with along the Who changed my OS desktop ? Win8p not prepare me any Backup for previosu one ?

June 05 2013 17:46 win8p5
I am Host/Server sometimes looks like , as control the gpedit.msc and flush ipconfig / registerdns, flushdns... but not always?
Who did the OS changed ANYWAY? I did not. Since OS win8pro5 has not ready me any OS backup yet.
The desktop unexpectedly changed from mine to previous of mine while Win8p there is not any OS backup for me ?
Who "Modified it" for me for what , why not I was not noticed please?
See the edited attach please...
BLEUOISOU

gp such not the domain , users , network share unsimilar !
Feb. 23 2015 10:49 w7uw8.1p Updated
GLF2 was ever mine PCname with McAfee who is not allowed to change the PCname. GLF, GLF2 were 1st group label series when after the unlimited online back mcafee introduced into , PCname changed into some of by the Time-2nd-series PCname. That maybe
cause the complex with McAfee or Intruders who has copied the PCname & MAC & IPv4 working on the network to today.
Since there two Devices shown with the same PCname at the McAfee account. DNS just resolve the IP by a 24hr or 3 times or reboot pc time detect the IP in the dyndns solution currently.

Unity Express Backup: Can we use DNS name of FTP server instead of IP address?

Gentlemen!
In the Unity Express system, can we use DNS name of FTP server (Microsoft FTP Server) instead of IP address in the General configuartion for Backup Server?
e.g. FTP://FTP_Server_Name/Directory
Additionally we need to configure/add DNS server name in the Domain Name settings under system menu. Is there any additional configuration would require for setting up FTP server with DNS entry & above config?
Regards,
Sky_Voice

Hi Sky_Voice,
This is a supported config
Backing Up and Restoring Data
Last Updated: May 12, 2010
Cisco Unity Express backup and restore functions use an FTP server to store and retrieve data. The backup function copies the files from the Cisco Unity Express application to the FTP server and the restore function copies the files from the FTP server to the Cisco Unity Express application. The FTP server can reside anywhere in the network if the backup and restore functions can access it with an IP address or hostname.
We recommend that backups be done regularly to preserve voice-mail messages and configuration data.
Backup and restore commands are available in configuration mode and in offline mode.
•In configuration mode, commands are available to set the following parameters:
–Number of backup files to keep (the oldest file is deleted).
–URL of the FTP server where the files will be stored.
•In offline mode, perform the backup or restore procedure. Decide the following:
–Type of files to be backed up: all files (configuration and data), only configuration files, or only data files. Data files consist of voice-mail messages. Configuration files consist of all other system and application parameters.
–URL of the FTP server where the files will be stored.
http://www.cisco.com/en/US/docs/voice_ip_comm/unity_exp/rel3_2/administrator/voicemail/11bkrst_ps5520_TSD_Products_Administration_Guide_Chapter.html
Cheers!
Rob

Practical Backup DNS

Hi all,
Let's say I have two XServes. Mail service is running on both of them. They each have a respective MX record in our domain.
One day, the connection to the primary (higher precedence) mail server is severed. Other people's mail servers attempting to contact our primary defer to our secondary (lower precedence). Assuming the secondary is online, mail servers successfully contact our secondary and deliver mail for the domain.
Now what?
There seems to be very little documentation regarding the "what happens next" of this scenario, which is quite important. Our older Cobalt RAQs would automatically hold the mail until the primary was available for contact, then re-deliver to the primary. Is this a typical out-of-the box scenario?
What I need next are the practical considerations for this configuration. If automatic redelivery does not occur, should I duplicate all my users and mailing lists on the secondary, then configure the clients to check both the primary and secondary servers for mail? How is the secondary MX typically and/or intended to be used?
Thanks.

Now what?
Your secondary (if configured properly) will regularly try to deliver held mail to the primary. As soon as the primary is up, this will happen.
There seems to be very little documentation regarding
the "what happens next" of this scenario, which is
quite important.
There is tons of information. Google is your friend.
Our older Cobalt RAQs would
automatically hold the mail until the primary was
available for contact, then re-deliver to the
primary. Is this a typical out-of-the box scenario?
It's not an out of the box scenario. it's a matter of configuring Postfix correctly. I have posted links to this in at least 5 other threads.
What I need next are the practical considerations for
this configuration. If automatic redelivery does not
occur, should I duplicate all my users and mailing
lists on the secondary, then configure the clients to
check both the primary and secondary servers for
mail?
No. This defeats the purpose. You should fix the primary and delivery will happen. The secondary will not have mailboxes you can access, only a queue.
How is the secondary MX typically and/or
intended to be used?
As a backup queue. Nothing else.

Backup DNS Records

Afternoon,
Is there a way to create a back-up A record in order to provide redundancy?
I'm currently in the middle of setting up a DR site and looking to find a way to have a set of DNS record pointing at existing servers host name but with different IP addresses so in the event that we require to bring a replicated server up at the DR site
the DNS record would automatic switch over after the TTL has expired on the primary link.
our DNS service runs on a windows server 2012 environment in a cluster of 3 servers for redundancy.
Thanks

To answer/address the question about the same records with different IPs, unfortunately it doesn't work that way with AD. The IPs registered are absolute for the service locations, and they must be consistent across the organization for AD DC to DC communications
including replication, and client to DC communications. If you attempt to alter them, it will cause numerous errors and additional headaches that I'm sure you do not want to deal with.
Just setup two DCs at the DR, do not make them GCs. Just make them GCs in case a down issue occurs. Depending if you have 3 or more sites, this may also require to make individual site links for each site and disable BASL. The reasons are long winded,
but it's technically how AD works. You can design around it, but you can't mess with DNS. And keep in mind, just because they are up, services and client apps may not be so forgiving to "see" the DR servers until they've been restarted.
So there's more to this than it appears.
You can read up in this stuff in the following link:
AD Site Design, DNS & the DC Locator Process, and Auto Site Link Bridging, or Bridge All Site Links (BASL)
http://blogs.msmvps.com/acefekay/2013/02/24/ad-site-design-and-auto-site-link-bridging-or-bridge-all-site-links-basl/
The blogs below discusses:
WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB). Troubleshooting the browser service.
Client side resolution process chart.
The DNS Client Side Resolver algorithm.
If one DC or DNS goes down, does a client logon to another DC or use the other DNS server in the NIC?
DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders or more than one IP in the NIC's DNS list)
Client side resolution process chart
Published by Ace Fekay, MCT, MVP DS on Nov 29, 2009 at 10:28 PM 1764 1
http://blogs.msmvps.com/acefekay/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm/
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Dns backup

Similar Messages

Maybe you are looking for