DPM on multiple sites with ML6000

Hi,
I must implement a new backup infrastructure. On the central location I will backup the servers with DPM2012 sp1 (Dell PowerEdge R720xd). On a co location I have another Windows 2012 server (PowerEdge R720xd). The central DPM1 server use the server from
the co location as storage server (SMB) for long term backup jobs.
On the co location I have a Dell PowerVault ML6000 tape robot connected to the location server with FC. (I can not place the tape robot in the central location (space problem)).
Can someone help me with my questions?
1: If I connect the tape robot with the server on the co location can i use it from the central DPM server?
2: Is there anyone who knows a way to communicate with the tape robot with iSCSI (can i buy something)
3: Is it smart to install DPM either on the server on the co location.
Thanks

Hi,
There are a few problems with your implementation.
A) Windows 2012 iSCSI targets (which use virtual hard drives) as a DPM storage pool is not a supported configuration.
B) DPM does support tape
library sharing, but only if both DPM servers have direct access to the tape drives. That would mean DPM server in the Datacenter would also need a fiber connection to the tape library located in the C0-Location center.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Similar Messages

IWeb 09 Multiple sites with multiple MobileMe accounts

Hi guys, one more for you,
i have my MobileMe account and my website, i also create to more small sites just for testing purpose, i want to know if i can have multiple websites on iWeb and each one with their own MobileMe account.
(e.g)
-- site1 ( [email protected])
-- site2 ( [email protected])
-- site3 ( [email protected])
i have only One Mac computer and i have to work on 3 different sites with only this computer.
Help please... I am new to Mac world ( but i love it )

Do you really have 3 separate users or just want to publish 3 separate sites? If it's the latter then you can do all of them with just one MMe account. In your domain file with three sites the top size will be the "alpha" site in that if you enter the minimum URL, http://web.me.com/YourMMe_AccountName/, the top site will come up. To go to the other two sites you'll need to add the site name on the end of the URL above, i.e. http://web.me.com/YourMMe_Account_Name/Site_1name/.
In this economy if you can do what you want with one account that's saving some $$$$.
OT

Muse uploading multiple sites with same domain?

It seems that when i upload my site via FTP, if i type the domain without www. and only Http, it is uploading and creating a separate site then when i submit an update with www.
www.threesistersgarden.org
http://threesistersgarden.org/
How can i fix this issue?

Hi Ho Yin Wong,
Are you referring to entering the domain name in the 'FTP server' field or the 'Site URL' field?
- Abhishek Maurya

Iweb 09 multiple sites and domains

