Max No Of Servers

I have a tape drive connected to a server which is running Data Protection Manager. I want to be able to backup data from 15-20 other servers to the tape drive connected to that server.
Is there a maximum number of servers which can be backed up by the server attached local tape drive, or is it unlimited? Having not used DPM before, I expect that it works like other 'traditional' backup applications such as BackupExec, NetBackup etc ie
I set the server with the tape drive connected to as a 'media server'.  Is there a config guide available?
Any help would be appreciated.

Hi,
I'm not sure what those 15-20 server are.  Are they A) production servers you want to have backed up to tape individually, or are they B) DPM Servers that want to share the tape library ?
If A - DPM does not work that way. The DPM agent installed on the protected servers can only communicate with the agent on the DPM server protecting it and does not have direct access to the tape library.  You need to add protection for the 15-20 servers
on the DPM server, and have DPM backup the servers data to the locally attached tape library on the DPM server.
If B - Then we do support tape library sharing between DPM servers.  I'm not aware of any hard limit, but there would need to be enought drives and slots to accomodate all the DPM server requirements of free tapes to use for backups when scheduled.
Set up tape library sharing
http://technet.microsoft.com/en-us/library/hh758124.aspx
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

  • Max limit job servers with bods

    Under Tools > options > job server > environment>
    max number of engine processes= 8
    what does that mean, does it mean this BODI can run 8 job servers parallell?
    Are there a max limit of job servers?
    thank you very much for the helpful info.

    Michael, good post .... follow-up question on this:
    Per your replay if I have a job that has 2 dataflows that run in parallel I should be able to see 3 processes being launched.
    And on my linux sever using "ps -f -u myuser" I would see processes like:
    /app/bods/sapbo/dataservices/bin/al_engine -PLocaleUTF8<snip>
    /app/bods/sapbo/dataservices/bin/al_engine -C/app/bods/sapbo/dataservices/log/command<snip>
    /app/bods/sapbo/dataservices/bin/al_engine -C/app/bods/sapbo/dataservices/log/command<snip>
    Correct?
    Mike

  • New FIOS Bundle Installati​on Questions

    Hi all,
    Currently a TWC customer and have been using VZ "wireless" for internet.  Our 2 story Home was set up 16 years ago with 3 each POTS (for hard line phones, Home alarm and dial-up) and 3 each coax hook ups for cable TV. We now have 4 TVs, 3 computers and 3 smart phones running.  The Wife said enough and wants FIOS.
    I prefer eithernet for internet access with wifi available.  Looked into the MOCA thing a few year back with the old actiontec and was not impressed.  VZ site says I have Gateway 300 up/down available to our address with all the other  stuff. 
    I have 1000' CAT6A plenum cable, 700' quad shield RG6 solid core plenum coax, tooling and most connectors needed to upgrade the house.   http://www.swhowto.com/ is a site I found helpfull though out of date on the tech.
    Any and all advice is requested regarding aditional equipment, bridging (if that's still needed) and issues to avoid before I commit this project.
    Thanks.

    Assuming you will subscribe to one of Verizon's triple play bundles (Internet, TV, Phone) w/Quantum TV my recommendation is to:
    1) A new ONT should provide MoCA 2.0. Unless you plan to use COAX for Internet access you really don't need to swap out any MoCA 1.0/1.1 splitters (if in your configuration) for MoCA 2.0 splitters.
    2) I recommend using an Ethernet connection to the ONT for Internet access. This enables you to integrate a 3rd party wireless router (I have the Linksys WRT1900AC) with your home network.
    3) A standard FiOS home install w/Quantum TV will include an Actiontec Rev. I wireless b/g/n GigE router. You will need this router to initially install/activate your service with Verizon. Once established you can replace the Actiontec router if desired. However you will need to, at minimum, configure the Actiontec router to provide a MoCA IP bridge to any Verizon DRV/STBs to support certain MoCA/IP based services (e.g. Program Guide, Video on Demand, etc.).
    4) You will need to rent as many DVRs/STBs/CableCARDs from Verizon for the number of TVs you want service to.
    5) For Quantum TV you have to rent (1) or (2) (at max) VMS1100 Media Servers. Each VMS1100 should be connected to your primary TVs and is equipped w/6 tuners and provide DVR service and network connectivity to other TVs. Client TVs require either a IPC1100 or CableCARD to receive FiOS TV programming.

  • User experience question for High Availability

    Hi Experters,
    Not sure whether this is right forum to post this message.
    If anybody has already captured user experience for the failover environment, will appreciate their help on this. I will give overview of environment. Using PowerHA for ASCS/SCS failover, ORACLE Data Guard for Database failover.
    Trying to capture user experience for the failover environment
    if ASCS/SCS fail,
    App Server Fail (using F5 Load Balancer which should reroute, unless all app server fail),
    Database fail
    with following cases:
    1. User logged in, NO ACTIVITY. I believe NO IMPACT either ASCS/SCS fail or DB fail or App Server fail.
    2. User logged in and run a transaction before failover.
         What will happen in case of ASCS / SCS
         What will happen in case of DB failover
       and  what will happen in case of App server fail (NO High Availability, only redundant app servers.      MAX 4 app servers for each component)
    3. User logged in and run a transaction during failover.
       What will happen in case of ASCS / SCS
         What will happen in case of DB failover
       and  what will happen in case of App server fail (NO High Availability, only redundant app servers.      MAX 4 app servers for each component)
    Not sure which one possible or not. Some case thinking system will hang need to refresh. Some case hour glass and then come back once failover complete. and some case session closed completely.
    Thanks for your time and god bless the knowledge you have.
    Saroj

    just try to answer as much as I can (guess)
    > 1. User logged in, NO ACTIVITY. I believe NO IMPACT either ASCS/SCS fail or DB fail or App Server fail.
    DB failed and SCS failed won't have any impact to enduser, but if app server failed, the user session will lost, user will see a pop up error message at their SAPGUI.
    > 2. User logged in and run a transaction before failover.
    >      What will happen in case of ASCS / SCS
    user wont'be effected during failover if user is doing nothing but idle (replica enqueue is working before failover)
    >      What will happen in case of DB failover
    App server won't be able to do much thing but it's work processes into reonnecting status. it should resume (reconnect to DB) when failover is compoleted. So user should be able to continue the sessions.
    >    and  what will happen in case of App server fail (NO High Availability, only redundant app servers.      MAX 4 app servers for each component)
    user sessions in failed app server will be lost. However user should be able to logon agan if
    1)  logon via group, and
    2) within the group, there is at least one appl server alive.
    > 3. User logged in and run a transaction during failover.
    hanging or
    >    What will happen in case of ASCS / SCS
    if the transaction is using enqueue service, for example, then user will get error message.  otherwise, user won't be effected, e.g. if use is just search a list of order. user wont to able to logon via group during the failover.
    You also should be pepared for user connected through message server, .e.g. http request dispatching through message server directly , or via web dispatchr. user wont be able to connect during the failover.
    >      What will happen in case of DB failover
    user will get error message, transaction will be aborted.
    >    and  what will happen in case of App server fail (NO High Availability, only redundant app servers.      MAX 4 app servers for each component)
    very similar case  as case 2.

  • Number of nfsd threads under Solaris 10

    In solaris 9 it was possible to get the Number of max. NFS Servers (threads) currently running with this command:
    echo "$<svcpool_list" | adb -k
    This does not work with Solaris 10. How can I get this information from the kernel?

    In 10.3 usually work managers are used for this purpose. (http://download.oracle.com/docs/cd/E12840_01/wls/docs103/upgrade/compat.html#wp1117123)
    You can use the 8.1 thread pool if you want (http://download.oracle.com/docs/cd/E12840_01/wls/docs103/perform/appb_queues.html#use81)
    but generally work managers are the preferred way: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/config_wls/self_tuned.html
    Coming back to your original question:
    "I was trying to increase the Min number of executable threads using the following startup argument "set USER_MEM_ARGS=-Dweblogic.threadpool.MinPoolSize=30" in startWeblogic.cmd. But doing so haven't increased the "execute thread total count" to the desired number when I verified it in console."
    Can you add the option in the setDomainEnv file, located in the ${DOMAIN_HOME}/bin directory, for example,
    @REM *************************************************************************
    set WL_HOME=C:\bea\wlserver_10.3
    for %%i in ("%WL_HOME%") do set WL_HOME=%%~fsi
    set BEA_JAVA_HOME=C:\bea\jrockit_160_24_D1.1.2-4
    set USER_MEM_ARGS=-jrockit -Xms512m -Xmx512m -Xgc:throughput -Dweblogic.threadpool.MinPoolSize=100
    set SUN_JAVA_HOME=To check if it indeed shows the number of threads you can follow the steps presented here: http://m-button.blogspot.com/2009/02/tuning-default-workmanager-on-weblogic.html

  • Cluster environment / OBIEE 10.1.3.4.1

    Hi All,
    Can anyone give me more information on Clustering
    1> Can we make schedulers work in a cluster environment ?
    2> Max number of servers in a cluster configuration ?
    Thanks
    Goutham

    The Cluster Server allows up to 16 Oracle BI Servers in a network domain to act as a single server.
    Schedulers can also work in a clustered configuration however only one instance will always be active...
    Active Scheduler. An active Scheduler is a clustered Oracle BI Scheduler instance which actively processes Scheduler jobs. The Cluster Controller determines the active instance at runtime and notifies the Scheduler cluster of this instance.
    Inactive Scheduler. An inactive Scheduler is a clustered Oracle BI Scheduler instance which is not actively processing Scheduler jobs but is ready to take over in the event of an active Scheduler failure. An inactive scheduler is idle at all other times.

  • Two Macs can't see each other on same network

    We have an iMac and a Mac Book Pro on the same apple network at home. The iMac can see and connect to the Pro and exchange files but the Pro can't see the iMac in Go > Network. All sharing settings are the same. Any thoughts welcomed.

    How many machines are on your network? If you have over 7, then here should be an entry called "All..." in Shared in the Sidebar. Click on that. It will show you all the servers that are available on your network. You can also get to this list via Computer (Command-Shift-C) and click on Network.
    Shared in the sidebar shows a max of 7 servers, with Back To My Mac's at the top (if any), then servers you have mounted share points on (if any), then the top 7 (in alphabetical order) servers in Network (a.k.a. "All...").
    Hope that helps.

  • Tuxedo: server with alternate APPDIR directory

    Good day,
    Is there a way to Change the application directory for a group of servers?
    We thought that by providing a different APPDIR in an ENVFILE affiliated to a specific GROUP, it would overwright the APPDIR  variable provided in the MACHINE section.
    But it does not! Our .exe file for the server has to be in the APPDIR (from *Machine section) or it is not found by Tuxedo.
    Any alternative?
    Ash
    Edited by: ashanty on 2012-02-02 16:21

    Hi Ash,
    As the name of the executable. So often the *SERVERS section looks like:
    *SERVERS
    simpapp SRVGRP=APPS SRVID=1 MIN=1 MAX=1
    You can instead use:
    *SERVERS
    /home/app1/simpapp SRVGRP=APPS SRVID=1 MIN=1 MAX=1
    Thus telling Tuxedo where the server binary is located. If you don't specify a full directory path, Tuxedo uses APPDIR as the default. So the following are equivalent:
    *SERVERS
    simpapp SRVGRP=APPS SRVID=1 MIN=1 MAX=1
    and
    *SERVERS
    /home/mine/simpapp SRVGRP=APPS SRVID=1 MIN=1 MAX=1
    where /home/mine is the location of APPDIR.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • Need info on Max number of report servers

    Hi ,
    We have some products( built on oracle 10G and forms 10G) running and for it to run we have 5 application servers .
    The OS is Solaris
    Oracle version is 10G R1.
    We had till now one dedicated Report server .
    But now we need to have more than one report server .
    Can we have more than one report server attached at same time and in working condition ?
    Kindly advise .
    Regards
    SHUBH

    You probably won't get one either. Just wild guesses. This isn't something that Adobe would release as fas as I know.
    If you want my wild guess, I'd say 95% of the computers in the US have Reader but again, I have no real information to base that number on.

  • Is it possible to increase max servers in dashboard?

    Hi,
    I'm using Spiceworks to monitor our render farm. The Issue I have is that we have 50 nodes rendering which I want to keep an eye on, however the dashboard only lets you view 10 nodes at once.
    Is there a way I can increase the dashboard size to allow me to include all our nodes?
    I essentially just need to see the CPU and memory usage to keep an eye out for when the render nodes crash so I can go in and restart the node.
    Any ideas?
    Thanks
    This topic first appeared in the Spiceworks Community

    Hi Mikael,
    The maximum number 20 was set for a reason. The reason is if more than 20 assignments are done then there is a major issue with performance and also object administration. The ACM thus retricts the user from using more than 20 assignments.
    Here is an example for performance:-
    The ACCs can have a parent child relation. The object which is owned by the leaf ACC (bottom most child) can be accessed by
    all the parents, super parents....super duper parents. This object can be loaned to another ACC which again can be a bottom most child of another ACC blood line. Lets have a look at this using numbers.
    We have an Object which is owned by an ACC which is the 100th child of ACC Bloodline1. Now this ACC is loaned to 99 different ACCs and each lie at 100th child of their respective bloodlines. So we have 100 Bloodlines of ACCs and each bloodline has 100 levels. So according to worst case analysis:-
    In worst case to access an user's right over this object we need to parse following number of records:-
    100(Level/bloodline) X 100(number of lendings) = 10,000 records
    Hence when we keep the count to 20, we have to parse only 2,000 records in this case.
    The number 20 is fixed at the domain level and with SAP delivery this should not be changed.
    Regards,
    Ravi.

  • High memory usage in SQL Servers

    Hi,
    I have few SQL servers which are having memory utilization more than 95% when checked in task manager.
    Servers OS - Windows server 2008 R2
    SQL Sever 2008 and SQL Server 2012
    AWE option is not enabled, Min memory setting  - 1 GB and Max memory setting - 80% of the total memory in server.
    SQL process is using less than max memory, when checked in task manager. So i was thinking where is remaining memory.
    Used RAMMAP tool and found memory in AWE, even if i disabled AWE in SQL Server. Please let me know how to avoid AWE.

    Hi,
    Task manager does not always show you correct value so I would advise you not to loot at task manager but in this case since you SQL Server service account does not have Locked pages in memory privilege(LPIM) task manager can be referred
    please use below query to see SQL Server memory utilization
    select
    (physical_memory_in_use_kb/1024)Memory_usedby_Sqlserver_MB,
    (locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB,
    (total_virtual_address_space_kb/1024 )Total_VAS_in_MB,
    process_physical_memory_low,
    process_virtual_memory_low
    from sys. dm_os_process_memory
    Is your SQL server 64 bit version, then no need to enable AWE option.
    Its totally normal behavior for SQL Server to utilize memory. It can also utilize memory greater that what is limit in max server memory setting as this only controls buffer pool allocation.
    You can reduce max server memory value IF you really want SQL Server memory utilization in tak manager to come down. But I would again say its normal.
     What is max server memory value anyway?
    How much you have left for OS on atleast 5-6 G id required for OS. Value may vary.
    >>SQL process is using less than max memory, when checked in task manager. So i was thinking where is remaining memory
    SQL Server caches memory to store as much data and index pages(in memory)  as possible to avoid any physical I/O which is costly and once taken memory it will not release unless SQLOS asks it to do so . It will start trimming its mmeory consumption when
     SQLOS says it to do because of some memory pressure or other requirement. The process is totally dynamic and is managed perfectly so you dont need to worry.
    More about SQL Server memory and troubleshooting
    http://social.technet.microsoft.com/wiki/contents/articles/22316.sql-server-memory-and-troubleshooting.aspx
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • Full 64-bit Aperture 3 Performance Maxed

    All Macs running Snow Leopard that are Core2Duo or better are capable of full 64-bit, but from reading the threads I would say almost nobody is doing this.
    Currently, of all Macs on the market now, only the X-Serve boots into full 64 bit mode by default.
    I guess that this is because Apple assumes a server is typically professionally managed, meaning the operator would have the technical savvy to verify that all required software is 64 bit clean....ALSO servers do not tend to have any excess software on them that is not needed for them to function.
    Stark contrast to the overstuffed user machines cluttered with useless old files PLUS there is still lot of current valid user software not 64-bit capable yet, like PS CS4. Knowing this, Apple does not want a lot of complaints from average, non IT professional users for current non-64 bit incompatibilities, and that is understandable. This makes Apple's default boot mode for Snow Leopard on user machines 32 bit mode. Currently Apple makes users DELIBERATELY select full 64 bit mode at boot...and in so assuming that these hopefully savvy users know the possible consequences.
    Now when running in the default 32 bit mode, 64 bit apps will operate in either 64 bit, or if so selected in their Info box, 32 bit to maximize compatibility. While running a 64 bit app increases its performance, it is only a portion of the performance running a full 64-bit machine will do.
    If your system has a lot of extensions or old drivers or other associated crapola <(technical term) left over from years of upgrades, you might just want to pass on this suggestion right now...HOWEVER if your system is decently clean, a fresh install of the OS and Aperture 3, you will most likely be fine.
    Aperture 3 running on a full 64-bit machine is a delightful improvement, and in my limited experience to date SMOKIN' fast.
    Now if you are on still on Leopard, congrats, you kept better performance than the early SL adopter folks on Aperture 2...BUT Aperture 3 NEEDS SL to make it sing, so if you are going to move to Aperture 3, UPGRADE to SL 10.6.2 NOW.
    Assuming we are all on SL 10.6.2 now let's talk full 64 bit, and getting all the performance your hardware can deliver.
    OK then...On this clean system, restart and hold both the 6 and 4 keys down during boot. You can then verify the full 64 bit mode by looking in the System Profiler. Select About this Mac... More Info... then click on the Software title header in the left column and in the second to last line you should see:
    " 64-bit Kernel and Extensions: Yes"
    WELCOME to your full 64 bit machine.
    After checking you are in full 64 bit, launch Aperture 3, and Activity Monitor...to monitor performance.
    If all goes well, Aperture should now be SMOKIN fast. I can hold the arrow key down in full screen and D3X .NEFs render almost immediately, smaller files a blink. 6GB on my MBP shows no pageouts running just Aperture 3. An 8 core Mac Pro with lots of RAM will be MUCH faster due to full 64 bit AND the parallel core thread processing.
    Imports with backups to a secondary disk (YAAY!!!) are so fast I cannot believe it, I think it is faster than Photo Mechanic, which is my gold standard for import/ingest speed.
    Now the two finger 6 and 4 key reboot method is only temporary, the next reboot it will revert to 32 bit mode, which is handy at this point in time if you have run into crashing or other problems.
    If you find you have a clean system you can make it boot into 64 bit all the time, but that is part of a larger performance discussion...just try this and see if you are doing better in terms of performance.
    Remember, most plug-ins, etc. are not going to be 64 bit yet...in fact Aperture even displays this in the File:Export... menu where it says (32 bit) next to the names of plug-ins. OBVIOUSLY (I hope) it probably would not be such a great idea to try these in this full 64-bit mode (ya think?). Just enjoy the stuff that does =).
    So...chances are VERY good you probably cannot do all your work in this mode just yet...BUT...if you are limiting tasks for the moment to just Aperture and the OS, like library conversion, or learning the new features, you probably will blow through this much faster than in 32 bit.
    ALSO, while I am talking Aperture performance...
    Aperture also needs really fast storage to see max performance with big libraries (500GB+), and I mean an eSATA host with a striped array. Firewire 800 and lesser technologies are 3-4 times slower on average. Sadly, Only the 17" MBP (and all previous size version MBPs) and the Mac Pro can run an eSATA host. To me this is the single biggest drawback to the iMac, and seems REALLY silly now that you can buy an iMac with an i7 processor with a great graphics card...but only the internal single drive is eSATA, and you are stuck with FW800 for storage.
    Anyway, I am running a Sonnet Tempo Pro Express 34 card in my MBP connected to Sonnet Fusion D500P array with 10TB of disk space, formatted using SoftRAID. My dedicated space for Aperture benchmarks on this setup at about 130MB/sec on average of all tests. Two crucial facts here is that the Sonnet drivers for the card (v2.2.1) are full 64-bit as well as the fact that a 64 bit version of the SoftRAID driver is included with Snow Leopard for users in 64 bit mode, which will allow you to keep existing volumes and access data from the 64 bit version of Snow Leopard.
    Anyway, fellow Aperture 3 adopters I encourage you to give it a shot...and I hope this results in some smiling faces...
    Sincerely,
    K.J. Doyle
    PS No flames please... of course since this is all new ground YMMV... proceed at your own risk, there is a reason Apple is not making this easy right now...'nuff said, I hope.

    Kevin -- is it your understanding that Aperture can and will default to 64 bit performance without need to reboot 6-4?
    Hi Miguel,
    He is correct, Aperture will be running in 64 bit, but the rest of the machine will not, and Aperture is dependent on many other subsystems, storage being #1 given the huge size of libraries. As I said above, I am pretty sure Apple would not recommend you run full 64 because of the other incompatibilities that exist on the machine, it would cause too many complaints from those who do not understand the need for 64 bit clean operation, and that all apps are not there yet.
    HOWEVER, there is a lot more to this than just Aperture's operation, as it is an app that uses many resources.
    There is a very significant difference in operating my eSATA array with 64 bit drivers and a full 64 bit machine, and therefore Aperture runs much faster than it would using the 32 bit drivers for the storage.
    There are other issues as well with greatly improved OS memory operations and other technical issues that impact this as well. The more RAM you have the bigger the improvement. This impacts parallel processing of threads, and again gives more time to Aperture in the bargain.
    Sincerely,
    K.J. Doyle

  • Asking for your help to Connect 4 Servers Toghether!

    Hi. for more than 3 days i'm trying to build multi server's cast Based on the attached model.
    Everything I've tried have not helped me.
    can you kindly help me to build the right " vhost " file for each server as described in the attached model ???
    I really appreciate it
    Thank you very much
    Elad.
    ----- THE VHOST -----
    <VirtualHost>
              <!-- This tag contains a list of <Alias> tags. -->
              <AliasList>
                        <!-- You can specify additional names by which to connect to this -->
                        <!-- virtual host by specifying the name(s) in one or more Alias  -->
                        <!-- tags. Use this tag if you want to be able to connect to this -->
                        <!-- virtual host with different names. For example, if the name  -->
                        <!-- of this virtual host is "abc.macromedia.com", but you wish   -->
                        <!-- to connect by simply specifying "abc", then you can specify  -->
                        <!-- an alias "abc". Note that "abc" must still map to the same   -->
                        <!-- IP address as "abc.macromedia.com". If more than one virtual -->
                        <!-- host on the same adaptor has defined the same alias, then    -->
                        <!-- the first match that is found is taken. This may result in   -->
                        <!-- unexpected behavior.                                         -->
                        <Alias name="alias1"></Alias>
              </AliasList>
              <!-- Specifies the applications directory for this virtual host. -->
              <!-- The applications directory is the base directory where all  -->
              <!-- applications for this virtual host is defined. An app is    -->
              <!-- considered to be defined if there exists a directory with   -->
              <!-- the application name. If nothing is specified in this tag,  -->
              <!-- the applications directory is assumed to be under the vhost -->
              <!-- directory.                                                  -->
              <AppsDir>${VHOST.APPSDIR}</AppsDir>
      <!-- You can override the settings specified in Server.xml for -->
      <!-- this vhost by uncommenting the tag below. You can disable -->
      <!-- auto-close idle clients for this vhost, or change the max -->
      <!-- idle time for clients connected to this vhost. If the max -->
      <!-- idle time is not specified here, or invalid (i.e. <= 0),  -->
      <!-- then we use whatever was set at the server level.         -->
      <!--
      <AutoCloseIdleClients enable="false">
        <MaxIdleTime>3600</MaxIdleTime>
      </AutoCloseIdleClients>
      -->
              <!-- Specifies max resource limits for this virtual host. -->
              <!-- Resource limits are only honored when running in vhost scope. -->
              <ResourceLimits>
                        <!-- Max number of clients that can connect to this vhost when running as local.  -->
                        <!-- enforced by License key -->
                        <MaxConnections>-1</MaxConnections>
                        <!-- Max number of clients that can connect to this vhost when running as remote. -->
                        <!-- This is enforced by License key -->
                        <MaxEdgeConnections>-1</MaxEdgeConnections>
                        <!-- Max number of app instances that can be loaded. -->
                        <MaxAppInstances>15000</MaxAppInstances>
                        <!-- Max number of streams that can be created. -->
                        <MaxStreams>250000</MaxStreams>
                        <!-- Max number of shared objects that can be created. -->
                        <MaxSharedObjects>50000</MaxSharedObjects>
                        <!-- GC interval for application instances resources in minutes : SharedObjects, Streams and Script engine. -->
                        <AppInstanceGC>1</AppInstanceGC>
              </ResourceLimits>
              <VirtualKeys>
                        <!-- Sets the virtual key mappings for connecting players.          -->
                        <!-- When a FlashPlayer or other connects, they receive a          -->
                        <!-- virtual key that corresponds to the ranges below                    -->
                        <!-- The virtualKey may be reset as a client property in the          -->
                        <!-- server script.  If no key is specified for a player          -->
                        <!-- it will not have a key applied by default: example                    -->
                        <!-- <Key from="WIN 7,0,19,0" to="WIN 9,0,0,0">A</Key>                    -->
              </VirtualKeys>
              <!-- This section specifies virtual directory mappings for resources -->
              <!-- such as recorded streams. By using virtual directories, you can -->
              <!-- share resources across different applications. If the beginning -->
              <!-- portion of a resource's uri matches the virtual directory that  -->
              <!-- is specified, then the storage location of the resource maps to -->
              <!-- the location specified by the virtual directory mapping. To     -->
              <!-- specify a virtual directory mapping, you first specify the      -->
              <!-- virtual directory, followed by a colon, followed by the actual  -->
              <!-- storage location. Finally the first item in the key mapping     -->
              <!-- is the virtual key mapping that corresponds to this directory   -->
              <!-- If the client attempting to play has a key matching this listed -->
              <!-- virtual key, it will take that virtual mapping, example:               -->
              <!-- <Streams key="virtualKey"><virtual dir>;<actual dir></Streams> -->
              <VirtualDirectory>
                        <!-- Specifies virtual directory mapping for recorded streams.   -->
                        <!-- To specify multiple virtual directory mappings for stream,  -->
                        <!-- add additional <Streams> tags; one for each virtual dir     -->
                        <!-- mapping. Syntax for virtual directories is as follows:      -->
                        <!-- <Streams key="virtualKey">foo;c:\data</Streams>.                      -->
                        <!-- This maps all streams whose virtual                               -->
                        <!-- key matches the listed key, if given and                                -->
                        <!-- names begin with "foo/" to the physical directory c:\data.  -->
                        <!-- For example, the stream named "foo/bar" would map to the    -->
                        <!-- physical file "c:\data\bar.flv". Similarly, if you had a    -->
                        <!-- stream named "foo/bar/x", then we first try to find a vdir  -->
                        <!-- mapping for "foo/bar". Failing to do so, we then check for  -->
                        <!-- a vdir mapping for "foo". Since there is one, the stream    -->
                        <!-- "foo/bar" corresponds to the file "c:\data\bar\x.flv".      -->
                        <!-- Virtual keys are optional, but if set allow more than one           -->
                        <!-- mapping                                                                        -->
                        <Streams></Streams>
              </VirtualDirectory>
              <!-- This tag specifies the primary DNS suffix for this vhost. If a  -->
              <!-- reverse DNS lookup fails to return the domain as part of the    -->
              <!-- hostname, then this tag is used as the domain suffix.           -->
              <DNSSuffix></DNSSuffix>
              <!-- This tag specifies a comma delimited list of domains that are   -->
              <!-- allowed to connect to this vhost. If this tag is empty, then    -->
              <!-- only connections from the same domain that is being connected   -->
              <!-- to will be allowed. If this tag is not empty, then only the     -->
              <!-- domains explicitly listed will be accepted. For example,        -->
              <!-- <Allow>macromedia.com, yourcompany.com</Allow> will only allow  -->
              <!-- connections from the macromedia.com & yourcompany.com domains.  -->
              <!-- If you wish to allow localhost connections, you will specify    -->
              <!-- "localhost". For example, <Allow>localhost</Allow>. To allow    -->
              <!-- all domains, specify "all".  For example, <Allow>all</Allow>.   -->
              <Allow>all</Allow>
              <Proxy>
                        <!-- A vhost may be configured to run apps locally or remotely.  -->
                        <!-- A vhost that is not explicitly defined gets aliased to      -->
                        <!-- the default vhost and is configured as such. A proxy server -->
                        <!-- runs all its apps remotely, while a normal server runs all  -->
                        <!-- its apps locally. The following parameter defines whether   -->
                        <!-- this vhost is running local or remote apps, the default is  -->
                        <!-- local. It may be set to either local or remote              -->
                        <Mode>local</Mode>
                            <!-- This setting specifies the time for which this server  -->
            <!-- wait for a response from the remote server before      -->
            <!--  timing out.  Time specified is in seconds. Default    -->
            <!--  value is 2 seconds.                                                   -->
                            <RequestTimeout>2</RequestTimeout>
                        <!-- Whether this is an anonymous proxy. An anonymous proxy does -->
                        <!-- not modify the incoming url. This way it does not disturb   -->
                        <!-- the routing of explicitly chained proxies. It is false by   -->
                        <!-- default, must be true for interception proxies.             -->
                        <Anonymous>false</Anonymous>
                        <!-- Proxy server disk cache settings                            -->
                        <CacheDir enabled="false" useAppName="true">
                                  <!-- Specifies the physical location of the proxy cache.  By default   -->
                          <!-- they are placed in cache/ in the server installation directory.   -->
                                   <!-- The value entered here must be an an absolute path; relative      -->
                                  <!-- paths will be ignored and will revert to the default directory.   -->
                                  <Path></Path>
                                  <!-- Specifies the maximum allowed size of the disk cache, in          -->
                                  <!-- gigabytes.  AMS does LRU cleanup of the cache to keep it under    -->
                      <!-- the maximum.  The default value is 32 GB.  A value of 0 will      -->
                                  <!-- disable the disk cache.                                                                   -->
                                  <MaxSize>32</MaxSize>
                        </CacheDir>
                        <!-- A proxy's outgoing connection can be bound to a specific    -->
                        <!-- local ip address. This allows for separating incoming and   -->
                        <!-- outgoing connections onto different network interfaces. This-->
                        <!-- is useful in configuring a 'Transparent' or 'Interception'  -->
                        <!-- proxy. If a LocalAddress is not specified, then outgoing    -->
                        <!-- connections bind to INADDR_ANY, which is the default.       -->
                        <!-- If a literal address is specified here, the IP version of literal -->
                        <!-- address must match the IP version of the Origin server's address. -->
                        <!-- The workaround is to use the hostname of the network interface    -->
                        <!-- (hostname with both A and AAAA DNS records) that will bind to     -->
                        <!-- either the IPv4 or IPv6 address of the interface.                 -->
                        <LocalAddress></LocalAddress>
                        <!-- This section specifies routing information. Administrators  -->
                        <!-- can configure how to route connections based on the desired -->
                        <!-- destination.                                                -->
                        <!-- The protocol attribute specifies the protocol to use for    -->
                        <!-- the outgoing connection. If specified, it must be set to    -->
                        <!-- either "rtmp" or "rtmps" to indicate a non-secure or secure -->
                        <!-- connection respectively. If nothing is specified, the       -->
                        <!-- out-going connection will use the same protocol as the      -->
                        <!-- in-coming connection. You can override this for each route  -->
                        <!-- entry by specifying a protocol tag attribute in each        -->
                        <!-- <RouteEntry> tag. If none is specified, it will use what is -->
                        <!-- configured in the <RouteTable> tag.                         -->
                        <RouteTable protocol="rtmp">
                                  <!-- Maps a host:port pair, to a different host:port pair.   -->
                                  <!-- This tag is in the form <host1>:<port1>;<host2>:<port2> -->
                                  <!-- where host1:port1 is the host and port of the desired   -->
                                  <!-- destination, and host2 and port2 is what should be used -->
                                  <!-- instead. In other words, connections to host1:port1 are -->
                                  <!-- routed to host2:port2 instead. For example,             -->
                                  <!-- <RouteEntry>foo:1935;bar:80</RouteEntry>                -->
                                  <!-- This says to route connections destined for host "foo"  -->
                                  <!-- on port 1935, to host "bar" on port 80.                 -->
                                  <!-- We also allow the use of the wildcard character '*' to  -->
                                  <!-- replace <host> and/or <port>. For example,              -->
                                  <!-- <RouteEntry>*:*;foo:1935</RouteEntry>                   -->
                                  <!-- This says route connections destined for any host on    -->
                                  <!-- any port to host "foo" on port 1935.                    -->
                                  <!-- '*' can also be used on the right-hand side. When used  -->
                                  <!-- on the right-hand side, it means that the corresponding -->
                                  <!-- value on the left-hand side should be used. For example -->
                                  <!-- <RouteEntry>*:*;*:80</RouteEntry>                       -->
                                  <!-- This says route connections destined for any host on    -->
                                  <!-- any port, to the same host on port 80.                  -->
                                  <!-- Additionally, you can also specify that a host:port     -->
                                  <!-- combination be routed to null, which essentially means  -->
                                  <!-- that connections destined for that host:port combo will -->
                                  <!-- be rejected. For example,                               -->
                                  <!-- <RouteEntry>foo:80;null</RouteEntry>                    -->
                                  <RouteEntry>1.1.1.1:1935;2.2.2.2:1935</RouteEntry>
                        </RouteTable>
                        <!-- This section configures edge auto-discovery. When an edge   -->
                        <!-- connects to another server, that server may be part of a    -->
                        <!-- cluster. This edge will try to determine which server in    -->
                        <!-- that cluster we should connect to (which may or may not be  -->
                        <!-- the server specified in the uri).                           -->
                        <EdgeAutoDiscovery>
                                  <!-- Specifies whether edge auto discovery is enabled (true) -->
                                  <!-- or disabled (false). Default is disabled.               -->
                                  <Enabled>true</Enabled>
                                  <!-- This specifies whether or not to allow overriding edge  -->
                                  <!-- auto-discovery (by specifying "rtmpd" protocol). If     -->
                                  <!-- enabled, edge auto-discovery is performed by default.   -->
                                  <AllowOverride>true</AllowOverride>
                                  <!-- Specifies how long to wait (msec) for auto-discovery.   -->
                                  <!-- Warning: don't set this too low. It must be long enough -->
                                  <!-- to establish a TCP connection, perform a UDP broadcast, -->
                                  <!-- collect the UDP resposnes, and return an XML response.  -->
                                  <WaitTime>1000</WaitTime>
                        </EdgeAutoDiscovery>
                        <!-- If this vhost is remote mode, and you wish to configure the -->
                        <!-- properties of an out-going ssl connection to an upstream    -->
                        <!-- server, then enable this section and configure SSL props    -->
                        <!-- appropriately. The absence of the <SSL> tag will mean that  -->
                        <!-- ssl connections to upstream servers will use the default    -->
                        <!-- configuration specified in the <SSL> section of Server.xml. -->
                        <!-- For more information on each of these tags, see comments in -->
                        <!-- Server.xml. Note: this section if uncommented is ignored if -->
                        <!-- proxy mode is local.                                        -->
                        <!--
                        <SSL>
                                  <SSLVerifyCertificate>true</SSLVerifyCertificate>
                                  <SSLCACertificatePath></SSLCACertificatePath>
                                  <SSLCACertificateFile></SSLCACertificateFile>
                                  <SSLVerifyDepth>9</SSLVerifyDepth>
                                  <SSLCipherSuite>ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH</SSLCipherSuite>
                        </SSL>
                        -->
                        <!-- When a VHost is configured as proxy, the "enabled"       -->
                        <!-- attribute will determine whether aggregate messages will -->
                        <!-- be delivered from the edge cache.  Default is "true".   -->
                        <!-- If the edge server receives aggregate messages from the  -->
                        <!-- origin when this setting is disabled, the messages will  -->
                        <!-- be broken up before being cached.                        -->
                        <AggregateMessages enabled="true">
                                  <!-- This setting determines the size (in bytes) of aggregate  -->
                                  <!-- messages returned from the edge cache (when aggregate     -->
                                  <!-- messages are enabled).  Note that this setting only       -->
                                  <!-- applies to messages retrieved from the disk cache.        -->
                                  <!-- Aggregate messages received directy from the origin server-->
                                  <!-- will be returned as-is, and therefore their size is       -->
                                  <!-- determined by the origin server's settings for aggregate  -->
                                  <!-- message size. Default is 65536                            -->
                                  <!-- <MaxAggMsgSize>65536</MaxAggMsgSize> -->
                                  <!-- Maximum Duration in Millisconds of an aggregate message while -->
                                  <!-- reading from edge disk cache. Default is 10000 Millisconds. -->
                                  <!-- <MaxAggMsgDuration>10000</MaxAggMsgDuration >                    -->
                        </AggregateMessages>
              </Proxy>
              <!-- This section controls some of the logging behaviors.                      -->
              <Logging>
                        <!-- This section controls access log.                                 -->
                        <Access>
                                  <!-- You can override the settings specified in Server.xml for -->
                                  <!-- this vhost by uncommenting the tag below. You can disable -->
                                  <!-- logging checkpoints for this vhost, or change the         -->
                                  <!-- checkpoint interval of this vhost. If the checkpoint      -->
                                  <!-- interval is not specified here, or invalid (i.e. <= 0),   -->
                                  <!-- then we use whatever was set at the server level.         -->
                                  <!--
                                  <Checkpoints enable="false">
                                            <LogInterval>3600</LogInterval>
                                  </Checkpoints>
                                  -->
                        </Access>
              </Logging>
    </VirtualHost>

    You've now posted at least three times now and have been given the same answer every time. You've also had your posts editied for personal information every time.
    We cannot help you get past the Activation Lock, only the person to whom it is locked can. We cannot help you unlock the phone from a carrier; only the carrier to which it is locked can.

  • MTS - Shared servers die when stressed...

    RedHat 6.2, Oracle 8.1.5, Running MTS
    MTS is up and running, but when I start to stress the box, the background processes and the shared servers just die. This doesn't happen with dedicated servers, only with shared servers. When it happens, it happens fast...boom their dead! I am low on memory, but I have plenty of swap space. I heard there was a problem with MTS on Linux...anyone know the details?
    Thanks,
    Craig.
    null

    Craig,
    I am using MTS, RH 6.2, and 8.1.6.
    After stress testing with my max number of connections for a prolonged period my servers
    die. Instance crash.
    My test includes connections from a web and telephony server. I'm not totally convinced its a sole MTS issue. My only common denominator in testing is java, so I'm looking further here.
    8.1.7 is due for release soon.
    What type connections are you making (e.g any web servers ?)
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Craig Shallahamer ([email protected]):
    RedHat 6.2, Oracle 8.1.5, Running MTS
    MTS is up and running, but when I start to stress the box, the background processes and the shared servers just die. This doesn't happen with dedicated servers, only with shared servers. When it happens, it happens fast...boom their dead! I am low on memory, but I have plenty of swap space. I heard there was a problem with MTS on Linux...anyone know the details?
    Thanks,
    Craig.<HR></BLOCKQUOTE>
    null

  • Max. No. of People in a meet me conference

    Dear All,
    I have 6 software conference bridges in one cluster. All the servers are running Cisco CallManager and IP Voice Media streaming application services
    In service parameters for Cisco CallManager service "Maximum MeetMe Conference Unicast" is set to 48
    Now I have two doubts
    1. Is it correct that max 48 persons can join one conference
    2. Is it possible to increase this limit
    Here I do not want to increase the MeetMe parameter value above 48 as Cisco does not recommend it. However since there are 6 bridges, is there any way to get more people in the conference

    for a softwareConferenceBridge, the maximum number of streams is 128, which will allow upto 128 users in a single conference (or 42 confs w/3 conferees each)
    see this link for more info:
    http://www.cisco.com/en/US/products/sw/voicesw/ps752/products_tech_note09186a008009476a.shtml
    per cisco documentation, if you have the resources available, the maximumMeetMeConferenceUnicast can be set upto 128 participants.

Maybe you are looking for

  • Can I update multiple forms with the same dropdown at the same time

    I have 20+ forms that have a common dropdown.  Each form has between 1 and 15 instances of this dropdown.  The values in the dropdown are updated on a frequent basis. Currently I have an identical Document JavaScript named 'UpdateDropdowns' in each f

  • How do i delete a movie that has frozen on the download page at "processing"?

    In downloading a movie from itunes - through the cloud for some reason it got hung up at the end and keeps indicating "processing" - i was able to delete the data from my "video " app but cannot eliminate the movie from the "downloading" page in itun

  • Reading Byte [] in JSP - Struts

    Hi,           I am storing PDF files as BLOB object in Oracle 9i Database.           In my struts action class I am reading the file and converting it into byte [].           I am storing this value in the session as an object and while reading in th

  • Instance not accessible (ora-12514) and recovery..

    So, I was doing some changes on a network (from dhcp to fixed ip's), and after that I was not able to access my oracle (10.2.0) instance (win xp), and I don't know why. Of course, listener starts (and I can tnsping it), but when I start instance, no

  • How to get the best from 8gb ram in macbook pro_bootcamp Win 7

    Hi guys,   I know what you are going to say, (run 64 bit windows) but bare with me.  I have brand new 2011 unibody macbook pro 13" 2.8 ghtz dual core 8gb of ram.  When running bootcamp windows 7 it shows only 2.16 gb ram usable.  I thought that 32 bi