I have had one iWeb site working properly for the last few years with past iweb versions with no problems. I purposely upgraded to 09' so I could publish multiple sites with individual domains. I created a second and third site and they seemed to up load ok via either the iweb FTP or Cyberduck. (Im not using Mobile me) When I'd go to the web page all I'd see was "under construction". I triple checked if erverything was loaded correctly on the server. They looked just like the original site that had been working and was in the right order.
I got on the phone with Apple yesterday for nearly 3 hours and two different techs. After all their help/suggestions I seemed to have lost my original working site. The site (.sites) shows up in the iWeb library folder and when I click on it to open, iWeb seems to be opening okay as I can see the file menu. However there is NO WINDOW. All I see is my desktop like the window was closed or something. (It wasn't) I've clicked on my other (non working) sites from the same iWeb folder and they open up just fine.
Needless to say, my original problem has now turned into two problems. Apple is confused and has turned the issue over to an engineer and I am waiting to hear back. The tech told me Apple might be adding a software fix soon because others have had uploading multiple sites issues.
Has anyone had a similar experience or suggestions? I'm proficient on the machine but this is ridiculous.

My suggestion would be to ignore the iWeb FTP until it works.
I still keep my sites on separate domain files, publish to a folder and optimize and upload with Web Site Maestro.
Until Apple fixes their FTP and adds optimization or rebuilds iWeb to create less cumbersome files, this feature is useless to anybody who wants their website to download in a reasonable time and have an even chance of loading in IE.

Multiple site simultaneous upload

Is there a way to simultaneously upload open pages from multiple sites with a single keyboard shortcut or extension?
eg. I have pages A, B and C open from sites 1, 2 and 3. I make changes on all 3 pages and want a single action to upload them all, one after the other, without any further actions from me.
Thanks for any information.

No, there is no way to do this. Well, there is (sort of, depending on exactly what you are trying to do) but it requires that all three sites be on the same server and use a database to populate the pages.
I assume that you have 3 sites that are identical with different domain names? If so, the way that I have gotten around this is to just have all three sites point to the same place so that when you update one you update all three.
Brad Lawryk
Community Expert: Dreamweaver
Usergroup Manager: Northern British Columbia Adobe Usersgroup

Multiple websites with iWeb?

I'd like to create multiple sites with iWeb. For instance, I'd like a personal site and a business site. Can this be done or are we only allowed a singel website?

sjesser...
Since iWeb goes through every page in its calculations when publishing, you might find having two sites together in the same instance of iWeb to be cumbersome if you update one or the other site frequently. Additionally, if you ever plan on hosting your personal and business sites in different places, it will be impossible to edit or publish your two sites independently of one another.
The solution to this would be to keep your personal and business sites in different instances of iWeb....different Domain files. Since you have not yet made your second site, this may be a good time to adopt this practice. You can still publish both sites to the same .Mac account....the difference is that iWeb only has to go through one site when you publish.
Check out this program called iWebSites...
http://mistergregg.com/cocoadrillosoftware/
This software will help you create and maintain fully separate websites with iWeb in an easy to use interface. This is the best time to start.....BEFORE you make that second site! Best of luck!

Azure multiple site-to-site VPNs (dynamic gateway) with Cisco ASA devices

Hello
I've been experimenting with moving certain on-premise servers to Azure however they would need a site-to-site VPN link to our many branch sites e.g. monitoring of nodes.
The documentation says I need to configure a dynamic gateway to have multiple site-to-site VPNs. This is not a problem for our typical Cisco ISR's. However three of our key sites use Cisco ASA devices which are listed as 'Not Compatible' with dynamic routing.
So I am stuck...
What options are available to me? Is there any sort of tweak-configuration to make a Cisco ASA work with Azure and dynamic routing?
I was hoping Azure's VPN solution would be very flexible.
Thanks

Hello RTF_Admin,
1. Which is the Series of CISCO ASA device you are using?
Thank you for your interest in Windows Azure. The Dynamic routing is not supported for the Cisco ASA family of devices.
Unfortunately, a dynamic routing VPN gateway is required for Multi-Site VPN, VNet to VNet, and Point-to-Site.
However, you should be able to setup a site-to-site VPN with Cisco ASA 5505 series security appliance as demonstrated in this blog:
Step-By-Step: Create a Site-to-Site VPN between your network and Azure
http://blogs.technet.com/b/canitpro/archive/2013/10/09/step-by-step-create-a-site-to-site-vpn-between-your-network-and-azure.aspx
You can refer to this article for Cisco ASA templates for Static routing:
http://msdn.microsoft.com/en-us/library/azure/dn133793.aspx
If your requirement is only for Multi-Site VPN then there is no option but to upgrade the device as Multisite VPN requires dyanmic routing and unfortunately there is no tweak or workaround due to hardware compatibility issue.
I hope that this information is helpful
Thanks,
Syed Irfan Hussain

Multiple Web Sites with Personal Domain Names - Overview

I have read through the last 10 pages of these discussions and have almost worked this out, but I need some help.
Problem:
I want to publish and edit two separate web sites with their own, individual, personal web addresses
from the same user account on the same Mac using iWeb '08 (2.0.2) and my .Mac account
_So far:_
I have purchased and registered the two domain names (with Cheap-DomainRegistration.com)
I have configured the CNAME to point to web.mac.com, and "Set up a Personal Domain" in iWeb successfully, but using a separate Mac for each web site.
The two sites work great.
_What (I think) I need to know:_
(excuse me for copying these posts out, but I can't find a way to link them to this post)
1) Should I be using iWebSites as suggested by Old Toad (posted Jan 24 in response to StAnNe's "Multiple Websites--HELP!!!")?
I use iWebSites to manage multiple sites.. It lets me create multiple sites and multiple domain files.
2) Should I be using Mireille's approach (also posted Jan 24 in response to StAnNe's "Multiple Websites--HELP!!!")?
Yes you are correct in the thought that with a family pack you can use different accounts and that is the easiest way to upload with one click to .mac. But it is still possible to publish differents sites to one .mac account if that is all one has. Even if the sites are in one domain file each purchased mysite.com domain name purchased can be pointed to a different page in the site
Look at it this way
Original Poster has
site1 page 1 page 2 and so on
then he/she has brothersite page 1 and so on.
They each have a domain name purchase wherever
then site1domain.com is forwarded to site 1 page1
and brotherdomain.com is forwarded to brothersite page 1.
Even though both sites are in the same file they do not have anything to do with each other.
This is one possibility there are others but for a novice user this could be the way to go for simplicity.
(Mireille, if you're there, can you clarify what you said - thank you)
3) Would I use Roddy's fix (posted Jan 23 in response to canadensis' "Publishing Multiple Websites?")?
Here's an example of how you can separate two websites that are on the same domain file.
Quit iWeb
Create a new folder on your desktop and call it "iWeb Sites".
Inside this folder create two more - Website A, Website B.
Go to Home Folder/Library/Application Support/iWeb and copy your domain file - command C
Paste this into folders A and B - command V - and also paste a copy of it somewhere else - like in Docs - in case you make a mistake!
Double click the domain file in the folder Website A - this will launch iWeb.
In the left column, delete site B, save and quit iWeb.
Double click the domain file in the folder Website B to launch iWeb.
Delete website A, save and quit.
Drop the iWeb sites folder into your Home Folder.
If you want quick access to this folder you can highlight it and do command L to create an alias to leave on the desktop.
From now on, to launch any site in iWeb you open its folder in the iWebsites folder and double click the domain file.
This is not necessary when you are working on only one site as iWeb saves the domain file of the last site you were working on to Home Folder/Library/Application Support/iWeb. When you open the iWeb application, the last site you worked on will be launched.
Summary:
I'm not sure if some of the answers in previous discussions allow for personal domain names, which is what I need.
I would be very grateful for any suggestions as I'm getting bogged down.
Many Thanks,
Jeff

When you said, "you don't need to do CNAME for both sites…", would this method still allow me to use personal web addresses for both sites?
Yes. With "Ordinary Forwarding" you normally just type your .Mac url (web.mac.com/username/sitename) into a form at the place where you have your name.
I thought I was using 'web.mac.com' as the 'www' CNAME (alias) for my personal domain name (web address), so that when someone typed in my personal domain name they would 'go' to the domain registration location, which would then pass it on to the .Mac server, where my web site is hosted.
That's exactly right. It's just not the only way to do that. Ordinary Forwarding is another way, but it differs in terms of what appears in the address bar of the browser. Either you will see web.mac.com/username/.... or, if you add "masking", you will see your personal name for all pages. The CNAME method results in a address bar that reads www.myname.com/sitename/pagename.html.
Am I way off?
All help gratefully received,
Jeff

Noob needs help with hosting multiple sites

Hello I am new to this multi hosting. I have looked on the forum for answers but haven't found any. I am trying to figure out how to host multiple sites. I have my dns working for my default site "example1.com", but need to know if I need to add another dns record for my second site. "example2.com". Also when I point to the new fold that has the second site in it and I assign it port 82 for testing purposes I get an error message saying 403 access forbidden. I need to find out how get permission to view the site for the public. Its in a separate folder on an external hard drive right now for testing purposes. Can any body help me or point me in the right direction? Thanks so much!!!
-Kcam1999

{quote}
While what you are telling him is technically functional, it is not correct
I beg to differ, Paul. You are the one that is not correct.
CNAMES have been deprecated as of some years ago
What? huh? really?
Please show me any official document that states this (and not someone who just started a rumor because he didn't understand them). Indeed, the DNS RFC makes no such claim.
{quote}
I stand very much corrected. CNAMEs are not officially deprecated. Interestingly, your post cites precisely what happens when CNAMES used carelessly. How many transactions are needed to resolve Apple's CNAME chain below? RFC1912 (http://www.faqs.org/rfcs/rfc1912.html) has some recommendations that suggests Apple's own network folks have, like me and perhaps even others here, some learning to do. Is that a 'best practice?'
{quote}> Then make sure you tell Apple since this site depends on the use of CNAMEs:
dig discussions.apple.com
discussions.apple.com. 492 IN CNAME discussions.apple.com.edgesuite.net.
discussions.apple.com.edgesuite.net. 4427 IN CNAME a1399.b.akamai.net.
a1399.b.akamai.net. 2 IN A 128.241.220.82
a1399.b.akamai.net. 2 IN A 128.241.220.72
In fact, it uses TWO CNAMES in a chain. Oh my.{quote}
From RFC1912 (which I'm sure many have now read here), section 2.4 is as follows:
{quote}... having chained records such as CNAMEs pointing to CNAMEs may
make administration issues easier, but is known to tickle bugs in
some resolvers that fail to check loops correctly. As a result some
hosts may not be able to resolve such names.{quote}
{quote}> It is not valid to say "don't use these because they could cause problems'. A records can be just as problematic, as can PTRs. Let's not even talk about MX.{quote}
How, exactly, does is an A record problematic? No chains, no additional lookups, no wasted cycles...
We differ here -- and if we are dealing with a newbie, we don't need to enter into unnecessary complexity UNTIL it is a requirement for their solutions.
{quote}> There are many valid reasons to use CNAMEs in DNS, not least of which is the ease of moving a service if it uses CNAMEs. For example, if you have 10 A records all pointing at the same server and you want to migrate to a different machine you have to locate and update all 10 records. If they used a CNAME to the physical server you could move them all at once using a single change. This is especially important in cross-domain links where you may not control all the origin zone files.
{quote}
You're somewhat reaching here, and it is well beyond the scope of the OP's post or needs (well, until they tell us more about their needs, I suppose). There is nothing difficult about 'finding' and updating the necessary records. The final example you gave is a good one and I'll say THAT is an appropriate use of a CNAME, 'though there are other workarounds for it.
Thanks for keeping me honest.

After installing 2014.3 my site had multiple issues with Google Chrome

After installing 2014.3 my site had multiple issues with Google Chrome. After I rebuilt the home page in 2014.3 the site is still not well. With the old software the site worked well with all the browsers and loaded incredibly. Despite Adobe's claim of a faster load with the new software it is much slower and in Chrome at times it won't load up at all.
The home page had two "Video-Animation light box galleries" by Visual pictures company. One had 12 videos, the other 3 videos. All the videos were streamed from Vimeo. There was also an Edge Animate animation in the middle of the page imported as a .oam file. the rest of the page was nothing special except using some web fonts. Again, these elements worked together well before the update.
After the update everything loads slower in all browsers and in Chrome all types of weirdness happened. Videos would play randomly, all of the audio from all the videos played as the site loaded. Videos would play in the wrong place. Instead of my animation playing a video from the galleries played in it's place instead.
I rebuilt most of the home page using a new video gallery and that helped some what but when I placed the animation.oam file in the page had new issues. To survive, I've taken the Animation out which helped but the functionality is still far from being acceptable. My boss is un my backside, other work is not getting done the stress level is through the roof because I was the one who encouraged using all these new Adobe tools (which I'm paying for personally). Now you broke it with a new update. This is not the first time I've been caught out with problems with updates. I couldn't use SpeedGrade for months following an update. ADOBE MUST VET THEIR

Sorry,
It was slated to go to the Creative Cloud - Muse area. How it got to Photoshop is beyond me.
Bob

LYNC 2010 with Multiple Sites and Pools

We have LYNC 2010 Enterprise Pool in North America with 5 Front End servers, 2 Edge Servers. No Director servers deployed. We want to enable Dial-In Conferencing feature for all users across the Globe (to avoid 3<sup>rd</sup> party conferencing
cost…) and proposing 2 additional pools ( one in EMEA and another in APAC regions). I am looking for best practices to deploy multiple pools on multiple central sites.
Do we need to deploy Director Servers? (Microsoft recommend Director, however is this mandatory for multiple pools?)
How can we handle Simple URLs and DNS entries in multiple Edge pools (edge pool in each frontend pool)?
Do we need to publish different ISA firewall rules for simple URLs and mobility?
As we are not planning to replace PBX now, and only looking to provide dial-in Conferencing Bridge with SIP trunking, what is the best practice to provide site resilience in case one central site is down?
Thanks in advance for your help…
Tek-Nerd

Hello.
1. This is a recommendation and it's not mandatory even with multiples pools. The only point if you don't deploy director is that for the first connection, all sig wil go through one pool (the one behind the srv and dns record) and after this pool redirect
the user to the good one (and also do the authentification) .Also director is made to avoid this type of load on one pool (connection from other pool and from edge authentification), but still not mandatory.
2.Simple URL point only on one entry (or pool of RP) somewhere in the world (after there are some unofficial workaround) but don't forget that behind that there is the external web service URL (for each pool) and also an edge association to one pool. And
the user is really using thoses URL and svc (edge associated to the pool as the ext web url)
For the external web svc & edge association, you can create a local edge pool closer to your internal pool so for those user the media will be closer and don't go trhough the world. (exemple you add one emea pool, the media that come from internet goes
through the emea edge and emea RP handling Lync external web services). But the simple urls still point to your main edge/RP pool.
3. Like point before, not mandatory, recommendation if you don't want your media going around the world and coming back. Be carefull the association is still fixed (depending of the user's pool parameter), so if the user travel still using original edge/rp
settings.
4. You can create multiple trunk with lync so have backup in case of one is no more working. After this is hard to say what is the best, this is depending of your infrastructure.
David

Best way of dealing with multiple sites?

As I make more and more sites the time it takes to "publish to folder" grows because I have all the old sites in my project file, so everything gets re-published to the folder, even old sites I have no interest in editing any more.
What is the best way of handling iWeb so I can concentrate just on the site I'm currently working on without worrying about other sites? Yet, I might still want to leave the possibility open of returning to one of the old sites at some point...
Thanks,
doug

The following is from the iWebSites site:
*How iWebSites Works*
iWeb normally stores a user’s websites in one folder (or package) called “Domains.sites,” in the user’s home library located at “~/Application Support/iWeb/”. It expects this package to be present, but if it isn’t, it will create it when launching iWeb. iWebSites manipulates “Domains.sites” to create more than one website package (a “.sites” file) in the Application Support/iWeb folder. Simply, iWeb opens up “Domains.sites” when it launches, and whatever website happens to be in that package is the website that iWeb uses while running. *iWebSites renames “Domains.sites” when creating a new site*, and it leaves the newly named “.sites” file in the Application Support/iWeb folder. iWebSites enables the user to switch between sites (by creating the appropriate “Domains.sites” package), delete sites, create new sites, and duplicate sites.
So one should open iWebSites first and select which site to open. If iWeb is launched after once opening a site with iWebStes it will open that domain file. If you want to work on a different site you'll need to launch iWebSites and open the desired site file from within iWS so that the file names are changed.
To create a new, separate file click on the New Site button in iWebSites. Then select the New Site (still in iWebSites) and change it's name to something that will reflect the content of the new site. As seen in the screenshot I posted above giving a site a relevant name makes determining which site you want to open much easier.

Managing multiple sites in different iWeb versions - PLEASE HELP!

apnewbie/cyclosaurus/roddy/old toad (and any others more knowledgeable than i):
i've run into a bit of a pickle. i am hoping someone can help straighten me out. i am about to jump out of a window. here's the rundown:
(for starters, i have a .mac account and am publishing to .mac.) i created a site in iWeb 1.1.2 on my work computer (mac book pro). worked great, really lovely. thought to myself, "hey, i'd like to create another site from home, but i don't have iWeb at home (powerbook G4) - i should buy iLife 08 so i can build these things from home and not have personal files on my work computer."
so: i had a site that i created within 1.1.2 with files written to iDisk. i purchased iWeb 08 and would like to have another site, but this one is being created in 2.0. i also am using a personal domain name this time around bought with google apps and hosted by godaddy. i published the new work in progress for a test run and...you guessed it...my original 1.1.2 site was rewritten by the 2.0 site. and the 2.0 site comes up as the standard google search page for domains that aren't up and running. whooopsie.
sorry for the lengthy intro, but that's the background. i guess my specific questions are:
1) i want to be able to maintain multiple sites from iWeb 2.0...can i open my 1.1.2 domain file in 2.0 and successfully bring that site into 2.0?
2) what is the most efficient and easiest way to get both of these sites running in 2.0? right now i have two domain files (created on two different computers).
3) for domain management, is it best to move from the iWeb folder in my home library to different folders (one for each site, with separate domain files, and my 2.0 domain file is NOT called domain, it's the name of the site) to another location? (and of course, i will back these up just in case.) and when i want to update a site, i just open that individual domain file, right? or will these sites publish over each other?
please help. i am at my wits end. i'm sure this is a relatviely simple issue, but i'm new to iWeb.
thanks, thanks, thanks for your help guys.
joojy

joojy,
Welcome to the forums!
First of all, your original 1.1.2 site may not, in fact, have been overwritten. It is quite possible that the site remains in it's position on the iDisk, Web/Sites/iWeb/YourSite, but because you published to the iDisk (.Mac) from 2.0, a different index.html file has been placed in the root level Web directory which is causing the 404 error. Navigate to the directory on the iDisk, using the Go menu in Finder, and look to see what is actually there. Follow this path:
Go/iDisk/My iDisk/Web/Sites/iWeb/YourSiteWillBeHereIfYourLuckIsGood
If your site is there, great; if it isn't, it's not really a problem because hopefully you still have the Domain.sites file on the MacBook Pro and you can republish it if necessary. If it is there, you can modify the index.html file on the iDisk using a text editor and get your url redirected back to where it should be.
Second, do not open your 1.1.2 Domain.sites file with 2.0 until you have a backup of this Domain file. External drives are best for this. Assuming the backup is in place, launch 2.0, choose the Domain.sites file, and click on "update". It will be updated to a Domain.sites2 file. If the site looks ok then continue on with editing/publishing.
Skipping to question (3), by all means, abandon the default location of the Domain.sites file in the Home folder's Library and get accustomed to keeping your Domain files in their own, respective folders. When you want to open one just double-click it.
You are going to encounter difficulties publishing multiple sites in 2.0.2, unless you keep all of the sites in a single Domain file. 2.0 is publishing to a different directory on the iDisk than 1.0; it publishes to /Web/Sites/, as opposed to /Web/Sites/iWeb/. Publishing a site from a separate Domain file erases previously published sites. I have been able to publish multiple sites, from multiple Domain.sites2 files, by mounting the iDisk and actually moving the Site folder back one level, into the root Web folder, and then publishing. When finished, I move it back again. If you have RSS feeds you will probably get a 'file in use' error. The alternative, (other than keeping all sites in a single Domain), is to publish the site to a folder and then manually drop the Site folder into the Web/Sites/ directory on the iDisk. Of course, some .Mac functions are lost when publishing this way.
Work through this info and post back.
-Mark

Multiple Domain files, Multiple Sites, Publishing Problems

I am frustrated beyond belief. I'm an old hand-coder, coming from BBEdit, but I've been using iWeb almost exclusively since its release, because it really is a great product for quick, easy, stylish designs.
However.... In that year, my collection of sites has grown to 12. Discovering that iWeb becomes a major dog when dealing with that much material, I found and followed the instructions - today - to separate my sites into individual domain files, and edit them individually. iWeb is much snappier and publishing goes much more quickly.
The problem? Well... after editing, "Publish to .Mac" rarely works. Only "Publish All to .Mac" will get the site online (something about an error with the index.html file). But "Publish All to .Mac", I've just discovered, DELETES the other websites that I have previous published. All day I've been doing updates and publishing my sites, only to discover that the uploads have all been wiped out by the most recent one!
I'm a big enough fellow to admit that my knowledge isn't total nor perfect - so please, would someone out there with a better handle on iWeb than I (preferably someone who actually deals with multiple domain files rather than someone who thinks they can guess the problem) please clue me into how we make use of this program non-destructively?
I suppose I could always publish everything to folders and upload it to my iDisk (which itself remains ridiculously slow after how many years now? Sheesh!), but that detracts from the elegance of the .Mac integration, the counter features, - not to mention the little fact that I'm a paying .Mac customer and this darn thing should just work, no?

Mark:
I was where you were also. You should give iWebSites a try. It's to iWeb what iPhoto Library Manager is to iPhoto.
I use iWebSites to manage multiple sites.. It lets me create multiple sites and multiple domain files.
If you have multiple sites in one domain file here's the workflow I used to split them into individual site files with iWebSites. Be sure to make a backup copy of your Domain.sites files before starting the splitting process.
This lets me edit several sites and only republish the one I want. Just remember to put a copy of your current Domain.sites file somewhere else on your HD in case the splitting gets messed up. It went very smoothly for me and I now manage 19 or so sites.
Do you Twango?

More than one site with iweb - now my original site forwards to new one

Could anybody help me please?!!
Right. I set up a portfolio website using iweb with a domain from ipage, and that was all fine. Then a few months later, I have set up a website for my Mum's artwork with a new domain bought through the same account on ipage - because ipage allows you to have multiple domains.
Now that I have set up my Mum's site, my own original site just forwards straight to my Mum's. I have checked loads of times that I've entered the right web addresses etc in the bit for the info so that's all correct. I don't know what else to do now. I don't speak the code lingo and am quite basic in my website building knowledge...
Please if there is anyone who can tell me what to do, I'm guessing there's probably a simple solution to this!!
Thankyou!!!
Josephine
P.S I don't know if my version is iweb '08 but it was the only iweb one to select in 'product' options..

Here's how to have multiple sites in a single MMe account with one or more sites having a domain name.
A. All sites are in the same Domain.sites2 files
1 - only one site can use the CNAME method of domain name forwarding and it must the top site in the left hand pane of iWeb.
Click to view full size
2 - the other sites must use URL domain name forwarding which directs the domain name to the site's full MMe URL, http://web.me.com/MMe_Username/Site_Name, or, if there is no domain name, just MobileMe's full URL.
B. Each site is in its own Domain.sites2 file.
Again, only one site can use CNAME forwarding. This presents a problem since CNAME forwarding directs the domain name to the basic MMe account URL: http://web.me.com/MMe_Username/ which uses an index.html file in the root folder of the account, iDisk/Web/Sites. Each time a new site is published or an existing site uses the File->Publish Entire Site a new index.html file is created in that root directory, iDisk/Web/Sites folder, directing the browser to that particular site. This file is what the CNAME method uses to find the site it represents. Therefore some steps must be taken to assure that the index.html file in the MMe Accounts root directory always points to the correct site. This can be accomplished is three ways.
1 - don't use the CNAME method. Just use URL forwarding . This, IMO, is the simplest method as it doesn't requre any additional effort on the user once the domain name has been set up.
2 - use the following method suggested by Wyodor in this topic: Is it possible to have multiple sites when using ur Domain name?
In iWeb domainfile 1:
Create a dummy site : _dummy
with a blank page.
Create your working site : Whatever
Add pages
Publish both Sites to the same same location on the same server.
Your _dummy site is now the default Site.
Check.
In iWeb domainfile 2:
Create/Use your CurrentSite.
Move a page to the top of the Site and back. Publish the Site.
iWeb will create a new index.html file in the root of the server and from now on CurrentSite is the default site.
Check.
From now on, never move your Whatever Site to the top of the list in the iWeb sidebar and never change the page in the _dummy site.
Simply do not touch your _dummy ever again. And never forget that.
3 - use Ethmoid's suggested method in Using two sites - setting one up with separate domain? or republishing the entire site that uses CNAME forwarding. Just making a minor change and publishing the site changes does not create a new index.html file.
The entire site must be republsihing in order to get that new site.
Or keep a copy of the CNAME site's index.html file on your Mac and replace it manually in the iDisk/Web/Sites fodler when necessary.
NOTE: the CNAME method provides a shorter URL: http://www.Domain_Name.com/Site_Name/Page_Name. CNAME does not have masking.
The URL forwarding displays the full MMe URL:   http://web.me.com/MMe_Username/Domain_Name/Page_Name.   With domain name masking that will be shortened to:   http://www.Domain_Name.com for every page of your site.
However, with masking visitors will only be able to bookmark and enter at the first page of the site. If a page is refreshed the visitor is taken back to the first page. Also search engines will only be able to index the first page of the site.
As you know MobileMe will be discontinued next June 30th. With at in mind this might be of some interest to you at this time: Life After MobileMe.
OT

DPM on multiple sites with ML6000

Similar Messages

Maybe you are looking for